Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • Thread Starter vivien streit

    (@vivien-streit)

    Thank for your answear.

    What I want is to redirect http://vivialix3.16mb.com/ directly to http://www.vivialix3.16mb.com/en/. So redirect non-www to www with correct extension language without an intermediate step. This was perviously the case before I instal WPFC. I don’t know if the intermediate step is neeeded for WPFC.

    Thread Starter vivien streit

    (@vivien-streit)

    Thank you for you answer.

    As I have no notion in arabic I read your article with google translate. But, if I’m right, you doesn’t talk about the function pll_register_string which I’m trying to call from inside a widget method.

    Have you more information about this case?

    Thread Starter vivien streit

    (@vivien-streit)

    Hi Alex,

    I just updated page Builder to 2.4.15 version. It works perfectly ! Thanks to the teams for the bug fix. 🙂

    Bests

    Thread Starter vivien streit

    (@vivien-streit)

    Hi Alex,

    Great news! Thank you very much for your reactivity and your work! I look forward to the new version of PageBuilder 🙂

    Bests

    Thread Starter vivien streit

    (@vivien-streit)

    Hi Alex,

    Thank you. No problem, really. I’m not in a hurry 🙂

    Thread Starter vivien streit

    (@vivien-streit)

    Hi Alex,

    Yes I have try with both latest version.

    You can found here a table that resume all the test I performed on a website with only Pagebuilder, Polylang, and Virtue Premium as theme.

    The different tests made me think that the problem come from PageBuilder 2.4.10 when PolyLang (any version is active) and the permalink are set to custom.

    Thread Starter vivien streit

    (@vivien-streit)

    Hi Alex,

    I pretty sure that PageBuilder 2.4.10 introduced something that conflict with PolyLang. Indeed, the permalink was fine and I only update PageBuilder from 2.4.9 to 2.4.10 and after saving permalink the bug happens. (If I save parmalink with PageBuilder 2.4.9 the bug does not occur.)

    However I will set a completely new WordPress installation with only the keys factors I identified and perform the installation of the plugin with FTP (it may be that the update of PageBuilder 2.4.9 went wrong and that the code corresponded to a earlier versions).

    I let you know when it is done. This won’t be before a few hours has I haven’t currently access to a computer.

    Thanks for your support!

    Thread Starter vivien streit

    (@vivien-streit)

    Hi Alex,
    Thank you for your answer.

    If I save the permalink (option: Custom: /%postname%_%day%-%monthnum%-%year%/) the bug is not resolved.

    If I deactivate Page Builder and save permalink, the custom post permalink work again.

    I found out that this bug only happens when:

    • Page builder 2.4.10 is active (Page builder 2.4.9 doesn’t provoke this bug)
    • and polylang is active
    • and permalink set to another option than Plain
    Thread Starter vivien streit

    (@vivien-streit)

    *I forget to said that I’m also sure that it’s the upadate of Page Builder that cause the bug, because when I have page builder at version 2.0.7 and i update to 2.1.2 then resaved permalink the bug occured.

    Thread Starter vivien streit

    (@vivien-streit)

    Ok, after a lot of try i now when the bug occured !
    Here are the conditions:

    -Polylang active either version (i tested with 1.7.2 or 1.7.3)
    -Page Builder by SiteOrigin 2.1.2
    -Permalink set as Custom Structure
    -Theme: Virtue Premium (because the bug occure on the portfolio provide by this theme)

    *Note: that the tricky things is that the bug appear only after i resave permalink with the above conditions… (take ma a long time to figure)
    *Note2: test performed under WP4.1.1

    -If I desactivate Polylang bug is fixed
    -If I desactivate PageBuilder 2.1.2 & resaved permalinks after that, bug is fixed
    -If I set permalink to default bug is fixed
    What I conclude is that “Page Builder by siteOrigin 2.1.2” introduce a conflict with polylang on the permalinks to portfolio. I’m not sure of exactly wich upadate of Page Builder introducte the bug, but it’s a version higher then 2.0.7.

    To be sure of what I said, I performed a test: I recreate a new website with only the conditions that I present above leaving all things i can to default (no other plugin then polylang & Page Builder ever install on this website) and the bug occured.

    Thread Starter vivien streit

    (@vivien-streit)

    Hello,

    I have also tried to uninstall polylang and to put an older version but problem stay the same. So i’m suspecting that’s it’s perhaps a plugin that uninstalled incorrectly and some code or data somwhere.

    I restore my website from a stable save. I will also put the same save on a test website and try to see exactly witch plugin or theme update cause the problem.

    I let you know what i found.

    Best
    Vivien

    Thread Starter vivien streit

    (@vivien-streit)

    Hi,

    I had help from the virtue developement team. Here what they said.

    I did some testing, polylang is just conflicting with the permalinks. everything is fine if your settings are default in the permalinks page.

    That way all is ok, so I use for now default settings for permalinks. But i really like using pretty permalinks, it would be great if i can use pretty permalinks again! In the case you plan to correct this issue (when using language set from the subdomain name in pretty permalink) I would be at your disposal for tests needed.

    Thanks again for help and for this plugin
    Vivien

    Thread Starter vivien streit

    (@vivien-streit)

    Thanks to take care of my problem.

    1) I’m not sure of what you mean by “resave your permalinks”. I resave (=submit) all my portfolio. Did you mean that? But bug is stil here.

    2) Yes my portfolio are provide by my theme. I have desactived all other plugin. Unfortunately links to portfolio are still broken. Just to be sure I desactivate polylang and in this case links are ok.

    *I’m currently using polylang version 1.7.3.5

    Let me now for further test i can do
    Thanks in advance
    Vivien

    Thread Starter vivien streit

    (@vivien-streit)

    Just to calrify my settings:
    – theme: virtue premium
    – The language is set from the directory name in pretty permalinks
    – static home page
    – Delete / language / in permalinks
    – The management of the languages and the translations for the media is desacivate

    I also want to add that I’m very gratefull for the devloppment of this great plugin !

Viewing 14 replies - 1 through 14 (of 14 total)