Best practice forum (Archived)

Lose ability to control Custom Responsive Theme after every upgrade

After every single time we upgrade our totara environments, our custom site logo shows a red X (missing img type error) and when we try to go to Appearance > Themes > Custom Totara Reponsive.. we get the below error. So we can no longer use the theme or fix the logo. I've opened a trouble ticket a couple times now but they can't seem to replicate the issue. The issue does NOT occur if we go in and switch the theme off of Custom Totara Responsive to something else before doing an upgrade .. Although we found this method to get around the issue, it's some times missed by our system admins when they upgrade the environment.. so it's still an issue i'd like to figure out why it's happening. Does anyone have any clue? This is getting quite annoying!

Permalink | Rispondi

Hi John,

I responded to your helpdesk ticket on our Support Desk 11th Nov - Ticket ID : 2771. There are a couple of options which may be worth investigating - have you tried to temporarily switch your theme to "standard" theme during the upgrade? You can do this by adding "theme=standard" on the URL or by adding this to your Moodle config.php:

$CFG->theme = "standard";

Another solution is to complete your upgrade via a CLI.

The proper place for tracking this issue is on the Support Ticket - if you have a look at that we can proceed from there, our front-end specialist is aware of this and hopefully we can isolate the problem which is causing the behaviour youre seeing.

thanks,

George.

Permalink | Visualizza intervento genitore | Rispondi

George..... we FINALLLLYYYYYYYY figured it out!!!! Our SA was moving the sitedata directory off and renaming it sitedata_oldversion and letting the upgrade rebuild the sitedata folder.. Can you tell me what other data might be lost by doing such a thing? Just want to make sure we are aware of what kind of impact doing that would have. Luckily we are still in the demo stage so the environment isn't production ready.. but we will be sure to leave sitedata alone from now on.

Permalink | Visualizza intervento genitore | Rispondi

Hi John,

config.php must contain a valid link to the sitedata folder which contains the contents of all used files and other data. Please make sure you always have a back-up of this folder as it cannot be recreated, when restoring the sitedata you have to restore the matching database snapshot.

regards,

George.

Permalink | Visualizza intervento genitore | Rispondi