New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fatal error with Polylang #1303
Comments
It seems to me that it is caused by following query (inserting multiple rows into a table): https://github.com/polylang/polylang/blob/852e5b1e616186eb19f8f68c23b29241cdbd8833/admin/admin-model.php#L319 Example: VersionPress probably does not parse this query correctly. |
Do you see any solution for integrating Polylang? |
@juanitopons: This issue is not the only problem (it is related only to mass assigning languages), I am trying to debug why some relationships are not correctly tracked by VersionPress. |
After some further research it seems to me that problem is not query parsing, but missing entity for Example query: Parsed object:
I am not sure about So
$entityInfo is NULL in this case
And later it leads to unknown column error, warnings and fatal error in the end (see first post). It is general VP error, but for Polylang it appears only in case of setting default language for all posts (after activating plugin). |
Well it sounds quite tricky to solve. SO, here is my question. Is there a way to stop VERSIONPRESS versioning specific plugin actions? |
@juanitopons: This issue is not a big deal when you do not click to mass setting of default language. See issue #1306, this is the source of sync problems :-( |
Are there any further updates on this issue. Polylang Bulk update with wp_term_relationships not having a primary key value and duplicate values for object_id breaks in versionpress. |
Probably small problem with Polylang leads to a fatal error for VersionPress.
The text was updated successfully, but these errors were encountered: