WP Turned UP
Forum Replies Created
-
Hi. Marking closed, as we are just going to start the whole process over again. We don’t have those emails any longer.
There really should be an easier way to contact MailPoet, for free customers. I’m a paying customer and a partner of MailPoet…but I was THIS CLOSE to looking for another solution for this particular site, rather than getting into the MailPoet sales funnel.
RETHINK the communication.
- This reply was modified 1 year, 3 months ago by WP Turned UP.
Forum: Plugins
In reply to: [MailPoet - Newsletters, Email Marketing, and Automation] Account ReviewHi. Marking closed, as we are just going to start the whole process over again. We don’t have those emails any longer.
There really should be an easier way to contact MailPoet, for free customers. I’m a paying customer and a partner of MailPoet…but I was THIS CLOSE to looking for another solution for this particular site.
The tests before were when I was logged out of the site. I thought to test it while logged in, and this is what I’m getting. Nothing in the logs.
“Your submission failed because of an error.
MailPoet 3 Subscriber added to lists, but confirmation email failed to send: there was an error when sending a confirmation email for your subscription. please contact the website owner.
This message is not visible to site visitors.”No entries are showing today. However, the below is showing, from yesterday.
[2025-02-02T20:43:40.052839+00:00] mss.ERROR: key-validation.failed {“http_code”:403,”home_url”:”https://getpolicyproof.com”,”key_type”:”premium”} {“free_plugin_version”:”5.6.3″,”premium_plugin_version”:”premium not installed”}
Hi. Yeah, that’s the exact error. Here’s the screenshot.
I wouldn’t think that needing account approval would present an error like this, but if that’s the case, the method for reaching out to follow up for approval is quite flawed. If you look at the message below, it’s not possible to contact MailPoet unless you have a paid plan.
“If you don’t hear from us within 48 hours, please check the inbox and spam folders of your MailPoet account email for follow-up emails with the subject “Your MailPoet Subscription Review” and reply, or contact us.“
Hi. Nowhere did I request for your plugin to be a subscription plugin. That wouldn’t make sense.
You can close this ticket, as we’re going backwards here.
Hi. Simple Subscriptions are absoutely a use case. We’ve used them for years, as part of Woo’s Grouped Product, for allowing switching of plans.
Only being able to used Variable Subscriptions is limiting, as that type cannot be used in some cases.
Anyway, I don’t want to complain about a FREE plugin here. If you charged for this, allowing more than just Var Subs, I’d buy it. ; )Hi. I’m not seeing that. When setting up a ‘Simple Subscription’ product, I only see Download and Virtual options.
Thanks!
Thank you for the detailed response, Kevin. I’ll roll with what you’ve done so far, which is great, and be closely following along. Thanks again!
You’re gaslighting. Responding just because your company told you to and not because you can actually illicit change.
That’s not a way to “regain my trust,” as you say.+1 I just filed a support request for the same issue. This has worked before with the same tech stack. Nothing has changed as far as the theme, plugins, etc.
Thanks!
- This reply was modified 2 years ago by WP Turned UP.
Forum: Plugins
In reply to: [System Dashboard] Fails to run and throws a critical error👍
Forum: Plugins
In reply to: [System Dashboard] Fails to run and throws a critical errorHi. Yes, all good now. Thanks!
Forum: Plugins
In reply to: [System Dashboard] Fails to run and throws a critical errorI’m on Kinsta. NGINX.
Here’s the info after installing QM.
Fatal error: Uncaught Error: Unsupported operand types: string - string in /www/mylistingsandbox_698/public/wp-content/plugins/system-dashboard/admin/class-system-dashboard-admin.php on line 1849 Call stack: System_Dashboard_Admin::sd_disk_usage() wp-content/plugins/system-dashboard/admin/class-system-dashboard-admin.php:11526 System_Dashboard_Admin::sd_dashboard_page() wp-includes/class-wp-hook.php:307 WP_Hook::apply_filters() wp-includes/class-wp-hook.php:331 WP_Hook::do_action() wp-includes/plugin.php:476 do_action() wp-content/plugins/system-dashboard/vendor/codestar-framework/classes/setup.class.php:250 CSF_Setup::setup() wp-includes/class-wp-hook.php:307 WP_Hook::apply_filters() wp-includes/class-wp-hook.php:331 WP_Hook::do_action() wp-includes/plugin.php:476 do_action() wp-settings.php:576 require_once() wp-config.php:100 require_once() wp-load.php:50 require_once() wp-admin/admin.php:34 require_once() wp-admin/index.php:10- This reply was modified 3 years, 11 months ago by WP Turned UP.
In my testing, the issue is present regardless of the theme in play.
The issue only seems to lie with ‘Posts’. When testing with a custom post type, the issue is not there like it is with ‘Posts’.
The workaround to first select anything under ‘Posts’ and then circle back to select ‘Posts’…works just fine.