upgraded 1.39 to 1.56, admin missing options

[mc12345678]

So. The concern (if can call it that) related to changing HTTP_SERVER to begin with https:. Let's talk about the internet a little.

People reach out to a computer using a web address. Part of that web address is the protocol to use and in some cases some specific information about that protocol. In this case let's keep with http. When someone tries to access your site using http:, the server is configured to accept the request, but then to forward it to https: (encryption is expected to be used and in most cases a different port on the computer).

So the visitor gets redirected to https:, ok. Great.

That method of connection is detected by ZC to indicate that the customer has reached the site using https. So there is software that recognizes that. Knowing that information, ZC prepares to present the page to the customer.

As part of preparing the page, the applicable configure.php file is reviewed/read. It comes across HTTP_SERVER and ENABLE_SSL (store side) and as the files continue to be accessed, anywhere HTTP_SERVER is encountered, the software substitutes the value from the configure.php file. In some cases there is an evaluation performed: if ENABLE_SSL is true, then use HTTPS_SERVER instead. There also are some where if the page was accessed using https: then present all links using https:...

Well, by forcing every arrival by a customer to https:, that means that all links to your site should be by https:. Otherwise, the link would be generated with http:, the link clicked, the server would redirect to https:. In that process, there would initially be an attempt to access without encryption and therefore that information could be captured...

By changing HTTP_SERVER to start with https:, all links generated will always be https: and therefore the server does less "work" and the information that could otherwise be viewable via http: would not be available.

So, in the case of the server forcing all https:, the software should do the same...

[Dinnages]

Okay, the general way around the web I follow, I started off with a 286 and DOS in the eighties, been writing web pages for clubs in notepad for years.

Up until very recently my site did not use https, my pages and shop only used outside merchant sites to take the money so why would be the need for https.
With Paypal failing on the 1.39 shop (incompatable PHP versions I gather), hence my jump to 1.56 and all the issues encountered this time making the upgrade.
Never had so much of an issue upgrading before from earlier versions up to 1.39, I felt it was pretty much plain sailing.

This time its come unstuck on so many different little things, maybe once my own doing saving a file in the wrong place.

Since starting this in late December, I feel nowhere nearer my goal of upgrading in my quietest time of my online trading year, now reached 30 of them.
Start my outside stalls soon, and wanted to get the store afreshed really by then, so somewhat disapointed I cant fix it this time even with help from you this time & in the past was mainly DrByte.

I am sure theres even less knowledgeable folk out there who start with ZenCart shops and need even greater help with more of the mundane issues, but surely upgrading is one of the biggest tasks of them all. I'd help others if I knew the answer, thats usually what the forums are about.

Maybe its looking for 'paid for' assistence? That will be a first for me, usually end up solving a problem in the end with guideance, where to look.

[Dinnages]

Well at the 11th hour, my host (lots of different staff) has come up with the very simple fix, a missing slash /

Frustrating to say the least, so however many times you can go through the configure.php files, get others to look over them, just like proof reading a book.

I must say, out of everyone, Zencart member here mc12345678 has been the most patient and consistant in trying to help with this 'problem' and it really had to be a simple issue as the store front other than a template that needs tinkering, admin was inaccessable, and as everyone says here 90% of the time it IS an error in the configure file/s. Certainly worth 'a pint' at least!

define('DIR_FS_CATALOG', 'home/nostalg/public_html/store/');

Corrected the path to:

define('DIR_FS_CATALOG', '/home/nostalg/public_html/store/');

It certainly is not immediately obvious.

My next task is getting rid of this;

WARNING! Welcome Email Discount Coupon expires in -17937 days

During the upgrade I started late December I deleted all the related Welcome coupons.

[Dinnages]

Looking back on post #27 the fault was clearly there, now I know what the error was...

define('DIR_FS_CATALOG', 'home/nostalg/public_html/store/');

mising the single forward end /

define('DIR_FS_CATALOG', '/home/nostalg/public_html/store/');

So maybe that has been there all along.
Those that read the thread at a later date, your configure.php is most likely containing a simple small error.

Have donated to the ZenCart team today, however its been mainly the help via my host early on and member MC12345678 here at ZenCart