I only get this on Google Chrome. It gives a pop-up with <!--SHTML Wrapper - 500 Server Error --> and under that error it has boxes, diamonds with question marks, and what seems like random text interspersed.
Has anyone else seen this behavior on Open Cart 1.5.6?
Thank you,
Mike
The oddball characters probably mean that the character set needs to be dealt with in the browser itself (it sees characters that won't display in the character set is is now told to use), but the 500 derives from the server's response to your website. When you see that, what do you see in the address bar, between http and https, and between html and shtml?
Did you search for "SHTML Wrapper"?
There are two links for "SHTML Wrapper", try the upper one with 500 seeming to relate more directly than the lower does:
http://forum.opencart.com/viewtopic.php?t=61533
http://forum.opencart.com/viewtopic.php?t=24058 (no 500, not really helpful, Google dinna have anything else, so . . .)
Did you search for "SHTML Wrapper"?
There are two links for "SHTML Wrapper", try the upper one with 500 seeming to relate more directly than the lower does:
http://forum.opencart.com/viewtopic.php?t=61533
http://forum.opencart.com/viewtopic.php?t=24058 (no 500, not really helpful, Google dinna have anything else, so . . .)
The address bar doesn't have anything that shows if it is https or http but on Internet Explorer it is http.
I did search for SHTML Wrapper and I came up with the same post (the 1st one) you did but didn't think it was applicable since we don't have url rewriting turned on yet.
So far I am at a loss but it happened a while back, went away, and now came back but both times I have ran across this it is only using Google Chrome. I am at a loss but I will try the suggestion at the bottom of the first post and see what happens.
Mike
I did search for SHTML Wrapper and I came up with the same post (the 1st one) you did but didn't think it was applicable since we don't have url rewriting turned on yet.
So far I am at a loss but it happened a while back, went away, and now came back but both times I have ran across this it is only using Google Chrome. I am at a loss but I will try the suggestion at the bottom of the first post and see what happens.
Mike
cue4cheap not cheap quality
Tried it and same result. (Commenting out the symlinks and Indexes)
The only place I seem to come up with is erro is on the check out page.... http://www.store.com/index.php?route=checkout/checkout
The only place I seem to come up with is erro is on the check out page.... http://www.store.com/index.php?route=checkout/checkout
cue4cheap not cheap quality
You would have four alternatives in address bar, in formats
http://[. . .]index.html
http://[. . .]index.shtml
https://[. . .]index.html
https://[. . .]index.shtml
Chrome is stumbling on shtml wrapper, which seems to indicate a css wrapper (page, container, wrapper, box, div, etc., are options). You might check your .css, as well as your .tpl and .php, for "wrapper" to see if that leads somewhere. This would not be the first time that one or another browser has had its own view of a website.
http://[. . .]index.html
http://[. . .]index.shtml
https://[. . .]index.html
https://[. . .]index.shtml
Chrome is stumbling on shtml wrapper, which seems to indicate a css wrapper (page, container, wrapper, box, div, etc., are options). You might check your .css, as well as your .tpl and .php, for "wrapper" to see if that leads somewhere. This would not be the first time that one or another browser has had its own view of a website.
As of right now I have cleared the history on google chrome and things are "good" but now I have another issue across all browsers that I'll post in another thread. (Starting to wonder why I am getting odd stuff going on with not too many changes done on a new 1.5.6 install - I have disabled 90% of the extensions and only made one non-vqmod change which was a language file change only)
Mike
Mike
cue4cheap not cheap quality
Yup, just checked. It was just adding in a couple of words and semicolon is good.
I might, might, install from scratch again since I am still online with my old shopping cart software so I can afford to work on this in the back-ground but I have 3 weeks until I have to have my new cart online.
Thank you for the replies and I'll revive this thread if the problem pops back up with google chrome.
Mike
I might, might, install from scratch again since I am still online with my old shopping cart software so I can afford to work on this in the back-ground but I have 3 weeks until I have to have my new cart online.
Thank you for the replies and I'll revive this thread if the problem pops back up with google chrome.
Mike
cue4cheap not cheap quality
You could try upgrading it, from itself, in situ, as it sits, before trying a complete install, and with a fresh upload of the fileset, just to give it opportunity to check itself out again. Then the difference between upgrade and install would reside primarily in status of the pairs of config.php and index.php, .htaccess.txt and .htaccess, and whether the db is given null or same or new prefix. You would install vqmod anew (replace or just rerun installer) -- that would be necessary with install, perfunctory with upgrade, just so that vqmod has also checked itself out. Be certain that you are using the correct version of vqmod of the two -- the one for OC.
Hmm, Could you explain how I could do that? "upgrading it, from itself, in situ, as it sits"
My guess is that you mean re-upload all files except the config.php files? Or re-upload all of the files and run the install?
I could think of a couple of ways on what you might mean so I thought I would ask.
Thank you,
Mike
My guess is that you mean re-upload all files except the config.php files? Or re-upload all of the files and run the install?
I could think of a couple of ways on what you might mean so I thought I would ask.
Thank you,
Mike
cue4cheap not cheap quality
I think it is time to just wipe the directory and start new.... I can't afford to find out later that one of the mods I tried actually caused a hack to get in... I downloaded a couple of free extension from other locations then the extension part of open cart and I have a fear one of them might have contained nefarious code.
Mike
Mike
cue4cheap not cheap quality
A clean install seems best. (Good choice; had left early last night.) Then the entirety will be fresh, including directories themselves (none lurking with wrong permissions, hidden names, etc.). Whichever way, upload or install, you can replace the fileset as well as vqmod. Upgrading would essentially rerun the installer to let it finish anything it might have missed (not necessary to start all over again with reinstallation of an older predecessor, though that could be done). The vqmod installer rewrites two index.php or notices that it already did, and checks itself.
Clean install done. No error with about 10 test of going through the checkout process up to the payment method (used to give me the error most of the time between the delivery method and payment method step).
I will run a bunch more tests then add one extension and test and continue.... I hope I never run into the problem again but so far (not too far along) so good.
Mike
I will run a bunch more tests then add one extension and test and continue.... I hope I never run into the problem again but so far (not too far along) so good.
Mike
cue4cheap not cheap quality
Test some more before you're content enough that it stays fixed to edit your opening title Solved. At least you have a solution, bail out and fly another one. Most of the time 500 (server confused) does NOT necessitate or warrant that extreme action, you need only look at your .htaccess, config,php, php.ini, and other essential files for whatever befuddled the server.
[Ya know, sometimes these Submit buttons are not at all useful . . . a blanked box is not what we expect to see.]
[Ya know, sometimes these Submit buttons are not at all useful . . . a blanked box is not what we expect to see.]
It wouldn't be the first time that an author rescinded Solved, but, yeah, best to give it some time so you're at least pretty sure. It'll help not to do very many things at once, so that you can still pinpoint what you just did that can be reverted right after a 500 or a white nullity hits the screen. Often very simple changes cause them, and the corrections are quick if you keep track of yourself -- by making backups and keeping your own changelogs.
Who is online
Users browsing this forum: No registered users and 306 guests
