tcorrea
Forum Replies Created
-
I have finally had enough time to look into the issue details. From 1.4.6 on wards (including latest 1.5.5) the URL is inside esc_url (looks like most of this version chances were esc_ related). The problem is, my links were child page names, or, in other words, relative links. The previous working version would generate hrefs=”MyProductName” and that is a child page from the current page where the catalog is called.
What esc_url did was append it with https:// on it’s own. The docs doesn’t say it would do that, but it does. Perhaps a bug in WordPress. Either way, reverting that change I got 1.5.5 to work.
Forum: Plugins
In reply to: [Download Manager] Missing fileThanks for looking into it.
No, they both have http, but 1.4.5 uses the current page + custom link, while 1.4.6 doesn’t use the current page path.
Real example, with 1.4.5:
https://www.comm5.com.br/produtos/modulos-de-acionamento/MA-5000-2with 1.4.6 it gives:
https://ma-5000-2Obviously the page that contains the catalog is in https://www.comm5.com.br/produtos/modulos-de-acionamento on both cases.
I can’t break my site and send you an email with the broken site for you to check, I would be annoying my customers. Please do a git diff on whatever code that generates the link and see where the unintended change is.
Forum: Plugins
In reply to: [Product Catalog for WordPress] Polylang or gettext supportHi Support.
Having different catalogs can solve the problem of different language texts in the product description, yes.
But the text that is entered in the General Options not possible to be translated into multiple languages at the same time for a multi language site. That’s the “bug” with no workarounds. ??
Will this ever be solved?If you were to use PolyLang API it would be easy to check if pll_register_string is available and call it to leave translations to the plugin.
Forum: Plugins
In reply to: [Product Catalog for WordPress] Polylang or gettext supportWhich is both insufficient for a multi language site with a language switch in the front-end.
The “View Product” string can’t be changed to a single value in the General Options. It has to be “View Product” in English, “Ver Produto” in Portuguese and so on.
The pot file is a proper solution, yes, but it’s not available to the front-end text which is what really matters.
Is there any way to support multiple languages on the front end (visitor switchable)? Or are there any plans to do so?