# Import/Export Bug

**URL:** <https://community.localwp.com/t/import-export-bug/38628>\
**Category:** Support\
**Created:** [August 16, 2023, 4:59am UTC](https://community.localwp.com/t/import-export-bug/38628 "2023-08-16T04:59:56Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [August 16, 2023, 1:30pm UTC](https://community.localwp.com/t/import-export-bug/38628/2 "2023-08-16T13:30:23Z")

</div>

Hi @designmindz!

It looks like you’re running into an issue we’ve been tracking on the thread below. There are some workarounds and other discussion around this over there. I’ll merge your thread so you can follow along for assistance and any future changes we roll out that address this.

> [@Importing a WP 6.3 exported site with block theme results in CSS problems \[with solution\]](https://community.localwp.com/t/importing-a-wp-6-3-exported-site-with-block-theme-results-in-css-problems-with-solution/38552/12):
>
> Thanks for the help in hunting this down team, especially @emmtre! It sounds like there are multiple ways to handle it. We could delete the transient on the fly… or set that DEVELOPMENT\_MODE and go from there. It does seem this is an issue with WordPress 6.3 as it isn’t specific to Local, and as mentioned above, has been on other hosts as well. I wonder if this is on the community’s radar at all? Or if this is just the new way WordPress works and changes should be made on our end to accommodat…

---

_[View the full topic](https://community.localwp.com/t/import-export-bug/38628)._
