Reynier C. (woo-hc)

Hi @thehappymagda ,

Thanks for reaching out with the error details, it’s very helpful. After reviewing what you’ve provided, it looks like changing the autoload options might have caused some unexpected issues with Woo Payments.

First, could you let me know how you modified the autoload option? Did you use a plugin, or did you access the wp_options table in the database?

Just to add insights about the situation: Autoload is a feature that helps your website load faster by pre-loading certain settings every time someone visits your site. This feature is turned on by default. Think of it like having a small basket of essentials you always carry with you, so you don’t have to go back and forth to get what you need.

When you set some autoload options to ‘no’, it’s like you decided not to carry some items in the basket to make it lighter. But it turns out, one of those items was important for processing payments with WooPayments. Without it, your website didn’t know how to handle payments, which caused the crash.

The error message you got is basically saying there was a misunderstanding in the website’s language when it tried to handle payment information. It’s like it was expecting a number (like how much to charge for an item) but got a word instead (which it didn’t know how to charge).

To attempt a fix, try enabling the autoload and then safely reactivating WooPayments. Sometimes, deactivating and reactivating a plugin can resolve issues. Kindly note, it’s best to do this on a staging site or ensure you have backups first, saving a backup is always a good idea before pushing an update.

• Disable WooPayments and any caching plugins you might have.
• Clear your site’s cache.
• Re-enable WooPayments to see if the problem persists.

If this doesn’t fix the issue, the safest bet is to restore your site from a backup before the changes were made.

Hi @hairyhobo ,

Thanks for reaching out and for the clarification from the earlier thread.

Should i change the status of the order to “pending payment” and resend order details to the customer again? and will this allow them to get to the payment gateway screen again?

To answer, when an order fails payment, the link may expire for security reasons. So, yes, please set the order status to “pending payment.” This will allow you to resend the order details to the customer. They should then see the option to attempt payment again.

You won’t need to create a new order. Just ensure the payment method is set up correctly. If there’s still trouble, you might want to check in with Payl8r to make sure everything’s good on their end.

Hope that helps!

Hi @seasonalsports ,

Really appreciate your feedback about this thread!

If anything else comes up, please feel free to open a new topic. ??

Hi @tazcrzy ,

Thanks for reaching out and providing the error message! It looks like the error you’re seeing is because the WooCommerce plugin update can’t find the page it’s looking for. This could be due to a broken link or a problem with the update process itself.

To fix the issue, please try these steps:

1. Ensure the staging site URL is correct and accessible.
2. Deactivate and reactivate the WooCommerce plugin. This sometimes resolves the issue.

If you’ve tried these steps and still need help, please reach out with details such as the system status report. You can find it by going to WooCommerce → Status, selecting Get system report, and then Copy for Support. Then paste it here using the <code> block.

Let us know how it goes.

Hi @spets24 ,

Oh that’s an interesting question! To include product attributes in your main menu, you need to first make them available by turning them into terms in a custom taxonomy. This makes it available through an attribute search filter (URL).

I made a video here to show you how it’s done: https://www.loom.com/share/c238b0f0d607477498d87ba43c2f0645?sid=241211d6-e55c-4513-9401-7687821bac63

Here are the steps if your prefer to read through:

1. Go to Products > Attributes in your WordPress dashboard.
2. Create the attribute you want (e.g., Attribute = “Size” and Terms = “Jumbo”) and add its values.
3. Add this attribute/term to your products.
4. This lets you use search filter with a link like this: yourdomain.com/shop/?filter_size=jumbo and will show all the products that had the “jumbo” size attribute.
5. Go to Appearance > Menus in your dashboard.
6. Add a custom link use the one above as a sample, replacing “size” with your attribute and “jumbo” with your term, and of course “yourdomain.com” with your domain.
7. Don’t forget to save your menu changes.

Let me know if this helps!

Hi @dionijoe ,

Thanks for reaching out! May I ask for further clarification about what you’re experiencing? Before the update, was your site showing a different language but now only displays English?

You mentioned the default site language works fine in the frontend only, is the backend showing English while the frontend displays a different language? Also, are you using a translation plugin for translations, if so which plugin?

Looking forward to your response.

Hi @momo-fr ,

I understand that you’re having trouble after the latest update, where you’re unable to add more than the first product to your cart. That definitely sounds frustrating, especially when you’re trying to run your store smoothly.

The error you’re getting seems to be a technical concern where the system expects one type of information but gets something it can’t work with. It’s like trying to dial a phone number and accidentally hitting a letter key, things don’t connect as they should.

This miscommunication in the code can often be caused by a few different things. It could be a conflict between WooCommerce and another plugin or even your theme that wasn’t there before the update.

Here are some suggestions to troubleshoot further:

• First, check that all your other plugins and themes are up to date. If they’re not, update them and see if that resolves the issue.
• If the error persists, try switching to a default theme and deactivating other plugins for a moment. This is a way to pinpoint the source of the trouble.
• Reach out to your hosting provider to see if your PHP environment matches what’s recommended for WooCommerce.

Running these checks should give us a clearer picture of what’s going on. Please keep us posted on your progress.

Hi @alberez ,

I understand how frustrating it must be to have trouble saving the cart page settings in your WordPress admin panel after the update. And we appreciate you sending the error logs.

The “403 (Forbidden)” errors typically indicate permission issues on your server that prevent the requests from being accepted. This could be due to incorrect file permissions, security plugins, or server configurations that are too restrictive.

Regarding the “Store ‘core/interface’ is already registered” message, it can suggest a script conflict or a problem with the WordPress data module. Also, have you updated your active plugins, theme, and WordPress itself? If not, please try updating them, but make sure to back up your site first for safety.

If the issue persists and to help narrow down the cause, please send us the system status report so we can take a look at your site’s setup and find any other possible causes. You can find it by going to WooCommerce → Status, selecting Get system report, and then Copy for Support. You can paste it here using the <code> block.

Looking forward to getting this sorted out.

Hi @alausbaras7 ,

I understand that you’re trying to translate certain strings on your checkout page using custom code snippets. While I can’t provide extensive support for custom coding as stated on our scope of support, I would suggest translating those strings on your checkout page, using a plugin like Loco Translate. It allows you to find and update any specific text directly within your site’s interface, making the process simpler.

This method is generally more straightforward and avoids the potential concerns from code edits.

Kindly try this solution and let me know how it goes.

Hi @comyu ,

Thanks for reaching out and sharing your experience.

Could you give me more details about the error messages or perhaps a screenshot of the cryptic errors you’re seeing? It would be really helpful to understand exactly you’re seeing. You can take one and upload it to snipboard.io, then share the link here.

It does sounds like a plugin conflict but I’d like to narrow it down further. You can also try updating all plugins related to the checkout page (if you haven’t already) to see if it fixes the issue. But be sure to back up your site before making any updates.

Looking forward to your response and getting this sorted out.

Hi @reberiii ,

Thanks for trying the suggested steps and sharing your observations. The sluggishness in bulk editing despite a more robust server and ample resources indicates there might be complex factors at play. The new install you’re setting up could shed light on whether the issue is tied to your current environment or the sheer volume of data.

When your test on the fresh WooCommerce/WordPress install is complete, the results should give us a clearer picture. If the problem persists even in the simple setup, it might be due to how WooCommerce processes bulk edits with large datasets.

Should that be the case, and the test doesn’t lead to any breakthrough, exploring optimization plugins specifically designed for heavy WooCommerce stores, or custom solutions may be necessary.

Please keep us posted on the outcome of your new install test.

Hi @rittermann ,

Thanks for sending the screenshots! When I visited your site, I do see that your site is up and running, and the shop items are showing as seen here: https://snipboard.io/zyvX6i.jpg. Based on your screenshots, I understand that this is happening in the wp-admin area.

As a quick first step, could you try clearing your browser cache or using a different browser you haven’t used to visit your site before?

Just a hunch, an outdated browser cache could be behind the setup page reappearing or even your mailbox having concerns. By the way, is this mailbox also accessed via your WordPress dashboard through a plugin?

Note that clearing the cache will force your browser to load the most recent version of your WooCommerce pages. So if it’s already setup before, this will clear any cached data that might have been stuck, causing the re-appearing setup wizard. After clearing the cache, close the browser, reopen it, and try accessing WooCommerce again.

Please keep us posted on your progress.

Hi @jacquiescarlett1933 ,

Thanks for reaching out to us. It sounds like the update to Woocommerce 9.4.2 might have conflicted with your current payment settings. Good job on rolling back to the previous version of Woocommerce as a temporary fix.

To ensure we’re on the right track and provide you with the most accurate assistance, could you confirm which payment processing plugin you’re using alongside WooCommerce?

Looking forward to your response.

Hi @adamipl ,

Thanks for the update! I’m glad @ckadenge suggestion worked well for you.

Just an added note: Clearing your browser cache can fix visual issues because it forces your browser to load the latest version of a page. Sometimes, outdated files saved in your cache can cause display problems like a blank page. When you clear the cache, your browser gets a fresh start and this often solves the problem.

Since it’s working fine now, I’m going to mark this as resolved. If anything else comes up, please feel free to open a new topic. ??

Hi @mervyntsao ,

I understand you’re looking to improve how visitors interact with the login and registration process on your site.

While this does involve code customizations and is outside of the standard scope of support, you can get some guidance by joining the WooCommerce Community Slack. Many of our developers are active there and might be able to help.

Additionally, you can also check out our Woo Experts page if you’d like help from other professionals.

Hope this helps point you in the right direction.