Sauter la navigation

[Résolu] can't access modules – Make sure you are connected to the Internet to access…

This support ticket is created Il y a 4 années et 11 mois. 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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

Marqué : 

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

Dernière mise à jour par Shane Il y a 4 années et 10 mois.

Assisté par: Shane.

Auteur
Publications
#1537017

I am trying to: install and use a module

Link to a page where the issue can be seen:

I expected to see: a list of modules available to install

Instead, I got: A long load time and then this error: "Make sure you are connected to the Internet to access our modules library server." I am definitely connected to the internet.

#1537427

Shane
Supporter

Les langues: Anglais (English )

Fuseau horaire: America/Jamaica (GMT-05:00)

Hi Dallas,

Thank you for getting in touch.

That is quite odd. I'm assuming that you're not working on a localhost but your site is on a live server that I can access correct?

If so would you mind allowing me to have admin access to the site to check on this for you ?

The private fields will be enabled for your next response.

Thanks,
Shane

#1537813

Shane
Supporter

Les langues: Anglais (English )

Fuseau horaire: America/Jamaica (GMT-05:00)

Hi Dallas,

I was able to replicate the issue and have escalated to our 2nd tier supporters for further checks.

Once there is an update I will inform you.

Thanks,
Shane

#1549905

Shane
Supporter

Les langues: Anglais (English )

Fuseau horaire: America/Jamaica (GMT-05:00)

Hi Dallas,

Our team has resolved the issue and the fix will be made in a future release.

Thanks,
Shane