![]() |
Re: XC SEO v1.1.0 Released
The froogle modification is incorrect, please ignore it for now. Don't modify your froogle module, use it as you normally would. When someone visits your website from froogle, they'll be auto-redirected to the new SEO'd url.
The froogle modification will be fixed soon. |
Re: XC SEO v1.1.0 Released
I just added this mod to a new store, and everything went smooth.
As soon as I add the htaccess file and check the box to use the mod, I get total internal server errors. I remove the htaccess file and I see html links rewritten in url, but until I uncheck the box for the mod to be enabled, the cart will not work again. I have quadroopled the installation notes and actions, and I am dead on for installation, but it must be a server setting. B4 anyone asks, yes, I am on linux base with apache, and I use rewrite rule for other attributes, so I know it works. I need to open within a week, and need an SEO mod, so if I cannot get this to work, I must revert to another mod I have used in the past (pay version) Was hoping to save money and time, but looks like it will be neither. Anyone have any suggestions on internal server errors? Server settings that may not allow this mod to woek oujt of box and require work around? |
Re: XC SEO v1.1.0 Released
please paste (inside CODE blocks) the full htaccess you were using when the mod did not work (including the changes that were required by XC SEO)
|
Re: XC SEO v1.1.0 Released
Quote:
Keep in mind, I have my site blocks in here as well. I also have to place my zlib compression statements into a php.ini file, as well as my statement to keep TransIDs from appearing in the headers. I will show my php.ini file below the htaccess file. Also keep in mind, this htaccess file is in the root, and so is my cart installation. Code:
<Files .htaccess> |
Re: XC SEO v1.1.0 Released
Got nailed for too much text, so I had to remove some and add it here for your use, as I thought some of this additional info may come in handy, and then again, maybe not...
I was told by a vendor that I have used for a commercial rewrite mod that I have used in the past for other sites, that the php.ini file was interfearing with one installation I had, and there had to be another snippet of code devised to accomodate this. This particular site is also on the same host, so maybe this is what is happening here? Not sure, thought I would offer that tidbit up for your thought. Here is the php.ini file. Code:
magic_quotes_gpc on Thanks for the review. Also FYI... when I remove all of the rewrite statements from this mod, I keep the sercurity portion, as I have this enabled in all of my sites with or without this mod. In this case, I simply grouped my secure portion of my htaccess to match yours, and added the grouped portion of redirect gone files like copyright, version, install etc, as I had them listed individually, and not grouped like this, but it looked like this saved some space, so I decided to use your layout. Other than that, it all looks the same as I have used in the past. Hope some of this info helps. |
Re: XC SEO v1.1.0 Released
What's the difference between...
RedirectMatch gone ^.*/shipping/.*$ Redirect gone /shipping |
Re: XC SEO v1.1.0 Released
Quote:
the simple redirect gone shipping is only for the shipping file and the other is for the shipping file and all php files in it dealing with shipping. |
Re: XC SEO v1.1.0 Released
Quote:
Thanks for your reply.. RedirectMatch gone ^.*/shipping/.*$ - This one deals with all php files with shipping... Redirect gone /shipping - This one deals with only shipping Should I be using both or just one..? |
Re: XC SEO v1.1.0 Released
You have it listed correctly, so you see the just of it.
In my personal experience, I have used the simple shipping directory denial, and it was to keep bots from that area, or prying eyes, and crawlers from personal crawler that builds my Google Site Map. Now I am not sure how this SEO mod operates, but there may be a need to keep the files associated with shipping from being rewritten. I guess that in itself would have to be answered initially, to then follow up with the question of which is to be used. If that was the case, and you wanted to keep the rewrite mod away from the shipping files, and you also want to keep prying eyes away, then that would justify using both I guess. OR, if you are really paranoid, lol, I guess you could use the one that uses the most secure protocol, and that would be the denial of the file area AND the files within it. Was that clear as mud? This is how I see this anyhow. Someone else may have another opinion or an idea as to why to use one over the other. There are always ideas and different thoughts when it comes to things like this. You know how that goes. |
Re: XC SEO v1.1.0 Released
the secure.htaccess file that I included with XC SEO has nothing to do with actual rewriting, just my recommendation (based upon reading in the X-Cart forum) for securing your x-cart installation. as for the issue that you're experiencing with XC SEO, it looks as if you've implemented the htaccess stuff correctly.
what version apache are you running? i believe you mentioned running a commercial seo mod before, i assume it worked without any issues? can you post a url that hasn't been rewritten by xc seo, post a url that HAS been rewritten by xc seo? also, do you have access to your Apache error logs? might be good to post the logs, they should list any issues occurring due to htaccess rules. |
All times are GMT -8. The time now is 02:23 AM. |
Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2023, Jelsoft Enterprises Ltd.