Magento - 2.2.6 Possible Problems? Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Magento 2.2.6 Cannot create a symlink for… after UpdateMagento 2.2.6 - Attribute with ID “Manufacturer” does not existMagento 2.2.6 upgradation error?Magento 2.2.6 Web Setup Wizard missingMagento 2.2.6 bin/magento catalog:image:resize taking so much timeCurrency is not changing in magento 2.2.6magento 2.2.6 Indexer:reindex errorHow to enable extension in magento 2.2.6?Improving server response times for magento 2.2.6Magento 2.2.6 Checkout issueMagento - 2.3.1 Possible Problems?
Selecting the same column from Different rows Based on Different Criteria
In predicate logic, does existential quantification (∃) include universal quantification (∀), i.e. can 'some' imply 'all'?
Why do people hide their license plates in the EU?
Using audio cues to encourage good posture
Generate an RGB colour grid
Resolving to minmaj7
porting install scripts : can rpm replace apt?
2001: A Space Odyssey's use of the song "Daisy Bell" (Bicycle Built for Two); life imitates art or vice-versa?
Why aren't air breathing engines used as small first stages
Is the Standard Deduction better than Itemized when both are the same amount?
Bete Noir -- no dairy
ListPlot join points by nearest neighbor rather than order
Should I discuss the type of campaign with my players?
Why are Kinder Surprise Eggs illegal in the USA?
What does an IRS interview request entail when called in to verify expenses for a sole proprietor small business?
At the end of Thor: Ragnarok why don't the Asgardians turn and head for the Bifrost as per their original plan?
List *all* the tuples!
Should I use a zero-interest credit card for a large one-time purchase?
What's the meaning of 間時肆拾貳 at a car parking sign
51k Euros annually for a family of 4 in Berlin: Is it enough?
Sci-Fi book where patients in a coma ward all live in a subconscious world linked together
Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?
A coin, having probability p of landing heads and probability of q=(1-p) of landing on heads.
Using et al. for a last / senior author rather than for a first author
Magento - 2.2.6 Possible Problems?
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Magento 2.2.6 Cannot create a symlink for… after UpdateMagento 2.2.6 - Attribute with ID “Manufacturer” does not existMagento 2.2.6 upgradation error?Magento 2.2.6 Web Setup Wizard missingMagento 2.2.6 bin/magento catalog:image:resize taking so much timeCurrency is not changing in magento 2.2.6magento 2.2.6 Indexer:reindex errorHow to enable extension in magento 2.2.6?Improving server response times for magento 2.2.6Magento 2.2.6 Checkout issueMagento - 2.3.1 Possible Problems?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Magento was released Magento-2.2.6 version on 18th Sep, 2018.
This release includes :
- 25 critical enhancements to product security, over 150 core code fixes and enhancements, and over 350 community-submitted pull requests.
- Although this release includes these security enhancements, no confirmed attacks related to these issues have occurred to date.
- However, certain vulnerabilities can potentially be exploited to access customer information or take over administrator sessions, so we recommend that you upgrade your Magento software to the latest version as soon as possible.
The Magento is recommending to upgrade our Magento software to the latest version ASAP.
What are the Possible Issues with this Magento-2.2.6 release?
discussion magento2.2.6
bumped to the homepage by Community♦ 5 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 |
Magento was released Magento-2.2.6 version on 18th Sep, 2018.
This release includes :
- 25 critical enhancements to product security, over 150 core code fixes and enhancements, and over 350 community-submitted pull requests.
- Although this release includes these security enhancements, no confirmed attacks related to these issues have occurred to date.
- However, certain vulnerabilities can potentially be exploited to access customer information or take over administrator sessions, so we recommend that you upgrade your Magento software to the latest version as soon as possible.
The Magento is recommending to upgrade our Magento software to the latest version ASAP.
What are the Possible Issues with this Magento-2.2.6 release?
discussion magento2.2.6
bumped to the homepage by Community♦ 5 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 |
Magento was released Magento-2.2.6 version on 18th Sep, 2018.
This release includes :
- 25 critical enhancements to product security, over 150 core code fixes and enhancements, and over 350 community-submitted pull requests.
- Although this release includes these security enhancements, no confirmed attacks related to these issues have occurred to date.
- However, certain vulnerabilities can potentially be exploited to access customer information or take over administrator sessions, so we recommend that you upgrade your Magento software to the latest version as soon as possible.
The Magento is recommending to upgrade our Magento software to the latest version ASAP.
What are the Possible Issues with this Magento-2.2.6 release?
discussion magento2.2.6
Magento was released Magento-2.2.6 version on 18th Sep, 2018.
This release includes :
- 25 critical enhancements to product security, over 150 core code fixes and enhancements, and over 350 community-submitted pull requests.
- Although this release includes these security enhancements, no confirmed attacks related to these issues have occurred to date.
- However, certain vulnerabilities can potentially be exploited to access customer information or take over administrator sessions, so we recommend that you upgrade your Magento software to the latest version as soon as possible.
The Magento is recommending to upgrade our Magento software to the latest version ASAP.
What are the Possible Issues with this Magento-2.2.6 release?
discussion magento2.2.6
discussion magento2.2.6
edited Oct 17 '18 at 7:23
Teja Bhagavan Kollepara
asked Sep 19 '18 at 7:20
Teja Bhagavan KolleparaTeja Bhagavan Kollepara
2,99341949
2,99341949
bumped to the homepage by Community♦ 5 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♦ 5 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 |
2 Answers
2
active
oldest
votes
If you use custom attributes and use those attributes to create widget rules, most of the widgets I used, caused errors and had to be removed.
In my case, it seemed that some of the attributes being called were having errors with 'back-ticks' replacing single quotes ' with back-ticks when rendering the page.
I deleted the widgets using those attributes and the page loads without issue.
I also need to re-write some of the cart and catalog rules as well, again, due to the back-tick issue.
1 major issue I am having,
"Remove pub/media/catalog/product/cache . (Removing this folder frees up space.) & Run bin/magento catalog:image:resize to generate a new image cache. (This step is necessary because we’ve changed the path to cached images and must remove the previously cached images.)"
Removing the 'pub/media/catalog/product/cache' isn't a problem, but the 'bin/magento catalog:image:resize' is just creating new images inside of the folder I just removed. It said there would be a new path, but that doesn't seem to be the case so far, unless I'm missing something. But do plan on the image resize to take a LONG time. 22 minutes so far and less than 500 images processed.
add a comment |
I've encountered 2 problems regarding price reindexing. One problem is that configurable price indexer (and probably other complex products too but I have no production project who uses bundles and grouped products extensively) relies on its child product index to be properly executed. Configurable price indexer works in 2 step:
- build index data based on configurable product price which is null as magento does not allow you to set price on configurable price level
- update min and max columns in
catalog_product_index_price
table based on children data from the same table
The first bug I found was that reindexList
method which is fired by scheduled reindex reindexed the given list by product type which was sorted based on ids provided. If the lowest id in the list was simple then all simples were reindexed before configurables, if it was configurable then configurables before simples.
The second bug relied on the fact that in the first step of the configurable price reindex proces table catalog_product_index_price
was updated based on a query which created where
part as where e.entity_id BEETWEEN ? and ?
and values where min and max ids from the provided list. This resulted in index table being updated for all configurables form the range based on its data and in most cases all price column were set to 0. In the second step, where indexer should update min and max price based on children query was executed with where
part like where le.entity_id IN (?)
, so only for the configurables provided to the reindexList
method making all other in the base state.
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%2f242801%2fmagento-2-2-6-possible-problems%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you use custom attributes and use those attributes to create widget rules, most of the widgets I used, caused errors and had to be removed.
In my case, it seemed that some of the attributes being called were having errors with 'back-ticks' replacing single quotes ' with back-ticks when rendering the page.
I deleted the widgets using those attributes and the page loads without issue.
I also need to re-write some of the cart and catalog rules as well, again, due to the back-tick issue.
1 major issue I am having,
"Remove pub/media/catalog/product/cache . (Removing this folder frees up space.) & Run bin/magento catalog:image:resize to generate a new image cache. (This step is necessary because we’ve changed the path to cached images and must remove the previously cached images.)"
Removing the 'pub/media/catalog/product/cache' isn't a problem, but the 'bin/magento catalog:image:resize' is just creating new images inside of the folder I just removed. It said there would be a new path, but that doesn't seem to be the case so far, unless I'm missing something. But do plan on the image resize to take a LONG time. 22 minutes so far and less than 500 images processed.
add a comment |
If you use custom attributes and use those attributes to create widget rules, most of the widgets I used, caused errors and had to be removed.
In my case, it seemed that some of the attributes being called were having errors with 'back-ticks' replacing single quotes ' with back-ticks when rendering the page.
I deleted the widgets using those attributes and the page loads without issue.
I also need to re-write some of the cart and catalog rules as well, again, due to the back-tick issue.
1 major issue I am having,
"Remove pub/media/catalog/product/cache . (Removing this folder frees up space.) & Run bin/magento catalog:image:resize to generate a new image cache. (This step is necessary because we’ve changed the path to cached images and must remove the previously cached images.)"
Removing the 'pub/media/catalog/product/cache' isn't a problem, but the 'bin/magento catalog:image:resize' is just creating new images inside of the folder I just removed. It said there would be a new path, but that doesn't seem to be the case so far, unless I'm missing something. But do plan on the image resize to take a LONG time. 22 minutes so far and less than 500 images processed.
add a comment |
If you use custom attributes and use those attributes to create widget rules, most of the widgets I used, caused errors and had to be removed.
In my case, it seemed that some of the attributes being called were having errors with 'back-ticks' replacing single quotes ' with back-ticks when rendering the page.
I deleted the widgets using those attributes and the page loads without issue.
I also need to re-write some of the cart and catalog rules as well, again, due to the back-tick issue.
1 major issue I am having,
"Remove pub/media/catalog/product/cache . (Removing this folder frees up space.) & Run bin/magento catalog:image:resize to generate a new image cache. (This step is necessary because we’ve changed the path to cached images and must remove the previously cached images.)"
Removing the 'pub/media/catalog/product/cache' isn't a problem, but the 'bin/magento catalog:image:resize' is just creating new images inside of the folder I just removed. It said there would be a new path, but that doesn't seem to be the case so far, unless I'm missing something. But do plan on the image resize to take a LONG time. 22 minutes so far and less than 500 images processed.
If you use custom attributes and use those attributes to create widget rules, most of the widgets I used, caused errors and had to be removed.
In my case, it seemed that some of the attributes being called were having errors with 'back-ticks' replacing single quotes ' with back-ticks when rendering the page.
I deleted the widgets using those attributes and the page loads without issue.
I also need to re-write some of the cart and catalog rules as well, again, due to the back-tick issue.
1 major issue I am having,
"Remove pub/media/catalog/product/cache . (Removing this folder frees up space.) & Run bin/magento catalog:image:resize to generate a new image cache. (This step is necessary because we’ve changed the path to cached images and must remove the previously cached images.)"
Removing the 'pub/media/catalog/product/cache' isn't a problem, but the 'bin/magento catalog:image:resize' is just creating new images inside of the folder I just removed. It said there would be a new path, but that doesn't seem to be the case so far, unless I'm missing something. But do plan on the image resize to take a LONG time. 22 minutes so far and less than 500 images processed.
answered Sep 19 '18 at 19:38
dawhoodawhoo
521322
521322
add a comment |
add a comment |
I've encountered 2 problems regarding price reindexing. One problem is that configurable price indexer (and probably other complex products too but I have no production project who uses bundles and grouped products extensively) relies on its child product index to be properly executed. Configurable price indexer works in 2 step:
- build index data based on configurable product price which is null as magento does not allow you to set price on configurable price level
- update min and max columns in
catalog_product_index_price
table based on children data from the same table
The first bug I found was that reindexList
method which is fired by scheduled reindex reindexed the given list by product type which was sorted based on ids provided. If the lowest id in the list was simple then all simples were reindexed before configurables, if it was configurable then configurables before simples.
The second bug relied on the fact that in the first step of the configurable price reindex proces table catalog_product_index_price
was updated based on a query which created where
part as where e.entity_id BEETWEEN ? and ?
and values where min and max ids from the provided list. This resulted in index table being updated for all configurables form the range based on its data and in most cases all price column were set to 0. In the second step, where indexer should update min and max price based on children query was executed with where
part like where le.entity_id IN (?)
, so only for the configurables provided to the reindexList
method making all other in the base state.
add a comment |
I've encountered 2 problems regarding price reindexing. One problem is that configurable price indexer (and probably other complex products too but I have no production project who uses bundles and grouped products extensively) relies on its child product index to be properly executed. Configurable price indexer works in 2 step:
- build index data based on configurable product price which is null as magento does not allow you to set price on configurable price level
- update min and max columns in
catalog_product_index_price
table based on children data from the same table
The first bug I found was that reindexList
method which is fired by scheduled reindex reindexed the given list by product type which was sorted based on ids provided. If the lowest id in the list was simple then all simples were reindexed before configurables, if it was configurable then configurables before simples.
The second bug relied on the fact that in the first step of the configurable price reindex proces table catalog_product_index_price
was updated based on a query which created where
part as where e.entity_id BEETWEEN ? and ?
and values where min and max ids from the provided list. This resulted in index table being updated for all configurables form the range based on its data and in most cases all price column were set to 0. In the second step, where indexer should update min and max price based on children query was executed with where
part like where le.entity_id IN (?)
, so only for the configurables provided to the reindexList
method making all other in the base state.
add a comment |
I've encountered 2 problems regarding price reindexing. One problem is that configurable price indexer (and probably other complex products too but I have no production project who uses bundles and grouped products extensively) relies on its child product index to be properly executed. Configurable price indexer works in 2 step:
- build index data based on configurable product price which is null as magento does not allow you to set price on configurable price level
- update min and max columns in
catalog_product_index_price
table based on children data from the same table
The first bug I found was that reindexList
method which is fired by scheduled reindex reindexed the given list by product type which was sorted based on ids provided. If the lowest id in the list was simple then all simples were reindexed before configurables, if it was configurable then configurables before simples.
The second bug relied on the fact that in the first step of the configurable price reindex proces table catalog_product_index_price
was updated based on a query which created where
part as where e.entity_id BEETWEEN ? and ?
and values where min and max ids from the provided list. This resulted in index table being updated for all configurables form the range based on its data and in most cases all price column were set to 0. In the second step, where indexer should update min and max price based on children query was executed with where
part like where le.entity_id IN (?)
, so only for the configurables provided to the reindexList
method making all other in the base state.
I've encountered 2 problems regarding price reindexing. One problem is that configurable price indexer (and probably other complex products too but I have no production project who uses bundles and grouped products extensively) relies on its child product index to be properly executed. Configurable price indexer works in 2 step:
- build index data based on configurable product price which is null as magento does not allow you to set price on configurable price level
- update min and max columns in
catalog_product_index_price
table based on children data from the same table
The first bug I found was that reindexList
method which is fired by scheduled reindex reindexed the given list by product type which was sorted based on ids provided. If the lowest id in the list was simple then all simples were reindexed before configurables, if it was configurable then configurables before simples.
The second bug relied on the fact that in the first step of the configurable price reindex proces table catalog_product_index_price
was updated based on a query which created where
part as where e.entity_id BEETWEEN ? and ?
and values where min and max ids from the provided list. This resulted in index table being updated for all configurables form the range based on its data and in most cases all price column were set to 0. In the second step, where indexer should update min and max price based on children query was executed with where
part like where le.entity_id IN (?)
, so only for the configurables provided to the reindexList
method making all other in the base state.
answered Oct 3 '18 at 8:13
ZefirynZefiryn
4,63321728
4,63321728
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%2f242801%2fmagento-2-2-6-possible-problems%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