PHP Warning: preg_match(): Unknown modifier '-' in /wp-content/plugins/sitepress-multilingual-cms/inc/absolute-links/absolute-links.class.php on line 186
Hello There,
Thanks for reaching out to WPML Support.
Before this thread gets assigned to my colleague, I'd like to offer some initial guidance or potential solutions.
In similar past cases, resetting the permalink structure has resolved the issue. Could you please navigate to "Settings > Permalinks", simply save the permalink settings again, and see if this addresses the problem?
Let us know the update. We will be happy to help if you need further assistance in this matter.
We reset the permalinks as you mentioned, but still, we are seeing the same error on the logs. Do we need to clear the caches? The website is on a WP Engine server.
My apologies if I am not being clear enough. After those steps you can reactivate the plugin and see if problem is resolved.
I assume that you'd have done that and problem has been resolved. But is this possible if you've a backup prior to this fix, where the problem exists? And if you'd like to share with us?
Our team is interested in working on a proper fix for this, so it can be prevented in the future.
If you agree and interested in sharing that, I'll request a copy of your site having that problem (not the one which fixed it). I've enabled your next reply as private to share the details safely.
P.S.: In case if you're unable to create a package using Duplicator plugin, you can use All-in-One WP Migration (https://wordpress.org/plugins/all-in-one-wp-migration/) plugin. Despite that if you've that copy of the site up and running somewhere, we can arrange for a direct copy to our Cloudways servers too, please let me know.
We have a staging server with a copy of the live site, and it has the same issue. I can provide the credentials for the same, so you can check and find possible solutions.
Note: Do not share databases, files, analytics, or anything related to coinedition.com with anyone. Please make sure it is only used for your studies and testing.
Thank you for the access. I'll login on Monday and 'll clone the site to our secure servers. I'll also make sure that the site isn't accessible publicly and is only used for our internal testing purposes.
I'll then let you know and you can revoke the access as needed.
Thank you for your patience and cooperation. I've tried to migrate the site to our secure servers, but looks like the site is very huge and migration fails in the half way. So I've cancelled the migration.
I am discussing with the team if they can login to your dev site and have a look what we may need for understanding about the said issue.
I'll update you soon on this, so we can move forward accordingly.
Our team analyzed the DB dump, as well as, your staging site but can't find anything relating to that problem. Perhaps it's been fixed in there too.
However, if in future, you run into the same issue again, please isolate the problem by creating a site package and DB dump, before fixing it. And I'll request to report accordingly, so we can then investigate and try to find the actual reason behind it.
