Difference between revisions of "Extension talk:Wikiskin.php"
(New section: Setup Questions) |
m (→Setup Questions) |
||
(6 intermediate revisions by 3 users not shown) | |||
Line 46: | Line 46: | ||
- [[User:Tdoyle|Tdoyle]] 07:28, 4 November 2007 (NZDT) | - [[User:Tdoyle|Tdoyle]] 07:28, 4 November 2007 (NZDT) | ||
+ | |||
+ | P.S. I think I figured it out - the solution appears to be to copy the contents of /skins/monobook/main.css as well as any content at Mediawiki:Monobook.css to Mediawiki:WikiSkin.css. | ||
+ | :Have a look at [[Freelance]] for an example. --[[User:Rob|Rob]] 09:51, 4 November 2007 (NZDT) | ||
+ | ::Yes, the purpose of wikiskin is to allow all skin features (content and CSS) to be defined in-wiki. I'll eventually add the ability to turn wikiskin on or off from preferences, but for now you could add a hack into the ''wfSetupWikiSkin'' function which bails if the user isn't you, | ||
+ | <php> | ||
+ | global $wgUser; | ||
+ | if ($wgUser->getName() != 'You') return; | ||
+ | </php> | ||
+ | |||
+ | == Example broken == | ||
+ | Looks like the [{{fullurl:Freelance/Demo|skin=Freelance}} example here] has stopped working. Seems to be ignoring the ''skin'' key. --[[User:Rob|Rob]] 09:56, 4 November 2007 (NZDT) | ||
+ | :Fixed - it was when LocalSettings was re-organised the skin setting got put after the wikiskin extension include, but should be before. --[[User:Nad|Nad]] 10:38, 4 November 2007 (NZDT) |
Latest revision as of 21:45, 3 November 2007
Where can I see a page that uses this extension? --Rob 14:58, 6 Apr 2007 (NZST)
Has anyone an more detailed demo or description for setting up the wikiskin? --User:nope 14.5.2007
- It's still in beta state, but is working ok, just save the code into a file and include the file from your localsettings.php, but make sure your skin article is created first (the name of the article is set in $wgWikiSkin, the default name for the article is WikiSkin). OrganicDesign and our other wikis use it, OrganicDesign:Default-skin is the $wgWikiSkin article on it. We're just using it to replicate the standard monobook layout currently, but it's been developed for use with MW:Extension:Wiklets which is a desktop-like skin where different articles and forms work like windows on a desktop. --Nad 21:50, 14 May 2007 (UTC)
Brilliant! Question: Why did you decide to put the skin variables like {{ACTIONS}} into the global MediaWiki variable namespace instead of using wikiskin-specific tags along the lines of @@ACTIONS@@? Ehartwell 00:07, 11 July 2007 (NZST)
- I want them to be expanded by the wiki-parser as usual, so they need to be either mediawiki variables or parser-functions. --Nad 09:41, 11 July 2007 (NZST)
Contents
Private wiki & Public www
See Maintaining websites with a wiki
Propsed variables to add
- Anonymous
- Regexp
see MW:Extension talk:WikiSkin
Edit icons
I like this extension becasue it enables the use Treeviews and I have a complex nested subject taxonomy,
Suggestions
It would be very nice to see the edit icons when editing a pages.
FCKeditor
I am also trying to get Mediawiki FCKeditor extension to work on my site. Next step would be have Wikiskins, Treeveiws and FCKeditor working together
Talk continues
Made a new article called Blog-skin, and trying to activate it with this URL. Checking out the extention code, seems this line is defaulting to WikiSkin as the skin article.
$wgWikiSkinArticle = isset($_REQUEST['skin']) ? $_REQUEST['skin'] : 'WikiSkin';
But this article does not exist. Is $wgWikiSkinArticle set in LocalSettings? --Rob 22:48, 16 September 2007 (NZST)
Setup Questions
Hello and thank you for such an interesting extension. I am trying to get this running on my wiki, but I am having some issues.
I've loaded the extension, activated it in localsettings, and added the recommended Mediawiki:WikiSkin article. However, when I view pages, they all look like the classic skin layout instead of the Monobook layout. I noticed in the WikiSkin article that it references the division IDs of "column-content", "content", "bodyContent", and "column-one". On my wiki, these are defined in /skins/monobook/main.css, and it is this definition that makes the columns appear where they do in Monobook. However, I can't see where your extension is loading /skins/monobook/main.css and I can't see where else it might be loading these division specifications to show a skin which behaves like monobook.
Also, is it possible to have this extension only activate if a user has a certain skin selected in their preferences? I'd like to test this without affecting all of my users. It seems to me that this might be doable with a small change in the function wfApplyWikiSkin and a dummy WikiSkin skin created to make WikiSkin show as an option in preferences.
Thank you!
- Tdoyle 07:28, 4 November 2007 (NZDT)
P.S. I think I figured it out - the solution appears to be to copy the contents of /skins/monobook/main.css as well as any content at Mediawiki:Monobook.css to Mediawiki:WikiSkin.css.
- Have a look at Freelance for an example. --Rob 09:51, 4 November 2007 (NZDT)
- Yes, the purpose of wikiskin is to allow all skin features (content and CSS) to be defined in-wiki. I'll eventually add the ability to turn wikiskin on or off from preferences, but for now you could add a hack into the wfSetupWikiSkin function which bails if the user isn't you,
<php> global $wgUser; if ($wgUser->getName() != 'You') return; </php>
Example broken
Looks like the example here has stopped working. Seems to be ignoring the skin key. --Rob 09:56, 4 November 2007 (NZDT)
- Fixed - it was when LocalSettings was re-organised the skin setting got put after the wikiskin extension include, but should be before. --Nad 10:38, 4 November 2007 (NZDT)