Page ID filtering, multlingual

  • Resolved kitelab

    (@kitelab)


    5 years, 4 months ago

    Hi Jose, looks nice, your plugin, which we have not installed yet.

    Currently we use autoptimize, livan asset clean up, cache enabler (uses page-id’s for exceptions), woocommerce, and finally, most important: “qtranslate-x” with “slug-translate”.
    Which means that in wordpress-backend there’s one single page per language ( [:de]deutscher text[:en]english text[:] ) but with 2 different manually written urls on the public site.

    Does Freesoul use the url in any case or would there be a chance to use the wordpress-page-ID for filtering the plugins?

    What do you think: Would we have to make the settings 2 times per page with Freesoul (for each language separately) or just 1 time per page?
    This is an example page, it’s one single page with one ID in wordpress backend, but on frontend it’s this:
    https://www.horvath.ch/en/infos-zerowind-kites/ = https://www.horvath.ch/de/infos-nullwind-drachen/

    We used the mu-plugin “plugin logic” in the past, but unfortunatly had to list all the urls for our 2 languages, which was too error-prone.

    Thanks and best regards … Thomas

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Jose

    (@giuse)

    Hi @kitelab, thank you for your questions.

    The actual version of Freesoul Deactivate Plugins uses the WordPress core function get_page_by_path to fetch the page ID. I know this function doesn’t work if custom rewrite rules are defined.

    Once Freesoul Deactivate Plugins knows the page ID, it all depends on how the translation plugin works.
    Usually, each translated page has its own ID, in this case, you will need to set the enable/disabled plugins for the pages of each language. I don’t think qtranslate-x maganges manages the translations without having dedicated pages (so different page IDs).

    I’ve tested FDP with Polylang, WPML Multilingual CMS and Translate Press, but unfortunately never with qtranslate-x. If using q-translate-x some issues occur, of course, don’t hesitate to open a thread, I will be happy to check.

    As said Freesoul Deactivate Plugins uses the function get_page_by_path to fetch the page ID. I know this function doesn’t work if custom rewrite rules are defined.
    Freesoul Deactivate Plugins is not compatible e.g. with plugins as Permalink Manager Lite. So I’m afraid it will not work with slug-translate.

    I don’t exclude that in the future I will add compatibility with custom rewrite rules, but at the moment it’s not so, and I can’t say when it will be compatible.

    If you have other questions, don’t hesitate to ask.

    Best regards

    Jose

    Thread Starter kitelab

    (@kitelab)

    Hi Jose, thanks for your kind and detailed answer.
    We will test all the things in future.

    Btw. I’m still convinced that the language tagging

    [:en]english text[:de]deutscher Text[:]

    within pages is clever (think of product stocks etc.).
    Anything translates in an easy way without doubling (or x-times) the page count.

    Enjoy your evening, have a marvelous flight … Thomas

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Page ID filtering, multlingual’ is closed to new replies.