Leaderboard

It seems like every other question posted nowadays is about how to upgrade an older version of oscommerce and the op usually references the official version. This post is meant to provide a quick reference for how to convert an older shop to the current, recommended, one. First, the version that should be used is commonly called the Bootstrap, BS or Responsive version. It can be located here. One should not use the official version. The official version can be installed via the hosts control panel so it is easy to think that is the one to use - it is not. Since the BS version is not directly compatible with other versions, the following steps will be needed: Install the BS version into a new location Convert the database. See this thread for help with that. Install whatever addons the site needs. You need to be sure the addon will work with the BS version. This thread mentions specific ones but there are many others that will work. If in doubt, ask in the support thread for the addon in question. If you intend to use paypal, then install the Paypal App. At this point you should have a working shop. Test it thoroughly, especially the payment and shipping modules, before going live with it. When you are ready to go live, Mark your current shop as down for maintenance ( a simple index.html file is fine for this purpose ). Make a backup of the current shops database and files. Convert the database to the BS version. Replace all of the files with the new shops files. Edit the configure files so they work as the live shop. Remove the blocking page. If everything has gone correctly, the conversion should be complete.

Rainer, @raiwa thank you, all looks ok now. emails and order status all check out now. thank you again👍

There was a problem with the webhook connection. Fixed now and order status is now correct. The problem with the missing order number on the email is still there: Order Number: Detailed Invoice: https://xxxxxx/account_history_info.php?order_id= Date Ordered: Tuesday 27 October, 2020

You could create your own topic and provide more info: What you are trying Code you have already added

Same problem as I mentioned in the other thread. I can't follow the problem.

This is probably telling you that the file is not writable by the web server. Info Pages edits database entries, not files.

settings are as you quoted, php log shows this PHP Notice: Undefined variable: modal_size in /xxx/xx/xxx/includes/hooks/shop/checkout_confirmation/finalisedOrder.php on line 24, referer: https://xxxx/checkout_payment.php PHP message: PHP Deprecated: The checkout/reset segment has been deprecated. in /xxx/xx/xxx/includes/system/segments/checkout/reset.php on line 13, referer: https://xxxx/checkout_confirmation.php

@raiwa updated my test environment with your beta version and I'm getting the following in the email sent Order Number: Detailed Invoice: https://xxxxxx/account_history_info.php?order_id= Date Ordered: Monday 26 October, 2020 notice there is no order number. Also the order status doesn't get set to the default i.e. 'pending'

The files in Phoenix are almost totally different than in non-Phoenix shops so upgrading your current shop to the 2.3.4 version won't accomplish anything. You need to do the following: Set up a test site and install Phoenix. This might be a problem off the bat if you are not able to run php 7. Convert your database and apply it to the test shop. Install whatever addons you need for your shop. Make any appearance changes that are needed. Test the shop thoroughly. If it all looks good, block your live shop with a down for maintenance page to prevent database changes. Do a final conversion of the database. Make the test site live. It can be a lot of work, depending upon what addons and appearance changes are needed. For the addons, many of the popular ones that have Phoenix versions are just file uploads so the installation is much easier. Good luck.

uploaded update: Store Hotline 3.1 Phoenix Compatibility: OSCOM Phoenix CE 1.0.5.1+ Tested with Phoenix 1.0.7.9 PHP: 7.0-7.4 Changelog: Version 3.1 Updated to abstarct executable module Moved all html output into template file

kgtee, it's a know bug and will be solved in the new version. If you check the core you can see the solution. It's simple. Will check in a minute where it is. Here it is: https://github.com/gburton/CE-Phoenix/commit/7aa066375b030455032691033fb6eda016cd1ffa HtH

Uploaded Shop By Price v5.2.2 Shop by Price CE Phoenix v.5.2.2 Requires Phoenix 1.0.7.2+ Tested with Phoenix 1.0.7.9 Changes in Shop By Price v5.2.2 - Minor code updates to match core coding standards - tested under PHP 7.4

Uploaded: Ajax Attribute Manager 3.3.0 Requires: OsCommerce Phoenix 1.0.5.9+ (tested with 1.0.7.9) PHP 7.0 to 7.4 + removed duplicated language definitions. Thanks to @kgtee + fixed unbalanced table columns. Thanks to @radhavallabh + added table titles. + updated to bootstrap design elements (buttons, tables etc). + replaced image icons by fontawesome icons. + removed deprecated css + removed deprecated image icons + replaced jquery with native javascript in admin hooks. Thanks to @PiLLaO + removed qtpro support. It's now available in it's own tab on the product edit page. + updated sort order support modifications in cm_pi_options_attributes.php

I think that a "non-consecutive numerical sort order" is probably the best solution. Note that it doesn't need to be a database entry. A hook file in includes/hooks/system would work as well. The closest thing to documentation is the commit notes (and the commit itself): https://github.com/gburton/CE-Phoenix/commit/ae01e0d4d91b2e4a561735168ef4fbe6ba8e6899 Related commit: https://github.com/gburton/CE-Phoenix/commit/d2adabebe2efbdcd28513c6057758cd25ed48fc4 I don't think that it is very complicated. HTTP_SERVER . DIR_WS_CATALOG should always be used now, where previously it was only sometimes used (in the ENABLE_SSL false case). For the most part, this is just simpler. Because instead of having to check various things to determine the correct link, the code can just consistently use one thing. The old system was complicated, as it had to try to mix SSL and non-SSL pages. But this always uses whatever the HTTP_SERVER is configured to provide.

Hi @ecartz, I finally got a free day to check this contribution. I found your solution will not work because Usu_main has to be initialized after set_session_language and before ensure_navigation_history to work. If not, links are correctly generated but $_GET variable is not updated and Phoenix redirects to index in all pages that expects parameters, like product_info. I found its code could be placed in application.php inside the set_session_language function, or it could be loaded by creating an entry inside hooks table between those two functions (an startApplication method). But as far as I see it implies giving a non-consecutive numerical sort order to the table entry (something like _16B_start_SEO ) and it seems a bit dirty to me. Is there a cleaner way to do it? Another thing: I've seen fix_numeric_locale is being called twice (from a hook and inside set_session_language function. Is this needed or has the function call just been forgotten? Files outside ROOT seems to work now; I'm into fixing the ENABLE_SSL stuff. Is there any post where the changes introduced has been explained?

That's correct for other SEO contribution. This is Ultimate SEO 5 and it's different, it needs a lot more tweaks. I wonder if the contribution name should be changed to avoid this kind of confusions.

If you are on the latest previous version, you can just upload and replace everything. No need to uninstall/reinstall the modules.

You can make the subcat titles show up by editing one line in the file includes/modules/boxes/bm_catagories.php: To show the quantities, you can edit the file includes/classes/category_tree.php Find: Edit the line that comes after:

The difference is that with a blog article, customers can reply to it. So an article might be a page explaining how to use a knife. While a blog article would be about the various knifes you sell and where customer can respond with their views on which is the best one. Getting customers involved is a way of keeping them coming back. I have one client that sells baby clothes and the site has a blog article where customers can post images of their babies.