Change Default Theme

[aubreyisland]

I am using a low end server for testing Sugar. So, I need to only enable the White Sands theme, for server bandwidth issues, etc.

I would like to set all users to this theme and possibly remove the option of using other themes.
Anyone know how to do this? In administrator settings I don't see a 'Default Theme' option?

Thanks-

[simple]

Hi

you can change the "default_theme" in config.php (or better config_override.php). And if you delete (or zip/tgz) the other themes they won't be available anymore.

[aubreyisland]

Interesting- I considered deleting, but I thought there must be another way haha!
I will look at the override thing and see what happens- thanks!

[aubreyisland]

So, I wanted to have only one theme enabled, this is what I did...

First I went in and deleted all the themes except for the one I wanted.
[I can upload them later, if I want them... I left WhiteSands]

Next I modified the config.php in Sugar's root.
*This is required, otherwise the login does not have a theme and says Invalid Theme.

I changed...

'default_theme' => 'Sugar',

to...

'default_theme' => 'WhiteSands',

Doing both of these resulted in only having the WhiteSands theme enabled, used, an available in users theme menu.


Now I wanted to see how easy it was to install other themes for users to optionally pick after logging in.

*Remember, I still have WhiteSands as the default.

So I uploaded the Sugar theme folder, and... Sugar was under the theme's list.

Hope this helps someone.

[chrisky]

Delete?

Bad practice boys & girls....

If I caught one of my team doing such opposed to my [required] way of achieving such, I'd wish them the best and give them a wonderful reference while hoping that they move forward and even end up better in life than they were while with us..

In such case, my {required} way would the following:

In the same parent directory that such themes directory exists,
you would create a directory with a name that indicates what it is [such as: the original items/content] while also including the original directory name as part of the new directory name.
In this case, I myself would create a new directory named 'original-themes'
Then proceed to move (though I would use copy and once satisfied that I have a good copy complete and uncorrupted) the unwanted themes from the within the themes folder to the new folder previously created.

And hopefully the 'rocket scientisists' will take the time to explain why [how, and the benefits of doing such] I personally require such practice.

P.S. The act of compressing the unwanted themes was a step above 'deletion' and in the right direction; however, still the wrong way [imho]. though I suppose in fairness, compression of such is not bad or 'technically' wrong but rather just takes a little more time [uncompressing] before one is able to either restore such or even just work with it (i.e. opening a PHP file for viewing its code)..

Not to mention, that the powerful ability to search directories, files, and their contents for a string....is essentially made non-existent should one choose to go the route of compressing such as discussed above..

[aubreyisland]

Too bad I'm not on your team... But, for those of you out there who want to preserve the themes, 'simple' suggested a similar solution by tar'ing the files, from which you can extract a given theme from at any given time. I, too, don't believe in the deletion of things, but... never mind.

[KaleStud]

Hmmm...

looked good the first time on v5.
But, of course, something weird happened.
If a normal user changes their theme, it changes for all users?!

so the next login I did under a different username was in a different theme?
Weird huh?!