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.
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
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
'spirit of sharing', Ken
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.
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…
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...
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!
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
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
But: I cannot believe there is nothing else I can do to solve this. ???
> useexternalyui 0
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.
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
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...
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