This thread is over two years old and may be outdated. Please create a new thread if you need help, or email us if you have an active Premium license.

Update from 2.4.9 to 2.4.10 broke multilingual permalinks from polylang

Open 8 replies bug-reportpluginplugin-page-builder
David Faber
9 years ago · Last reply by Greg Priday 9 years ago

Hi there,
I’m not sure which plugin-update it is:
– Page Builder by SiteOrigin 2.4.9 -> 2.4.10 OR
– SiteOrigin Widgets Bundle 1.6.1 -> 1.6.2

But one of these updates breakes my multilingual custom post type permalinks. Somehow the language prefix on the url (e.g. http://some.url/en/projects/foobar) makes the page result in an 404 page. For internationalisation I use the plugin Polylang (https://wordpress.org/plugins/polylang/). It tested a lot, but it is definitely one of those two plugins.

If you need any more details, please let me know.

Thx,
David

This is our free support forum. Replies can take several days.

Need fast email support? Get SiteOrigin Premium

Replies

8
  1. hugodebe 9 years, 7 months ago

    Thanks David for the report. I currently work on a fresh new install with Polylang + WooCommerce and they can bring some problems together, so I tested for hours without suspecting Page Builder to mess permalinks. Version 2.4.9 works fine for me.

    SiteOrigin – Free WordPress Themes and Plugins rel=”nofollow”>My thread: Page: SiteOrigin – Free WordPress Themes and Plugins

  2. Andrew Misplon Staff 9 years, 7 months ago

    Hi everyone

    URL’s seem to be working normally for me in local testing with Page Builder 2.4.10 and Polylang 1.9.3 and Widgets Bundle 1.6.3 and WooCommerce 2.6.3.

    David, have you tested with all plugins deactivated except for Page Builder and Polylang? Saving Permalinks from SettingsPermalinks to rewrite the htacess file might also be worth a try.

  3. Cyril Arnaud 9 years, 5 months ago

    Hi Andrew,
    I’m using Polylang 2.0.3 and Page Builder 2.4.13 and I had the same problem as reported by David.
    The only difference is that I had the problem with events created with Event Maker from dfactory and not with woocommerce (I’m not using woocommerce on this website).

    I downgraded page builder to 2.4.9, refreshed the permalinks settings and everything is working again.

    Should you re-open this issue or should I open a new thread ?

    Thanks

    Ref : https://wordpress.org/support/topic/polyang-and-events-maker-give-me-error-404

  4. Andrew Misplon Staff 9 years, 5 months ago

    Hi Cyril

    Thanks for reaching out. The team took a long look at this issue this morning. In the next Page Builder update we’ll introduce an option to disable sidebar emulation for Page Builder wigdets. It will fix the issue but might cause widget issues in Page Builder, users will need to test to see if that happens, it isn’t a given and depends on the widgets.

    Here is the commit: https://github.com/siteorigin/siteorigin-panels/commit/ad004d05205db418216d6d2029f98f5c90dd117d

    The new option will be in the General tab at SettingsPage Builder in the next release.

  5. Cyril Arnaud 9 years, 5 months ago

    Thanks

    I’ll make sure to test it out and report back here.

  6. Andrew Misplon Staff 9 years, 5 months ago

    Thanks :)

  7. Cyril Arnaud 9 years, 5 months ago

    Hi,
    I just upgraded Page Builder to 2.9.14 and the option Sidebars Emulator is activated by default.
    And even with the option activated by default everything seems to work perfectly.

    I’ll continue testing but everything seems fine.

    Thanks

  8. Greg Priday Staff 9 years, 5 months ago

    Hi Cyril

    Thanks for the feedback! The option to disable the sidebars emulator was just a precautionary measure in case any incompatibilities like this come up in the future. We were able to solve this particular issue though, so you can leave the emulator enabled :)

Replies on this thread are closed.

Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Have a different question or issue?

Start New Thread