"You are using an expired account of Toolset."

Ce fil est résolu. Voici une description du problème et la solution proposée.

Problem:

We get this message:
"You are using an expired account of Toolset."

Solution:

If the account is expired and you subscribe again, it might take time for the payment gateway to finish the processing.

0% of people find this useful.

This support ticket is created Il y a 3 years, 6 months. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Marqué : Account Issues

Ce sujet contient 2 réponses, a 2 voix.

Dernière mise à jour par jasonJ-8 Il y a 3 years, 6 months.

Assisté par: Christopher Amirian.

Auteur

Publications

November 25, 2022 at 5:23 pm #2504025

jasonJ-8

We use Toolset on lien caché, and everything has been working fine. But we got a poke from the client this morning that Toolset was claiming to be expired.

We checked our Toolset account, and it is set to auto-renew today. There is no indication that there was any problem with auto-renewal.

I tried de-registering and re-registering on the WordPress side. I manually upgraded to the latest version. I deactivated the plugin and re-activated it. I removed it from our Toolset account and re-added it, yielding a new registration code. Still, WP reports "You are using an expired account of Toolset. "

November 27, 2022 at 9:00 am #2504817

Christopher Amirian

Supporter

Les langues: Anglais (English )

Hi there,

Usually, it takes time for the payment to be processed.

Would you please check with the gateway processor to be sure that the payment is done?

If yes, I can ask the account team to take a look into your account.

Thanks.

November 27, 2022 at 4:20 pm #2504993

jasonJ-8

We did nothing, and the problem disappeared. It appears that the expiry warning started triggering earlier in the day than the payment was processed perhaps?