Magento not using URL rewrites in product display or for incoming links

Question

All the links on my Magento 1.14.2 site are showing up as (literally):

".../catalog/product/view/id/1234/s/my-really-cool-product" instead of ".../my-really-cool-product"

Reindexing seems to build the rewrites in the database, but they don't seem to be acted upon at all. When traffic comes in to the site from ".../my-really-cool-product" it results in a page not found error.

I copied the files of the site to another directory and am using an older version of the database, and the issue does not seem to be replicated, so I'm thinking that the problem lies somewhere in the database, but I haven't been able to find it yet.

Any ideas what might be going on here and how to fix it?

Answer 1

Go to the catalog >> url rewrite and check your SEO friendly url is generated or not. After that check goes to system >> index management and check url rewrite index is in the ready mode not red.

If it is showing red then open ssh and go to the shell folder which is in the magento root directory. Then run below command:

shell>  php indexer.php --reindexall

Remove cache folder rm -rf var/cache Hope this helps you !!!

Answer 2

For Magento 2 run below command in Magento root:

php bin/magento indexer:info

By above command you will know the name and code of each indexer. After that you can execute below command to reindex one or all the indexer:

php bin/magento indexer:reindex <indexer_code>
php bin/magento indexer:reindex 

Dont forget flushing the cache. Thanks in advance.

Answer 3

Although I'm still not sure what caused the rewrites to initially stop working and to stop displaying as the front end product links, I was able to restore the rewrites/redirects and the displayed product links by truncating the enterprise_url_rewrite table in the Magento database.

I used this query:

SET FOREIGN_KEY_CHECKS = 0;
TRUNCATE TABLE `enterprise_url_rewrite`;
SET FOREIGN_KEY_CHECKS = 1;

And subsequently, things started working again as expected.

I had tried this early on after running into this problem, so I'm not sure why doing it a second time a couple of weeks afterwards had the desired effect when truncating the table at the beginning did not, but, in any case, that's what I did to fix it.