Request Path for Specified Store already exists during Indexing
In magento 1.9
, whenever I save any configurable product in admin panel, all the product urls
goes to 404
unless I do reindexing
.
In reindexing
there are 8 processes, 7 of which works fine but the 8th one Vendor Product Url Rewrite get stuck with
Reindexing Required
And the error I get is
Request Path for Specified Store already exists during Indexing
This error also gets fixed once I empty the table "core url rewrite
" and reindex
it.
Note: I have using VES
vendor extension which is creating "Vendor Product Url Rewrite" process for indexing.
Can Anyone help me with this situation?
magento-1.9 php
bumped to the homepage by Community♦ 35 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
In magento 1.9
, whenever I save any configurable product in admin panel, all the product urls
goes to 404
unless I do reindexing
.
In reindexing
there are 8 processes, 7 of which works fine but the 8th one Vendor Product Url Rewrite get stuck with
Reindexing Required
And the error I get is
Request Path for Specified Store already exists during Indexing
This error also gets fixed once I empty the table "core url rewrite
" and reindex
it.
Note: I have using VES
vendor extension which is creating "Vendor Product Url Rewrite" process for indexing.
Can Anyone help me with this situation?
magento-1.9 php
bumped to the homepage by Community♦ 35 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
In magento 1.9
, whenever I save any configurable product in admin panel, all the product urls
goes to 404
unless I do reindexing
.
In reindexing
there are 8 processes, 7 of which works fine but the 8th one Vendor Product Url Rewrite get stuck with
Reindexing Required
And the error I get is
Request Path for Specified Store already exists during Indexing
This error also gets fixed once I empty the table "core url rewrite
" and reindex
it.
Note: I have using VES
vendor extension which is creating "Vendor Product Url Rewrite" process for indexing.
Can Anyone help me with this situation?
magento-1.9 php
In magento 1.9
, whenever I save any configurable product in admin panel, all the product urls
goes to 404
unless I do reindexing
.
In reindexing
there are 8 processes, 7 of which works fine but the 8th one Vendor Product Url Rewrite get stuck with
Reindexing Required
And the error I get is
Request Path for Specified Store already exists during Indexing
This error also gets fixed once I empty the table "core url rewrite
" and reindex
it.
Note: I have using VES
vendor extension which is creating "Vendor Product Url Rewrite" process for indexing.
Can Anyone help me with this situation?
magento-1.9 php
magento-1.9 php
edited Sep 22 '17 at 10:32
Roushan Choudhary
asked Sep 22 '17 at 9:58
Roushan ChoudharyRoushan Choudhary
14
14
bumped to the homepage by Community♦ 35 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 35 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
In VES vendor extension, after reindexing, it creates its own request URL for that product. VES vendor extension added its key which is saved in
"Mage::getStoreConfig('vendors/vendor_page/url_key')"
i.e. in VES configuration (admin) -> Vendor Page -> URL Key
and also it added vendor id for that specific product.
So product URL becomes for e.g:
http://local.example.com/shop/MV0011/test-product.html
where "shop" is the URL key which is saved in VES configuration and
"MV0011" is the vendor id of that product. If we hit such URL it will show 404.
Please find the below file path.
app/code/community/VES/VendorsPage/Model/Resource/Product.php
All the code is written in processUrlRewrite()
function.
Also, one more problem related to that is if we make any changes in admin for a product and saved, it will again create above product URL which will also redirect to 404.
Below is the file path to prevent such creation of URL.
app/code/community/VES/VendorsPage/Model/Observer.php
Function catalog_product_save_after()
is create such problem.
So either you can comment out the event trigger in config.xml
as
<!-- <catalog_product_save_after>
<observers>
<vendorspage>
<class>vendorspage/observer</class>
<method>catalog_product_save_after</method>
</vendorspage>
</observers>
</catalog_product_save_after> -->
In app/code/community/VES/VendorsPage/etc/config.xml
Hope this will help you to solve this issue.
Thank you.
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%2f194306%2frequest-path-for-specified-store-already-exists-during-indexing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In VES vendor extension, after reindexing, it creates its own request URL for that product. VES vendor extension added its key which is saved in
"Mage::getStoreConfig('vendors/vendor_page/url_key')"
i.e. in VES configuration (admin) -> Vendor Page -> URL Key
and also it added vendor id for that specific product.
So product URL becomes for e.g:
http://local.example.com/shop/MV0011/test-product.html
where "shop" is the URL key which is saved in VES configuration and
"MV0011" is the vendor id of that product. If we hit such URL it will show 404.
Please find the below file path.
app/code/community/VES/VendorsPage/Model/Resource/Product.php
All the code is written in processUrlRewrite()
function.
Also, one more problem related to that is if we make any changes in admin for a product and saved, it will again create above product URL which will also redirect to 404.
Below is the file path to prevent such creation of URL.
app/code/community/VES/VendorsPage/Model/Observer.php
Function catalog_product_save_after()
is create such problem.
So either you can comment out the event trigger in config.xml
as
<!-- <catalog_product_save_after>
<observers>
<vendorspage>
<class>vendorspage/observer</class>
<method>catalog_product_save_after</method>
</vendorspage>
</observers>
</catalog_product_save_after> -->
In app/code/community/VES/VendorsPage/etc/config.xml
Hope this will help you to solve this issue.
Thank you.
add a comment |
In VES vendor extension, after reindexing, it creates its own request URL for that product. VES vendor extension added its key which is saved in
"Mage::getStoreConfig('vendors/vendor_page/url_key')"
i.e. in VES configuration (admin) -> Vendor Page -> URL Key
and also it added vendor id for that specific product.
So product URL becomes for e.g:
http://local.example.com/shop/MV0011/test-product.html
where "shop" is the URL key which is saved in VES configuration and
"MV0011" is the vendor id of that product. If we hit such URL it will show 404.
Please find the below file path.
app/code/community/VES/VendorsPage/Model/Resource/Product.php
All the code is written in processUrlRewrite()
function.
Also, one more problem related to that is if we make any changes in admin for a product and saved, it will again create above product URL which will also redirect to 404.
Below is the file path to prevent such creation of URL.
app/code/community/VES/VendorsPage/Model/Observer.php
Function catalog_product_save_after()
is create such problem.
So either you can comment out the event trigger in config.xml
as
<!-- <catalog_product_save_after>
<observers>
<vendorspage>
<class>vendorspage/observer</class>
<method>catalog_product_save_after</method>
</vendorspage>
</observers>
</catalog_product_save_after> -->
In app/code/community/VES/VendorsPage/etc/config.xml
Hope this will help you to solve this issue.
Thank you.
add a comment |
In VES vendor extension, after reindexing, it creates its own request URL for that product. VES vendor extension added its key which is saved in
"Mage::getStoreConfig('vendors/vendor_page/url_key')"
i.e. in VES configuration (admin) -> Vendor Page -> URL Key
and also it added vendor id for that specific product.
So product URL becomes for e.g:
http://local.example.com/shop/MV0011/test-product.html
where "shop" is the URL key which is saved in VES configuration and
"MV0011" is the vendor id of that product. If we hit such URL it will show 404.
Please find the below file path.
app/code/community/VES/VendorsPage/Model/Resource/Product.php
All the code is written in processUrlRewrite()
function.
Also, one more problem related to that is if we make any changes in admin for a product and saved, it will again create above product URL which will also redirect to 404.
Below is the file path to prevent such creation of URL.
app/code/community/VES/VendorsPage/Model/Observer.php
Function catalog_product_save_after()
is create such problem.
So either you can comment out the event trigger in config.xml
as
<!-- <catalog_product_save_after>
<observers>
<vendorspage>
<class>vendorspage/observer</class>
<method>catalog_product_save_after</method>
</vendorspage>
</observers>
</catalog_product_save_after> -->
In app/code/community/VES/VendorsPage/etc/config.xml
Hope this will help you to solve this issue.
Thank you.
In VES vendor extension, after reindexing, it creates its own request URL for that product. VES vendor extension added its key which is saved in
"Mage::getStoreConfig('vendors/vendor_page/url_key')"
i.e. in VES configuration (admin) -> Vendor Page -> URL Key
and also it added vendor id for that specific product.
So product URL becomes for e.g:
http://local.example.com/shop/MV0011/test-product.html
where "shop" is the URL key which is saved in VES configuration and
"MV0011" is the vendor id of that product. If we hit such URL it will show 404.
Please find the below file path.
app/code/community/VES/VendorsPage/Model/Resource/Product.php
All the code is written in processUrlRewrite()
function.
Also, one more problem related to that is if we make any changes in admin for a product and saved, it will again create above product URL which will also redirect to 404.
Below is the file path to prevent such creation of URL.
app/code/community/VES/VendorsPage/Model/Observer.php
Function catalog_product_save_after()
is create such problem.
So either you can comment out the event trigger in config.xml
as
<!-- <catalog_product_save_after>
<observers>
<vendorspage>
<class>vendorspage/observer</class>
<method>catalog_product_save_after</method>
</vendorspage>
</observers>
</catalog_product_save_after> -->
In app/code/community/VES/VendorsPage/etc/config.xml
Hope this will help you to solve this issue.
Thank you.
edited Nov 14 '17 at 11:26
ABHISHEK TRIPATHI
1,6881626
1,6881626
answered Nov 14 '17 at 11:08
user60793user60793
1
1
add a comment |
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%2f194306%2frequest-path-for-specified-store-already-exists-during-indexing%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