Going with 1.5.3.x for a while may be worth the peace of mind -- while the other is being pursued by several people and does raise (anew or again) idiosyncrasies of OC, SSL, and server variations in mutual contexts (as distinguished from raising a "bug" as such in OC itself).
@flywatches.. hate to say it but it's the host.. they do not know how to set things up to work with OC properly.. it is hard to get them to acknowledge it and in the end switching may just be easier.. months later for me and not a single glitch with the issue with Jeff & wxhosting.. all I do now is box up products with my time.. I actually was at a point where I backed up my site 2 to 3 times a day manually and that is all but a memory.. its like being freed from prison.. best move I made. Good luck with your decision.
If there are problems with SSL encryption/functionality it's always either HUMAN ERROR ( in terms of not configuring correctly or you have items on your website that are breaking the encryption) or SERVER SIDE ERROR (where the cert was not installed correctly. This especially is common for 3rd party certs outside of your hosting provider) However, it's rarely an Opencart issue directly.
Make sure to check your website at http://www.whynopadlock.com
Make sure to check your website at http://www.whynopadlock.com
Thanks for the feedback. If it were my host or server, I would assume it wouldnt have worked on on 1.5.3. It only seems to be an issue now that I've upgraded to 1.5.5.1. I also tested it on the padlock site and it passes every test.
Jonathan
Some of the core and database changes from the 1.5.3.x to the 1.5.5.1 are significant. Unlike most software, OC is routinely tested on practicably every combination of hardware and operating systems in use as servers. Server nuances vary more than most people would guess, and more than experienced hands fully anticipate. Having one 1.5.5.1 running smoothly would allow borrowing from its setup to make a second one run smoothly. Not having one of those allows running prior old trusty for a while longer.
I have just noticed that my domains are not being redirected to HTTPS were they should be. This was definitely working a few days ago. I have no clue how to resolve this.
Any suggestions?
Any suggestions?
Make sure your SSL is enabled in your admin (if you have multistore you'll need to enable it for each). Also make sure that if your HTTPS url's are defined in the config.php file that you change the http:// to https:// for them
With the other .htaccess scripts, the add to cart functionality was not working.
But this code did the trick:
I also had to comment out this line:
and update the config files (root and admin) of course.
But this code did the trick:
Code: Select all
#Force HTTPS for Storefront
RewriteCond %{HTTPS} off
RewriteCond %{QUERY_STRING} ^route=checkout/checkout
RewriteRule (.*) https://%{SERVER_NAME}%{REQUEST_URI} [L,R]Code: Select all
#RewriteRule ^(.*)$ https://beyondthesparkle.com/$1 [R=301,L]Pay-As-You-Go Web Development - Full service website, mobile and software development.
http://www.webdeveloperlabs.com
This is a brilliant idea, finally I found this code work well for all the 3 major browsers (IE, FF, Chrome), after searching high & lowwebdeveloperlabs wrote:With the other .htaccess scripts, the add to cart functionality was not working.
But this code did the trick:
I also had to comment out this line:Code: Select all
#Force HTTPS for Storefront RewriteCond %{HTTPS} off RewriteCond %{QUERY_STRING} ^route=checkout/checkout RewriteRule (.*) https://%{SERVER_NAME}%{REQUEST_URI} [L,R]and update the config files (root and admin) of course.Code: Select all
#RewriteRule ^(.*)$ https://beyondthesparkle.com/$1 [R=301,L]
How if I want my other pages (specially for products and information) to force to http, instead also published under https ?
Thanks!
It's actually not that brilliant. You shouldn't be using .htaccess to specify which pages should be SSL and which should not. There are simple procedures for this that are already in place in most of the Open Cart control files for example if you want to call category.tpl to be SSL then take a line like this:
and change to this:
This is assuming of course that you have SSL turned on and your htaccess is correct. I'm not talking about your custom .htacces edits.
Code: Select all
'href' => $this->url->link('product/category', 'path=' . $category['category_id'])Code: Select all
'href' => $this->url->link('product/category', 'path=' . $category['category_id'], 'SSL')Thank you for enlighten meavvici -arvixe- wrote:It's actually not that brilliant. You shouldn't be using .htaccess to specify which pages should be SSL and which should not. There are simple procedures ...........
I will try this, and I have also problem in my admin backend, I posted another treat here:
http://forum.opencart.com/viewtopic.php?f=20&t=119772
On "Second issue (admin)", I have check an online tool saying my ssl has installed correctly (was installed by my host), but I have some codes on htaccess on pervent image hotlink; compression. I am not sure this causing my admin backend problem. This only happened after SSL installed.
Thanks again!
Who is online
Users browsing this forum: No registered users and 63 guests
