You will need to provide some URLs to an example post / page, and a description of the issue on that post page (which URL works, and which doesn’t), then we can have a look for you. 😉
See the forum sticky for more info: https://wordpress.org/support/topic/must-read-before-posting-in-this-forum
js.
Is this still an issue? If not, then I’ll mark this thread resolved.
Thanks,
js.
Well, it’s resolved in the sense that I’ve discovered that the cache has to be deleted through the ngfb plugin for the second language to be updated, and not the regular cache setting, although it’s not necesary to delete the cache for the 1st language. (It also would be great to be able to empty cache for a single post.)
thanks!!
When a post is updated, the cache is refreshed for that language (using the WP locale value). Why would the cache be refreshed for the other languages?
js.
Is this still an issue? If not, then I’ll mark this thread resolved.
Thanks,
js.
When I update a post, it is always both english and french that are modified. so both should be refreshed. (sorry I didn’t see your reply!)
I’m not sure I understand… You’re updating one post, but you’re editing two posts at the same time? I’m missing something here… NGFB is hooked into the post saving hook, so when you save a post, it’ll clear the cache for that post, using the WordPress locale value for that language.
js.
Yes, my site is multilanguage, so every post is both english and french. I’m using the plug-in qTranslate-X. Cache is cleared on the first language, but not the second.
(http://petluck.ca)
I installed qTranslate-X to see what’s going on, and as you describe, this plugin uses a single post ID for all languages. This negates the use of many WordPress functions to return information about the content (permalink, etc.). They’ve tried to get around this by using a bunch of hooks, but it’s a bad design from the start. I may add support for qTranslate-X in NGFB Pro, but that would be in another week or two, when I have a bit more time…
js.
ah I see, thanks very much for looking into it!
You may want to look at Polylang — it integrates with WordPress much better. 😉
js.
Yeah, when I picked Q-Translate it was the best option at the time. but seems things have changed 🙂
I looked further at qTranslate-X and it’s so bad that I will not be adding support for it.
js.
that’s unfortunate, I don’t know anything about coding but when I had decided on Q-Translate 7 years ago, I checked all the translation plug-ins, and Q-Translate was one of the best. The original developer dropped it however, and it was taken on by another group. I looked at Polylang, but I can’t afford their pro version, my site is running for free.
