I had a similar problem..
I purchased a really awesome theme by Koev (Althemist) through Themeforest and recently out of the blue the "add to cart", compare & wishlist. I couldn't get it to work for about a week. Koev tried to help me but no go.
I run a win 7 pro 64bit system and I have OC 1.5.4.1 and I'm running SSL through out my site: www.tekno-gecko.com
The solution was that my .htacess file had been written to re-route all http traffic to https but it was sending it to https://tekno-gecko.com instead of https://www.tekno-gecko.com. Somehow the www makes all the difference when running SSL?
Maybe someone can explain this to me.
I purchased a really awesome theme by Koev (Althemist) through Themeforest and recently out of the blue the "add to cart", compare & wishlist. I couldn't get it to work for about a week. Koev tried to help me but no go.
I run a win 7 pro 64bit system and I have OC 1.5.4.1 and I'm running SSL through out my site: www.tekno-gecko.com
The solution was that my .htacess file had been written to re-route all http traffic to https but it was sending it to https://tekno-gecko.com instead of https://www.tekno-gecko.com. Somehow the www makes all the difference when running SSL?
Maybe someone can explain this to me.
Hi guys
For past 4 hours of this beautiful Sunday i'm trying to get my shop to work, without any luck.
At http://www.aranzmaji.si you can see, that (almost) everything is working, except;
- Cannot add to cart in IE and Chrome
- Cannot login in IE and Chrome
- Cannot login to admin in Chrome
I've read many topics, with my knowledge (not coder) but cannot solve this thing.
Please, take a look, you can test it (it's slovenian language, but i guess you will see the one and only button to add to cart). Shop is live, but no orders come in .. obviously of these errors
Thank you in advance!
For past 4 hours of this beautiful Sunday i'm trying to get my shop to work, without any luck.
At http://www.aranzmaji.si you can see, that (almost) everything is working, except;
- Cannot add to cart in IE and Chrome
- Cannot login in IE and Chrome
- Cannot login to admin in Chrome
I've read many topics, with my knowledge (not coder) but cannot solve this thing.
Please, take a look, you can test it (it's slovenian language, but i guess you will see the one and only button to add to cart). Shop is live, but no orders come in .. obviously of these errors
Thank you in advance!
Okay, this is essentially a quick romp around the garden to zero in on any unflattened flowers and flatten them, too.
Since (or among you, where) you're using a non-default theme, it presents three immediate options: search themename plus add to cart, ask for support, rename default/ and then rename themename/ to default/ and see if the default templates cause that. If the answer is that they don't, either reinstate themename/ or keep default/ reinstated till somebody figures out what went wrong in themename/. Some have said outright that they're using themes, but some have not outright said default or other. IF THE DEFAULT THEME IS CAUSING THE PROBLEM, THEN PLEASE NOTE THAT OUT FRONT.
That one of you "looked and the www is in the address bar" doesn't go far enough. Look in both config.php to see how both HTTP and HTTPS sections are preset. You may have confused OC.
That avvici -arvixe- doesn't see the problem in his Chrome with the given link means that browser versions or settings (those would be defaults, swallowed whole) are part of the problem.
One quick check can be made by temporarily renaming .htaccess to X.htaccess so that it takes a nap, or sliding it aside into a setaside/ directory so that it takes a vacation, in order to see whether the dysfunctions stop. Flushing vqmod/ of its cache file and flushing vqmod/cache/ of its files may help. From patterns above, probably worth a try.
Theme templates to some extent and sometimes their further reaching model or controller files will handle portions of core code or its processing. Those would be the places to begin looking for something amiss that somehow affects IE andChrome, as to adding to cart or logging into admin/.
Overall URLS with "www." and ending with trailing "/" work best, some of the reasons are esoteric but do matter. The presence or lack of www. affects the traffic pointing, redirection if any, and landing, and to some extent whether Apache and OC itself during the reiterations when index.php self-executes still find all of its own parts, such as where seo begins balking under a certificate between www. and none), not whether something even displays. Accordingly, there is a reduced likelihood that paying attention to the two IE .css files will resolve the matter for IE and Chrome, which both use an IE engine rendering engine. If ANYTHING in .css interferes with executable code, then failure to load into or to remove from cart becomes feasible, although that would seem secondary to look at. Alike Netscape before it, Firefox is surprisingly agile and forgiving in figuring out what was intended that may have been mistyped or mis-nested or even omitted or inserted that was not quite ideal according to proverbial Hoyle standards. Unlike those, IE and to a possibly lesser extent Chrome do not have that agility or forgiveness, and are actually NOT as standards-compliant as is current (and recent) Firefox. Themes diverge from the known stabilities of OC versions.
Inability to log in springs from a different series of core code. Inability in IE and Chrome alone to log in invites attention to the same sorts of approaches as for inability to add to cart.
As for machine-resident problems, there is the idiosyncrasy of IE and along with it Chrome that they utilize (Firefox does not) the resident Win Internet Settings gibberish, which may bear attention for trusted and untrusted permissiveness in secured or unsecured transactions (not meaning money) between browser and website. Basic connection to the websites effectively rules out that problem, except where SSL may intrude in win-specific ways.
Since (or among you, where) you're using a non-default theme, it presents three immediate options: search themename plus add to cart, ask for support, rename default/ and then rename themename/ to default/ and see if the default templates cause that. If the answer is that they don't, either reinstate themename/ or keep default/ reinstated till somebody figures out what went wrong in themename/. Some have said outright that they're using themes, but some have not outright said default or other. IF THE DEFAULT THEME IS CAUSING THE PROBLEM, THEN PLEASE NOTE THAT OUT FRONT.
That one of you "looked and the www is in the address bar" doesn't go far enough. Look in both config.php to see how both HTTP and HTTPS sections are preset. You may have confused OC.
That avvici -arvixe- doesn't see the problem in his Chrome with the given link means that browser versions or settings (those would be defaults, swallowed whole) are part of the problem.
One quick check can be made by temporarily renaming .htaccess to X.htaccess so that it takes a nap, or sliding it aside into a setaside/ directory so that it takes a vacation, in order to see whether the dysfunctions stop. Flushing vqmod/ of its cache file and flushing vqmod/cache/ of its files may help. From patterns above, probably worth a try.
Theme templates to some extent and sometimes their further reaching model or controller files will handle portions of core code or its processing. Those would be the places to begin looking for something amiss that somehow affects IE andChrome, as to adding to cart or logging into admin/.
Overall URLS with "www." and ending with trailing "/" work best, some of the reasons are esoteric but do matter. The presence or lack of www. affects the traffic pointing, redirection if any, and landing, and to some extent whether Apache and OC itself during the reiterations when index.php self-executes still find all of its own parts, such as where seo begins balking under a certificate between www. and none), not whether something even displays. Accordingly, there is a reduced likelihood that paying attention to the two IE .css files will resolve the matter for IE and Chrome, which both use an IE engine rendering engine. If ANYTHING in .css interferes with executable code, then failure to load into or to remove from cart becomes feasible, although that would seem secondary to look at. Alike Netscape before it, Firefox is surprisingly agile and forgiving in figuring out what was intended that may have been mistyped or mis-nested or even omitted or inserted that was not quite ideal according to proverbial Hoyle standards. Unlike those, IE and to a possibly lesser extent Chrome do not have that agility or forgiveness, and are actually NOT as standards-compliant as is current (and recent) Firefox. Themes diverge from the known stabilities of OC versions.
Inability to log in springs from a different series of core code. Inability in IE and Chrome alone to log in invites attention to the same sorts of approaches as for inability to add to cart.
As for machine-resident problems, there is the idiosyncrasy of IE and along with it Chrome that they utilize (Firefox does not) the resident Win Internet Settings gibberish, which may bear attention for trusted and untrusted permissiveness in secured or unsecured transactions (not meaning money) between browser and website. Basic connection to the websites effectively rules out that problem, except where SSL may intrude in win-specific ways.
Who is online
Users browsing this forum: Baidu [Spider] and 132 guests
