• Resolved JSin

    (@jsin)


    I posted a reply in this thread and was told to make my own, so here it is.

    Basically, several people in the previous thread spoke of an issue they all encountered, where Yoast being enabled when hosting servers upgraded to PHP 7.2 — namely that the HTML editor had issues, including the toolbar disappearing entirely. I also encountered this, and here is my comment from that thread:

    Hi, all – this is NOT resolved. I came across this thread and upgraded anyway to observe what might happen. Just like @miqser said, the exact same thing happened to my editor.

    I did what @devnihil and @amboutwe suggested and followed the instructions for How to Check for Plugin Conflicts.

    For the sake of being thorough, these were the following plugins installed on my site:

    • Accelerated Mobile Pages
    • Advanced Custom Fields PRO
    • Better Font Awesome
    • Contact Form DB
    • Contact Form 7
    • Cornerstone
    • Custom Post Type UI
    • GitHub Updater
    • Health Check & Troubleshooting
    • Icegram – Popups, Optins, CTAs & lot more…
    • WPBakery Page Builder
    • PHP Compatibility Checker
    • Redirection
    • Slider Revolution
    • Yoast SEO
    • WP All Export
    • WP Responsive Photo Gallery
    • Smush Pro
    • WP Sync DB
    • WP Sync DB Media Files
    • WPMU DEV Dashboard

    The steps I took were:

    1. Disabled all site plugins
    2. Verified the issue was no longer occurring
    3. Enabled Yoast SEO
    4. Observed that the problem still did not occur
    5. Went through enabling one plugin at a time, then refreshing the “Add New Page” and seeing if the issue of which @miqser occurred
    6. If I saw the toolbar, I kept that plugin enabled and then would enable another. If I enabled a plugin and the toolbar went away, I disabled it and tried again, observing that the toolbar came back. I’d then move on to the next plugin and repeat this process.

    In the end, all of the bolded plugins above caused the toolbar to disappear if Yoast is enabled.

    I don’t think that this is a circumstance of all these individual plugins having their own separate issues, because the common thread is that they all work (all together even) until Yoast is enabled, meaning that it’s something within there causing the conflict.

    Hoping someone can resolve this issue.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support amboutwe

    (@amboutwe)

    Thank you for starting a new topic. The next step is to check the browser console for JavaScript errors in the various setups you identified. How to find JavaScript errors with your browsers console?

    Using the Health Check plugin, please check for JavaScript errors in the following environments:

    1. Default environment (no active plugins on a default theme like Twenty Nineteen)
    2. Yoast SEO on a default theme
    3. Yoast SEO with Advanced Custom Fields PRO on a default theme
    4. Yoast SEO with Contact Form DB on a default theme
    5. Yoast SEO with Custom Post Type UI on a default theme
    6. Yoast SEO with WPBakery Page Builder on a default theme
    7. Yoast SEO with Slider Revolution on a default theme
    8. Theme environment (no active plugins on your preferred theme)
    9. Yoast SEO on your preferred theme
    10. Yoast SEO with Advanced Custom Fields PRO on your preferred theme
    11. Yoast SEO with Contact Form DB on your preferred theme
    12. Yoast SEO with Custom Post Type UI on your preferred theme
    13. Yoast SEO with WPBakery Page Builder on your preferred theme
    14. Yoast SEO with Slider Revolution on your preferred theme

    If your preferred theme is a child theme, please repeat the JavaScript checks for the parent theme as well.

    Please provide each Javascript error(s) that you encounter in the above environments. Screenshots are acceptable if you see multiple errors in a particular environment.

    Additionally, please provide the following information:

    • WordPress version
    • Default theme and version
    • Preferred theme and version
    • Parent theme and version, if preferred theme is a child theme
    • Yoast SEO version
    • Advanced Custom Fields PRO version
    • Contact Form DB version
    • Custom Post Type UI version
    • WPBakery Page Builder version
    • Slider Revolution version
    • This reply was modified 6 years, 4 months ago by amboutwe. Reason: Add 's' to plugin making it plugins
    • This reply was modified 6 years, 4 months ago by amboutwe.
    • This reply was modified 6 years, 4 months ago by amboutwe. Reason: Add link to 2019 theme
    Thread Starter JSin

    (@jsin)

    Thank you. I will get to the above as soon as possible and report back here thereafter.

    Thread Starter JSin

    (@jsin)

    Hi all – I will get to this first thing tomorrow morning. My apologies. Please do not yet close this.

    Thread Starter JSin

    (@jsin)

    Due to emergencies at work, I won’t be able to get to this until next week.

    Plugin Support devnihil

    (@devnihil)

    @jsin Thanks for the update. Please let us know the results once you’ve had a chance to check for conflicts and javascript errors.

    Plugin Support amboutwe

    (@amboutwe)

    We understand being busy so we’ll set this to resolved, for now. It helps limit the list of topics our team reviews. When you have more information, please set it to unresolved and it will appear in our list again.

    Thread Starter JSin

    (@jsin)

    Hi, all! I’ve resolved this on my end but wanted to update this ticket since it shows up in search engine results.

    Basically, I was wrong. It is not Yoast giving the issues. I was able to verify this by installing a new WordPress install altogether, and systematically only installing/activating one plugin at a time (starting with Yoast, btw) on a default theme, then refreshing the Add New Page of WordPress.

    What I did learn is that a browser plugin I had for Chrome was actually the issue at hand! Imagine that! Somehow, Typio Form Recovery for Chrome (which saves text as you type, in case your browser crashes in the middle of a long thing you were typing up, such as this very reply here) was the cause.

    Again, I verified this by disabling one browser extension at a time and refreshing the page. It was only with this browser extension disabled that everything worked as intended.

    In short, sorry for wasting your time, but know that Yoast works with 7.2, verified — quite extensively, even — by myself.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Yoast not compatible with PHP 7.2’ is closed to new replies.