An update (or something) seems to have broken styling...

[girish]

@jdaviescoates looks like some misconfigured mimetype. js file is being served as html

[luckow]

mh. Nothing useful, but I get a 404

[rmdes]

I'v got the same, on a unmodified Castopod
it's been broken since at least 2 weeks actually, haven't had the time to report earlier

[nebulon]

Looks like all those assets are not found and thus also the content-type is wrong.

[jdaviescoates]

@nebulon OK, but why? Is this an upstream issue or a problem with the Cloudron package?!?

Sounds to me like it could well be an issue with the package given @rmdes and I have both had this issue on basically unchanged installs (all I'd done was change the name, essentially nothing else).

[nebulon]

@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.

[nebulon]

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 ?

[luckow]

This is how it worked for me: Install Castopod, make a backup, clone from the backup under a different domain.
Boom.

[luckow]

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.

[nebulon]

Well spotted, maybe the package misses some startup tasks then

[nebulon]

Just tried to reproduce this with cloning and changing location. But it seems to work fine actually. We already run some houskeeping tasks in cron, could this be some timing issue?

[rmdes]

@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 ?

[jdaviescoates]

Yeah, something is wrong with the package.

I've literally done nothing to this and the same thing has happened:

https://podcasting.uniteddiversity.coop

[girish]

@jdaviescoates I have pushed a new package now to clear the cache. Does it help?

[jdaviescoates]

@girish yep, that seems to have done it