Issue: CSS Manager

Issue Tools
- View Changes

August 12, 2008 2:00 AM

pegasus

VaultWiki Team

CSS Manager

AdminCP interface for special.css

This Feature Request was created in response to this thread: https://www.vaultwiki.org/showthread.php?t=1474

A CSS Manager similar in design to vBulletin's Style Manager -> Main CSS should be used to handle special.css. Properties that preserve the overall layout should be hidden, except in Debug Mode, so the extent of control permitted should be tailored to each specific selector.

The manager should use vBulletin's option to decide whether or not to generate a CSS file.

Issue Details

Issue Number 180

Issue Type Feature

Project VaultWiki 3.x Series

Category Styling / CSS

Status Implemented

Priority 2 - Fatal / Database Errors

Suggested Version 2.0.0

Implemented Version 2.2.0

Milestone VaultWiki 2.2.0

Software DependencyAny

Votes for this feature 1

Votes against this feature 0

Attachments 0

Assigned Users (none)

Tags (none)

August 12, 2008 4:09 PM

sowosammerneger

Junior Member

Why would you like to make a new CSS manager?
Can't you use the one already implemented in vb?
I don't see the reason to invent the wheel a second time, but maybe I don't get you right.

Reply
August 12, 2008 6:27 PM

pegasus

VaultWiki Team

The reason for this is that the wiki's CSS has to be imported to the page separately from vBulletin's. If we use the same manager for this, we risk mixing these up. On top of this, there are some CSS properties that should not be modified or your wiki's layout will break. vBulletin's existing system does not support "read-only" properties.

Reply
August 19, 2008 7:06 AM

sowosammerneger

Junior Member

Wouldn't that be possible with a headinclude template?
I have never seen that vb changes anything other then their own templates and those we don't have to touch or have we?

Reply
August 19, 2008 10:53 AM

pegasus

VaultWiki Team

I mean that there are some properties we do not want admins to change. For this reason it would be more practical to have a validator. Also, because we still want to support saving CSS to files to avoid HTML clutter, we cannot simply use a headinclude template.

Reply
August 19, 2008 12:11 PM

sowosammerneger

Junior Member

Originally Posted by pegasus

I mean that there are some properties we do not want admins to change.

I got your point, but I don't think there is anything an admin can't change ...

Reply
January 25, 2009 2:32 AM

pegasus

VaultWiki Team

Well this was a nice, simple feature that had a hard-to-make implementation. Basically, the Wiki Style Manager shows the wiki headinclude and footer templates.

It also controls the Wiki CSS, which is divided into a number of templates, to make it easier to find the CSS selectors you're looking for. The fact that the CSS uses templates means that your changes will not be overwritten on upgrades and you can have different CSS for each of your forum's styles. In addition - and this was the crazy part to write, if your forum stores its CSS as files, the Wiki's CSS will also be saved to style-specific files in the vbulletin_css directory.

Getting the file to rewrite every time a wiki CSS template was possibly changed was the hard part. After considering all of vBulletin's methods, we also added support for the Advanced Product Management and Template Modification System mods.

Reply
January 26, 2009 1:05 AM

pegasus

VaultWiki Team

It took an additional day, but it looks like we've ironed out most of the bugs in this feature, and now our wiki's style is entirely controlled by it.

Reply

+ Reply

All times are GMT -4. The time now is 1:58 AM.

This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.

Learn more… Accept Remind me later

Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

Issue: CSS Manager

Issue Tools