rsmithgs

Sorry for the delay, but I wanted to wait a bit longer to confirm it is actually functioning as expected now. I’m still unsure what would have caused the 1 additional person to go to the trash as subscribed, but I can confirm now that WordPress Users are now landing in the Subscribed section and not in the trash.

Thank you @lynnjat7,

I successfully moved over the subscribers I wanted from the trash to Subscribed, but I noticed that someone who subscribed today still landed in the Trash and their status changed to Subscribed and they were not moved out.

My WordPress Users List was still in the Trash, but I thought the update was going to make it so that even when this list was in the trash the WordPress Users would initially be placed in the Trash and then once they double-opt in they would be listed as Subscribed and moved out of the Trash.

Restoring and Enabling my WordPress Users list moved all of the Subscribed and Unconfirmed out of the Trash, thus putting me over the 1,000 limit for free accounts (I didn’t plan on this happening because I had some people in the Trash who were marked as subscribed from about 2 years ago that I’m assuming never received an email because they were in the trash. About 200 subscribed and 200 unconfirmed were added from that maneuver).

Is there not a way to Restore the WordPress User List without Enabling it so that WordPress Users are not immediately trashed, but have the option to be subscribed or not? Like I said before, we don’t plan on sending using the WordPress Users list, we just need WordPress Users to be able to be added to other lists that they do subscribe to.

Thank you @lynnjat7, could you tell me if there’s an easy way to export the segment of users in my Trash so I can compare this list to those who have active memberships on my site?

It looks like the Export tool only allows segmentation by List, but even if someone is marked as in a List, if they are in the trash it doesn’t look like those subscribers are exported (at least in the preview number provided).

Hello @lynnjat7, thank you so much for this update! I had a question though. Will the update change current subscribers that are Trashed and Subscribed? Or will I need to manually untrash those users and the update will only work for WordPress Users going forward?

Thank you @lynnjat7 and @danielinhou for confirming that this is a replicable issue. Since this seems to be an issue that is secondary to whether the API code works or not, I believe this would still fall under support right?

There’s not an ETA, but is this forum correct place to keep an eye out for a solution or timeline to a solution?

Hello @lynnjat7,

Thank you for your quick response! Are you saying that when a new user is created they are immediately put in the trash because the WordPress Users List is trashed and they are automatically applied to that list?

My process is, that someone signs up and creates an account on my site, and then when they do a membership checkout I assign them to the Newsletter list through an API call.

Since the user creates an account they should already exist in MailPoet so it should bypass a large part of code and always be running the else line:

// Check if subscriber exists. If subscriber doesn't exist an exception is thrown
        try {
            $get_subscriber = $mailpoet_api->getSubscriber($subscriber['email']);
        } catch (\Exception $e) {}
    
        try {
            if (!$get_subscriber) {
                // Subscriber doesn't exist let's create one
                $mailpoet_api->addSubscriber($subscriber, $list_id_arr);
            } else {
            // In case subscriber exists just add him to new lists
            $mailpoet_api->subscribeToList($subscriber['email'], $list_id);
            }
        } catch (\Exception $e) {
        $error_message = $e->getMessage(); 
        }

But my users are not being removed from the Trash after they subscribe, so I assume they aren’t getting any actual emails besides the double opt-in email required to use MailPoet Sending Service.

Is there another line I need to add to check if they are in the trash, and if they are, remove them from the trash before subscribing them to my list?

I was trying to figure this out! Thank you for confirming! This is also occurring on websites running on PHP 7.4.

I was working with my hosting provider the entire time and the host provides us the SSL certificate.
I tried again today and was able to reconnect all of my websites. I’d like to keep this ticket open though in case I run into the same problem where it will say there is a connection issue in Central in about 24 hours.

Please let me know if there is anything I can send to make troubleshooting this easier.

Hello @wfadam, unfortunately, it doesn’t look like removing the AAAA record helped. I just attempted to reconnect to Central again after going to Tools > Diagnostics > clear data connection and it still says “Unable to resolve domain redirects”.
I have no known redirects and that can be confirmed here: https://httpstatus.io/

Any other suggestions would be greatly appreciated!

Unfortunately, it doesn’t seem like removing the AAAA records helped.
When I go to Tools > Diagnostics > Other Tests > Clear all Wordfence Central connection data and then go back to Dashboard I am still seeing “Wordfence Central Status” “Disconnected by on June 26, 2021” “Reconnect This Site” “Visit Wordfence Central”

If I Clear all Wordfence Central connection data why is this still recognizing that it was once connected? Perhaps it is not truly deleting all connection data?

I have tried again, but no luck. I’m assuming this is because the AAAA record hasn’t been purged from everywhere yet. I will try again when I see all AAAA records purged at https://dnschecker.org/#AAAA

My website host found an AAAA record related to the domain with the issue and has removed and purged the cache. I will try again in an hour.

I see your previous test at ssllabs.com and it seems that it was successful with the IPv4 address, but IPv6 experienced an unexpected failure.

I had previously tested with stanxxxxxx.org and it still gave the unable to resolve domain redirects issue. I just tested again with thinkingxxxxxxxxx.org but it is showing the same issue. I will look through https://www.ssllabs.com/ for issues related to collxxxxxx.org, but all 3 of my websites were provided SSLs through the same source.

I have followed the instructions again, but no luck.