treanormp
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Mailster] Email to list failed with no error indicatedI did not notice until now that WordPress had sent me an error notification on March 5th, well prior to my issue but possibly related since my WP-Mailster version (1.8.21.0) has not been updated since then. I have removed the site-specific info; let me know if that makes it harder to debug:
Howdy!
WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, wp-mailster.
First, visit your website () and check for any visible issues. Next, visit the page where the error was caught () and check for any visible issues.
Please contact your host for assistance with investigating this issue further.
If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.
https://.../wp-login.php?action=enter_recovery_mode&rm_token=dbSGmcmExZhcHIhmcJNZgs&rm_key=y0gDmWsp7q8Dz16IcFFau3
To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.
When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.7.2
Active theme: Twenty Seventeen (version 3.8)
Current plugin: (version )
PHP version 8.3.6
Error Details
=============
An error of type E_ERROR was caused in line 63 of the file .../public_html/wp-content/plugins/wp-mailster/wp-mailster.php. Error message: Uncaught Error: Failed opening required '.../public_html/wp-content/plugins/email-subscribers/.../public_html/wp-content/plugins/wp-mailster//mailster/includes.php' (include_path='.:/opt/cpanel/ea-php83/root/usr/share/pear') in /.../public_html/wp-content/plugins/wp-mailster/wp-mailster.php:63
Stack trace:
#0 /home1/.../public_html/wp-content/plugins/wp-mailster/wp-mailster.php(1581): wpmst_mailster->__construct('/home1/site...')
#1 /home1/.../public_html/wp-settings.php(526): include_once('/home1/site...')
#2 /home1/.../public_html/wp-config.php(103): require_once('/home1/site...')
#3 /home1/.../public_html/wp-load.php(50): require_once('/home1/site...')
#4 /home1/.../public_html/wp-login.php(12): require('/home1/site...')
#5 {main}Forum: Plugins
In reply to: [WP Mailster] Email to list failed with no error indicatedThank you for considering my problem. I think my system diagnostics error was a red herring. I learned from mxtoolbox that my ip address was “Added to Spamhaus ZEN” on 3/23/2025 11:32:15 PM and remained until 4/3, which of course includes the date of our group’s attempted conversation. My ip address was also on a UCEPROTECTL3 blacklist. But the last time Spamhaus was the issue my send report was clear about the emails not processing. Despite the clean report, could that be it? If you like, I will make up a small list to test this theory. Thank you again.
Forum: Plugins
In reply to: [WP Mailster] from email addressMy apologies for somehow not seeing your reply. I see now where your Sending behaviour tab, when editing the mailing list, gives me these options and the Settings provide further control over the From name and address. I will try combinations on a test list and report back, but mark this as resolved for now. In the meantime I will just ask my group to be aware of their addressee. Most want to reply-all anyway. Looking at these gives me ideas for addressing a different problem that I had yesterday, but I will submit a new question for that. Thanks very much.
Forum: Plugins
In reply to: [WP Mailster] A possible blocklist or blacklist issueThank you for your quick and thorough reply, and apologies for not acknowledging for over a month. It does appear this UCEPROTECT-Level3 blacklist is due to a neighbor in my shared hosting neighborhood, as I have been off and on the list since then without broadcasting emails. The impact is minimal as an email to the listserv was successful today while I am still on that list. SPAMHAUS blocked it last time – now I’m not sure why!
I find that running the “optimizer” from a Microsoft Edge page does not produce this error, while Chrome does. I also find that it only lasts a couple days, tops, and then the site health tool reports a critical error – critical css is out of date.
Hi actdree,
Thank you for reviewing this plugin. I have had some strange problems that may have started with installing AIOSEO, but I have not made that connection. Would you just mention some of the “other” plugins and the nature of the problems? Thanks very much,
treanormp
Forum: Fixing WordPress
In reply to: Mismatched “post_max_size” and “upload_max_filesize” values.For what it’s worth, here is where I went wrong: the cPanel settings to which @darkwatergroup11 refers overrides whatever you place manually in the php.ini file. Setting limits within the php.ini file has no effect. Making the changes in cPanel as he says fixes the site health recommended improvement. Thanks everyone.
Forum: Fixing WordPress
In reply to: Mismatched “post_max_size” and “upload_max_filesize” values.Thanks for the feedback. I must have something else going on and I will suppress my OCD until the site health tool is fixed. I don’t get many people uploading to the site anyway.
Forum: Fixing WordPress
In reply to: Mismatched “post_max_size” and “upload_max_filesize” values.For me, making any or all of these changes did not affect the site health. This mismatch still shows up as a recommended improvement. However, I also have an active PHP session, so that is maybe affecting me? Initially my php.ini file did not specify any of this. I am making the changes with an editor using PuTTY.
Forum: Plugins
In reply to: [WP Mailster] site health problemsI do get the same error and I notice the page I have with the subscribe shortcode cannot be edited using the block editor. I must disable the plugin to edit that page. This sounds related to the site health critical errors.