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.

Stopped working after WordPress update..

Resolved 7 replies bug-reportpluginplugin-page-builder
Tim Rogers
Started · Latest reply by Andrew Misplon

As the previous poster mentioned SiteOrigin has stopped working after the latest wordpress update. While it renders on the front end of the site, it will not load in the admin area / editor.

As is usual I have tried deactivating plugins and changing theme but without any success. Its this a problem that you are seeing elsewhere?

Tim R

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

Need fast email support? Get SiteOrigin Premium

Replies

7
  1. Andrew Misplon Staff

    Hi Tim

    This isn’t an issue we can replicate.

    If the issue persists with all other plugins deactivated and a default theme, please, check for JS errors, if there are any, screenshot, upload to imgur.com or any sharing site and send us the link. https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis. If you normally use the Classic Editor plugin it can stay activated during this test.

    Additionally, enable debug and debug log, replicate the issue, check the log file and let us know what’s there. This is an intermediate level task but necessary if you can’t establish a working baseline. https://www.wpbeginner.com/wp-tutorials/how-to-set-up-wordpress-error-logs-in-wp-config/

  2. Tim Rogers

    Hi Andrew,

    I tried to add post this but couldn’t

    Uncaught TypeError: Cannot read property ‘getBlocks’ of null
    at t.isAnnotationAvailable (wp-seo-post-scraper-1100.min.js:5)
    at e.value (wp-seo-post-scraper-1100.min.js:5)
    at HTMLDocument. (wp-seo-post-scraper-1100.min.js:5)
    at i (load-scripts.php:2)
    at Object.fireWith [as resolveWith] (load-scripts.php:2)
    at Function.ready (load-scripts.php:2)
    at HTMLDocument.J (load-scripts.php:2)
    wp-seo-post-scraper-1100.min.js:1 Uncaught ReferenceError: YoastSEO is not defined
    at u (wp-seo-post-scraper-1100.min.js:1)
    at e.exports (wp-seo-post-scraper-1100.min.js:1)
    at _.saveScores (wp-seo-post-scraper-1100.min.js:5)
    at j.runKeywordAnalysis (analysis-1100.min.js:21)
    at j.runAnalyzer (analysis-1100.min.js:21)
    at j._pureRefresh (analysis-1100.min.js:21)
    at z (analysis-1100.min.js:1)
    at analysis-1100.min.js:1
    at j.y [as _pureRefresh] (analysis-1100.min.js:1)
    at j.refresh (analysis-1100.min.js:21)
    djtflbt20bdde.cloudfront.net/:14 Uncaught TypeError: Cannot read property ‘searchSuggestions’ of undefined
    at Object.searchSuggestions (djtflbt20bdde.cloudfront.net/:14)
    at Object.suggest (djtflbt20bdde.cloudfront.net/:15)
    at Object. (djtflbt20bdde.cloudfront.net/:15)
    at djtflbt20bdde.cloudfront.net/:15
    shortpixel.min.js:1 1574193154
    shortpixel.min.js:1 Empty queue 2086->2086

  3. Andrew Misplon Staff

    Thanks. Where is that error originating from? You can hover on the right and see the full path. Is that a Yoast SEO file?

  4. Tim Rogers

    Update..

    The issue is the Yoast Premium plugin.

    Thanks for your help!

    Tim

  5. Andrew Misplon Staff

    For sure, glad to hear you’re making progress.

    To help your correspondence with Yoast the next step would be to temporarily deactivate all plugins except those authored by Yoast and switch to a default theme. In that baseline state, if the console issue persists then it most likely isn’t a plugin/theme conflict causing the issue.

  6. Tim Rogers

    Thanks again Andrew – appreciate your swift help.

    Tim

  7. Andrew Misplon Staff

    For sure :)

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