Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter modrobes22

    (@modrobes22)

    @doublezed2 Thank you for the help! I’ll definitely try that. I do have one question though, if the woocommerce update is only changing files inside woocommerce then how come both my themes (the original one and the duplicate for tests) are reverting back ONLY when I do a woocommerce update? Everything single aspect outside of woocommerce plugin is up to date. I purposely leave updates separate to know exactly what causes and issue. This is part of how I found the woocommerce plugin just makes my css go crazy and revert to months ago.

    Thread Starter modrobes22

    (@modrobes22)

    @omarfpg Yes, I updated the css directly on the theme files but I stopped ever since the update started reverting back my changes. I haven’t done any major css changes to my site since then. I’m guessing what I could do is make a child theme, update woocommerce plugin which will revert back my changes, then on the child theme just put the same css so it looks good again then in theory, on the next wooocommerce update my css won’t revert correct? Also here’s the system file, I had set it up to 72 hours and 2 views so someone else must’ve seen it. https://quickforget.com/s/7471e9fee2936cedb77a21fc702d42c2a303792634e073da

    Thread Starter modrobes22

    (@modrobes22)

    @anastas10s Hi, Yes, no matter what theme is selected, edited or updated, updating the core woocommerce plugin always reverts our custom themes back, even if they are not active AND even if they aren’t even on the same folder. I also spent time updating the template files exactly how woocommerce/wordpress recommended. I also talked with my hosting support to try different things, as the old template is clearly stored somewhere and overwrites everything when the plugin is updated we tried playing around with cache settings and different combinations but nothing worked. Here is the secret link: https://quickforget.com/s/7ecff1b0c6fc7a419013e091e107397bc6fb3f04b44162fa

    Thread Starter modrobes22

    (@modrobes22)

    Hello, I have tried all the fixes mentioned here. I also tried updating the woocommerce plugin with my main theme then switching it to a duplicate of the theme I had made previously to see if the files were really going to be overwritten with the woocommerce update. If it was the case and the problem is that the files are being overwritten then switching it to a new theme would fix my issue as the duplicate would have the correct files. Switching the theme did nothing so this leads me to believe that the core woocommerce plugin is doing something else. I also just tried duplicating the theme a third time, moving the third theme away from the themes folder, then updating the site, moving the third theme back to themes folder and it still didn’t work. I even disabled all forms of caching server wide and I’m still running into the same problem. I write this now as I need the plugin to be updated to the latest version.

    Thread Starter modrobes22

    (@modrobes22)

    @seank123 Okay this makes a lot of sense, thank you for the help! I will try this and see if my files stop being overwritten. I appreciate the help and how quick you were to respond.

    Thread Starter modrobes22

    (@modrobes22)

    @seank123 I know it’s my problem but I don’t know how to fix it, the core css files are being replaced with old ones for no apparent reason, like I mentioned in my original post message it’s like there’s a cache somewhere and whenever the plugin is updated, that cache takes over and replaces all the files.

    Thread Starter modrobes22

    (@modrobes22)

    @seank123 I edit by replacing the code directly on the files through my hosting site.

    @ckadenge I already tried this, basically a copy paste of the site was done by staging, the theme is completely handmade but the problem is that there’s no “issue”, the core files just get reverted back as if my code changes were never done, this only happens when the woocommerce core plugin is updated, all the other plugins can be disabled, updated, removed, turned off if the plugin allows it, but it still happens, it even happened on a localsite where those changes were being done first before putting them live.

Viewing 7 replies - 1 through 7 (of 7 total)