The link you followed has expired.

This support ticket is created 6 years, 7 months ago. 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
-	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	-
-	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	-

Supporter timezone: Europe/London (GMT+00:00)

Tagged: Views plugin

This topic contains 4 replies, has 2 voices.

Last updated by Nigel 6 years, 7 months ago.

Assisted by: Nigel.

Author

Posts

June 1, 2018 at 4:56 am #907266

scottC-6

I am trying to install the plugin and each plugin returns this: The link you followed has expired.
I've tried this on a live website and on localhost - all plugins are causing the same problem.

June 1, 2018 at 10:27 am #907361

Nigel

Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Scott

Where and when are you seeing this message?

Could I get a screenshot?

June 1, 2018 at 10:54 am #907370

scottC-6

Hiya Nigel.

So i just downloaded toolset views from the download page.
during the upload i get this message (see screenshot). I've tried 4 other plugins from toolset - all the same issues.
I'm using elementor pro with WP astra - no other issues with other plugins

June 1, 2018 at 10:57 am #907373

scottC-6

hmmmm. i just unzipped the package and uploaded it with FTP.
Then activated the plugin and all works....so i think something is wrong with the compression of the file which can be downloaded from toolset website.

Just a hunch because all other plugins i download from wordpress repo works just fine

June 1, 2018 at 11:12 am #907379

Nigel

Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Scott

I just tested the same (it's not the typical way I install plugins) and found it worked as expected, I couldn't see the same error.

We don't have any other reports of this (though we do have some installer issues).

Do you want me to pursue this?