Plugin Support
Jamie
(@codente)
Hi Emma,
What theme were you trying to use when this issue occurred?
Hi Jamie,
I am using a child theme for the Kadence theme. I’ve been using this plugin with this theme setup for over a year without any issues. I’ve since also tested on the latest version of WP, and it’s still not able to import.
To clarify: Both sites have their own child themes and using Kadence as the parent themes. Both child themes are named different.
Plugin Support
Jamie
(@codente)
Hi Emma,
Thanks for that info. I’ve tested with 2 different sites using different Kadence child theme names and it works for me.
A couple further questions so I can consult our development team:
– Do the folder names match for the child themes on both sites or are they different?
– What versions of PHP are you using on each site?
– Are both sites using the same version of the parent theme? Meaning the same version # and also are both using free or both using the pro version?
Thanks for your help so we can identify the cause (hopefully)!
Hi Jamie,
The folder names are different on the two sites (one is being used as a “base” of sorts, to house all the default settings when we set up a new site). However, this same error is also happening when I export and import from & to the same site.
Both sites have the same version of the parent theme, and the pro theme addon plugin. Both sites are currently on WP 6.7.1, but I’ve had issues on previous versions of WP. Also tested on PHP 8.1, 8.2, and 8.3.
I appreciate your time investigating this with me.
I just dug up an old export file from the base site in August and imported that successfully to the new site. So I compared the two.
The one that isn’t working has an empty line at the top of the file, and the charset is us-ascii. The old one that worked has no empty line at the top and the charset is utf-8.
Then I removed the empty space at the top of the new file, saved, and imported successfully. The charset stayed us-ascii so it’s that empty line at the top. Any ideas why that might be in there?
Plugin Support
Jamie
(@codente)
That is definitely a clue and another user is reporting the same. Could you share the URL of the site that you are exporting from?
Plugin Support
Jamie
(@codente)
We updated the plugin today to trim whitespace from the file so hopefully you won’t see this issue again!