Picard

Yes, this works, thanks for the response. But this should’ve been automatic in my opinion. Since a specific product is not allowed in a specific country it makes no sense to set it separately in all languages. I know that WMPL is a separate plugin, but also this is a WP ecosystem and WPML is on of two major language plugins so its support is kind of a must have of a good plugin that wants to enter this ecosystem.

WPML makes a separate post (so post id) for each language version – and this is the issue here. This plugin should allow only edit restrictions for the default language and then propagate automatically to the rest.

It depends how you look at it:
Classic Editor is an official WordPress plugin, and will be fully supported and maintained until 2024, or as long as is necessary.

Lots of people still use and are planning to use the Classic Editor (5+ million active installations, top 5 WP plugin), so I don’t think it’s so exotic yet. On the other hand it’s your plugin and your business strategy I can kind of understand that but still this way it is kind of useless for all these people.

I’m using the classic WP editor and I don’t see any support, so only Gutenberg in the Lite version?

This must be so complicated question so I have to go through all this.
Looks like the beginning of problems with support when I actually buy any plugin…

Thanks @flotschie – that was it – definitely it should be in the docs.

Well my custom endpoint is unprotected too… Have you solved this problem?
I assume that the plugin protects only standard endpoint, so I started looking for a hook to add my endpoint but no luck so far.

None I know of, unless you modify the plugin files itself:

file: qtranslate_utils.php
add function:
function qtranxf_setLanguage($lang) {
global $q_config;
$q_config[‘language’] = $lang;
qtranxf_set_language_cookie($lang);
}

and then just: qtranxf_setLanguage(‘de’);

you’re right – medpark theme does it
plugin works with the standard themes

thanks

the same here (wordpress 4.1) I click the “add a marker” link the whole screen goes grey (besides the box title “build a map”) and nothing happens – no JS errors, no missing files, just nothing – this plugin is useless without markerks ??