• Resolved Chris.V

    (@chrisv234)


    Hi,

    I have the same issue described in this post https://www.ads-software.com/support/topic/polylang-issue-with-menu-sections/. The post is marked as “resolved” but no solution is provided.

    Any updates on this issue?

    The best workaround I found is to create one menu for each language you use and add them on separated pages. Do not link menus/sections/menu-items with each other. Just link the final pages you made so the right menu appears when changing language.

    Regards,

    Chris

    • This topic was modified 1 year, 5 months ago by Chris.V.
    • This topic was modified 1 year, 5 months ago by Chris.V.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support jaysupport

    (@jaysupport)

    Hi Chris,

    Given that, the way menu is designed to be used, there shouldn’t usually be any reason to have people publicly visiting the taxonomy archive pages for the menu sections, I’d say that you workaround provides pretty much all the functionality you require.

    As for why your issue is happening, I’m not certain. We don’t normally run tests specifically with Polylang. The sections are a registered taxonomy, so, as long as Polylang supports the translation of taxonomy terms, it should work the same as translating any other taxonomy. Is there some kind of option in Polylang that lets you enable specific taxonomies or taxonomy terms? If so, can you check to make sure ours is correctly enabled?

    You can also try enabling debugging in WordPress (https://www.ads-software.com/documentation/article/debugging-in-wordpress/). Then go through the process again, until it erases your menu layout, and see if it displays any errors. If not, check the debug log to see if there are any relevant errors in there (hopefully with reference to a specific file in our plugin with a line number) and share that here.

    Thread Starter Chris.V

    (@chrisv234)

    While I agree that people have no reason to visit any taxonomy pages, this issue does affect the way the section is displayed on the front end. While all the items in your dedicated menu page (containing the shortcode) will be displayed in the correct language, the menu section that a user clicks to scroll on the desired section is being displayed in the wrong language.

    Related screenshot with the said issue: https://i.ibb.co/XsXWrYg/Screenshot-1.jpg

    Polylang includes an option for ‘Custom post types and Taxonomies’ but it is deactivated. In order to activate it the theme/plugin must use the same actions and filters as WordPress. I don’t know if this is the case with the Five Star Restaurant plugin. More info at this link: https://polylang.pro/doc/multilingual-custom-post-types-and-taxonomies/

    • This reply was modified 1 year, 5 months ago by Chris.V.
    • This reply was modified 1 year, 5 months ago by Chris.V.
    • This reply was modified 1 year, 5 months ago by Chris.V.
    Plugin Support jaysupport

    (@jaysupport)

    Does Polylang provide a way to search for and translate specific strings (like WPML’s string translation extension)? Perhaps you can search for Fish (and any other section names) that way and translate all instances that you find.

    Thread Starter Chris.V

    (@chrisv234)

    Unfortunately in the free version, Polylang, does not offer a way to search and translate those specific strings. For now I will go with my workaround. Thanks for the fast reply!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Polylang issue with menu sections’ is closed to new replies.