Saltar navegación

[Resuelto] Plugin Updates Error

This support ticket is created hace 5 años, 10 meses. 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)

Este tema contiene 3 respuestas, tiene 2 mensajes.

Última actualización por Nigel hace 5 años, 10 meses.

Asistido por: Nigel.

Autor
Mensajes
#1208526
toolset_plugin_updates.png

I am trying to:
Update Toolset Plugins

Link to a page where the issue can be seen:
Screenshot attached

I expected to see:
Updates successful

Instead, I got:
The Errors

#1208543

Nigel
Supporter

Idiomas: Inglés (English ) Español (Español )

Zona horaria: Europe/London (GMT+00:00)

From the error message I can see in your screenshots I can tell you that this is a specific issue that occurred with the version of Installer included in Types 3.2.5.

It didn't affect all users (depends on server settings), but for those it did there is unfortunately no alternative but to manually update Types, which should then restore the normal installer functionality.

So on your plugins page delete the current version of Types.

Download the current version from toolset.com/account/downloads

On the Add new plugins page upload the zip file and activate Types.

Sorry for the inconvenience.

#1208759

I already had this problem during the Views update to V 2.7.3.
How can this be solved in future?

#1209234

Nigel
Supporter

Idiomas: Inglés (English ) Español (Español )

Zona horaria: Europe/London (GMT+00:00)

The installer code is in Types, not Views.

All software has bugs, but with our last round of updates too many slipped through and last week we adopted new procedures to improve our testing to make this less likely.

In the case of the installer bug, it didn't affect all users—it depends on the server environment, making it harder to anticipate—and unfortunately such a bug cannot be fixed with an automatic update because it was automatic updates itself that was broken, therefore requiring manual intervention.

Sorry for the inconvenience.