Exported theme using odd extension and erased" my theme."

Hi Michael. I’m sorry to hear that you’ve run into this frustrating issue. The .sktheme extension is nothing to be suspicious about; Skuid themes no longer have the .zip extension, but the actual file format is the same as a zip file. So, you can technically rename an old theme file to have the .sktheme extension instead of .zip. I will make sure our documentation gets updated to reflect this change - thank you for bringing it to our attention!

Regarding your theme issues, I have a few questions:

• Have you made sure your themes are up to date? When you import themes, you sometimes need to re-run the “Update out of date themes” process to bring the imported theme up to date with the Skuid version you’ve got in your org. You would see the “Update out of date themes” button appear on your themes page if this was the case. 
• Which version of Skuid are you working with? There was a product issue that prevented the theme builder from loading in Firefox. This would have been resolved in Skuid version 10.0.3 (look for issue CORE-399 on the releases page). Before making any upgrades to your Skuid version, you would of course want to thoroughly test a new version in a non-mission critical sandbox, as Salesforce does not allow reverting managed packages like Skuid to old versions.
• When you say the original theme has been erased, can you elaborate? Was this one of the pre-built base themes? If so, which one?

Just ran ‘Update out of date themes’ and my loaded theme still will not load. 

We are on Skuid version 10.0.2 (using Google Chrome). 

When I say erased I mean, when I attempt to edit the theme in the theme builder (the original theme I made in sandbox) the page stays stuck loading indefinitely. Also when I load the test page that the theme was used on, the entire page has reverted to the skuid default theme (the one that looks a bit like Salesforce classic). 

The theme was made from a clone of one of the base themes. 

Thank you for the clarification. When you try to open the theme, are you seeing any console errors? And, are you able to open any other themes successfully?

I read the other post you’ve made, asking which permissions are required for theme editing, and Zach helped clarify what was needed as far as permissions go. If that hasn’t helped resolved the issue, I’m happy to keep looking at this. 

If you have the theme saved in a local file, you should be able to rename the file so it doesn’t overwrite your existing custom theme, and re-import it as a separate copy. Make sure the file extension is .sktheme and not zip.

Console error reads as follows:

The permissions aren’t an issue anymore as I know how to change those now (Thanks). The main issue is that I don’t know why the export/import process is failing.

I will try to re-import and see what happens.

Re-importing was unsuccessful with the same console error. 

When you try to enter the editor for this imported theme, can you try this?
Edit your theme - if theme loader is stuck loading (and the UI is frozen), open your browser console. If in Chrome, you can click and hold down the refresh button, to see a few refresh options. Choose to “Empty Cache and Hard Reload.” This has helped with similar issues in which the theme loader won’t load completely. 

You had mentioned that the theme looks different in your sandbox than it did before - Would you mind looking at the theme file you imported into your Prod org, and check the file size? It should be a few hundred kilobytes, I believe. I’m wondering if you’d be able to re-export the source theme, now that you have the permissions settings necessary for theme management, to see if the exported file looks different. 

Empty Cache and Hard Reload yielded the following error:

Here is the uploaded theme detail:

Upon export of the same resource I got a file of size 393 bytes

I am making the theme again. I think something funny happened the first time as I made it off of a cloned theme. 

I was successful in recreating the theme then importing and exporting. I believe something happened when using a cloned theme. 

Thank you for sharing this update. I’m glad you were successful, but sorry that you had to recreate your theme. If you run into anything similar please let us know.