deepee Posted March 6, 2013 Share Posted March 6, 2013 In older versions of Prestashop it was easy to include 301 redirects in .htaccess when a product was removed from the catalogue. In 1.5 that's not possible because .htaccess if frequently overwritten by the system. I bought a 3rd party module that didn't work as expected for handling these redirects. As an example, I have a product that is being replaced be a very similar product. When visitors visit a link to the URL of the old product I want to them to land on the new product page. I would normally set it up as: Redirect 301 /mysite/oldproduct http://mysite/newproduct What are people using to handle this in 1.5 ? Link to comment Share on other sites More sharing options...
Trip Posted March 6, 2013 Share Posted March 6, 2013 (edited) I am not sure if it works but the automatically changed parts should only be within the comment section. At least this is how I interpretet # ~~start~~ Do not remove this comment, Prestashop will keep automatically the code outside this comment when .htaccess will be generated again ............................................... # ~~end~~ Do not remove this comment, Prestashop will keep automatically the code outside this comment when .htaccess will be generated again in the .htaccess. If this is not working you might post it on the bug tracker? Edited March 6, 2013 by Trip (see edit history) Link to comment Share on other sites More sharing options...
deepee Posted March 6, 2013 Author Share Posted March 6, 2013 Thanks, Trip, I was unaware of that. I'll try it and post back to this thread. Anyone else have any thoughts as to what is best practice for removing old products without losing valuable incoming links and incurring search engine 404 penalties? Link to comment Share on other sites More sharing options...
Bill Dalton Posted March 7, 2013 Share Posted March 7, 2013 Take a look at, http://www.presto-changeo.com/en/prestashop-modules/25-duplicate-url-redirect.html Link to comment Share on other sites More sharing options...
deepee Posted March 7, 2013 Author Share Posted March 7, 2013 Thanks, Bill. I had this module installed early after moving to 1.5.0 and had to remove it. Thatwas the 3rd party module I mentioned in my original post. Despite assurances from presto-changeo that it was working properly and was not the cause of links resolving to blank pages, I eventually discovered that it was. Coupled with the buggy .htaccess subdomain redirect issues it was a nightmare trying to work out what was going on. Not to mention the loss in business. Even the installation instructions in the back office that presented when starting the module for the first time, were wrong. Again a big waste of time. I noticed on their website they had an update that I assume fixes the issues. They say you can request an update via the webform which my partner did. I wasn't impressed to see the return email that wants to charge us for the update. We should send them an invoice for the waste of our time trying to work out what was happening and the loss of business incurred. Link to comment Share on other sites More sharing options...
tomerg3 Posted March 7, 2013 Share Posted March 7, 2013 If you have any issue with our module, you are more than welcome to contact us using our contact form and we will gladly investigate. We sometime increase the prices of module when major new development is made, this module was at $25 for over 3 years, and just recently had a price increase, which you don't have to get if you don't want to use the new features. Regardless of the upgrade, the version you bought should work, and if it doesn't we can help (if you write to us). Link to comment Share on other sites More sharing options...
deepee Posted March 8, 2013 Author Share Posted March 8, 2013 (edited) My partner has been through this with you Tomer but it was not resolved. We eventually disabled your module and gave up. This is the reason I was looking for other suggestions as to how other people are handling 301s I tried re-installing your original module again a few minutes ago. It tells me it's installed correctly. In "Preferences" with "Automatically redirect to Canonical URL" set to "yes", an error is thrown after browsing a few products: "The page isn't redirecting properly. Firefox has detected that the server is redirecting the request for this address in a way that will never complete." If I then disable Cononical URL I can browse products and categories o.k. until I try to place an order. From the Shopping Cart Summary page, as soon as I click "Next" I get : "Server not found. Firefox can't find the server at mysite.com.au%2forder%3fstep%3d1%26multi-shipping%3d0." Switch your module off, re-instate Canonical URL's and everything returns to normal. This is exactly the same behaviour as when you were originally corresponding with my partner. Edited March 8, 2013 by deepee (see edit history) 1 Link to comment Share on other sites More sharing options...
gudata Posted June 29, 2013 Share Posted June 29, 2013 If you can't do it from the presta you can aways put the redirects directly in your webserver config. Link to comment Share on other sites More sharing options...
breda_Mcg Posted September 28, 2013 Share Posted September 28, 2013 Hi Deepee, Did you get this problem resolved? Did you find a module that worked for you? Thanks, Breda Link to comment Share on other sites More sharing options...
El Patron Posted September 28, 2013 Share Posted September 28, 2013 updating 'around' the PrestaShop .htaccess generation to handle such things as 301 redirects is very easy. learn more here Link to comment Share on other sites More sharing options...
Recommended Posts