Incompatible with new All in one seo v4

[andreysneg]

Qtranslate xt Incompatible with new All in one seo v4

[herrvigg]

I don't use it but the version 4 seems to get quite bad feedbacks... Did you encounter some specific problems or "just" the qTranslate integration missing?

Version 4 was release on Nov 14, 2020 but this seems to be for the PRO version only. The free version is lagging behind apparently: https://wordpress.org/support/topic/all-in-one-seo-pack-version-4-update-in-the-free-version/

But if i look to the changelog i can't see any breaking change directly or any link describing how the upgrade should be done. https://aioseo.com/changelog/

Without more information this will be hard to maintain.

[herrvigg]

Couldn't it rather be a specific problem of support for the PRO version like here in #845 ?

[bagaweb]

I confirm that:

1. version 4 is quite bad (free version)
2. not integrating properly

[herrvigg]

We should probably restart this module from scratch. Every item that had id aiosp_ does not exist anymore, for example aiosp_title. But aioseop_snippet_title is also gone.

What are the main functionalities needed? Let's first focus on the most important things.

[arnaudbroes]

@herrvigg I'm one of the developers of AIOSEO and I'll be happy to provide you with some more details about this and collaborate with you on adding compatibility for the new version.

In 4.0.0, we've switched to using our own custom tables to store post/term meta. If you're not able to easily pull from those because of how your codebase works, we can look into adding support for your plugin on our end.

[bagaweb]

Excellent news, thanks @arnaudbroes

[herrvigg]

@arnaudbroes great, thank you to reach out here, much appreciated!

As a quick intro, what we do with qTranslate-XT (and its predecessors) in the administration part is to handle multilingual content by storing value with tags and content for each language, but still using the same unique field in DB, for example: [:en]English Text[:xx]Other language Text[:]. I must concede it's a very hacky solution but this is what makes qTranslate so specific and also popular because it simplifies some aspects. This works actually great for many websites.

The integration with other plugins can be a real headache though. In the admin sections, some hidden fields are added to handle the translations storing the value for each language and allowing to switch between language before posting the updates.

What we need is to be able to identify the fields of interest in the HTML through tag ID, name or class (via jquery in that case). Previously, i suppose valid up to AIOS v3, we had this:

settings form

(now in V4 this seems to correspond to aioseo-search-appearance)

    $fields[] = array( 'tag' => 'textarea', 'name' => 'aiosp_home_title' );
    $fields[] = array( 'tag' => 'textarea', 'name' => 'aiosp_home_description' );
    $fields[] = array( 'tag' => 'textarea', 'name' => 'aiosp_home_keywords' );

post

    $fields[] = array( 'id' => 'aioseop_snippet_title', 'encode' => 'display' );
    $fields[] = array( 'tag' => 'input', 'name' => 'aiosp_title' );
    $fields[] = array( 'tag' => 'textarea', 'name' => 'aiosp_description' );
    $fields[] = array( 'tag' => 'input', 'name' => 'aiosp_keywords' );
    $fields[] = array( 'tag' => 'input', 'name' => 'aiosp_custom_link' );

In V4 we can see all these fields are gone. But they have changed quite a lot. The difficulty is to be able to integrate with the new fields under aioseo-editor, for example:

<div class="aioseo-editor">
<div class="ql-toolbar ql-snow"><span class="ql-formats"></span></div>
<div class="aioseo-editor-single ql-container ql-snow"><div class="ql-editor" data-gramm="false" contenteditable="true">
<p>Title of my website</p>
</div>
<div class="ql-clipboard" contenteditable="true" tabindex="-1"></div>
<div class="ql-tooltip ql-hidden">...
<div class="aioseo-input">...

It doesn't seem trivial to just replace the values that are in the <p></p> tags, this is what we want to translate dynamically. I suppose you have also some JS code to handle the specific labels such as separator, title and so on which makes it more complex. I don't know what is the best solution. To do as usual, we'd need a way to update ourselves the whole field values, detect changes and read everything, But these don't look as standard form fields so i don't know if it's even feasible now. Another approach would be to have custom labels to handle the translation.

The crucial part is the edition of the translatable fields. For display such as the title snippet, we'd also need some kind of event to tell when the field value is changed so we can update the value to display (after translation).

[blw]

@arnaudbroes, any update on AIOSEO supporting this?

[arnaudbroes]

@blw not yet I'm afraid. We're not actively working on this but I'll discuss it with the team soon and get back to you.

[andreysneg]

Or Yoast. Or others SEO plugins. What is easier for work - is better.

Now only works good with qtranslate - All in one seo v3.7.1 . This version is enough for a normal SEO.

[bagaweb]

Or Yoast. Or others SEO plugins. What is easier for work - is better.

Now only works good with qtranslate - All in one seo v3.7.1 . This version is enough for a normal SEO.

Is this version safe? Or are there security problems?

[andreysneg]

Is this version safe - Don't know. I use it everywhere. no problem. PHP 8 compatible.

Attached. all-in-one-seo-pack.zip

[bagaweb]

Thanks @andreysneg

[arnaudbroes]

I've discussed this with the team and for now we've added this to our Feature Request site so that we track how much demand there is for QTranslate-XT. We'd love to work on this right away but unfortunately our resources are currently quite stretched so we'll first evaluate how many people are requesting support for this plugin.

We'll also continue keeping an eye on this thread so I advise anyone that would like us to add support for QTranslate-XT to at least leave a simple comment here so that we can reevaluate this periodically and move it up in our roadmap if needed.

[blw]

Where's the feature request site so I can go vote for it. Thanks.

[arnaudbroes]

Where's the feature request site so I can go vote for it. Thanks.

It's an internal tool. But just leaving a comment here, as you have already done, is enough and then I'll make sure to add it to our feature request tracker.

You can also submit a feature request here - https://aioseo.com/feature-suggestion/

[bagaweb]

I submitted the feature request on your page @arnaudbroes

[moskalukigor]

We'll also continue keeping an eye on this thread so I advise anyone that would like us to add support for QTranslate-XT to at least leave a simple comment here so that we can reevaluate this periodically and move it up in our roadmap if needed.

I will definitely subscribe to this topic. It is very important to add qtranslate-xt support. This is the most convenient multilingual plugin and I would not like to change it. So I'm looking forward to this integration.