An update (or something) seems to have broken styling...
-
wrote on Dec 8, 2023, 3:00 PM last edited by jdaviescoates Dec 11, 2023, 10:49 PM
See https://podcast.uniteddiversity.coop
I see this:
Although strangely enough I just went and installed a fresh instance and it seems to be working fine, see https://podcasting.uniteddiversity.coop
I'll probably just throw away the broken one as I hadn't actually even started using it, so nothing to loose, but figured I'd report it anyway
-
Seems like a content-type issue on that instance:
Loading module from “https://podcast.uniteddiversity.coop/assets/Dropdown-313ba7e5.js” was blocked because of a disallowed MIME type (“text/html”).
wrote on Dec 11, 2023, 2:09 PM last edited by@nebulon odd. Pretty sure that's nothing I've added myself.
-
@nebulon odd. Pretty sure that's nothing I've added myself.
@jdaviescoates looks like some misconfigured mimetype. js file is being served as html
-
-
wrote on Dec 12, 2023, 12:10 PM last edited by
-
@jdaviescoates said in An update (or something) seems to have broken styling...:
(all I'd done was change the name, essentially nothing else).
aha, such information is quite useful though, also is the broken app on the latest version? Trying to reproduce this.
-
Tried every customization I could find in the admin UI now but can't reproduce the issue. Have you set anything extra in the env file? Like something from https://code.castopod.org/adaures/castopod/-/blob/develop/env ?
-
-
translatorwrote on Dec 12, 2023, 3:07 PM last edited by luckow Dec 12, 2023, 3:08 PM
-
-
It's a problem with the cache. If you log into the admin interface and try to find Settings->General, there is a section for housekeeping. Select Cache and confirm. A second later it looks fine again.
wrote on Dec 27, 2023, 8:55 PM last edited by@luckow said in An update (or something) seems to have broken styling...:
It's a problem with the cache. If you log into the admin interface and try to find Settings->General, there is a section for housekeeping. Select Cache and confirm. A second later it looks fine again.
I followed this and now everything is fine.
my context was a clean install, nothing specific done to the config
just one podcast created with a bunch of episodes, what is clear to me is that this came after an upgrade (not sure which one tho) maybe there is a way to trigger the house cleaning (cache) once after upgrades ? -
wrote on Dec 27, 2023, 9:59 PM last edited by
Yeah, something is wrong with the package.
I've literally done nothing to this and the same thing has happened:
-
@jdaviescoates I have pushed a new package now to clear the cache. Does it help?
-
@jdaviescoates I have pushed a new package now to clear the cache. Does it help?
wrote on Dec 29, 2023, 1:14 PM last edited by@girish yep, that seems to have done it
-
-