.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
No real solid reason for not updating right now. I guess I am just afraid that upgrading might cause some new random problem to occur.
You really think upgrading to 1.3.9h would solve it? I just feel like I am doing a lot of guessing for something that feels like it should have a solid answer.
i'm sort of surprised no one else has had this problem. i keep thinking like that must mean i've got something wrong somewhere.
Upgrading between v1.3.9 versions is mostly just a matter of replacing a bunch of updated files, one letter-version at a time.
There were improvements made in the later 1.3.9 releases to handle some session problems unique to IE quirks. You need to apply each version-letter upgrade until you get to the latest version. You'll see the list of changed files in the files in the /docs/ folder.
(You can use the v1.3.9h zip file, and then just go thru all the lists of changed-files for each version-letter update, and replace those files on your server with the ones from the v1.3.9h zip file, since it contains all the updates from prior versions. But you need to use all the separate change logs because that's where all the filenames are mentioned.)
Plus, if you're using the latest version and still having the same problems then that rules out the known bugs and helps us focus on what *is* the problem, instead of making us guess what *might* be the problem and having to sort through code for several older versions. Plus, when you're using the latest version you and your customers will benefit from all the other unrelated bugs that are fixed in the process.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
Ok! You make brilliant sense!
Except I have never upgraded and don't understand this:
"You can use the v1.3.9h zip file, and then just go thru all the lists of changed-files for each version-letter update, and replace those files on your server with the ones from the v1.3.9h zip file, since it contains all the updates from prior versions. But you need to use all the separate change logs because that's where all the filenames are mentioned."
What do you mean separate change logs exactly? is that a file that i need to get from each prior version and install one after the other (like find a change log file from 1.3.9e, then9f, then 9g, then 9h)?
Correct.
However, it's a little simpler since all those changelogs are listed in the /docs/ folder of the v1.3.9h files. So you only need the v1.3.9h zip. Unzip it. Grab the e/f/g/h lists of changed files, and then go upload all those files from v1.3.9h since v1.3.9h contains all the e/f/g/h fixes.
Just remember: If you (or any of your addons) have made any changes to any of the files listed in the changelogs, you'll need to redo those changes in the updated files, else you'll lose those changes.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
Ok that doesn't sound so frightening (I say before starting, ha!).
If I understand it right without looking at the file. This change log is a text doc with a handy list of all the files in each version that have been 'changed.' So reading from those lists/change logs I pull the files out of 1.3.9h and install them over the older 1.3.9d versions. Voila.
I have thought about all the changes I've made to the files and been afraid I'd never figure out what I did where. This has all in a way been a learning experiment and as such I have not kept anywhere near perfect track of all the little tweaks I've made here and there. Part of that fear of updating factor.
I'll revisit this after I've had a chance to upgrade. Hopefully that'll fix the problems.
Thanks!
They are .html files, so can be viewed with your browser.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.