ispreview
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Super Cache] PHP Error: Undefined array key “author”Ok this went away after I pressed ‘Save Settings’ for “Accepted Filenames & Rejected URIs”.
Yep fixed.
I’d echo the same frustration. This made gallery management a lot easier, so why cull it and without notice? This makes the plugin less useful.
So I spent a bit of time and tracked this down to the class-gnpub-compat.php file, specifically these lines (around line 32):
public static function init() {
add_action( 'plugins_loaded', array( 'GNPUB_Compat', 'seo_plugins_strip_category_base' ), 20 );
}I think I’ve fixed it by tweaking the add_action line to use ‘init’ instead of ‘plugins_loaded’ because the latter fires immediately after all plugins are loaded, but before WordPress has finished loading translations, rewrites, and most plugin setup:
add_action( 'init', array( 'GNPUB_Compat', 'seo_plugins_strip_category_base' ), 20 );The conflict now seems to be solved because moving this compatibility check to ‘init’ ensures that when GN Publisher checks WPSEO_Options::get(), Yoast is fully ready — no premature translation loading. Thoughts?
I also get the same problem and I am using the very latest releases of WP, Yoast SEO and am also on PHP 8.4. I think it crops up again under only certain conditions, such as when certain other plugins are installed, but hard to pin down the exact reason why it’s still occurring.
- This reply was modified 7 months, 1 week ago by ispreview.
Any response?
Forum: Plugins
In reply to: [WP-Polls] Disabling WP-Polls Breaks Classic EditorFor what it’s worth, I fixed this by adding the following code to functions.php when WP-Polls is removed/disabled:
add_action('admin_head', function() {
echo '<style>
div#mceu_32 { height: auto !important; min-height: 30px; }
</style>';
});I’ve created a video, but as it exposes some secure information, then I can’t post it in public here. Where should I send it?
Please excuse the late reply. No, it has not been fixed, and also occurs under PHP 8.3. I am using the latest GN Publisher 1.5.23 and Yoast SEO 25.5 with the latest release of WordPress 6.8.2. I don’t know how to create a video of this, but it’s fairly simple to explain.
With Yoast SEO already installed and activated, if I then install GN Publisher and go to press ‘Activate’ in the plugin list then it activates the plugin but also starts displaying that error on all of my WP Admin Dashboard pages (with debug mode activated).
The only way to get rid of the error is to either disable Yoast SEO or disable GN Publisher.
Forgot to add that it also shows the same error across my public WP pages too, not only the admin ones.
- This reply was modified 10 months, 2 weeks ago by ispreview.
I’m not a PHP coder, but I got so tired of waiting for you to fix the most basic stuff that I’ve learnt and done it myself:
/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php on line 60
Change:
public function __construct(\YoastSEO_Vendor\Symfony\Component\DependencyInjection\ParameterBag\ParameterBagInterface $parameterBag = null)
To This:
public function __construct(?\YoastSEO_Vendor\Symfony\Component\DependencyInjection\ParameterBag\ParameterBagInterface $parameterBag = null)
/wp-content/plugins/wordpress-seo/vendor_prefixed/league/oauth2-client/src/Provider/AbstractProvider.php on line 416
Change:
public function authorize(array $options = [], callable $redirectHandler = null)
To:
public function authorize(array $options = [], callable|null $redirectHandler = null)
/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/Client.php on line 181
Change:
public function getConfig(string $option = null)
To:
public function getConfig(?string $option = null)
/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/ClientInterface.php on line 77
Change:
public function getConfig(string $option = null);
To This:
public function getConfig(?string $option = null);Forum: Plugins
In reply to: [WP Popular Posts] Seeing Loading Bar After v7.3.2 UpgradeDisabled as I want everything to be cached as much as possible for efficiency.
Forum: Plugins
In reply to: [WP Popular Posts] Seeing Loading Bar After v7.3.2 UpgradeSo I did a bunch of testing and identified that the cause of the problem is this new code in /src/shortcode/posts.php:
if ( is_numeric($ajaxify) ) {
$load_via_ajax = (bool) absint($ajaxify);If I change that back to what it was before (as below)..
if ( isset($attributes['ajaxify']) && is_numeric($attributes['ajaxify']) ) {
$load_via_ajax = (bool) absint($attributes['ajaxify']);..then I never have to see that ugly loading bar 🙂 and the list loads instantly. I am not skilled enough with PHP to know why the modified code under 7.3.2 is so much slower and showing the bar, while the 7.3.1 code does not and works well.
FYI – Tested with latest wordpress release, as well as both PHP8.3 and 8.4.
- This reply was modified 12 months ago by ispreview.
Forum: Plugins
In reply to: [WP Popular Posts] Seeing Loading Bar After v7.3.2 UpgradeNothing to do with that. I can literally CHMOD 0 the v.7.3.2 plugin and CHMOD 755 my backup of 7.3.1 and the loading line goes away, I never even see it under 7.3.1 – it’s all just instant. But with 7.3.2 you have to wait a second on my beta install for the list to load and on my public install it just stays showing the loading line.
Guess I’ll have to try manually adding each of the 7.3.2 changes to 7.3.1 until I find exactly which one causes it, but no time today.
Forum: Plugins
In reply to: [WP Popular Posts] Seeing Loading Bar After v7.3.2 UpgradeI’ve done some more testing and noted that something similar does occur on my beta install too, where it sits for a few seconds and then loads. My beta install isn’t using cache though and I’m also only calling ‘range’ => ‘daily’, rather than the last 7 days. Overall it seems like the plugin is now taking longer to pull the summaries on first load (under 7.3.1 it was instant), which might explain why my public install sees this constantly (i.e. so slow to pull summaries from the past 7 days due to more content, so WP Super Cache only ends up storing the loading bar screen). But I’m guessing.
Just to say, I am also getting the same error after upgrading to 8.4.3. Trying to save a draft of a new post returns the {“result”:false,”error”:”nonce”} error on /wp-admin/post.php . I have reverted for now.