Skip Navigation

[Resuelto] Unable to import Modules or Types config – PHP error message

This support ticket is created hace 1 año, 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
9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 - - 9:00 – 13:00
14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 - - 14:00 – 18:00

Supporter timezone: Africa/Casablanca (GMT+01:00)


This topic contains 3 respuestas, has 2 mensajes.

Last updated by Simon hace 1 año, 10 meses.

Assigned support staff: Jamal.


I am trying to:
- Import Types configuration
- Import Blocks configuration via Module import

In both cases I see the error 'Unable to open zip file' (Types import) and 'Unable to open .zip file' (Modules import)

In PHP error logs I see:

[Tue Apr 06 09:26:54.745270 2021] [proxy_fcgi:error] [pid 24951:tid 140155520153344] [client] AH01071: Got error 'PHP message: PHP Warning: Creating default object from empty value in /home/ on line 70', referer: hidden link

I have disabled all plugins except for Toolset and switched to a default theme (2021)


It's possible the issue is the export from the other site of course. I have checked that WP and all Toolset plugin versions are the same

I can share the export files if necessary




Languages: Inglés (English ) Francés (Français )

Timezone: Africa/Casablanca (GMT+01:00)

Hello and thank you for contacting the Toolset support.

It seems to me that The export has probably produced a corrupt zip file. Can you try to open the zip file in a desktop app(winzip, winrar, 7z)? Does it open correctly?
If yes, can you extract the XML files and try to import them instead of the zip file?

If this does not help, please share the zip files in Dropbox or GDrive and let me check them further. I am setting your next reply to be private.


The problem appeared to be on the site from which the files were being exported. Once I figured this out, the imports worked OK.