“补丁”核心文件 osCommerce(旧)或升级?

发布于 2024-10-23 22:41:19 字数 217 浏览 1 评论 0原文

大家好,我有一个客户希望我更新一个在 oscommerce v 1.18 上运行的网站。

他希望我做的是使 HTML 符合 w3c 标准。似乎有很多表被错误使用以及其他违反当今标准的行为,我想解决这个问题,但是视图层中有很多业务逻辑,而且它们非常混合在一起。

我应该尝试让客户升级系统吗?还有其他人处理类似的情况吗?无论哪种方式,这似乎都是一项相当大的任务。一如既往,感谢您的时间和意见!

Hey guys, I have a client who wants me to update a site, which is running on oscommerce v 1.18.

What he wants me to do is make the HTML w3c compliant. There appear to be lots of tables being incorrectly used as well as other violations of today's standards, and i'd like to fix this, but the view layer has a lot of business logic in it, and it's very mixed together.

Should I just try to get the client to upgrade the system? Anyone else deal with a similar situation? Either way, it seems like a fairly big undertaking. As always, thanks for your time and opinions!

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

风柔一江水 2024-10-30 22:41:19

基本上我会列出选项,并概述客户的安全问题。毕竟你可能是按小时付费的,所以只要你得到报酬,你就不应该担心所涉及的工作量。

话虽如此,与破解并尝试修复它相比,升级始终是最好的途径,即使您陷入困境(安全/更新/补丁方面)。

仅供思考。

Basically I would lay out the options, and outline the security concerns for the client. After all you are probably getting paid per hour, so you shouldn't worry about the work effort involved as long as you are compensated.

With that said, upgrade is always the best route compared to hacking it out and trying to fix it even tho you are in a hole (security / update / patch wise).

Just food for thought.

叹梦 2024-10-30 22:41:19

没有任何可以想象的情况可以继续使用 osCommerce。

不要尝试更新到较新的版本,而是调查并测试是否可以使用任何(半)自动迁移工具。
http://www.magentocommerce.com/magento -connect/Magento+Core/extension/114/os-commerce-import
花更少的时间获得更多的好处更有可能取悦客户。

There are no conceivable circumstances under which it would be ok to keep using osCommerce.

Instead of trying to update to a newer version, investigate and test if you can utilize any (semi-) automated migration tool.
http://www.magentocommerce.com/magento-connect/Magento+Core/extension/114/os-commerce-import
Spending less time for more benefits is more likely to please the client.

染火枫林 2024-10-30 22:41:19

更改应用程序的核心文件永远不会是一件好事(我并不是说它不能完成,但是......),您应该小心,因为也许其他人会收回该项目并尝试升级应用程序并破坏所有定制代码。
如果这是您最后的手段,那就去吧。

如果您只需要更新 html 标记,那么,这应该是可行的,但是作为一个专业人士,您确实应该建议您的客户并告诉他您认为什么是好的他。

也许你应该建议他改用更好的电子商务应用程序,现在有很多比 OsCommerce 更好的应用程序。

Changing core file of an application can never be a good thing (I don't say it can't be done but...), you should take care as maybe someone else will take back the project and try to upgrade the application and break all your custom made code.
Go for it if it is your last resort.

If you just need to update html markup, well, it should be feasible, however as a professional, you should really advise your client and tell him what you think is good for him.

Maybe you should advise him to switch to a better e-commerce application, there are plenty now which are far better than OsCommerce.

农村范ル 2024-10-30 22:41:19

编辑核心文件几乎总是一个坏主意。如果有一天你最终想要进行升级,你将无法确保所有数据都按照应有的方式进行管理,等等......

而且在触及核心文件时,我什至不谈论安全问题。

Editing the core files is almost always a bad idea. If one day you finally want to do the upgrade, you won't able to be sure that all the data are managed the way they should be, etc ...

And I don't even talk about security issues, when touching core's files.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文