Hi,
I'm trying to export my Views from one site to another... I've successfully exported my Views, but when I try to import it into my new site, it says that it can't read the file...
I tried to export it many times. I also saw that the site from which I exported was on 2.9-beta while the other was on 2.8, so I upgraded: no success. I downgraded both, still no success...
P.S. I also installed the Advanced Export, but doesn't make a difference.
Hi, can you provide a download link so I can inspect your exported Views?
Can I log in to the original site and create a copy using the Duplicator plugin?
I see a 404 error at the standard wp-admin address here. I also tried wp-login.php but it shows a 404.
Sorry, didn't know that this one had security features...
URL is : hidden link (or hidden link which will redirect there).
It seems to be related to the extra image sizes added by the Jupiter theme. If I activate Twenty Nineteen before exporting on my local copy, the Views can be imported in another site without failures. Is this an option for you, or is the new site using the Jupiter theme as well?
No, my client finally understood and is using Astra with Elementor now... haha.
But, if I understand right, exporting and importing that way (for both Types and Views) only exports/imports the structure, and not the actual data? For data, we would go with the regular WP export/import...? Because we are building a site with a similar structure, but it will have it's own data...
So, if I'm right, the theme (or any other data) shouldn't be part of the export... so, then, how come does it make any change in the export/import of Toolset?
Hmm, now it fails to import just because of one image (icon): iconevague.png... Can I get rid of that before exporting or (better) before importing...?
It has something to do with this custom image:
<div class="wave">
<img src="<em><u>hidden link</u></em>" width="200" height="26" class="size-full" />
</div>
When the Content Template is exported, the Toolset engine tries to include all the custom image sizes in the XML file. Jupiter injects its own custom image sizes there, and the XML produced is invalid. I can ask my 2nd tier team to investigate this if you plan to use Jupiter, but the fastest solution is to change to a different theme before exporting.
Thank you, but I see to what you are referring now... It's not Jupiter that adds this image; from memory, we added it manually in the code in one (or more) of the Views...
Since it's a live site, I think I'll simply delete those reference in the XML file it generates...
That being said, there IS a difference: with Jupiter enabled (on the original site), I had a "can't read file error", with Jupiter deactivated (i.e. Twenty-nineteen) it gives me the icon error...
Great! Edited the xml file to get rid of all the allusions to that file and it imported correctly!
Thank you for your time!
My issue is resolved now. Thank you!
