Daniel Hendricks

Thank you very much!

Ok, thank you. I will assume that it is an issue on our end. Unfortunately for us, it’s a huge site (which also happens to be headless) and the client will not allow third party access to WP Admin.

Thanks again.

To be fair, this plugin does more than just hide/disable comments. It also disables RSS/Atom feeds and the annoying pingbacks.

Thank you for your response. I somehow missed it earlier.

If anyone else stumbles across this post, it appears that Carbon Fields has fixed whatever was causing the conflict between the two plugins at some point (I’m not certain which version fixed it, but it was broken in versions <=3.1.8). I just updated Carbon Fields to the latest version (3.1.20 at the time of this writing), and the conflict appears to have gone away.

I am now able to install and run the latest versions of Rank Math, Carbon Fields and Classic Editor plugins simultaneously without needing to deregister lodash.

You should be able to hook into wpau_approve. Example:
https://recalll.co/ask/v/topic/php-User-registration-and-activation-email-in-custom-form/5583cf1d7d3563f16a8b5d29

You could try removing the register_new_user action:
https://wordpress.stackexchange.com/a/333830

The define() syntax is invalid on lines 126-128 in functions.php (third parameter expects boolean):

define('GRACE_NEWS_THEME_DOC','https://www.gracethemesdemo.com/documentation/grace-news/#homepage-lite','grace-news');
define('GRACE_NEWS_PROTHEME_URL','https://gracethemes.com/themes/magazine-style-wordpress-theme/','grace-news');
define('GRACE_NEWS_LIVE_DEMO','https://www.gracethemesdemo.com/grace-news/','grace-news');

…should be:

define('GRACE_NEWS_THEME_DOC','https://www.gracethemesdemo.com/documentation/grace-news/#homepage-lite');
define('GRACE_NEWS_PROTHEME_URL','https://gracethemes.com/themes/magazine-style-wordpress-theme/');
define('GRACE_NEWS_LIVE_DEMO','https://www.gracethemesdemo.com/grace-news/');

Excellent, thank you for your response and plugin!

Unrelated note/FYI, I tried to sponsor you on GitHub, but it is always giving me the error:

I tried three different payment methods that are all in good standing – two credit cards, plus PayPal ACH – and also tried updating my profile payment method as recommended here:
https://help.github.com/en/github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method

…but I still get the error. I am 100% confident that it is a GitHub issue and I created a support ticket for it there, but I thought that I would let you know in case you also wanted to contact them. You might be missing out on donations.

For reference, GitHub ticket ID: 642491

• This reply was modified 4 years, 7 months ago by Daniel Hendricks. Reason: Added GitHub ticket ID

the content you’re using is probably not defined that early in your wp-config.php file.

Agree and I understand that – “I set it to a constant that is not yet defined.”

It was quite easy to change it to an integer, of course – the constant is unimportant and the issue was obvious (to me, but I’m a developer). My point was that the admin page could possible display an invalid value differently. It makes it look like an invalid value is, indeed, acceptable and is being used by the plugin/drop-in. If you intval() the displayed value, it would show a zero if it is non-integer, which might make a little more sense to the user as it would trigger a, “Hmm, I set it to X but it is showing zero,” and this might encourage them to look into it/dig further.

Alternatively, you could display a “Invalid value defined” value or something, but I figured that simply adding the intval() to the displayed value was easier and didn’t require translation.

This is non-critical, obviously – I was just sharing a possible idea for giving feedback to users when an invalid value for WP_REDIS_MAXTTL (or other, similar constants) has been defined.

Thank you for your wonderful work. This plugin is a must have for any WordPress site where Redis is an option. ??

I would not recommend doing this if you are going to distribute your plugin to the public – it leaves users at your plugins mercy to receive updates, and also might conflict if they already have ROC installed. It is also non-standard WordPress architecture. If it really is necessary for your plugin, it would be better to display an activation notice that ROC is either recommend or required (using your own code, or something like TGMPA or Requirements, etc).

That said, I’m betting that wp-content/object-cache.php isn’t being created/copied using your method, since the activation hook isn’t triggered. You could modify your code to copy it over itself on activation/remove on deactivation (the file is located in the plugin’s includes directory), but again, this is unorthodox and not recommended.

Daniel

Yup, that fixed it. I renamed the file and blew away the git cache.

Can you please try to clear all the caches, server, browser, website, and Cloudflare (if you are using it)?

I am connecting directly to the instance’s private IP – no caching or proxying (including nginx proxy, Cloudflare, etc), except for Redis and opcache. I flushed the Redis cache and restarted PHP-FPM but it made no difference. I also tried:

• Completely deleting and re-installing the plugin by downloading the 1.0.41.2 distribution ZIP from here and extracting it manually. I still got the error.
• Disabling all plugins except Rank Math 1.0.41.2, flushing Redis, restart PHP-FPM. Same error.

I was able to “fix” it by installing the cmb2/cmb2 composer library to the theme. This eliminated the error. As a test, I then reverted/removed the addition of cmb2/cmb2 and the error came back.

UPDATE: As I type this, I just noticed the problem – When I pull the plugin from git, is see that vendor/cmb2/cmb2/includes/CMB2_hookup.php has a lowercase ‘H’ (CMB2_hookup instead of CMB2_Hookup). However, when I look at the repo and/or extract the ZIP on macOS or the Linux instance, the ‘H’ is capitalized.

I suspect that git must is holding on to a lowercase filename reference and that is causing it. I will try deleting it, clear the git cache, reinstalling it and see if it fixes it (it probably will). This appears to be a git (or possibly local file system issue, but most likely git) and is not an issue with Rank Math.

Thank you,
Daniel

What is that?

If you read it, it is a security advisory recommending that you upgrade to the latest version of Rank Math where the vulnerability has been patched.

Sorry to hijack, but I’m assuming that your are using the Delicious Brains plugin and have it configured to delete local images (?). I can confirm that the images must exist locally in order for this tool to regenerate them.

If you want to bring them back locally (even if temporarily, solely for the regeneration process), you could use an S3-compatible SFTP client to download all of the images to the uploads dir on the web host, run Regenerate Thumbnails, and then copy over/delete the images in the uploads directory as you wish (assuming that you have enough storage space).

If you do not have enough storage space, you might be out of luck unless you clone the site to an instance that has sufficient storage space, run the process, then upload/replace/delete the images as necessary (or if you’re on shared hosting, perhaps you could ask the provider to temporarily increase your disk quota until you’re done).

Daniel