Can I Delete The Thousands Of URL Rewrites? Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Magento core_url_rewrite table excessively largehow do i delete urls of other stores in magento?Store code in URL for every store view except for defaultMagento Redirects to Old Website regardless of what changes are made!Redirecting URLs when switching over from VolusionHow to access subcategory without having url-key of the parent category in the url?htaccess rewrites domain redirectsHow can i fix the url of magento?What Happens to Redirects if Product Deleted in MagentoKeep query string in urlMagento 1.9.1 - Unable to edit (click) URL Rewrite fields in backendMagento URL rewrite from SEO friendly URL's to new store
How do I deal with an erroneously large refund?
Why did Bronn offer to be Tyrion Lannister's champion in trial by combat?
Why do people think Winterfell crypts is the safest place for women, children & old people?
Can gravitational waves pass through a black hole?
Can this water damage be explained by lack of gutters and grading issues?
Compiling and throwing simple dynamic exceptions at runtime for JVM
Protagonist's race is hidden - should I reveal it?
Short story about an alien named Ushtu(?) coming from a future Earth, when ours was destroyed by a nuclear explosion
Can I ask an author to send me his ebook?
Putting Ant-Man on house arrest
What is the definining line between a helicopter and a drone a person can ride in?
Determine the generator of an ideal of ring of integers
Does GDPR cover the collection of data by websites that crawl the web and resell user data
2 sample t test for sample sizes - 30,000 and 150,000
How to ask rejected full-time candidates to apply to teach individual courses?
Does traveling In The United States require a passport or can I use my green card if not a US citizen?
Does Prince Arnaud cause someone holding the Princess to lose?
Network questions
false 'Security alert' from Google - every login generates mails from 'no-reply@accounts.google.com'
How to get a single big right brace?
Marquee sign letters
Married in secret, can marital status in passport be changed at a later date?
Why not use the yoke to control yaw, as well as pitch and roll?
Can I take recommendation from someone I met at a conference?
Can I Delete The Thousands Of URL Rewrites?
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Magento core_url_rewrite table excessively largehow do i delete urls of other stores in magento?Store code in URL for every store view except for defaultMagento Redirects to Old Website regardless of what changes are made!Redirecting URLs when switching over from VolusionHow to access subcategory without having url-key of the parent category in the url?htaccess rewrites domain redirectsHow can i fix the url of magento?What Happens to Redirects if Product Deleted in MagentoKeep query string in urlMagento 1.9.1 - Unable to edit (click) URL Rewrite fields in backendMagento URL rewrite from SEO friendly URL's to new store
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am wanting to add redirects from old site URL to new site URLs however when I go into URL Rewrite Management there are over 8,000 records there already. Can I delete these?
Most of them are in the following format:
ID Path: product/1483
Request Path: brilliant-whisper-300-1483.html
Target Path: catalog/product/view/id/1483
I'm hesitant about deleting them if they are necessary...
magento-1 redirect
add a comment |
I am wanting to add redirects from old site URL to new site URLs however when I go into URL Rewrite Management there are over 8,000 records there already. Can I delete these?
Most of them are in the following format:
ID Path: product/1483
Request Path: brilliant-whisper-300-1483.html
Target Path: catalog/product/view/id/1483
I'm hesitant about deleting them if they are necessary...
magento-1 redirect
add a comment |
I am wanting to add redirects from old site URL to new site URLs however when I go into URL Rewrite Management there are over 8,000 records there already. Can I delete these?
Most of them are in the following format:
ID Path: product/1483
Request Path: brilliant-whisper-300-1483.html
Target Path: catalog/product/view/id/1483
I'm hesitant about deleting them if they are necessary...
magento-1 redirect
I am wanting to add redirects from old site URL to new site URLs however when I go into URL Rewrite Management there are over 8,000 records there already. Can I delete these?
Most of them are in the following format:
ID Path: product/1483
Request Path: brilliant-whisper-300-1483.html
Target Path: catalog/product/view/id/1483
I'm hesitant about deleting them if they are necessary...
magento-1 redirect
magento-1 redirect
edited Apr 18 at 7:04
Teja Bhagavan Kollepara
2,99241949
2,99241949
asked Sep 4 '14 at 0:50
emmaemma
16112
16112
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
The answer is - as always - it depends :)
In general, you can truncate (not delete!) the table core_url_rewrite. If it is empty, your SEO URLs like brilliant-whisper-300-1483.html will not work for the time being. But if you do a full reindex of the catalog URL rewrites, these URLs will be generated again, so that your SEO URLs should work again.
If you struggle with a very big core_url_rewrite table, then have a look at this Magento StackExchange question.
What can cause problems is if you did one of the following:
- You changed the URL key of a catalog/product and ticked the box
Create Permanent Redirect for old URL. Assumed you changed the URL key frommy-old-product-nametomy-new-product-name. Then, when this box is ticked, a rewrite frommy-old-product-name.htmltomy-new-product-name.htmlwill be created in thecore_url_rewritetable. If you truncate the table, this rewrite will be gone, so that your old product URL will not work any more. - You created custom URL rewrites under
Catalog - URL Rewrite Management. These custom URL rewrites will also be gone if you truncatecore_url_rewrite.
Thank you for giving a more objective answer. If you're worried about 301 redirects for pages whose URL keys have been changed after Google has indexed the pages and they've been linked to elsewhere, you get a little less cavalier about just blindly truncating this table. Only in 1.7 and 1.8 where there's a category save bug, do you get concerned about "excessive" numbers of entries. SUPEE-389_EE_1.12.0.2_v1.patch
– Fiasco Labs
Sep 5 '14 at 2:47
add a comment |
for me with 1.9.2 this does a temporary fix. Simons link is more permanent..check it out.
So instead of truncating all of the data, especially if your custom urls are THE most important function of the core rewrites, you can query the database to omit custom url rewites and to show only the system url rewites. Then you can delete your system url rewrites. However, this will cause problems IF you still NEED your old urls, you will lose your old URL's this way.
Some people do not need the old url's. Its a quick dirty way to clean that rewrite table.
as always export backups FIRST.
add a comment |
Truncate core_rewrite table after doing a backup of that table. That should do the job.
And after you do that, have him tell you how to get the ones you need back... They're there for a reason and SEO friendly URLs require them. You may be fixing a conceived problem by creating a real problem.
– Fiasco Labs
Sep 4 '14 at 2:46
@FiascoLabs you can regenerate the required rows executing "reindex".
– lrkwz
May 22 '15 at 8:00
Not the ones you hand entered...
– Fiasco Labs
May 22 '15 at 14:25
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "479"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f34643%2fcan-i-delete-the-thousands-of-url-rewrites%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
The answer is - as always - it depends :)
In general, you can truncate (not delete!) the table core_url_rewrite. If it is empty, your SEO URLs like brilliant-whisper-300-1483.html will not work for the time being. But if you do a full reindex of the catalog URL rewrites, these URLs will be generated again, so that your SEO URLs should work again.
If you struggle with a very big core_url_rewrite table, then have a look at this Magento StackExchange question.
What can cause problems is if you did one of the following:
- You changed the URL key of a catalog/product and ticked the box
Create Permanent Redirect for old URL. Assumed you changed the URL key frommy-old-product-nametomy-new-product-name. Then, when this box is ticked, a rewrite frommy-old-product-name.htmltomy-new-product-name.htmlwill be created in thecore_url_rewritetable. If you truncate the table, this rewrite will be gone, so that your old product URL will not work any more. - You created custom URL rewrites under
Catalog - URL Rewrite Management. These custom URL rewrites will also be gone if you truncatecore_url_rewrite.
Thank you for giving a more objective answer. If you're worried about 301 redirects for pages whose URL keys have been changed after Google has indexed the pages and they've been linked to elsewhere, you get a little less cavalier about just blindly truncating this table. Only in 1.7 and 1.8 where there's a category save bug, do you get concerned about "excessive" numbers of entries. SUPEE-389_EE_1.12.0.2_v1.patch
– Fiasco Labs
Sep 5 '14 at 2:47
add a comment |
The answer is - as always - it depends :)
In general, you can truncate (not delete!) the table core_url_rewrite. If it is empty, your SEO URLs like brilliant-whisper-300-1483.html will not work for the time being. But if you do a full reindex of the catalog URL rewrites, these URLs will be generated again, so that your SEO URLs should work again.
If you struggle with a very big core_url_rewrite table, then have a look at this Magento StackExchange question.
What can cause problems is if you did one of the following:
- You changed the URL key of a catalog/product and ticked the box
Create Permanent Redirect for old URL. Assumed you changed the URL key frommy-old-product-nametomy-new-product-name. Then, when this box is ticked, a rewrite frommy-old-product-name.htmltomy-new-product-name.htmlwill be created in thecore_url_rewritetable. If you truncate the table, this rewrite will be gone, so that your old product URL will not work any more. - You created custom URL rewrites under
Catalog - URL Rewrite Management. These custom URL rewrites will also be gone if you truncatecore_url_rewrite.
Thank you for giving a more objective answer. If you're worried about 301 redirects for pages whose URL keys have been changed after Google has indexed the pages and they've been linked to elsewhere, you get a little less cavalier about just blindly truncating this table. Only in 1.7 and 1.8 where there's a category save bug, do you get concerned about "excessive" numbers of entries. SUPEE-389_EE_1.12.0.2_v1.patch
– Fiasco Labs
Sep 5 '14 at 2:47
add a comment |
The answer is - as always - it depends :)
In general, you can truncate (not delete!) the table core_url_rewrite. If it is empty, your SEO URLs like brilliant-whisper-300-1483.html will not work for the time being. But if you do a full reindex of the catalog URL rewrites, these URLs will be generated again, so that your SEO URLs should work again.
If you struggle with a very big core_url_rewrite table, then have a look at this Magento StackExchange question.
What can cause problems is if you did one of the following:
- You changed the URL key of a catalog/product and ticked the box
Create Permanent Redirect for old URL. Assumed you changed the URL key frommy-old-product-nametomy-new-product-name. Then, when this box is ticked, a rewrite frommy-old-product-name.htmltomy-new-product-name.htmlwill be created in thecore_url_rewritetable. If you truncate the table, this rewrite will be gone, so that your old product URL will not work any more. - You created custom URL rewrites under
Catalog - URL Rewrite Management. These custom URL rewrites will also be gone if you truncatecore_url_rewrite.
The answer is - as always - it depends :)
In general, you can truncate (not delete!) the table core_url_rewrite. If it is empty, your SEO URLs like brilliant-whisper-300-1483.html will not work for the time being. But if you do a full reindex of the catalog URL rewrites, these URLs will be generated again, so that your SEO URLs should work again.
If you struggle with a very big core_url_rewrite table, then have a look at this Magento StackExchange question.
What can cause problems is if you did one of the following:
- You changed the URL key of a catalog/product and ticked the box
Create Permanent Redirect for old URL. Assumed you changed the URL key frommy-old-product-nametomy-new-product-name. Then, when this box is ticked, a rewrite frommy-old-product-name.htmltomy-new-product-name.htmlwill be created in thecore_url_rewritetable. If you truncate the table, this rewrite will be gone, so that your old product URL will not work any more. - You created custom URL rewrites under
Catalog - URL Rewrite Management. These custom URL rewrites will also be gone if you truncatecore_url_rewrite.
edited Apr 13 '17 at 12:54
Community♦
1
1
answered Sep 4 '14 at 6:05
SimonSimon
4,63911960
4,63911960
Thank you for giving a more objective answer. If you're worried about 301 redirects for pages whose URL keys have been changed after Google has indexed the pages and they've been linked to elsewhere, you get a little less cavalier about just blindly truncating this table. Only in 1.7 and 1.8 where there's a category save bug, do you get concerned about "excessive" numbers of entries. SUPEE-389_EE_1.12.0.2_v1.patch
– Fiasco Labs
Sep 5 '14 at 2:47
add a comment |
Thank you for giving a more objective answer. If you're worried about 301 redirects for pages whose URL keys have been changed after Google has indexed the pages and they've been linked to elsewhere, you get a little less cavalier about just blindly truncating this table. Only in 1.7 and 1.8 where there's a category save bug, do you get concerned about "excessive" numbers of entries. SUPEE-389_EE_1.12.0.2_v1.patch
– Fiasco Labs
Sep 5 '14 at 2:47
Thank you for giving a more objective answer. If you're worried about 301 redirects for pages whose URL keys have been changed after Google has indexed the pages and they've been linked to elsewhere, you get a little less cavalier about just blindly truncating this table. Only in 1.7 and 1.8 where there's a category save bug, do you get concerned about "excessive" numbers of entries. SUPEE-389_EE_1.12.0.2_v1.patch
– Fiasco Labs
Sep 5 '14 at 2:47
Thank you for giving a more objective answer. If you're worried about 301 redirects for pages whose URL keys have been changed after Google has indexed the pages and they've been linked to elsewhere, you get a little less cavalier about just blindly truncating this table. Only in 1.7 and 1.8 where there's a category save bug, do you get concerned about "excessive" numbers of entries. SUPEE-389_EE_1.12.0.2_v1.patch
– Fiasco Labs
Sep 5 '14 at 2:47
add a comment |
for me with 1.9.2 this does a temporary fix. Simons link is more permanent..check it out.
So instead of truncating all of the data, especially if your custom urls are THE most important function of the core rewrites, you can query the database to omit custom url rewites and to show only the system url rewites. Then you can delete your system url rewrites. However, this will cause problems IF you still NEED your old urls, you will lose your old URL's this way.
Some people do not need the old url's. Its a quick dirty way to clean that rewrite table.
as always export backups FIRST.
add a comment |
for me with 1.9.2 this does a temporary fix. Simons link is more permanent..check it out.
So instead of truncating all of the data, especially if your custom urls are THE most important function of the core rewrites, you can query the database to omit custom url rewites and to show only the system url rewites. Then you can delete your system url rewrites. However, this will cause problems IF you still NEED your old urls, you will lose your old URL's this way.
Some people do not need the old url's. Its a quick dirty way to clean that rewrite table.
as always export backups FIRST.
add a comment |
for me with 1.9.2 this does a temporary fix. Simons link is more permanent..check it out.
So instead of truncating all of the data, especially if your custom urls are THE most important function of the core rewrites, you can query the database to omit custom url rewites and to show only the system url rewites. Then you can delete your system url rewrites. However, this will cause problems IF you still NEED your old urls, you will lose your old URL's this way.
Some people do not need the old url's. Its a quick dirty way to clean that rewrite table.
as always export backups FIRST.
for me with 1.9.2 this does a temporary fix. Simons link is more permanent..check it out.
So instead of truncating all of the data, especially if your custom urls are THE most important function of the core rewrites, you can query the database to omit custom url rewites and to show only the system url rewites. Then you can delete your system url rewrites. However, this will cause problems IF you still NEED your old urls, you will lose your old URL's this way.
Some people do not need the old url's. Its a quick dirty way to clean that rewrite table.
as always export backups FIRST.
edited Aug 19 '15 at 8:25
Marius♦
168k28324692
168k28324692
answered Aug 19 '15 at 8:05
user26152user26152
415
415
add a comment |
add a comment |
Truncate core_rewrite table after doing a backup of that table. That should do the job.
And after you do that, have him tell you how to get the ones you need back... They're there for a reason and SEO friendly URLs require them. You may be fixing a conceived problem by creating a real problem.
– Fiasco Labs
Sep 4 '14 at 2:46
@FiascoLabs you can regenerate the required rows executing "reindex".
– lrkwz
May 22 '15 at 8:00
Not the ones you hand entered...
– Fiasco Labs
May 22 '15 at 14:25
add a comment |
Truncate core_rewrite table after doing a backup of that table. That should do the job.
And after you do that, have him tell you how to get the ones you need back... They're there for a reason and SEO friendly URLs require them. You may be fixing a conceived problem by creating a real problem.
– Fiasco Labs
Sep 4 '14 at 2:46
@FiascoLabs you can regenerate the required rows executing "reindex".
– lrkwz
May 22 '15 at 8:00
Not the ones you hand entered...
– Fiasco Labs
May 22 '15 at 14:25
add a comment |
Truncate core_rewrite table after doing a backup of that table. That should do the job.
Truncate core_rewrite table after doing a backup of that table. That should do the job.
answered Sep 4 '14 at 1:02
mbalpardambalparda
6,75831644
6,75831644
And after you do that, have him tell you how to get the ones you need back... They're there for a reason and SEO friendly URLs require them. You may be fixing a conceived problem by creating a real problem.
– Fiasco Labs
Sep 4 '14 at 2:46
@FiascoLabs you can regenerate the required rows executing "reindex".
– lrkwz
May 22 '15 at 8:00
Not the ones you hand entered...
– Fiasco Labs
May 22 '15 at 14:25
add a comment |
And after you do that, have him tell you how to get the ones you need back... They're there for a reason and SEO friendly URLs require them. You may be fixing a conceived problem by creating a real problem.
– Fiasco Labs
Sep 4 '14 at 2:46
@FiascoLabs you can regenerate the required rows executing "reindex".
– lrkwz
May 22 '15 at 8:00
Not the ones you hand entered...
– Fiasco Labs
May 22 '15 at 14:25
And after you do that, have him tell you how to get the ones you need back... They're there for a reason and SEO friendly URLs require them. You may be fixing a conceived problem by creating a real problem.
– Fiasco Labs
Sep 4 '14 at 2:46
And after you do that, have him tell you how to get the ones you need back... They're there for a reason and SEO friendly URLs require them. You may be fixing a conceived problem by creating a real problem.
– Fiasco Labs
Sep 4 '14 at 2:46
@FiascoLabs you can regenerate the required rows executing "reindex".
– lrkwz
May 22 '15 at 8:00
@FiascoLabs you can regenerate the required rows executing "reindex".
– lrkwz
May 22 '15 at 8:00
Not the ones you hand entered...
– Fiasco Labs
May 22 '15 at 14:25
Not the ones you hand entered...
– Fiasco Labs
May 22 '15 at 14:25
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f34643%2fcan-i-delete-the-thousands-of-url-rewrites%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown