June 11, 20179 yr While this isn't exactly 6.4 related, presumably it could be an issue going forward. In my case, I had to revert a 6.4 install back to 6.3.5 to test an issue with CA. The 6.4 instance was running the Azure theme. Upon reverting, 6.3.5 was extremely messed up in its CSS because the azure css didn't exist. I had to go to display settings and switch it to "white" to get everything looking right (note that it did actually say it was running "Black") In this case, the issue here is with 6.3.5 not handling the case of a missing theme properly, but I'm more worried about if additional themes get added to 6.4+, then upon a reversion it won't gracefully handle a missing theme either. BTW, clearing the browser cache doesn't fix the issues either.
June 11, 20179 yr The new themes are ahum new to 6.4 and unkown to earlier versions. Selecting them will keep the corresponding setting stored in the configuration file even when downgrading to 6.3. I guess we can call that no backward compatibility... Edited June 11, 20179 yr by bonienl
June 11, 20179 yr Author 15 minutes ago, bonienl said: The new themes are ahum new to 6.4 and unkown to earlier versions. Selecting them will keep the corresponding setting stored in the configuration file even when downgrading to 6.3. I guess we can call that no backward compatibility... Completely understood on that. Just wanted Dynamix to handle the situation if a new theme in say RC4 is introduced that RC3 does not have that the system will gracefully handle it should the user for some reason be forced to downgrade.
Archived
This topic is now archived and is closed to further replies.