Pieter Bos

Hi Karla,

Hmmm, that is strange!

I will try it, no longer access to the site of the client, but will let them know.

Consider this as resolved then and thank you for your support!

Glad to know it works for you and thank you for your 5-star rating and review!

Many thanks for confirming this bug Karla, I will await your update here then.

Pieter

at least the slug should be changed too

For the slug specifically, there are some current technical limitations that wouldn’t allow the plugin to be updated (even with the security fixes) if we changed the slug.

What you actually mean is that by changing the slug (which is default for forking software) you could not hi-jack the existing users of the original free ACF plugin and would have started with a user-base of 0, like all real forks do.

• This reply was modified 1 month ago by Pieter Bos.

Many thanks for your 5-star review and glad to hear that the Quick Multilingual plugin is so useful for your site!

I developed the Quick Multilingual plugin first and foremost for simple brochure-like websites, that come with no more than a handful of pages, such as home, about, services, contact, and therefore do not need a full-blown multilingual plugin (in my opinion).

“All” the Quick Multilingual plugin really does is to add hreflang tags and the HTML language attribute to the source code to make sure that these simple bilingual websites can perform well for the search engines.

After working with multilingual plugins in a professional capacity for more than 15 years, I think it is safe to say that I have seen my share of websites. As such I have also come across sites for which it would have been far better to have a much simpler solution and that is the reason I have now released the Quick Multilingual plugin.

Sites that come with 5-6 languages (per your initial example) and numerous pages, posts, custom post types, taxonomies, etc., will most likely be much better off with one of the existing multilingual plugins, be it a free or premium solution.

Anyways, many thanks for your feedback, much appreciated!

Thanks for your feedback.

The idea is to keep this (Lite) version for 2 languages and 4 pages, really simple brochure-like websites.

Currently I am developing the premium version of the Quick Multilingual plugin which will come with more options for both content and number of languages.

Thank you for your 5-star rating and glad to hear that you think the Classic Editor + plugin is awesome ??

I once had a plugin that did stuff in the editor, you might want to have a look at it for ideas…

Hello @fossfolks

If you look at the code of the plugin, you will see that the only thing it does is to dequeue scripts and styles of the WP Block Editor and adds a filter to remove it as editor on the backend.

So in terms of TinyMCE it doesn’t do anything.

It “just” brings back the Classic Editor (and the Classic Widgets) and removes WP Block Editor related scripts and styles from the frontend.

Hope that clears it up.

Many thanks for your 5-star rating and review, much appreciated!

Yes, even here, we are forced to use this horrendous interface ??

Thank you for your 5-star rating and comment; my pleasure and it was just updated to be compatible with the new $autoload parameter of WP 6.6 which comes out next week ??

Your question has nothing to do with my plugin. Typically you ask these type of question in the WPML Support forums.

Need some kind of function that applies this css block to the xml inline

That’s not going to happen. The only way that I can do it, is by setting the generated output to display: none in the CSS. If that’s not what you want, then it is perhaps time that you switch to a different SEO plugin? ??

Hello,

Thanks for your question.

Yes, this is possible, but it will not be limited to only that sentence. I can hide the entire first paragraph (first two sentences) and leave the branding-less sentence that indicates the number of sitemaps included.

I am not entirely sure when I have the time to implement this. Very likely I will add it to a new version that will contain a few other things too.

If you want to hide it in the meantime, you can check out the solution over at Github where I have made a new ticket based on your feature request here: https://github.com/senlin/so-clean-up-wp-seo/issues/109 .

I will therefore close the issue here and you can use the Github thread for follow-up.