@jsoko @andreaborin @radimdolezal @tele0
We were able to get the styles back by disabling the Polylang plugin. It looks like this plugin is used on the sites mentioned here.
While we are still looking at possible solutions, it should be noted that we don’t do anything particularly unique with our loading of styles. We recently changed it to match the way the core block editor is loading styles.
You’ll want to reach out to Polylang and point them to this thread to see if they have any insights. We’ll be happy to share whatever info we have with them to expedite a fix.
Ok. I’ll reach polylang.
Have you finished your research on my site; can I reaktivate 2.4 and polylang?
Yes you can revert back now. Thanks so much for letting us experiment on your site! We’ll keep you updated on the progress.
Hello,
@atomicblocks
I’m running into this error as well. Right now it’s just the one website i’ve logged into today. I’ll be checking others.
https://genmac.packerlandwebsites.com/
@tommnorm It seems that your site doen’t use the polylang plugin. Is that right?
@atomicblocks
Would you mind to have another look to that issue?
That’s what’s been postet at polylang:
https://ww.wp.xz.cn/support/topic/malfunction-together-with-atomic-blocks-2-5/#post-12436161
Guys, Polylang does not prevent styles from being output on the front end.
Polylang is just for working with translated content and does not do anything on frontpage layout.
I had a quick look at the code and maybe you should investigate deeper the part with plugins_url. Polylang does modify the URL with the language code. Maybe the result for plugins_url is without the Polylang rewrite? If so, the style can not beloaded because the URL is wrong. I would check this first.
https://github.com/studiopress/atomic-blocks/issues/308
-
This reply was modified 6 years, 3 months ago by
jsoko.
-
This reply was modified 6 years, 3 months ago by jsoko.
-
This reply was modified 6 years, 3 months ago by jsoko.
-
This reply was modified 6 years, 3 months ago by jsoko.
Same issue here. The latest update to 2.5.1 broke the AB Blocks when using Chrome 79.0.3945.130 under macOS 10.15.3 and having Polylang 2.6.9 installed. Rolling back the plugin to version 2.4.0 solved the issue for me.
Same issue with AB Post and Page Grid and in general with all columns layout.
Still problem with compatibility between AtominBLock and Polylang. Maybe time for dont use both of plugins?
How can a multilanguage plugin create layout issues? Besides, I haven’t updated polylang while only after updating AB the issue appears. So what ever it is that is causing the problem AB should fix it.
Maybe someone who is better in coding than me can have a look at the PRs 288-302?
https://github.com/studiopress/atomic-blocks/pulls?q=is%3Apr+is%3Aclosed
I’m not using the poly plugin. And rolling back to 2.4 didn’t solve the issue.
Hey folks, we’re still looking at this. It’s unfortunate that Polylang isn’t providing any support on the forums.
@tommnorm Would you be willing to share a login with us so we can diagnose further? If so, you can send to mike.mcalister at wpengine.com and I’ll take a look this morning!
@outcats85 You’d be surprised how many of the language switching plugins can break other plugins and themes.
