Critical bug in version 2.6.7

  • Resolved brodward

    (@brodward)


    3 years ago

    Hello
    After upgrading to the latest version there was a critical error on my website, I explain:
    I was modifying a product of my store from the backend and when saving these modifications of the product the system automatically changed the url to another product of the store adding to the end of the url a -1 to differentiate it from the original product.
    I also noticed that when saving the modifications I changed the configuration of the product for the product of which I changed the url automatically.

    I had to go back to version 2.6.5 for my site to work normally again.

    Thank you and I remain attentive to the solution to be able to return to the most current version.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support B C. a11n

    (@battouly)

    Hi there!

    Thanks for the feedbacks. Would it be okay to share the error message?

    I recommend https://snipboard.io/ for easily sharing screenshots – please follow the instructions on the page, then paste the URL(s) in your reply.
    You can simply drag the image and drop it to generate a link to share.

    Thanks!

    Thread Starter brodward

    (@brodward)

    Hello
    It does not show me code errors, but it is generating errors when I edit a product from the backend, I explain:
    If I edit any product this changes me the url automatically, for example if I have the product with a url https://www.myweb.com/product after giving it update automatically changes me the url by the one of some other product and takes the configuration of the product by which I change the url.
    As I mentioned before it does not give me code error in the frontend but it is generating the conflict that I just mentioned.

    Plugin Support Chris M. – a11n

    (@csmcneill)

    Hi again @brodward,

    If I edit any product this changes me the url automatically, for example if I have the product with a url https://www.myweb.com/product after giving it update automatically changes me the url by the one of some other product and takes the configuration of the product by which I change the url.
    As I mentioned before it does not give me code error in the frontend but it is generating the conflict that I just mentioned.

    I can only imagine how frustrating this must be for you! I have a couple of questions to get a better idea of what you’re experiencing:

    1. How are you making modifications to product configuration? Are you modifying the product via Products > All Products, or via some other method?
    2. Can you provide us a URL of one of the products you are hoping to change?
    3. Does this issue happen regardless of what types of changes you’re making to your products? Or does it only happen when you try to make a particular change?
    4. Could you send us a screenshot of your permalink settings? These settings can be found by navigating to Settings > Permalinks.
    5. Could share your current System Status Report? You can get it by navigating to the WooCommerce / Status section of your site. Once there, click on the Get system report button and then copy it by clicking on the Copy for support button. Then paste it here in a comment.

    Looking forward to hearing from you!

    Thread Starter brodward

    (@brodward)

    1. I edit the products as it is normally done from: products >all products, select a product and click on edit.
    2. Deactivate the plugin
    3. It happens regardless of the change I make
    4 and 5 I deactivate the add-on because it started to generate all these errors, in version 2.6.5 it was not presenting these failures.

    Hi @brodward,

    it sounds like something on your site might be causing a conflict. Could you please go to WooCommerce > Status > Logs and check the dropdown for any recent error labelled “fatal-error” and share it here with us if it exists?

    Additionally, could you please send me a copy of your site’s System Status? You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”. Once you’ve done that, you can paste it into your reply.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Critical bug in version 2.6.7’ is closed to new replies.