Hi @shinagawa ,
Thanks for reaching out and providing the log! PHP warnings like the one you’re seeing are usually not critical, meaning they often don’t impact how your site runs or how customers use it. But, they’re good to check out because they can tell us if something might not be working.
Since you’re worried about the identifier property, it’s smart to be cautious. We want to make sure everything is set up properly for both you and your customers. In most cases, everything is okay, but it’s best not to ignore these warnings.
Here are things you can do:
- Make a backup: Before you make any changes, ensure you have a backup of your site. If available, it’s also a good idea to use a staging site for testing.
- Update your plugins and themes: Make sure everything is up to date as a first step, since updates often fix known bugs.
- Test for conflicts: Temporarily switch to the default theme (like Twenty Twenty-One) and turn off all plugins except WooCommerce and the Stripe gateway. If the warning goes away, then re-activate each one by one to identify the source of the problem.
- Look at your logs: Check the logs in WooCommerce > Status > Logs for any other messages that might give more clues.
If you’re comfortable, give those steps a try, and let me know what happens.
If you’d rather not or if the warning is still there, we can take a closer look at your System Status Report which you can find via WooCommerce > Status > Get system report > Copy for support. Once you’ve done that, you can paste the text in here using the “<code>” block.
Looking forward to your response.
