Skip Navigation

[Resolved] Error when I import the settings to a new site: file could not be read

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
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10: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: Asia/Kolkata (GMT+05:30)

This topic contains 11 replies, has 3 voices.

Last updated by Minesh 1 year, 9 months ago.

Assisted by: Minesh.

Author
Posts
#2654543
2023-10-18 09_27_28-Export _ Import ‹ Hamanasi Adventure & Dive Resort, Belize — WordPress.png
2023-10-18 09_27_28-Export _ Import ‹ Hamanasi Adventure & Dive Resort, Belize — WordPress.png

Good day,

I have Toolset setting and views on a staging environment, and I'm having an error when I want to import the settings to a new site. I get the following error: The XML file (zipfoldername.zip) could not be read
I also tried to unzip the folder and import the XML and the .PHP file separate but with no luck.

The new site has Toolset views version: Version 3.6.8
The old site has Toolset views version: Version 3.6.3

The new site has Toolset Types version: Version 3.4.20
The old site has Toolset views version: Version 3.4.16

Is there a way we can import the files?

Looking forward to hearing back from you soonest as this is quite a pressing matter

Kindest regards

#2654575

Nigel
Supporter

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

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

Hi there

First, can you review the debug logs to see if there are any errors relating to this which might explain why the import fails?

If you haven't already, turn on the debug log by editing your wp-config.php file and change the line with WP_DEBUG like so:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
define('WP_DISABLE_FATAL_ERROR_HANDLER',true);

That will create a debug.log file in your /wp-content/ directory which you can examine in any text editor. Try running the import again and then inspect the log. If you don't find the debug.log file it means it didn't generate any warnings or errors.

Second, you could try downgrading the versions of Views and Types on your target site so that the versions match those on the source site, and then try again with the import. If that works you can then update the plugins to the current versions.

Let us know what you find.

#2655057
2023-10-20 11_54_20-Hamansai - live + staging - sftp___elemental@sftp.flywheelsites.com - FileZilla.png

HI Nigel,

Thanks for getting back to me, I downgraded the plugins and updated the wp-config file but there is no debug.log file showing up, so there is no errors.

Is there anything else we can try to resolve this issue?

Kindest regards

#2655067

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

Can you please share the file you are trying to import as well as tell me what step you followed to export the file?

In addition to that, please share admin access details to your staging site from where I can export the settings agian.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.

I have set the next reply to private which means only you and I have access to it.

#2655069

Hi Minesh,

thank you for the quick respond. I cant seem to share the file with you. How can I do this?
And unfortunately I will need to get permission from our client before I can share the logins with you.

We have an old backup of the site on staging (over a year old) - where all the work was done on, and now we have a new staging site (that's recent) where we want to import all of Toolset to this site and the work that was done.

Once I have permissions to share the logins I can do so, The client will only respond in 3 hours.

#2655077

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

thank you for the quick respond. I cant seem to share the file with you. How can I do this?
==>
As shared, you can upload the file to any file sharing service for instance google drive and share the link to download the file.

I would like to know, do you want to move whole site from one domain to another or you want to just move some parts?

I also would like to know, did you created Views using blocks?

If you want to move whole site then you can use either duplicator. Please check the following Doc:
- https://toolset.com/faq/how-do-i-migrate-a-wordpress-site-from-one-domain-to-the-other/

#2655081

Thanks for getting back to me, we only want to move the views of toolset, as work was done on that staging than needs to move over to the new staging.

Please see files here: hidden link

#2655083

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

I would like to know - the view that you would like to move, is that build using classic views or using block view?

#2655085

How can I check this? as a previous developer built this 🙂

#2655087

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

You should go to your old staging site and navigate to Toolset => Views and take screenshot of that and share with me and tell me what views you want to move.

#2655093
2023-10-20 13_09_42-Views ‹ Hamanasi Adventure & Dive Resort, Belize — WordPress.png

Thanks, please see screenshot, we want all the views over to new staging, t prevent us from rebuilding them

#2655265

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

I downloaded the zip file you shared and I try to import it and I got the same error.

I've another workaround, What if you try exporting the views using the "Toolset Module Manager" plugin? You can download the Module Manger plugin from the following link:
- https://toolset.com/download/toolset-module-manager/#changelog

Here is a guide on using this plugin:
- Export:
- https://toolset.com/documentation/legacy-features/export-import/using-toolset-module-manager/#exporting-creating-modules

Import:
- https://toolset.com/documentation/legacy-features/export-import/using-toolset-module-manager/#importing-modules