Title: Joshua Fredrickson's Replies | WordPress.org

---

# Joshua Fredrickson

  [  ](https://wordpress.org/support/users/joshf/)

 *   [Profile](https://wordpress.org/support/users/joshf/)
 *   [Topics Started](https://wordpress.org/support/users/joshf/topics/)
 *   [Replies Created](https://wordpress.org/support/users/joshf/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/joshf/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/joshf/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/joshf/engagements/)
 *   [Favorites](https://wordpress.org/support/users/joshf/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 51 total)

1 [2](https://wordpress.org/support/users/joshf/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/joshf/replies/page/3/?output_format=md) 
[4](https://wordpress.org/support/users/joshf/replies/page/4/?output_format=md) 
[→](https://wordpress.org/support/users/joshf/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Easy Table of Contents] Fatal Error in 2.0.79](https://wordpress.org/support/topic/fatal-error-in-2-0-79/)
 *  Thread Starter [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [7 months ago](https://wordpress.org/support/topic/fatal-error-in-2-0-79/#post-18747932)
 * This looks to have fixed the issue. Thank you!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Auto Alt Text] Azure Computer Vision API deprecated](https://wordpress.org/support/topic/azure-computer-vision-api-deprecated/)
 *  Thread Starter [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [9 months, 1 week ago](https://wordpress.org/support/topic/azure-computer-vision-api-deprecated/#post-18668715)
 * Thank you! Great plugin by the way.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Widget Logic] current version is breaking pages with WP 6.8.1](https://wordpress.org/support/topic/current-version-is-breaking-pages-with-wp-6-8-1/)
 *  [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/current-version-is-breaking-pages-with-wp-6-8-1/#post-18501765)
 * Hey [@3cstudio](https://wordpress.org/support/users/3cstudio/) , you may want
   to remove the plugin entirely.
 * [https://secupress.me/blog/widget-logic-and-the-undesired-javascript-injection/](https://secupress.me/blog/widget-logic-and-the-undesired-javascript-injection/)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Widget Logic] current version is breaking pages with WP 6.8.1](https://wordpress.org/support/topic/current-version-is-breaking-pages-with-wp-6-8-1/)
 *  [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/current-version-is-breaking-pages-with-wp-6-8-1/#post-18501751)
 * The real question is why is this plugin calling js files hosted on an external
   domain on every page load. Oh… For… _<checks plugin page>_ …soccer scores?
 * That’s an instant removal for me.
 *  For those of you that missed it, this is from the [plugin overview page](https://wordpress.org/plugins/widget-logic/):
 * > **Interaction with External Services**
   > Widget Logic uses the external service to obtain up-to-date information about
   > the results of football matches. [widgetlogic.org](https://widgetlogic.org/)
   > is a source of sports information, that provides a wide range of information
   > about football, including various leagues, tournaments, and championships from
   > around the world.
   > The functioning of the [widgetlogic.org](https://widgetlogic.org/) service 
   > is based on delivering real-time data about selected matches without the need
   > to refresh the page. This means that data is automatically updated without 
   > requiring page reload. This approach ensures users quick and uninterrupted 
   > access to the latest sports data without the effort of manually updating information,
   > allowing them to stay informed about ongoing events in real-time.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[FakerPress] Multiple fatal errors in 0.7.0](https://wordpress.org/support/topic/multiple-fatal-errors-in-0-7-0/)
 *  Thread Starter [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/multiple-fatal-errors-in-0-7-0/#post-18471663)
 * You’re quick! Appreciate the plugin!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights)] ErrorException: “json_decode() expects parameter 1 to be string [2024 Edition]](https://wordpress.org/support/topic/errorexception-json_decode-expects-parameter-1-to-be-string-2024-edition/)
 *  Thread Starter [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/errorexception-json_decode-expects-parameter-1-to-be-string-2024-edition/#post-18041927)
 * Many thanks! I’ll be sure to keep an eye on the new version.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights)] ErrorException: “json_decode() expects parameter 1 to be string [2024 Edition]](https://wordpress.org/support/topic/errorexception-json_decode-expects-parameter-1-to-be-string-2024-edition/)
 *  Thread Starter [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/errorexception-json_decode-expects-parameter-1-to-be-string-2024-edition/#post-18028907)
 * This has happened across dozens of sites and has been a regular battle for the
   past 2.5 years. It only occurs with `WP_DEBUG` enabled. That’s the only common
   thread I’ve found beyond it being caused by AIOSEO. Deactivating AIOSEO (free
   or pro–doesn’t matter which), removes the error.
 * [@temereva](https://wordpress.org/support/users/temereva/) describes the exact
   issue in more detail in [this comment](https://wordpress.org/support/topic/errorexception-json_decode-expects-parameter-1-to-be-string/#post-15775452).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Environment & Debug Bar] Doesn’t correctly read WP_ENV](https://wordpress.org/support/topic/doesnt-correctly-read-wp_env/)
 *  Thread Starter [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/doesnt-correctly-read-wp_env/#post-17739819)
 * Many many thanks!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Speed Optimizer - The All-In-One Performance-Boosting Plugin] Fatal Error when SiteGround hosting inode quota limit is reached](https://wordpress.org/support/topic/fatal-error-when-siteground-hosting-inode-quota-limit-is-reached/)
 *  Thread Starter [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-when-siteground-hosting-inode-quota-limit-is-reached/#post-17437425)
 * I mean, it is related as it’s the only plugin across three sites that handed 
   out fatal errors due to SiteGround’s limitation. There are ways for the plugin
   to more gracefully fail, and an uncaught exception isn’t one of them. It would
   take just a little bit of effort to sidestep this issue.
 * I guess the crux of it is that there should be a warning about inability to write
   files vs taking down the entire site (both frontend and admin).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Envira Gallery - Image Photo Gallery, Albums, Video Gallery, Slideshows & More] PHP8 Warnings](https://wordpress.org/support/topic/php8-warnings/)
 *  [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/php8-warnings/#post-16506228)
 * I’m seeing this as well. It occurs when editing any post in the block editor.
 * Changelog suggests PHP8 notices were fixed back in 1.8.4.0, but I guess they 
   missed one.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights)] ErrorException: “json_decode() expects parameter 1 to be string](https://wordpress.org/support/topic/errorexception-json_decode-expects-parameter-1-to-be-string/)
 *  Thread Starter [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/errorexception-json_decode-expects-parameter-1-to-be-string/#post-15938968)
 * I dunno. I’m still seeing this in WP 6.1, AIOSEO 4.2.4 and PHP 8.0. Specifically,
   when attempting to view a CPT listing in admin. I’m seeing this across quite 
   a few sites on several different themes.
 *     ```
       ⇒  php -v
       PHP 8.0.21 (cli) (built: Jul  7 2022 13:13:21) ( NTS )
       ⇒  wp core version
       6.0.1
       ⇒  wp plugin list 
       +-------------------------------------+----------+--------+---------+
       | name                                | status   | update | version |
       +-------------------------------------+----------+--------+---------+
       ...
       | all-in-one-seo-pack                 | active   | none   | 4.2.4   |
       ```
   
 * `wp-admin/edit.php?post_type=example`:
 * `Fatal error: Uncaught TypeError: json_decode(): Argument #1 ($json) must be 
   of type string, array given in /site/wp-content/plugins/all-in-one-seo-pack/app/
   Common/Help/Help.php:73 Stack trace: #0 /site/wp-content/plugins/all-in-one-seo-
   pack/app/Common/Help/Help.php(73): json_decode(Array, true) #1 /site/wp-content/
   plugins/all-in-one-seo-pack/app/Common/Traits/Helpers/Vue.php(164): AIOSEO\Plugin\
   Common\Help\Help->getDocs() #2 /site/wp-content/plugins/all-in-one-seo-pack/app/
   Common/Standalone/DetailsColumn.php(117): AIOSEO\Plugin\Common\Utils\Helpers-
   >getVueData() #3 /site/wp-includes/class-wp-hook.php(307): AIOSEO\Plugin\Common\
   Standalone\DetailsColumn->enqueueScripts('edit.php') #4 /site/wp-includes/class-
   wp-hook.php(331): WP_Hook->apply_filters(NULL, Array) #5 /site/wp-includes/plugin.
   php(476): WP_Hook->do_action(Array) #6 /site/wp-admin/admin-header.php(118): 
   do_action('admin_enqueue_s...', 'edit.php') #7 /site/wp-admin/edit.php(397): 
   require_once('/site/...') #8 /Users/joshf/.composer/vendor/laravel/valet/server.
   php(234): require('/site/...') #9 {main} thrown in /site/wp-content/plugins/all-
   in-one-seo-pack/app/Common/Help/Help.php on line 73`
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Speed Optimizer - The All-In-One Performance-Boosting Plugin] Web Font Optimization breaks font display](https://wordpress.org/support/topic/web-font-optimization-breaks-font-display/)
 *  Thread Starter [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/web-font-optimization-breaks-font-display/#post-15851025)
 * Fonts enqueued per the above.
 * CSS:
 *     ```
       h1, h2 {
           font-family: Merriweather,serif;
       }
       ```
   
 * When signed in and Optimization enabled, the site properly enqueues the font:
 * `<link rel="stylesheet" id="google-fonts-css" href="https://fonts.googleapis.
   com/css2?family=Merriweather:ital,wght@0,400;0,900;1,900&family=Open+Sans:wght@
   400;600;800&display=swap" media="all">`
 * When logged out with Optimization enabled, the above line isn’t added to the 
   head. The `prefetch` and `dns-prefetch` tags are there, but no link to the stylesheet.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Duplicate Post] Errors on top screen](https://wordpress.org/support/topic/errors-on-top-screen/)
 *  [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/errors-on-top-screen/#post-15840466)
 * I agree that these notices aren’t as important in production, but it makes developing
   a site (with `WP_DEBUG` intentionally enabled) quite difficult as every admin
   screen is affected and essentially broken.
 * Thanks for the link! I’ll give it a go.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Duplicate Post] Errors on top screen](https://wordpress.org/support/topic/errors-on-top-screen/)
 *  [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/errors-on-top-screen/#post-15840033)
 * These notices make it challenging to develop a site with your plugin activated.
   Yes, they’re deprecations, but PHP 8.0 was released in 2020. 🙂 It’s time to 
   update the plugin.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights)] ErrorException: “json_decode() expects parameter 1 to be string](https://wordpress.org/support/topic/errorexception-json_decode-expects-parameter-1-to-be-string/)
 *  Thread Starter [Joshua Fredrickson](https://wordpress.org/support/users/joshf/)
 * (@joshf)
 * [4 years ago](https://wordpress.org/support/topic/errorexception-json_decode-expects-parameter-1-to-be-string/#post-15776062)
 * I can confirm that this has cropped back up across several different sites I’ve
   seen. We’ve had to migrate to Yoast for a few of them as the error proved too
   difficult to work around in some staging environments.

Viewing 15 replies - 1 through 15 (of 51 total)

1 [2](https://wordpress.org/support/users/joshf/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/joshf/replies/page/3/?output_format=md) 
[4](https://wordpress.org/support/users/joshf/replies/page/4/?output_format=md) 
[→](https://wordpress.org/support/users/joshf/replies/page/2/?output_format=md)