Joshua Fredrickson
Forum Replies Created
-
Forum: Plugins
In reply to: [Easy Table of Contents] Fatal Error in 2.0.79This looks to have fixed the issue. Thank you!
Forum: Plugins
In reply to: [Auto Alt Text] Azure Computer Vision API deprecatedThank you! Great plugin by the way.
Forum: Plugins
In reply to: [Widget Logic] current version is breaking pages with WP 6.8.1Hey @3cstudio , you may want to remove the plugin entirely.
https://secupress.me/blog/widget-logic-and-the-undesired-javascript-injection/
Forum: Plugins
In reply to: [Widget Logic] current version is breaking pages with WP 6.8.1The 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:
Interaction with External Services
Widget Logic uses the external service to obtain up-to-date information about the results of football matches. 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 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
In reply to: [FakerPress] Multiple fatal errors in 0.7.0You’re quick! Appreciate the plugin!
Many thanks! I’ll be sure to keep an eye on the new version.
This has happened across dozens of sites and has been a regular battle for the past 2.5 years. It only occurs with
WP_DEBUGenabled. 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 describes the exact issue in more detail in this comment.
Forum: Plugins
In reply to: [Environment & Debug Bar] Doesn’t correctly read WP_ENVMany many thanks!
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).
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.
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 73Fonts 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
prefetchanddns-prefetchtags are there, but no link to the stylesheet.Forum: Plugins
In reply to: [Duplicate Post] Errors on top screenI agree that these notices aren’t as important in production, but it makes developing a site (with
WP_DEBUGintentionally enabled) quite difficult as every admin screen is affected and essentially broken.Thanks for the link! I’ll give it a go.
Forum: Plugins
In reply to: [Duplicate Post] Errors on top screenThese 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.
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.