“Save” button doesn’t save changes editing product
-
Hello
Version 5.0.12
WooCommerce 11
Third-party plugins and themes are disabled.- Go to the vendor dashboard.
- Start adding or editing your product.
- The “Save” button doesn’t save changes.
Go to page=multivendorx#&tab=settings&subtab=appearance – from the WordPress admin side, and you’ll see that the dashboard color scheme settings are no longer displayed.
-
Hello @loralora,
Thank you for reaching out, and we’re sorry to hear that you’re experiencing this issue.
We have tested both the Dashboard Color Scheme settings under Appearance and the product saving flow in the Store Dashboard, and both are working correctly on our end. You can refer to the following screen recordings:
Since we are unable to reproduce the issue, we will need some additional information to investigate it further. However, as per the WordPress.org support guidelines, we are unable to request or exchange sensitive information within the support forum.
Could you please get in touch with our support team here? Our team will be able to communicate with you directly, gather the required details securely, and assist you in resolving the issue as quickly as possible.
We look forward to helping you resolve this.
Sent, you can see all the problems when you log in yourself.
Thank you for your update.
Our team will connect with you shortly and work towards resolving the issue you are experiencing.
Thank you for your cooperation. We truly appreciate your support.
Sent, you can see all the problems when you log in yourself.
@loralora Please revoke those credentials. @sangi00 made a mistake that could get their plugin removed from this site. It is that serious.
While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
- Ask the user to install the Health Check plugin and get the data that way.
- Ask for a link to the http://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
- Ask the user to create and post a link to their phpinfo(); output.
- Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
- Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site visitors).
- Ask the user for the step-by-step directions on how they can reproduce the problem.
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.
Thank you for the information, we are revoking access.
Hello
We see these errors in the console when the vendor is in the dashboard and tries to save changes to the product.
vendors.js?ver=5.0.12:1 Error loading tour: AxiosError: Request failed with status code 403
at He (vendors.js?ver=5.0.12:1:2084740)
at XMLHttpRequest.E (vendors.js?ver=5.0.12:1:2091443)
at Dt.request (vendors.js?ver=5.0.12:1:2104292)
at async vendors.js?ver=5.0.12:1:161455
at async vendors.js?ver=5.0.12:1:161439
index.js?ver=5.0.12:1 Error updating product: AxiosError: Request failed with status code 400
at i (vendors.js?ver=5.0.12:1:3430637)
at XMLHttpRequest.F (vendors.js?ver=5.0.12:1:3399848)We checked the server error log and found nothing there.
In the WordPress admin panel we see the following errors:
/wp-json/multivendorx/v1/tour:1 Failed to load resource: the server responded with a status of 403 ()
vendors.js?ver=5.0.12:1 Error loading tour: AxiosError: Request failed with status code 403
at He (vendors.js?ver=5.0.12:1:2084740)
at XMLHttpRequest.E (vendors.js?ver=5.0.12:1:2091443)
at Dt.request (vendors.js?ver=5.0.12:1:2104292)
at async vendors.js?ver=5.0.12:1:161455
at async vendors.js?ver=5.0.12:1:161439@moderator Thank you for taking the time to clarify the forum guidelines. We truly appreciate the guidance and will make sure to follow them carefully going forward, while continuing to assist users in the safest and most helpful way possible.
@loralora Thanks for sharing the errors. Our team will review them and get back to you.
You must be logged in to reply to this topic.