radhavallabh

Yes, sort of. I have a working be version except there is a problem with shopping cart links that have attributes. I will post here when that have been fixed.

Please see the PM I sent you.

It is planned but I don't know when. The class you mentioned has to be overridden most likely. There is probably a way to do that but I haven't gone through the code.
 
See if this post helps.

A new version has been uploaded with these changes:
Added a version for Phoenix 1.0.8.9 and above. Fixed problem that could cause "Headers Already Sent" failures.  

@radhavallabhSince it works in other shops but not yours, it must be something unique to yours. If you turn the addon off in admin do all of the urls work correctly? If it does, try using the Uninstall setting and then reload the shop side. Does that fix it? If not, try turning off all cache options in the settings and try again. If it still fails then the only thing I can think to do is to install it into a new, basic, shop. That should work since it works here. Then you can try it with your database and if it fails, then it is something there that is causing the problem.  

It’s missing in the products_attributes table, not products_options

Uploaded:
Ajax Attribute Manager 3.3.2
Requires:
OsCommerce Phoenix 1.0.7.10+ REQUIRED!
PHP 7.0 to 7.4
Changes Version 3.3.2.:
+ added support for Phoenix 1.0.7.10 core sort order
+ removed optional product_options_sort_order support
+ added auto update script for product_options_sort_order to core sort order columns.
+ normalized spacing and indents.
+ updated custom database functions to use core functions.
+ modernized coding to match core standards
*********************************************************************
If you were using attributes/options sort order from previous versions:
    - Make a database backup for security if something gets messed up.
    - On first load of this version, the old sort order entries will be migrated to the new core sort order columns.
    - Check your database for success after you loaded the new attributes manager.
    - Use the product info options/attributes sort order content module included in Phoenix 1.0.7.10
*********************************************************************
 
 

A new version had been uploaded with these changes:
Added a icon for the left column for Phoenix. Changed code to only show active products. Found by member @koopmanh. Changed code to fix php warnings. Corrected error in function declaration in admin. Moved the stylesheet file to ext/css/. Please note that this update only contains changes for Phoenix. It has been tested with V 1.0.7.10.

Uploaded:
Ajax Attribute Manager 3.3.1
Requires:
OsCommerce Phoenix 1.0.5.9+ (tested with 1.0.7.9)
PHP 7.0 to 7.4
Changes Version 3.3.1.:
+ fixed notice errors for new product. Thanks to @jonwix for the report
+ removed obsolete script type declarations. Thanks to @radhavallabh for the report and testing
+ removed deprecated sql support.

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?
 

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. 

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.

Just tested under PHP 7.4 and it seems to work ok.

Ajax Attribute Manager 3.3.0 beta
AJAX-AttributeManager-V3.3.0._CE_Phoenix_beta.zip
Requires:
OsCommerce Phoenix 1.0.5.9+ (tested with 1.0.7.9)
PHP 7.0 to 7.3
A  lot of changes, so please, give it a try and report back if there appear any issues.
+ 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

Thanx dear your previous advice of scanning database thoroughly .. helped me fixed the error..  
Thank you so much dear!
Very warm Regds./
radhavallabh

I'm working on an update to bootstrap buttons and icons which will address this as well as other minor issues.

Hi,
Does a upgrade version exist for Phoenix??

Nothing to do one with another. It's still the same error.
Revise your database. I can't give more support on this , it's your store's database.

Hi @radhavallabh,
Clean unmodified Phoenix store refers also to the database.
As I already pointed out, it seems to be a corrupted entry in your options/attributes tables.
I can't address this in the attributes manager addon.
You should try to remove step by step your options and attributes related to this product to find out which produces this error. Of course, make database backups before doing so.
Otherwise you can just switch off error reporting.
The first 2 errors are notice errors which are not important. The warning error is a subsequent error thrown because of the first 2 errors.
I'm sorry, but I can`t give further support for these errors within this support thread.
Best regards
Rainer
 

Hi,
I apologize. I forgot to fix this in the last update.
I took noite and will do it in the next update.
For now, just turn error reporting off and it will work. These are "only" notice errors.

You are on Phoenix 1.0.7.1 right?
Kissit Image has not been updated yet.

A new version has been uploaded with these changes:
Added an icon for Phoenix. Changes admin FAQ files to work with Phoenix 1.0.6.2.

If something is wrong in the shop, as with the last problem, then it might appear to be this addon but this addon can't be the cause since it has nothing to do with the shopping cart. I suggest you install a clean, new shop and install this addon. If it works correctly, which it should, then you can compare the two shops to find the cause of the problem.

@radhavallabh it needs a lot of changes to get rid of warnings and notices - you should turn them off by changing admin/includes/application_top.php
error_reporting(E_ALL & ~E_STRICT & ~E_NOTICE & ~E_WARNING & ~E_DEPRECATED); It's my hope to get a lot more of them eliminated by the next release which will be to go with 1.0.6.0

The instructions predate some of the hooks changes in admin so it's possible this one is no longer needed as all orders hooked may now load automatically. The setting is highlighted here: