et al.

Looks to be a triumvirate of errors. None of which were the fault of the OPC mod or it's author. The initial problem was that guest checkout was not working. All other features of OPC were operational. This under version 2.0.0. An Upgrade failed twice and removal/installation gave a worse result.


First, as mentioned in our prior post, a "hidden" mod was not compatible with OPC and we were not aware that it was even installed until we dropped to standard checkout. Recommend that all mods register in admin pages. That sure would have helped. Of course it would have helped more if the base load used was the correct one. A search of our base loads did not show the mod installed. Personnel problem to be addressed.


Second, as reported here, the error was being thrown. We had no idea of the language but were surprised to find several references to the exact phrase when Google was used. It suggested that a different terminology should have been used for the determination if a setting existed. That should have been my clue but didn't sink in till carlwhat jumped in.


I am next in line behind the last person that would question Cindy's coding. That's what made things puzzling until carlwhat posted the language info and the link. Lo and behold, the site was set to PHP 5.4! This is not supposed to be even an option on the server. Apparently, a recent change in cpanel method may have added levels under 5.6. Rest assured that will go away immediately. As the great detective said, "How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth?" While this got OPC to working, guest checkout would still not work.


This leads us to the third and mea culpa part of the problem. My dislike of putting changes in the template_default versus YOUR_TEMPLATE came back to bite me in the @$$. Right or wrong, I just hate to make changes to the template_default that might easily be lost in the upgrade process. If I make them in the YOUR_TEMPLATE folder, they are easily found when upgrade time rolls around. That's the same reason I started using stylesheet_zcustom.css to record all css changes to a template.

That said, Cindy has an excellent point in that moving from templateX to templateY may lose the OPC files while placing them in the templat_default will ensure that a template change will still have access to the OPC files.

Too often, I was failing to use initials or BOF/EOF to identify changes. Laziness is the true mother of invention. I was lazy.


Also, in my fog (fighting bronchitis), I failed to realize that I had previously disregarded Cindy's instructions and placed the files in YOUR_TEMPLATE. When haredo marshaled me step by step through the latest installation, my brain did not click on the use of YOUR_TEMPLATE. Therefore, there were older OPC files in the YOUR_TEMPLATE folder and (just as advertised) were overriding the proper files in the template_default. So, there's the flaw in my thinking.


I haven't decided my punishment but am hoping to only have to suffer through the remaining bronchitis treament/recovery.


Thanks to Cindy for putting up with me and carlwhat for derailing my train of thought and forcing it to the proper station.