This a known problem: The plugin Geodirectory is breaking the WordPress API on the post editor page. They know it and don’t care. Every plugin that expects a WP_Post here will be broken by that plugin.
Sorry to say that. All you can do is filing another bug report to them.
On a further note: take a look at your database. What that plugin is doing there … might make you want to find an alternative.
Hi toscho,
I am the developer of GeoDirectory. We have not yet looked into compatibility with your plugin because we already selected the market leader WPML to make compatible.
I am not sure what your reference to “take a look at your database” is about, yes we have our own tables, it is necessary for such a complex plugin.
Anyway, if you are willing (which it does not sound like you are) i would happily work with you to make our two plugins compatible.
Regards,
Stiofan
Hi Stiofan,
you don’t have to write anything special to be compatible with MultilingualPress, Polylang or any of the other currently popular multilanguage plugins. Just don’t break the WordPress API, namely, don’t overwrite the WP_Post object with a stdClass when the accompanying filter doc clearly states that it has to be a WP_Post. This is not necessary in your code, it is just a hack to save a few lines of code.
When other users came to us with exactly the same problem and we sent them to you, they were told by your support that would be “faster” (a lie) and you wouldn’t change it.
To be honest, that was the moment when I decided that I don’t want to work with you.
Your tables are missing normalization and indexes, the field declarations are partially wrong, and they are duplicating existing WordPress behavior without a real need. This could be much faster and cleaner.
Hi Toscho,
When the user came to us, i had not even looked at the problem as we had no plans to look at compatibility with your plugin, i was simply explaining why we were changing the post object, which is for speed, i was not aware of the context of the problem.
I assume somehow you took my comments out of context and were offended? If you want to start things over and make a concise effort to get the two plugins working together and tested then my door is open and we would be happy to recommend your plugin to our customers.
Regards,
Stiofan
Thread Starter
wci
(@wci)
Dear Dev’s,
referring to your discussion above stated, I apologize and did not want to start a dispute by starting this thread for problem resolve.
I am sure that I am not the only one who would like to use your plugins in a compatible way, because both of you have created a stunning product.
In customer point of view, I believe and trust in you to find a compatible solution in a fast way to use your products as an WPML alternative.
With my best regards, Alex
Hi Stiofan,
please contact me per email. I do have an idea how this can be resolved.
Alex, this is just about the code. Discussions like these are sometimes necessary, and it looks like we can find a way to resolve the problem. 🙂
Thread Starter
wci
(@wci)
Dear Dev’s (Toscho and Stiofan )
This is just a follow up. I just want to know if you are meanwhile in contact to each other and how the progress is.
Looking forward to your answers.
Thanks, Alex
