Installing and upgrading help

Update 3.2 to 3.5 - Themes not loaded

 
Picture of Andreas Giesen
Update 3.2 to 3.5 - Themes not loaded
 

Already at the start of the upgrade-process there was no theming. I thought it would work after upgrading, but no matter what theme I choose, the site is unthemed, has no images, no icons. I am out of ideas, what the problem might be. 

 
Average of ratings: -
Picture of Andreas Giesen
Re: Update 3.2 to 3.5 - Themes not loaded
 

If I deactivate "slasharguments" setting at least the "More" theme works, Boost and it's childtheme don't. With slasharguments on, no theme works... 

I tried PHP 7.1 and 7.2

 
Average of ratings: -
Picture of Andreas Giesen
Re: Update 3.2 to 3.5 - Themes not loaded
 

Started over again from scratch with a fresh copy and avoided all possible mistakes that I had to steer around the first time. The theme-problem persists in exactly the same fashion: 

With "slasharguments" on - no theme at all

With "slasharguments" off - "More" works, Boost (and Photo) don't. 

There is no CSS active already with the very first upgrade-message / screen - that is not related to any selected theme at all! 

So the problem can't be the theme per se. The issue is with the server(settings) and Moodle 3.5... Sadly I have not much control over the hosting. 

But it is new with 3.5 over 3.2 on the same server. Both run with PHP 7.1, Moodle 3.2 even with slasharguments on. 


I have 4 Moodles to upgrade till end of next week. First one was no trouble at all (VS). This 2. one (Hosting) only trouble so far with much unsolved. 3. should be ok as it's on a VS as well. 4th on different hoster, no experience yet with upgrades on that one. 

Thus any help is appreciated smile 

 
Average of ratings: -
Picture of Ken Task
Re: Update 3.2 to 3.5 - Themes not loaded
Particularly helpful Moodlers

So far, we know you have a problem and that you are upgrading from 3.2 to 3.5.  Have a theme issue when arriving to 3.5, but ....

Might help to know some specs of server as well what OS ... and versions of PHP and MySQL and Apache.

Have experience at updating/upgrading and troubleshooting ... but helps to know above and have to ask what might appear to be stupid questions (and give some strange advice), but ... no Vulcan Mind Meld is possible!

Take one at a time ... and don't consider the experience you've had with the first clone to be what the others will also have to undergo ... I've not seen 2 Moodles exactly the same - there's always a little something .... :\

How are you upgrading?    I see this and wonder what it means ...

"new with 3.5 over 3.2 on the same server"

So does that mean you had a moodle code directory, then downloaded the 3.5 code and tired writing over the code that was 3.2?

Did you check plugins and themes when the site was a 3.2?   How many addons?   Do those addons have compat versions for 3.5?   Are the themes compat with 3.5?   How about the environment check under servers when the site was a 3.2 ... did you update the component then use the drop down pick list of future versions of Moodle to see what Moodle said you needed to address (other than version of PHP)?

Did you purge caches ... both server and browser?

Did you manually purge caches ... in moodledata/cache ... did you manually remove all ... moodledata/localcache/ ... manually remove all ... how about opcache?   What's cached with opcache?

How about the database for the 3.2?   Was it already innodb with character set of what?  and collation of what?

Devil, even for things like themes, is in the detail. :|

'spirit of sharing', Ken


 
Average of ratings: -
Picture of Andreas Giesen
Re: Update 3.2 to 3.5 - Themes not loaded
 

So far, we know you have a problem and that you are upgrading from 3.2 to 3.5.  Have a theme issue when arriving to 3.5, but ....

> Might help to know some specs of server as well what OS ... and versions of PHP and MySQL and Apache. <

PHP as said: 3.2 on 7.0 or 7.1 runs fine. Tried 7.1 und 7.2 with the 3.5. 

Database

  • Server-Typ: MySQL
  • Server Version: 5.5.60-0+deb7u1-log - (Debian)
  • Protokoll-Version: 10
  • Server Zeichensatz: UTF-8 Unicode (utf8)

Webserver

  • Apache/2.2.22
  • Datenbank-Client Version: libmysql - mysqlnd 5.0.10 - 20111026 - $Id: c85105d7c6f7d70d609bb4c000257868a40840ab $
  • PHP-Erweiterung: mysqli 


> How are you upgrading?    I see this and wonder what it means ... 

"new with 3.5 over 3.2 on the same server" <

Wrong wording - I make a copy of moodledata and database, upload 3.5 files to empty directory, copy all mods, blocks, theme etc. pp. over and update the copy. That is why I have 3.5 and 3.2 where that upgrade came from running on the same server with the same serversettings, php-settings etc. which ist what I wanted to express... 

> Did you check plugins and themes when the site was a 3.2?   How many addons?   Do those addons have compat versions for 3.5?   Are the themes compat with 3.5?   How about the environment check under servers when the site was a 3.2 ... did you update the component then use the drop down pick list of future versions of Moodle to see what Moodle said you needed to address (other than version of PHP)? <

The plugin-check during the upgrade installed all updates for plugins, theme that does not work is vanilla "Boost" as well, no theme works at all, even vanilla More etc., when slasharguments is on. With slasharguments off at least vanilla "More" works.  On the same server with 3.2 all themes work with slasharguments on. 

The stuff the upgrade said to check was all the additional stuff that never made a problem. Character set of DB was changed from latin1 to utf8mp4 as the upgrade suggested. 

> Did you purge caches ... both server and browser? <

Yes, several times. 

> Did you manually purge caches ... in moodledata/cache ... did you manually remove all ... moodledata/localcache/ ... manually remove all ... how about opcache?   What's cached with opcache? <

No, will try that. Opcache is not in use on both. 

> How about the database for the 3.2?   Was it already innodb with character set of what?  and collation of what? <

Both database are as stated above. 



 
Average of ratings: -
Picture of Andreas Giesen
Re: Update 3.2 to 3.5 - Themes not loaded
 

After manually purging the caches in moodledata still the same: 


Boost theme, vanilla: 


"More" theme, vanilla (looks mostly like above with slasharguments setting in Moodle on)



 
Average of ratings: -
Picture of Andreas Giesen
Re: Update 3.2 to 3.5 - Themes not loaded
 

Could it have anything to do with https being active on the live system (3.2) but not on the working-copy (3.5)? 


I just upgraded from 3.1 to 3.5 in the same manner on a different server (also hosting, different hoster) where all subdomains are included in the certificate. Thus the working copy is on https, too. During the upgrade I had the same problems, no CSS. After logging in, everything looks fine. That Moodle runs "More" theme anyway, but I did not need to turn "slasharguments" off. I tried "Boost" vanilla and that also looks fine. 

I found it interesting that during the upgrade there was no css as well. I did not observe that on my testenvironment (VS) where I upgraded a 3.3 to 3.5beta last week. 

 
Average of ratings: -
Picture of Ken Task
Re: Update 3.2 to 3.5 - Themes not loaded
Particularly helpful Moodlers

Moodle records all internal links with the value from wwwroot in config.   You've clone a production server that used https to a server that doesn't have https ... no valid cert either, so yes, https could be a factor.

Some of code for Moodle relies on YUI libraries ... Yahoo .. as I understand it, Moodle trying to move away from YUI libraries as they are no longer maintained.  YUI libraries in Moodle could to use external ibraries or a combo load.  That to lead up to this:

from cli in moodlecode/admin/cli/ there is a cfg.php script ... shows all settings ...

php cfg.php |grep yui

output:

useexternalyui    0
yuicomboloading    1
yui2version    2.9.0
yui3version    3.17.2
yuipatchlevel    0

This on a system having no issues ... running https .... not a clone.

See if your test site is set to use externalYUI ... if so turn off ... use only combo loading.

One can use the php.cfg script for theme settings as well:

[root@sos cli]# php cfg.php |grep theme
theme    boost
themerev    1526389861
themelist   
themedesignermode    0
allowuserthemes    0
allowcoursethemes    1
allowcategorythemes    0
allowthemechangeonurl    1
theme_essential_putprops

'spirit of sharing', Ken

 
Average of ratings: -
Picture of Andreas Giesen
Re: Update 3.2 to 3.5 - Themes not loaded
 

The paths etc. in the config I always set to the actual paths and URLs, including http(s) of course. 

The php cli sadly does not help, as the hoster allows SSH, but hardly any commands actually work. "php" does not work. 

 
Average of ratings: -
Picture of Andreas Giesen
Re: Update 3.2 to 3.5 - Themes not loaded
 

Next one.... 

Great - the upgrade-docs tell me I need to upgrade to 3.0 first from < 3.0 - wich I did, from 2.9. 

Now starting the upgrade from 3.0 to 3.5 it's 3.1 I need... Once more, yeah... 

No problem to solve here, just… angry 


Edit: now on 3.5 - no further problems here either... CSS was there during upgrade already. Also went from https (2.9) to http (3.0) to https (3.2) and https (3.5) 


So out of 4 upgrades currently underway, the above theme-problem persists only on one configuration... 

 
Average of ratings: -
Picture of Ken Task
Re: Update 3.2 to 3.5 - Themes not loaded
Particularly helpful Moodlers

Yikes!   To be honest ... dunno how one manages a Moodle server now-a-days, let alone a march without *all* the tools that one could possibly use to accomplish the feat.   It's not a small undertaking ... but that's why you make the big bucks, huh! smile

One thing for sure ... you are learning the hosting setup ... which would have been almost required info before embarking on 'marches of Moodles'.   You seem to be in the un-fortunate situation of OJT!

All of this could be a good reason to research better Moodle hosting, ya think?

'spirit of sharing', Ken



 
Average of ratings: -
Picture of Andreas Giesen
Re: Update 3.2 to 3.5 - Themes not loaded
 

I wish I could... I took over existing setup that where sometimes chaotic to say the least. When installing a new moodle myself I go for Linux with full root with no exceptions. 

But of the 4 upgrades done 2 where on hosting and one of those was the smoothest of the 4. I had no SSH access at all on that one. 

I have no control over what hosting the clients use. The "problem child of the day" is moving to a completely different platform over the new months so migrating that Moodle to a VS is not an option for the client. 

In the worst case I would have to stick with the More theme, just after everyone got used to the Boost-UI sad 

But: I cannot believe there is nothing else I can do to solve this. ???


(BTW Big bucks well no, not really... The GDPR is more about driving me crazy than making me "rich"....)

 
Average of ratings: -
Picture of Andreas Giesen
Re: Update 3.2 to 3.5 - Themes not loaded
 

> useexternalyui    0
yuicomboloading    1
yui2version    2.9.0
yui3version    3.17.2
yuipatchlevel    0 <

I mean I do not need to set anything via cli, I have the more theme I can work with and even without css in Boost I can use the site. So the YUI settings I changed and tried different variants, that does not seem to be it. 


 
Average of ratings: -
Picture of Andreas Giesen
Re: Update 3.2 to 3.5 - Themes not loaded
 

Found something older in the forums about SCSS not compiling after upgrades with Boost Theme. Strangely after taking out some CSS from Photo theme, Boost theme started to work. The child theme should not impact it's main theme - at least I thought so. 

Now it is not working all the way yet, the functions the Photo theme adds, Backgrounds and color themes, don't work. But it is a big step forward smile 

 
Average of ratings: Useful (1)
Picture of Andreas Giesen
Re: Update 3.2 to 3.5 - Themes not loaded
 

Ok, it was a preset SCSS file that was added to the Photo theme to change colors, SCSS was partly invalid and compilation of SCSS failed, creating the problems. Those variables seem to have changed, because Boost has new functions etc. Also it now includes some of the functionality of Photo. Thus uninstalled Photo and remade the design-changes via new SCSS directly in Boost. 

Strangely though, slasharguments "on" still breaks all themes on this installation. So that is a different issue. But for now that's fine... 

 
Average of ratings: Useful (2)
Picture of Ken Task
Re: Update 3.2 to 3.5 - Themes not loaded
Particularly helpful Moodlers

Good ... you've figured out a work around to move forward!

It's too bad you can give yourself a rating of useful!   Congrats!   I'll do that for ya. ;)

'spirit of sharing', Ken

 
Average of ratings: -
Picture of Pablo Diaz
Re: Update 3.2 to 3.5 - Themes not loaded
 


hi there ,

there is a setting in the moodle admin backend

there is a seting i can not remember  exactly the path

but is something like a check box call slash, desactive it

it will recoginze the css of the theme inmediatly

it happens to me a few years ago

thats the solution


 
Average of ratings: -