Emily Griffin

Please place URGENT on my request, because we are loosing precious time. We have stopped new Consultants from registering on our site and can’t stop this for too much longer. We need this resolved within 24 hours.

Any update on this? I need it fixed by today, so I can push the changes live. I need your team of developers to respond ASAP.

I need to have this resolved ASAP. I have to push these changes live by July 5.

Ok. I’ll start testing shortly in dev to confirm.

Also, this morning I got an email from WordPress saying the following:

Howdy!

Since WordPress 5.2 there is 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 Pro Membership.

First, visit your website (https://aloetteeduddev.wpengine.com/) and check for any visible issues. Next, visit the page where the error was caught (https://aloetteeduddev.wpengine.com/wp-admin/edit.php?post_type=wppm_plan&page=wppm_subscribers) 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://aloetteeduddev.wpengine.com/login-form/?action=enter_recovery_mode&rm_token=zTjG0Qe7n5DmR2YNX4ohCU&rm_key=WhZvSSHDgotSXApnRcbps8

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 5.9.2
Current theme: Flatsome Child (version 3.0)
Current plugin: WP Pro Membership (version 3.5.0)
PHP version 7.4.28

Error Details
=============
An error of type E_PARSE was caused in line 22 of the file /nas/content/live/aloetteeduddev/wp-content/plugins/wppromembership/src/Subscription/list-subscribers.php. Error message: syntax error, unexpected ‘$e’ (T_VARIABLE), expecting identifier (T_STRING) or namespace (T_NAMESPACE) or \\ (T_NS_SEPARATOR)

Found another problem that I need fixed Today … see the video … when a consultant logs in, their role is automatically changed to “No Role” … you’ll see this in the video.

Can you record what you are doing on the backend so I can see what is going on and the changes you are making?

This is very frustrating and I need to publish the changes I have made.

• This reply was modified 3 years, 1 month ago by Emily Griffin. Reason: more notes to add

Ok. Let me test.

Here are a few users/Consultant subscription holders who keep getting reverted to “No Role” … I’ve changed them back to Consultant but afraid they will be put back into “No Role” again:
username – 10017 (Sandra Herritt)
username – 8920 (Karie Youngeberg)
username – R4_1312 (Valeri Wagner)

• This reply was modified 3 years, 1 month ago by Emily Griffin.

We are good to go! Thanks so much.