This thread is resolved. Here is a description of the problem and solution.
Problem: The client encountered a PHP warning related to
preg_match()
on their website. Solution: We have reproduced a similar issue and have provided a temporary workaround in our Errata. We recommend following the steps outlined there to resolve the issue:
If the issue persists, we advise the client to share the full error message from the WordPress Debug log for further assistance. For guidance on enabling WordPress debugging, please refer to:
Please note that the solution provided might be outdated or not applicable to your case. If the issue remains unresolved, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket with us for further assistance.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
I understand that you're seeing the "preg_match():" warning on your site. As you haven't shared the full error log, it is difficult to say from where it originates, however, we are aware of a "preg_match" warning that usually gets solved by saving the permalink structure. Would you please try doing the same?
- Please go to "Settings > Permalinks"
- Set the default permalink structure to "Post Name"
- Save the settings
Clear the caches from your site and check if that helps to solve the issue. However, since they are Warning only, you can ignore them by disabling the WordPress debug log. Check the guide below to understand the process of disabling the debug log.
Could you please activate the WordPress Debug mode and share the complete error log with me? This will allow me to more accurately assess the issue at hand.
I also would like to inform you that in one of the cases, we found that the same warning disappears when we deactivate the "XML Sitemap Generator for Google" plugin and resave the permalink structure. Since this plugin is also active on your site, would you please check again by deactivating the plugin nd then resaving the permalink structure?
Please let me know how it goes. I will be happy to help if you need further assistance in this matter.
Thanks for providing the WPML Debug Information. However, I was actually looking for the specific errors logged in the WordPress Debug log to better understand the issue.
I wanted to let you know that we've reproduced an issue similar to the warning you described. We've found a temporary solution for the issue and outline the solution in the Errata below. Please follow the workaround provided there to see if it resolves your problem.
Please let me know the outcome. If the problem continues, share the full error message from the WordPress Debug log in the next response. This will give me a clearer view of the issue and assist in finding a resolution.
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
