Hi Ismael,

I have contacted a WPML supporter. This is the conclusion from that message:

They added this piece of code to the XML editor:

<wpml-config>
  <shortcodes>
    <shortcode>
      <tag>av_textblock</tag>
      <attributes>
        <attribute>fold_more</attribute>
      </attributes>
    </shortcode>
  </shortcodes>
</wpml-config>

https://wpml.org/documentation/support/language-configuration-files/ > based on this documentation. Perhaps this could be added to a future release?

Hi both,

Thanks for the reply. The read more text translations are what seems to be for the placeholder text. But since I will put in my own custom language ‘Lees meer’ and ‘Lees minder’ this does not get recognised in the Advanced Translation Editor of WPML. I would be able to manually edit the page and add the translation there myself, but since that is not recommended by WPML, I would not want to use that method.

It seems the translations of the block is not being passed to WPML properly. Is this something I would have to contact them about, or should this be an Enfold feature?

TL;DR: So I would like to have a different translation for the ‘Read more’ and ‘Read less’ in 2 languages.

Kind regards,
Joost

Hi Mike,

Thanks for your reply! Noted that we can’t change the avia-element-paging name! For the SEO best practice, this was regarding this sentence:
Don’t use the first page of a paginated sequence as the canonical page. Instead, give each page in its own canonical URL.

The blog on our page has the following slug: /blog/?avia-element-paging=2 but the canonical URL for this is still https://grandia-aankoopmakelaars.nl/blog/. According to Google’s best practice for paging, this should be:
“Google is very clear now: each page within a paginated series should canonicalize to itself, so /page/2/ has a canonical pointing to /page/2/.”

We have the Yoast plug-in installed at this moment, but that does not seem to be adding the right canonical url to the pagination page. What could I do for this issue to work?

Kind regard,
Joost

It seems the issue only occurs when using the Block Editor instead of the old editor.