ISPC3 Theme/Template

I'm working on a new theme for ISPConfig3 and was working on using css classes for the left menu and got a bit of a problem with it.

I can't find unique var name I can use to define each menu item individually.
I tried cheating and using <tmpl_var name='title'> and got some success until I noticed the Monitor menu and the left side bar shows Server to Monitor with some screwed up text in the class name breaking html.

Is there a var name that contains unique names that can be used for css. ie ones without spaces etc.
Or is there a way to know what template vars are available. so far it appears the language text is possible but not sure what else, especially one for the combo server select box I have a problem with.

Tremors.

Attached Files:

I've noticed another issue.
Most if not all buttons to add are using the same class name which is fair enough if you want the same icon but not if you want to change it.
Since this is a template and not part of a theme, makes it hard to change it but not lose the changes over an upgrade as I believe these files would be overriden right?

yeah well i figured that would be the case.
what about naming convensions used as Add website, Add new FTP user, Add blah blah.. all use the same class name, can we in future have a different class for each?

Also, you didn't answer my questions about unique var names since atm, I have to use <tmpl_var name='link'> which means in the css i have to use :
#submenu li.sites\/web_subdomain_list\.php a { background-image: url("../../images/domain-sub-icon.png");background-repeat:no-repeat; padding-top: 0px;}

Yep, I used the var 'title' which i used the Subdomain.for.website method in the css, but this fails badly when rendering menus which have the pulldown combo like the server selection in the Monitor section. So ended up using the link instead.

Yeah that would be ideal method really but since the ispconfig3 upgrades are a little brutal and overwrite almost everything you changed, you have to keep backup copies and diff them in case they've added something to the page which a backup&restoring of your modified file would restore back to the old copy.
So i did it my way only for easy upgrade reasons only.
Would be nice if the ispc team styled everything a little better.

What you did was good work Mike, could try chattr +i on your files during upgrade to prevent overwriting and see how it goes. I know it doesn't work on custom postfix main.cf as complains before continuing, i know coz i tried it.
For some reason ispc3 upgrade screws my postfix configs so i have to always back it up.

it truely needs questionable sections for upgrades like templates, each service and so on..

Yeah that would be ideal method really but since the ispconfig3 upgrades are a little brutal and overwrite almost everything you changed, you have to keep backup copies and diff them in case they've added something to the page which a backup&restoring of your modified file would restore back to the old copy.

Click to expand...

That depends on how you work with a open source project. mike_p for example works actively with the ispconfig project and commits his changes and fixes back to the source tree. You decided to work only on your own without contributing to the ispconfig project, so your chnages does not go into the ispconfig sources and thats why you have ptoblems with overwritten files.

That depends on how you work with a open source project. mike_p for example works actively with the ispconfig project and commits his changes and fixes back to the source tree. You decided to work only on your own without contributing to the ispconfig project, so your chnages does not go into the ispconfig sources and thats why you have ptoblems with overwritten files.

Click to expand...

Well my work doesn't involve changing ispc3, hence why i only created the theme in a way which doesn't require making changes to ispc3 code and only the postfix main.cf i had issues because i have changes I needed, nothing wrong with that and that's not part of ispc3.
The same with my awstats plugin, it's a plugin which doesn't interfere with ispc3. So I really don't get your point.
I like to throw changes and ideas into the air and those who want to catch it can, if someone wants to take my idea and improve on it, then even better. I try what i can for the community with the little time i have. That's why if you check my theme code you'll notice it's not 100% themed and only the main parts and a lot of missing icons.

Yeah that would be ideal method really but since the ispconfig3 upgrades are a little brutal and overwrite almost everything you changed, you have to keep backup copies and diff them in case they've added something to the page which a backup&restoring of your modified file would restore back to the old copy.
So i did it my way only for easy upgrade reasons only.
Would be nice if the ispc team styled everything a little better.

Click to expand...

Custom themes never get overwritten. The only things that get overwritten are ispconfig core files. But you can not improve a software if you do not change the core sources. And changed source files have to be written on a update.

For customisations, ispconfig has a lot of areas which dont get ovewritten:

Custom themes never get overwritten. The only things that get overwritten are ispconfig core files. But you can not improve a software if you do not change the core sources. And changed source files have to be written on a update.

For customisations, ispconfig has a lot of areas which dont get ovewritten:

Just one question I was working on some little customizing myself nothing big,
I have just copied the default theme Dir. and added my own logo and favicon.
(of course left the powered by ispconfig were it is I am proud to use it)

So if I name this Dir, mytheme and put this beside the default one It won't get deleted upon a update.

So if I name this Dir, mytheme and put this beside the default one It won't get deleted upon a update.

Click to expand...

this is how i do it.

(just to know: the SVN- Version changes the template-handling, so that you only have to save the files, you change and not all files of the default-template - BUT DO NOT USE SVN IN PRODUCTION SYSTEMS!)

I did that... I created my new dir. and changed some colors on the side menu css.
Changed the template on both System and Client... checked if it updated on the DB and its ok.
When I use Firebug to view the css of the side menu, the original default color stills there, because the path to the css continues on the default, not the one I created.

Where on the code is the template set for the user?

I'd love vogelor, but my ISP is not available for external access yet... thanks!