Cécile J.
Forum Replies Created
-
Bonjour Sophie,
Idem ici (O2switch aussi). De mon côté, j’ai opté pour la désactivation de l’affichage de santé du site sur mon tableau de bord parce que j’en ai marre de voir ces pseudos recommandations qui sont parfois des faux négatifs ou qui font sauter le site et me font stresser pour rien 😀Hi
Thank you for your reply. I thought my message was not saved here and I’ve sent a message to your support dpt which have already reply to me. All is ok now and it was due to the Google Tag Manager which was duplicated 🙂
Forum: Reviews
In reply to: [Site Kit by Google - Analytics, Search Console, AdSense, Speed] Good supportHi James,
I appreciate your prompt react! I’ve check where the problem could come from by clicking on help, but it was told to check for an incompatibily with a plugin, and I haven’t time to do it (because for some of theme I have to redo setting 🙁 ). I must admit that I was a little rushed and annoyed 😀 . It was a question of “client ID” which did not work and refused any configuration. When you have read my answer, I will remove this star because your plugin is installed on another of my sites and it works correctly. WPML may be the plugin that could be the problem because it’s the only difference with the site that works and this plugin often affects urls.
Ok, thank you for these explainations
Have a good day
Hi,
The problem is always here! Just before I have checked the WPML Media translation center, my website (front only) broke down to error 500. When I have deactivated Yoast, all has came back. So the problem could come from WPML (I wouldn’t be surprised because, the behavior of this plugin is really special).Hello Kris,
Thank you for your prompt response. I may be a little naive but is it possible that the robots manage to pass the answers that are marked as required ? This is what questions me.
Have a good day
CécileForum: Fixing WordPress
In reply to: Warning: Attempt to read property “post_status” on null inDear @locoleader
These little bits of code seem very ridiculous in the face of this terrible tragedy. All my thoughts go out to you and your loved ones.Take care of yourself
Forum: Fixing WordPress
In reply to: Warning: Attempt to read property “post_status” on null inHey !
Thank you @locoleader for this sharing. I had the problem too ! And it was the solution. What I have learned is : be careful when you export a Divi template from one website to another because it comes with all the package 😉
Hi team,
Unfortunetly, the problem has came again ! I was working in the divi customizer and suddenly my website (in front) shutdown in error 500. In the instant I have deactivated Yoast, and all has coming back. May be a problem with DIVI ?
Hello !
It’s ok for me.
Thank you
Hi Maybellyne,
Thank you for your reply.
I’ve checked the error logs in my server logs and in the WordPress logs but it seems that nothing (known) appears about you plugin. The only think I can tell you is that I have Yoast 20.0 installed in 6 others website and it seems that they have no problem. The website with problem possess WPML and I expect that the problem could come from an incompatibility between you two.
Unfortunetly I don’t understand what you expect from me about this line 84 to be changed
Thank you
CécileHello Stéphane,
Merci pour ta réponse, j’ai finalement conservé Colissimo en évitant l’import-export des données qui semble avoir causé le problème. Pour le moment, ça tient mais je le surveille 😉
- This reply was modified 3 years, 4 months ago by Cécile J..
Hi Patrick,
Thank you for your fast and complete reply. Unfortunetly this option is too complicated for me 😉 It does’nt matter.
Have a nice day,Cécile
Hi,
I come back with exactly the same error logs. It was not the % – I have reactivated the plugin few hours ago but the errors appears now (after around 8/9 hours…) May be the plugin try to lanch a task at this moment.
I deactivate it.- This reply was modified 3 years, 5 months ago by Cécile J..
😀 Sorry ! Apparently I wasn’t concentrating. Indeed the French translation is not fair and there was indeed a % too much. I corrected and I will put the file back and reactivate the plugin. I will come back to confirm if it is ok.
Thanks