Magento 1.9.3.0 product page design is reverted to base/default The Next CEO of Stack OverflowShowing new products in RWD-ThemeHandling grouped product attributesMagento 1.9.2 - Home page in grid format shows wrong number of columns, no add cart buttonDescription on Product page disappears after update to 1.9.2Custom option templates (radio, checkbox, etc) for a single product)Magento 1.9 Product page customizationaddAttributeToSelect() does not work for newly created attributesMagento not saving custom product attributes after version upgradeMagento Product Detail Page doesn't fully load and description and options are missing

Would a galaxy be visible from outside, but nearby?

Received an invoice from my ex-employer billing me for training; how to handle?

Novel about a guy who is possessed by the divine essence and the world ends?

Why do airplanes bank sharply to the right after air-to-air refueling?

Anatomically Correct Strange Women In Ponds Distributing Swords

Help understanding this unsettling image of Titan, Epimetheus, and Saturn's rings?

Won the lottery - how do I keep the money?

Why is the US ranked as #45 in Press Freedom ratings, despite its extremely permissive free speech laws?

What exact does MIB represent in SNMP? How is it different from OID?

How to count occurrences of text in a file?

Why don't programming languages automatically manage the synchronous/asynchronous problem?

Sending manuscript to multiple publishers

How do I make a variable always equal to the result of some calculations?

Contours of a clandestine nature

Would this house-rule that treats advantage as a +1 to the roll instead (and disadvantage as -1) and allows them to stack be balanced?

How to start emacs in "nothing" mode (`fundamental-mode`)

Can we say or write : "No, it'sn't"?

Make solar eclipses exceedingly rare, but still have new moons

Are there any limitations on attacking while grappling?

Example of a Mathematician/Physicist whose Other Publications during their PhD eclipsed their PhD Thesis

How does the mv command work with external drives?

Why didn't Khan get resurrected in the Genesis Explosion?

WOW air has ceased operation, can I get my tickets refunded?

Interfacing a button to MCU (and PC) with 50m long cable



Magento 1.9.3.0 product page design is reverted to base/default



The Next CEO of Stack OverflowShowing new products in RWD-ThemeHandling grouped product attributesMagento 1.9.2 - Home page in grid format shows wrong number of columns, no add cart buttonDescription on Product page disappears after update to 1.9.2Custom option templates (radio, checkbox, etc) for a single product)Magento 1.9 Product page customizationaddAttributeToSelect() does not work for newly created attributesMagento not saving custom product attributes after version upgradeMagento Product Detail Page doesn't fully load and description and options are missing










4















I have a Magento 1.9.3.0 test shop for which I've created a new theme based on rwd. This shop uses a database that's been cloned from the production environment (Magento 1.8.1.0). Everything works very well except this weird bug:



When I visit a product view page the package/theme gets reverted to base/default from rwd/myCustom.



If I go in Admin and edit the product I was looking at earlier and just hit "Save" or "Save and continue" even without making any change, then refresh the product page again, the correct theme appears (rwd/myCustom)



enter image description here



I don't have many products (~50) so I could just manually go through them and "fix" them but I am more curious what causes this.



  • None of the products have a custom design set.

  • I've cleared cache, re-indexed a bunch of times so it's not that.

  • I've checked under Systems > Design and there's are no entries there.

  • I've tried a mass attribute update (Select All > Actions: Update
    Attributes > Change an attribute for all products > Save) but that
    doesn't seem to fix anything.

  • Logs (magento & apache) show nothing when accessing "bugged" product
    pages

Programatically loading and saving a product doesn't fix it.










share|improve this question
























  • as you are talking about the hitting save and it solves the issue, you still have indexing issues, although you reindexed seems still the tables were not indexed correctly.

    – Nickool
    Oct 20 '16 at 22:59















4















I have a Magento 1.9.3.0 test shop for which I've created a new theme based on rwd. This shop uses a database that's been cloned from the production environment (Magento 1.8.1.0). Everything works very well except this weird bug:



When I visit a product view page the package/theme gets reverted to base/default from rwd/myCustom.



If I go in Admin and edit the product I was looking at earlier and just hit "Save" or "Save and continue" even without making any change, then refresh the product page again, the correct theme appears (rwd/myCustom)



enter image description here



I don't have many products (~50) so I could just manually go through them and "fix" them but I am more curious what causes this.



  • None of the products have a custom design set.

  • I've cleared cache, re-indexed a bunch of times so it's not that.

  • I've checked under Systems > Design and there's are no entries there.

  • I've tried a mass attribute update (Select All > Actions: Update
    Attributes > Change an attribute for all products > Save) but that
    doesn't seem to fix anything.

  • Logs (magento & apache) show nothing when accessing "bugged" product
    pages

Programatically loading and saving a product doesn't fix it.










share|improve this question
























  • as you are talking about the hitting save and it solves the issue, you still have indexing issues, although you reindexed seems still the tables were not indexed correctly.

    – Nickool
    Oct 20 '16 at 22:59













4












4








4








I have a Magento 1.9.3.0 test shop for which I've created a new theme based on rwd. This shop uses a database that's been cloned from the production environment (Magento 1.8.1.0). Everything works very well except this weird bug:



When I visit a product view page the package/theme gets reverted to base/default from rwd/myCustom.



If I go in Admin and edit the product I was looking at earlier and just hit "Save" or "Save and continue" even without making any change, then refresh the product page again, the correct theme appears (rwd/myCustom)



enter image description here



I don't have many products (~50) so I could just manually go through them and "fix" them but I am more curious what causes this.



  • None of the products have a custom design set.

  • I've cleared cache, re-indexed a bunch of times so it's not that.

  • I've checked under Systems > Design and there's are no entries there.

  • I've tried a mass attribute update (Select All > Actions: Update
    Attributes > Change an attribute for all products > Save) but that
    doesn't seem to fix anything.

  • Logs (magento & apache) show nothing when accessing "bugged" product
    pages

Programatically loading and saving a product doesn't fix it.










share|improve this question
















I have a Magento 1.9.3.0 test shop for which I've created a new theme based on rwd. This shop uses a database that's been cloned from the production environment (Magento 1.8.1.0). Everything works very well except this weird bug:



When I visit a product view page the package/theme gets reverted to base/default from rwd/myCustom.



If I go in Admin and edit the product I was looking at earlier and just hit "Save" or "Save and continue" even without making any change, then refresh the product page again, the correct theme appears (rwd/myCustom)



enter image description here



I don't have many products (~50) so I could just manually go through them and "fix" them but I am more curious what causes this.



  • None of the products have a custom design set.

  • I've cleared cache, re-indexed a bunch of times so it's not that.

  • I've checked under Systems > Design and there's are no entries there.

  • I've tried a mass attribute update (Select All > Actions: Update
    Attributes > Change an attribute for all products > Save) but that
    doesn't seem to fix anything.

  • Logs (magento & apache) show nothing when accessing "bugged" product
    pages

Programatically loading and saving a product doesn't fix it.







product-page theme-fallback magento1.9.3.0






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 8 mins ago









Teja Bhagavan Kollepara

3,01241949




3,01241949










asked Oct 20 '16 at 22:33









Alexandru BangalăAlexandru Bangală

518




518












  • as you are talking about the hitting save and it solves the issue, you still have indexing issues, although you reindexed seems still the tables were not indexed correctly.

    – Nickool
    Oct 20 '16 at 22:59

















  • as you are talking about the hitting save and it solves the issue, you still have indexing issues, although you reindexed seems still the tables were not indexed correctly.

    – Nickool
    Oct 20 '16 at 22:59
















as you are talking about the hitting save and it solves the issue, you still have indexing issues, although you reindexed seems still the tables were not indexed correctly.

– Nickool
Oct 20 '16 at 22:59





as you are talking about the hitting save and it solves the issue, you still have indexing issues, although you reindexed seems still the tables were not indexed correctly.

– Nickool
Oct 20 '16 at 22:59










1 Answer
1






active

oldest

votes


















3














I just figured it out!



Notes:



The old (production) site is running a package called oldtheme.

The new (development) site is running a theme called myCustom under the rwd package.



After digging through app/code/core/Mage/Core/Model/Design/Package.php and logging the designPackageExists function with Mage::log I've noticed that Magento was looking for an oldtheme package instead of rwd.



I did a search in the database and revealed that under catalog_product_entity_varchar there were a bunch of entries with the oldtheme/default value.
I tracked the entry's entity_type_id in the eav_attributes table and found that its corresponded to the custom_design attribute (even though non of the products had a custom design set for any of the store views).



The fix was removing the offending entries from catalog_product_entity_varchar.






share|improve this answer























    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
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f141930%2fmagento-1-9-3-0-product-page-design-is-reverted-to-base-default%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









    3














    I just figured it out!



    Notes:



    The old (production) site is running a package called oldtheme.

    The new (development) site is running a theme called myCustom under the rwd package.



    After digging through app/code/core/Mage/Core/Model/Design/Package.php and logging the designPackageExists function with Mage::log I've noticed that Magento was looking for an oldtheme package instead of rwd.



    I did a search in the database and revealed that under catalog_product_entity_varchar there were a bunch of entries with the oldtheme/default value.
    I tracked the entry's entity_type_id in the eav_attributes table and found that its corresponded to the custom_design attribute (even though non of the products had a custom design set for any of the store views).



    The fix was removing the offending entries from catalog_product_entity_varchar.






    share|improve this answer



























      3














      I just figured it out!



      Notes:



      The old (production) site is running a package called oldtheme.

      The new (development) site is running a theme called myCustom under the rwd package.



      After digging through app/code/core/Mage/Core/Model/Design/Package.php and logging the designPackageExists function with Mage::log I've noticed that Magento was looking for an oldtheme package instead of rwd.



      I did a search in the database and revealed that under catalog_product_entity_varchar there were a bunch of entries with the oldtheme/default value.
      I tracked the entry's entity_type_id in the eav_attributes table and found that its corresponded to the custom_design attribute (even though non of the products had a custom design set for any of the store views).



      The fix was removing the offending entries from catalog_product_entity_varchar.






      share|improve this answer

























        3












        3








        3







        I just figured it out!



        Notes:



        The old (production) site is running a package called oldtheme.

        The new (development) site is running a theme called myCustom under the rwd package.



        After digging through app/code/core/Mage/Core/Model/Design/Package.php and logging the designPackageExists function with Mage::log I've noticed that Magento was looking for an oldtheme package instead of rwd.



        I did a search in the database and revealed that under catalog_product_entity_varchar there were a bunch of entries with the oldtheme/default value.
        I tracked the entry's entity_type_id in the eav_attributes table and found that its corresponded to the custom_design attribute (even though non of the products had a custom design set for any of the store views).



        The fix was removing the offending entries from catalog_product_entity_varchar.






        share|improve this answer













        I just figured it out!



        Notes:



        The old (production) site is running a package called oldtheme.

        The new (development) site is running a theme called myCustom under the rwd package.



        After digging through app/code/core/Mage/Core/Model/Design/Package.php and logging the designPackageExists function with Mage::log I've noticed that Magento was looking for an oldtheme package instead of rwd.



        I did a search in the database and revealed that under catalog_product_entity_varchar there were a bunch of entries with the oldtheme/default value.
        I tracked the entry's entity_type_id in the eav_attributes table and found that its corresponded to the custom_design attribute (even though non of the products had a custom design set for any of the store views).



        The fix was removing the offending entries from catalog_product_entity_varchar.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Oct 23 '16 at 23:57









        Alexandru BangalăAlexandru Bangală

        518




        518



























            draft saved

            draft discarded
















































            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f141930%2fmagento-1-9-3-0-product-page-design-is-reverted-to-base-default%23new-answer', 'question_page');

            );

            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







            Popular posts from this blog

            Can not update quote_id field of “quote_item” table magento 2Magento 2.1 - We can't remove the item. (Shopping Cart doesnt allow us to remove items before becomes empty)Add value for custom quote item attribute using REST apiREST API endpoint v1/carts/cartId/items always returns error messageCorrect way to save entries to databaseHow to remove all associated quote objects of a customer completelyMagento 2 - Save value from custom input field to quote_itemGet quote_item data using quote id and product id filter in Magento 2How to set additional data to quote_item table from controller in Magento 2?What is the purpose of additional_data column in quote_item table in magento2Set Custom Price to Quote item magento2 from controller

            How to solve knockout JS error in Magento 2 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?(Magento2) knockout.js:3012 Uncaught ReferenceError: Unable to process bindingUnable to process binding Knockout.js magento 2Cannot read property `scopeLabel` of undefined on Product Detail PageCan't get Customer Data on frontend in Magento 2Magento2 Order Summary - unable to process bindingKO templates are not loading in Magento 2.1 applicationgetting knockout js error magento 2Product grid not load -— Unable to process binding Knockout.js magento 2Product form not loaded in magento2Uncaught ReferenceError: Unable to process binding “if: function()return (isShowLegend()) ” magento 2

            Nissan Patrol Зміст Перше покоління — 4W60 (1951-1960) | Друге покоління — 60 series (1960-1980) | Третє покоління (1980–2002) | Четверте покоління — Y60 (1987–1998) | П'яте покоління — Y61 (1997–2013) | Шосте покоління — Y62 (2010- ) | Посилання | Зноски | Навігаційне менюОфіційний український сайтТест-драйв Nissan Patrol 2010 7-го поколінняNissan PatrolКак мы тестировали Nissan Patrol 2016рвиправивши або дописавши її