• Resolved Markus Wiesenhofer

    (@markusfroehlich)


    A wpml-config.xml has been implemented in the new version 1.16.0. Since then, the sitemap.xml from Yoast Seo no longer works in conjunction with Polylang. The translated URL slugs are ignored.

    Best regards

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Does the issue go away if you remove the wpml-config.xml file? Curious how its presence is affecting Yoast + Polylang, because logically it shouldn’t.

    Thread Starter Markus Wiesenhofer

    (@markusfroehlich)

    Yes, when i rename the wpml-config.xml the issue go away.

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Looks like Polylang tries to use an existing wpml-config.xml file if one is present.

    https://polylang.pro/doc/the-wpml-config-xml-file/

    Polylang does support the WPML language configuration file wpml-config.xml to avoid double work for themes and plugins author.

    It is also possible for users to create their own wpml-config.xml file and to upload it in /wp-content/polylang/ (create the directory if it does not exist).

    I know in our copy, we try to present the options that we store things in as translatable, but admit that this is a very basic file thus far and may have potential implementation bugs too.

    I admit I didn’t expect that Polylang would pick up on the file.

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Ever get a final solution figured out here?

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.