v1.0.8.0 Questions / Comments / Concerns

[lambro28]

The only difference between 1.0.7.18 and 1.0.8.0 is the version file. It's intended as an easy update.

Until you get some one like me come along

Thank you

[Moxamint]

We had no notice from the new owners of osCommerce that they preferred to abandon their obligations to Phoenix. Hence there will be a little bit of pain (ie incorrect URLs etc) while we get our ducks in a row.

It's been "all hands to the pump" to keep Phoenix flying, because of the way the new owners of osCommerce have behaved towards us (the behaviour, to be frank, has been shitty).

Really don't like how he showed a generous attitude toward Phonix in public but actually did something completely different underneath, whether or not his new software is going to be as awesome as he has been advocating at all

Off the topic, my apologies.

[burt]

Really don't like how he showed a generous attitude toward Phonix in public but actually did something completely different underneath, whether or not his new software is going to be as awesome as he has been advocating at all

I would say that there are many people in the osc forum who are glad to see some changes. What most of them do not realise is that the new osCommerce v4 is nothing like the osCommerce they know, and that it will be almost impossible to do the things they are used to (at least not without spending a lot of money).

There are some users there who will be very glad to see Phoenix leave (they think the old osCommerce is better) and to see me leave (there are some people who don't like truth, they just want to hear whatever it is they want to hear). What is happening now is "flim flam", everyone is being told whatever they want to hear, in my opinion.

I mean let's be frank;

1. Announce a new release for Jan 12th, which unfortunately did not happen.
2. Want Phoenix gone and won't man up to the obligations in the agreement I have with HPDL
3. Remove my access from (parts of) the forum.
4. Remove (some) administrative functions from me.
5. Not let any of the "Team" know about any of the "new ownership" stuff prior to implementing changes

As I've said elsewhere, we should all be very proud that for 6 years we carried osCommerce.
The new owners don't seem to see that osCommerce would (years ago!) be nothing without all of us

They (and HPDL) have gained massively through the hard work and support of about 100 businesses who kept the Project alive for so many years.

[puddlec]

with all the threads they have been putting out, either the "new oscommerce" it will either be incredibly bloated, or a lot of the features will be locked away as a paid-for addon, neither of which oscommerce has been known for. if I get a chance I write up a longer version of my opinion on a number of things covering old oscommerce, new oscommerce and phoenix (nothing too negative about the last one)

edited to add: I see they have now released a breif statement

[thierryc]

hello thank you all, i'm staying with phoenix, i won't go to v4 osc
it's not nice to have you out of the way
just a comment, I think there are a lot of russian names in their group
I have nothing against the Russians, but I find it curious
encore un grand merci à vous tous

[zeeshop]

Hi,

I thought I was keeping on top of my updates, as I was not able to visit the forum for last few weeks and whenever I used version checker, it showed me that I am running the latest version.

Capture.PNG

So as of today I am still on V 1.0.7.15, now it seem, there is new version 1.0.8.0 available.

Please advise what is a best way to update it to the latest version. Do I need to update each version or can I update directly to 1.0.8.0?

Where I can find update instructions.

Thanks

[ecartz]

Do I need to update each version

Yes. Instructions: https://github.com/CE-PhoenixCart/Updates

Specifically:

• https://github.com/CE-PhoenixCart/Updat ... 6/1.0.7.15
• https://github.com/CE-PhoenixCart/Updat ... 8/1.0.7.16
• https://github.com/CE-PhoenixCart/Updat ... 0/1.0.7.18

You can skip 1.0.7.17. The only change in that release was to the copyright declarations. The version checker should start working again after 1.0.7.18.

[zeeshop]

Hi,

@ecartz
I did all the updates and now using V 1.0.8.0, however not sure what caused this issue but when ever I make any changes, add or remove any Content module, I am getting page with this error on " https://www.mysite.com/backoffice/modul ... ction=save"
(on error reporting off, it opens blank page instead of Admin Content module page)

Code: Select all

Warning: Cannot modify header information - headers already sent by (output started at /homepages/31/d**********/htdocs/Live/includes/modules/content/checkout_success/cm_cs_pwa_keep_account.php:1) in /homepages/31/d***********/htdocs/Live/backoffice/includes/functions/general.php on line 36

Also on all admin pages getting this error on top:

Code: Select all

Deprecated: The tep_session_id function has been deprecated. in /homepages/31/d************/htdocs/Live/backoffice/includes/functions/sessions.php on line 113

Capture.PNG

Could you please advise how to fix this, and if I miss to upload any hook, how can I identify and upload that.

Many Thanks

[zipurman]

@zeeshop

The error: Warning: Cannot modify header information - headers already sent by (output started at /homepages/31/d**********/htdocs/Live/includes/modules/content/checkout_success/cm_cs_pwa_keep_account.php:1) in /homepages/31/d***********/htdocs/Live/backoffice/includes/functions/general.php on line 36

Would be due to the custom mod htdocs/Live/includes/modules/content/checkout_success/cm_cs_pwa_keep_account.php throwing an error before the page re-direct in htdocs/Live/backoffice/includes/functions/general.php. You'd have to inspect cm_cs_pwa_keep_account.php and see what errors it is throwing.


As for the tep_session_id error in the admin, you could rem out the line "trigger_error('The tep_session_id function has been deprecated.', E_USER_DEPRECATED);" in /homepages/31/d************/htdocs/Live/backoffice/includes/functions/sessions.php for now as it looks like a few places still call this function.

Hope that helps.

[zipurman]

@zeeshop

You could also replace mentions of tep_session_id() with session_id() in any custom mods to avoid this error.