Template Issue

From what I can see, it's not possible for a site to have two templates with different colour schemes when the Wall module is deployed.

I'm trying to develop two versions of the EVO template with different colours, but the Outline has its own CSS colours which affects all templates, even ALT. 

How can I control this so that each template has its own distinct outline colours?

See examples.

Simple.

Create a folder in the wall modules template folder for your template.

modules/boonex/wall/templates/tmpl_yourtemplatename

In there create a css folder. Copy the outline.css from modules/boonex/wall/templates/base to your new css folder and edit as needed.

You can do this for each installed template.

This is actually a common issue for template developers when developing templates that are darker than the default template. Every module can have a template folder for the specific template. The wall module would not be the only one. The shoutbox module can also be a issue. It really depends on how many colors are different between the two templates. Your lucky if only one module needs a template folder for your template. If you were trying to design a black template, half the modules would most likely need changes.

Thanks for responding so quickly Deano. 

That worked fine and thanks for the detailed explanation. There may be other areas where I'll need to apply the additional css but so far the Wall is the only one I've sruck trouble with. I don't use the shout box.

regards

John

A good manual on Dolphin Templates, how they work, the use of keys etc, should be done.  Maybe we can get some tech writers to help out when we fork Dolphin.

In my past life I specialised in developing technical manuals. I can't remember how many I've done, but it would be in the hundreds. Sadly I never wrote any of them, I just compiled them from information supplied. I did have to follow instructions, capture screen shots and bark if I couldn't understand anything. I guess that made me a beta tester and an editor, but people did explain how things were done. I just listened, tried what they said and wrote instructions for the next sucker.

You've seen my work here on the forum, but I hardly know anything about Dolphin's complexities. I need people to show me how to do things and I can then prepare a manual from what they tell me and from what I learn.

I've said it over and over again. Boonex can only blame themselves for Dolphin's demise because nobody has bothered to write a manual. There's some great (brilliant!) stuff out there, but it's like a train wreck. Oddly, I can find 90% of what I need doing a simple Google search, but rarely, if ever, do those searches take me to pages written by the Boonex team.

Someone at Boonex has spent a lot of time putting stuff on Boonex Trak, but finding it isn't easy. Without it, most newcomers will steer away and go elsewhere. People look for information and Boonex has constantly  failed to supply it, for Dolphin and for UNA which will also fail for the same reasons - Lack of documented support!

Surely we're not to young to remember programs like Wordstar that came with 400 page manuals and help files that took a year to read. Although programs have become more intuitive, Dolphin is not one of them. It's brilliant, fantastic and incredible, thus my reason for sticking with it, but it's an almost impossible learning curve for novice site managers and their members.

We need to make things easier, but it's a bit like closing the gate after the bull has bolted. I have hundreds of tips and tricks and there's hundreds, maybe thousands more on the forums. I'd love to compile them all into some kind of manual, but for whom? How many people frequent this forum? How many serious users are there out there? Boonex refuses to tell us and we can only guess. Are we flogging a dead horse, or can we keep people motivated? Without a Youtube presence, without a manual, without third party developers pulling their fingers our, I say we don't stand a chance.

Maybe the best place to start is with a clean slate and a module to move the Dolphin database to something else. Some time ago a member told me about Wiccle, an Irish script that died because of company infighting. It did everything Dolphin did in a package weighing in at 12 meg, not 60 or 80. Over half the pages in Dolphin could be made redundant and everyone would benefit. I say start from scratch, take ideas from Dolphin, but refine them for the twiddle box era. Forking Dolphin may do nothing more than fork the problems we constantly hear about on this forum.

'nough said.