I just installed OC 3.0 and migrated all my orders and info over from 1.5.6.4 using Excelport. I initially installed the site in its own folder and everything worked great. I moved it over to the root and now I'm getting "error undefined" when trying to edit or delete an order.
I searched the issue and it appears to be an SSL problem but I couldn't find any legitimate solves. Help!
Dedication and passion goes to those who are able to push and merge a project.
Regards,
Straightlight
Programmer / Opencart Tester
Dedication and passion goes to those who are able to push and merge a project.
Regards,
Straightlight
Programmer / Opencart Tester
Dedication and passion goes to those who are able to push and merge a project.
Regards,
Straightlight
Programmer / Opencart Tester
What's strange is the website functions just fine in the subfolder but I get these errors when I move it to the root. The other option is I can just leave it in the subfolder if there's a way to make it so the www.mysite.com points to www.mysite.com/oc3
Thanks for your assistance
Dedication and passion goes to those who are able to push and merge a project.
Regards,
Straightlight
Programmer / Opencart Tester
It's always a bad idea to move an existing store from its original position (the subfolder). If the whole point of the exercise is to eliminate the need for a customer to type in "/oc3", it's better to rewrite the URL in /.htaccess (assuming you're on a server that permits this). The following will rewrite a visit to https://www.mysite.com to https://www.mysite.com/oc3 without the customer having to do any extra effort:Garret H wrote: ↑Sun Aug 05, 2018 5:56 amWhat's strange is the website functions just fine in the subfolder but I get these errors when I move it to the root. The other option is I can just leave it in the subfolder if there's a way to make it so the www.mysite.com points to www.mysite.com/oc3
Code: Select all
RewriteEngine On
# force https and www.
RewriteCond %{HTTPS} !on [OR]
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^(.*)$ https://www.mysite.com/$1 [R=301,L]
# if visit to root, jump to /oc3
RewriteCond %{REQUEST_URI} !^/oc3
RewriteRule ^(.*)$ /oc3/$1
The advantage to doing it this way is that if you later add a "landing page" /index.html (for instance) to welcome visitors and direct them to various parts of the site (blog, gallery, etc.), all you have to do is remove the rewrite to /oc3 and all the existing bookmarks and search engine entries will still be valid.
I've used 1.5.6.4 for almost 7 years now. I upgraded to 3.0 because my site was constantly getting hacked. I was hoping 3.0 would be better than 1 .5.6.4 which had a ton of glitches and required numerous mods to fix. Sadly, I see it is no different. Simple things such as the contact us page didn't work properly. Opencart has some serious development issues and sadly, I don't have the time and money to spend fixing it like I did with 1.5.6.4. I've made the migration over to Shopify. The $26 a month is nothing compared to the thousands I've spent trying to keep OC working right over the years. It's refreshing to use a cart system that actually works properly out of the box.
Crystal Light Centrum Taiwan
Extensions: MailQueue | SUKHR | VBoces
“Data security is paramount at [...], and we are committed to protecting the privacy of anyone who is associated with our [...]. We’ve made a lot of improvements and will continue to make them.”
When you know your life savings are gone.
but i am getting error - Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://www.xyz.com/index.php?route=api/ ... store_id=0. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
Crystal Light Centrum Taiwan
Extensions: MailQueue | SUKHR | VBoces
“Data security is paramount at [...], and we are committed to protecting the privacy of anyone who is associated with our [...]. We’ve made a lot of improvements and will continue to make them.”
When you know your life savings are gone.
define('HTTP_SERVER', 'http://admin.xyz.com/');
define('HTTP_CATALOG', 'http://www.xyz.com/');
//define('HTTP_IMAGE', 'http://www.xyz.com/');
// HTTPS
define('HTTPS_SERVER', 'http://admin.xyz.com/');
define('HTTPS_CATALOG', 'http://www.xyz.com/');
define('HTTPS_IMAGE', 'http://www.xyz.com/');
// DIR
define('DIR_APPLICATION', '/home/xyz/admin_xyz_com/admin/');
i have used like this for admin
In any event, that is the problem, your calls via api from admin sub-domain to the catalog sub-domain is not allowed.
You could try this in htaccess, straight from stack overflow, it is supposed to set the correct CORS headers for sub-domains:
Code: Select all
SetEnvIf Origin ^(https?://.+\.mywebsite\.com(?::\d{1,5})?)$ CORS_ALLOW_ORIGIN=$1
Header append Access-Control-Allow-Origin %{CORS_ALLOW_ORIGIN}e env=CORS_ALLOW_ORIGIN
Header merge Vary "Origin"
Crystal Light Centrum Taiwan
Extensions: MailQueue | SUKHR | VBoces
“Data security is paramount at [...], and we are committed to protecting the privacy of anyone who is associated with our [...]. We’ve made a lot of improvements and will continue to make them.”
When you know your life savings are gone.
Crystal Light Centrum Taiwan
Extensions: MailQueue | SUKHR | VBoces
“Data security is paramount at [...], and we are committed to protecting the privacy of anyone who is associated with our [...]. We’ve made a lot of improvements and will continue to make them.”
When you know your life savings are gone.
Users browsing this forum: No registered users and 514 guests