.wp-die-message madness after update to v.4

Hi @kappekappesantecom,

Thanks for contacting us, and I’m sorry for the delay. We’re working on a backlog of support requests at this time, and we generally answer in the order received.

Could you also please post your site URL here so that we can have a look?

If you want it to remain private, you can also contact us via?contact form. Please include a link to this thread if you choose to contact us privately.

From your description, it sounds like there might be a conflict after updating to version 4 of Jetpack Social that is affecting the CSS on your site.

In order to provide you with the most accurate assistance, it would also be helpful if you elaborated on the specific CSS issues and console errors you are encountering. You can use screenshots to give us more details as shown here: https://wordpress.com/support/make-a-screenshot/.

Thank you!

Hi?@kappekappesantecom,

Do you have updates about that? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

i’m overriding a lot of stuff. example: https://www.federicobenuzzi.com/preferisce-messi-o-ronaldo/

any blog post comes with a lot of errors like these

[Error] ReferenceError: Can't find variable: _
Codice globale (preferisce-messi-o-ronaldo:1018)
[Error] ReferenceError: Can't find variable: wp
Codice globale (preferisce-messi-o-ronaldo:1027)
[Error] ReferenceError: Can't find variable: wp
(funzione anonima) (preferisce-messi-o-ronaldo:1034)
Codice globale (preferisce-messi-o-ronaldo:1035)
[Error] ReferenceError: Can't find variable: wp
Codice globale (preferisce-messi-o-ronaldo:1039)
[Error] ReferenceError: Can't find variable: wp
(funzione anonima) (preferisce-messi-o-ronaldo:1051)
Codice globale (preferisce-messi-o-ronaldo:1052)
[Error] ReferenceError: Can't find variable: wp
(funzione anonima) (preferisce-messi-o-ronaldo:1067)
Codice globale (preferisce-messi-o-ronaldo:1068)
[Error] ReferenceError: Can't find variable: wp
(funzione anonima) (preferisce-messi-o-ronaldo:1080)
Codice globale (preferisce-messi-o-ronaldo:1082)
[Error] ReferenceError: Can't find variable: wp
(funzione anonima) (preferisce-messi-o-ronaldo:1090)
Codice globale (preferisce-messi-o-ronaldo:1091)
[Error] ReferenceError: Can't find variable: moment
Codice globale (preferisce-messi-o-ronaldo:1096)
[Error] ReferenceError: Can't find variable: wp
Codice globale (preferisce-messi-o-ronaldo:1100)
[Error] ReferenceError: Can't find variable: wp
(funzione anonima) (preferisce-messi-o-ronaldo:1107)
Codice globale (preferisce-messi-o-ronaldo:1108)
[Error] ReferenceError: Can't find variable: wp
(funzione anonima) (preferisce-messi-o-ronaldo:1116)
Codice globale (preferisce-messi-o-ronaldo:1117)
[Error] ReferenceError: Can't find variable: wp
(funzione anonima) (preferisce-messi-o-ronaldo:1125)
Codice globale (preferisce-messi-o-ronaldo:1126)
[Error] ReferenceError: Can't find variable: wp
(funzione anonima) (preferisce-messi-o-ronaldo:1135)
Codice globale (preferisce-messi-o-ronaldo:1136)
[Error] ReferenceError: Can't find variable: wp
(funzione anonima) (preferisce-messi-o-ronaldo:1143)
Codice globale (preferisce-messi-o-ronaldo:1146)
[Error] ReferenceError: Can't find variable: wp
(funzione anonima) (preferisce-messi-o-ronaldo:1155)
Codice globale (preferisce-messi-o-ronaldo:1156)

deactivating jetpack makes the errors disappear

Hi @kappekappesantecom

Can you share a link where you are seeing those errors? I tried browsing the example link you have shared; however, it didn’t load the first time and showed a “Secure Connection Error”, then the page loaded without issues and with no errors mentioned although Jetpack is connected to your website.

Best,

please take a look at the console

https://www.federicobenuzzi.com/preferisce-messi-o-ronaldo/

https://www.federicobenuzzi.com/un-lungo-viaggio/

https://www.federicobenuzzi.com/fortuna-che-ce/

Ciao @kappekappesantecom,

I can see the ReferenceError: wp is not defined (I don’t see that in Italian on my browser, but that’s the same error) on the posts you linked.

This is usually due to a plugin conflict, which would also explain why it goes away when you deactivate Jetpack – something is not going along with Jetpack.

Can you please temporarily deactivate all your plugins and check if the problem gets fixed that way? If it works, then reactivate each plugin one by one to find out which one is causing problems.

Let me know what you find out! A presto ??

the issue is solved avoiding deferring many js stuff, but honestly i dont like this solution.. my console is clean now, but a lot of js is not deferred. i give up because its not easy to determine which js is actually causing errors.

i didnt defer lodash.min.js, moment-js-after, the infamous wp-i18n-js-after and then i just disabled the deferring. too much hassle.

so, it might be perfmatters was not deferring the right stuff in the right way, or it’s just impossible to do it right.

Hi @kappekappesantecom,

I’d agree that’s not the best solution at all: when dealing with issues related to JavaScript deferral and dependency management, it can indeed be tricky to find the correct balance between optimization and functionality. That’s also why I’d loved to make sure that no other plugins were in conflict with Jetpack – it could also be a theme conflict, which we haven’t ruled out yet, right?

Scripts like?wp-i18n, which you mentioned, have dependencies on other scripts like?wp-element?or?wp-blocks. These scripts should be loaded in the correct order to ensure that dependencies are fulfilled. The?wp?object is a part of the WordPress Core JavaScript library, which is likely a dependency for multiple scripts. It’s important not to defer scripts that have other scripts depending on them.

If you are happy to do that and have some time to dig further, I’d encourage you to set up a staging environment if you haven’t already. This allows for more aggressive testing without affecting their live site. You can try to selectively defer scripts one at a time and check for functionality and errors.

Hope it gives you some more troubleshooting ideas!

Hi,

I’m having the same issue. I don’t have any error in the console, but basically after Jetpack activation, the CSS get fucked up.

wp-die-message is apply neraly everywhere

I try to de-activate all plugin. Issue appaear right after enabling Jetpack (all other are deactivated)

• This reply was modified 8 months, 2 weeks ago by fifipil909.

the only safe way is to override css. or just disable it, but after so much time i haven’t found an alternative. quite frustrating, it’s for only one single fricking client and i’ve lost too much time on that.