I’m moving my store to a new server (VPS at VPS.net), and in the process I’m also upgrading to 2.0.6. As the upgrade script won’t work for my Norwegian site, it seems like some language variables are missing, but this isn’t a really big problem as I’ll just export the orders, customers,etc to the new store. And then setup the rest manually. (including some minor database modifications.)
But the main problem is the SEO. I’ve transfered the old store (1.3.5) to the server, and the SEO rewrite works fine.But it’s not working in 2.0.6, and when trying to turn it on I get an error telling me mod_rewrite isn’t installed.
Mod_rewrite has been installed, clearly, as the mod_rewrite is working for the 1.3.5 store. So do anybody have any idea about what the problem could be?
The server got the following:
Debian 5 (etchy)
Apache 2.2.9
Nginx 6.9 (working as cache infront of Apache)
MySL 5.0.51
ISPManager Pro (instead of the **** called cPanel…
cPanel uses way too much resources for a cp.)
Same here.
Version 1.3.5SP4 is working with SEo but version 2.0.6 isnt.
Any ideas?
Are you using the 2.0.6 .htaccess or the one from 1.35?
This message comes up when SEO is “enabled” by doing:
$result = fn_http_request(‘GET’, Registry::get(‘config.http_location’) . ‘/catalog.html?version’);
which translates to [url]http://www.yourstore.com/catalog.html?version[/url]
Which should try to resolve the catalog.html page and return 2.0.6 as the version. If the returned header is not 200 then it assumes mod_rewrite is not enabled.
The pre-requisite to all of this is that you must have a catalog. I.e. you must have active categories in the store. catalog.html should be the same as index.php?dispatch=categories.catalog
[quote name=‘tbirnseth’]Are you using the 2.0.6 .htaccess or the one from 1.35?
This message comes up when SEO is “enabled” by doing:
$result = fn_http_request(‘GET’, Registry::get(‘config.http_location’) . ‘/catalog.html?version’);
which translates to [url]http://www.yourstore.com/catalog.html?version[/url]
Which should try to resolve the catalog.html page and return 2.0.6 as the version. If the returned header is not 200 then it assumes mod_rewrite is not enabled.
The pre-requisite to all of this is that you must have a catalog. I.e. you must have active categories in the store. catalog.html should be the same as index.php?dispatch=categories.catalog[/QUOTE]
Please clarify in steps to what exactly needs to be done? or anyone else had the same problem and resolution please…
TIA
[quote name=‘coder’]Please clarify in steps to what exactly needs to be done? or anyone else had the same problem and resolution please…
TIA[/QUOTE]
Try uninstall and then reinstall the addon
if this problem is anything like the original one i suffered in 1.3.5 when SEO would not activate - it is to do with PHP being in CGI mode… They resolved it after a ticket last time, so i have dropped them a note again about this for me.
Also note, mine failed, when 1.3.5 works, activate does not work… but uninstall and re-install does work… so this will be fine for now!