Seemingly random loss (i.e. they don't even attempt to load) of css/js assets

Re: Seemingly random loss (i.e. they don't even attempt to load) of css/js assets

by Ken Task -
Number of replies: 2
Picture of Particularly helpful Moodlers

Welcome!  Your solution works ... for now ... but   '... special request!!!!???? ....'

php-cli isn't the same as the php that is used for web service (assuming apache ... php-fpm).

Think you might need to re-think.   Go to Site Admin -> Server -> Environment - update component ... then select higher versions of Moodle to see what you'll need

True RHEL vr 6,7, and probably 8 have always been 'conservative' when it comes to php versions provided by their repo.   Thus a reputable 3 party repo needed to keep pace with PHP.

For php,  remi repo and/or webtatic repo are pretty good.   There are others.

So you've got a work-around in place right now ... not yet done (never is).   And it's just for cron ... but, there are some useful CLI only scripts through out moodle code.

Those in moodlecode/admin/cli/ have been extremely useful.

Speaking of 'useful' .. please feel free to rate any of my responses as 'useful' ... it's a way of saying thanks + I 'earn a badge'! smile

'SoS', Ken



In reply to Ken Task

Re: Seemingly random loss (i.e. they don't even attempt to load) of css/js assets

by Chris Rockwell -
Unfortunately this didn't resolve the issue. I now have the "Background processing for caches" happening every 15 minutes and we're still getting this issue.

Any other things I might need to check?

Thanks!
In reply to Chris Rockwell

Re: Seemingly random loss (i.e. they don't even attempt to load) of css/js assets

by Ken Task -
Picture of Particularly helpful Moodlers

So is it safe to say this is theme related?

harold_boost theme is commercial ... from checking their page kinda an expensive one at that! :|   That to say, am not gonna try and load it up to see what's what.

https://elearning.3rdwavemedia.com/themes/moodle-theme-herald-boost/

Above link does say free theme support however.   So you might want to contact them.

Before you do, however, how about setting to the default 'boost' and let it run like that for a couple of days to see if issue continues.

Might be a good time to do a DB dump and archive of moodle code (a backup).

'SoS', Ken