Recent Changes - Search:

Cookbook

PmWiki

pmwiki.org

Light Skin Comments

These old comments were moved from the Light Skin page in order to keep that page shorter and easier to read.

  • I played a bit with the new siteadmin feature. How about using this string instead:
    <td align="left" <!--wiki:$Group.PageFootMenu $SiteGroup.AdminBar--> </td> so it would be possible to change conntent by editing Site/AdminBar and put a (:if auth admin:) to the header. MarcSeibert August 30, 2005, at 06:34 PM

It's a good suggestion, Marc. Ironically, I read about <!--wiki:--> markup in the new PmWiki.SkinTemplates page and was considering how it wold be useful. Did you mean to include $Group.PageFootMenu in that line? If so, why have $Group.PageFootMenu in there?

Ups, sorry that was a cut and paste error... It should be only $SiteGroup.AdminBar (I took that line from the Gemini Skin) So I tried this and it works fine - just a little problem when I want to text-align:left. Text for now is allways centered, dont no why ...The other problem is that an empty table is shown when doing a (:if auth admin:) and viewing the site in normal mode . so I excluded #siteadmin from site- and wikiview. MarcSeibert August 31, 2005, at 04:27 AM

The following code in light.php will show the (as-distributed) Admin Bar only if you have admin authorization.

if (CondAuth ($pagename, 'admin')) {
  SetTmplDisplay('PageAdminFmt', 1);
} else {
  SetTmplDisplay('PageAdminFmt', 0);
}

I think a good way to do it might be something like

<!--wiki:$Group.AdminBar-->
<!--wiki:$SiteGroup.AdminBar-->

and putting the whole table in a wiki page. Right now I can't think of any important group-specific links that would go into $Group.AdminBar.

Another thought is to include a capability to use something like a 'skinconfig.php' script and not mess with including wiki pages. No matter what, the equivalent to an (:if auth admin:) will be used.

The admin bar is in an extremely early stage right now. My main focus at this point is to figure out which links might belong in the admin bar (or elsewhere). The list is growing.

  • Non-page-specific
    • RefCount
    • Search-pmwiki.org form
    • Diag / phpinfo
    • User Management
  • Page-specific
    • Delete Page
    • Clear History
    • Rename Page
    • Change Attributes
    • Approve Sites
    • Approve URLs
  • User-specific
    • Profile Page
    • Preference Page
  • Non-admin
    • Login
    • Logout
    • Site Map
    • Create-new-page form
    • Backlinks
    • RSS feed (page, group recent, site recent)

Yes, there are many possibilities. For me there are some more like:

  • a link to confix to controll the server
  • a link to Webftp
  • a link to an Java-Shell

and some more. The fact is that I dont want to show the links to everyone because that doesnt make a website saver :) MarcSeibert August 31, 2005, at 04:37 AM

  • Thanks for the great skin. We've been using a modified version of it for about a year, on the PmWiki v2 beta. We moved over to PmWiki v2 in October, and I updated the skin at that point. I then turned on UTF-8 enablement in the config, but discovered that there were some conflicts (which I didn't then have time to track down). I now see that Light Skin sets a meta of ISO-8859-1, so I went in and modified that on our copy to UTF-8. David Ing 12/08/2005.
    • David, It's a translation setting. Rather than editing the template file you can just insert the following line in your XLPage:
      'ISO-8859-1' => 'UTF-8',
    It's probably better to use the XLPage method, because then you won't need to remember to do it again when you upgrade. --Hagan

  • Hi, I just have a quick question. Why are the links of the navigation bar not showing in mozila-firefox, and is there a way to have them show up? The skin looks great in lynx, which is what I use, but the navigation links don't show up in mozila, which would be a problem for new users. I couldn't find any reference to a config option which might allow one to change this behaviour. Thanks, and a happy new year to all. --S.M.
    • If the skin has a problem for new users it needs to be fixed, but I'm not sure what you mean by the "links of the navigation bar". Hence I don't know what behavior you want to change via a configuration option. As far as I know Firefox renders pages properly since that was the browser I used primarily during development. --Hagan
    • From what I understand, the navigation bar (view/edit/history/) doesn't show up in firefox, so that users cannot see any link to edit the page: do you observe the same behaviour? In lynx, thse links display just fine... --S.M.
    • Oh, the wiki links. They're also known as action links.
      Here's the short answer: Use
      SDV($View, 'wiki');
      in your config.php file.
      Here's the long answer: By default the action links don't appear unless you have authorization to edit the page, making your wiki look more like a web site to non-editor visitors. I'm guessing you've set a global edit password and the links disappeared when you did that. The version you're using uses CSS (specifically, {display:none;} ) to suppress the links. In future version the links just won't appear. One solution is to hit Alt-E (the accesskey for the Edit Page link) in Firefox to see a login prompt. Once you're logged in you'll see the links. Another solution is to use a Login link. Here's some code you can use to create Login/Logout links:
      (:if ! auth edit:)
      [[{$Name}?action=login | $[Login] ]]
      (:if auth edit:)
      [[{$Name}?action=logout | $[Logout] ]]
      (:ifend:)
      --Hagan
    • Update: With version 0.15.0, the "site" view isn't used unless you turn $EnableCMSMode on. (It's off by default.) In other words, the links stay visible by default. Thanks for the feedback. --Hagan

HOW TO SETVIEWS

Love the skin... but i want it to always default to what you use as an example "demo3" from start to finish on all pages. I thought the way to do it was to set the default view in the lightviews.php as follows: if (empty($View)) { SDV($View, 'demo3'); but that did not work...the view keeps changing. Where do i need to change to stay with the one look? Thanks for the great skin.

First, I apologize for not noticing your note for so long! The answer is to set the view in a local configuration file (e.g. config.php).

$View = 'demo3';

Alternatively you can place this CSS fileΔ at pub/css/local.css.

I'm not sure what you mean by "the view keeps changing" though. Something to keep in mind is that browser caching via If-Modified-Since HTTP headers may require you to do a "full refresh" (SHIFT-Reload in Firefox, SHIFT-Refresh or maybe CTRL-Refresh in MSIE) to avoid retrieving pages from your browser's cache. (Reference)
--Hagan


$EnableDrafts does not seem to work with this skin. When you edit a page, the "save as draft" button does not appear as it does with orginal pmwiki skin. jpg.

Try version 16.2, which has the button added to the form.
--Hagan

It's OK with 16.2. Thx, jpg

HaganFox September 21, 2006, at 02:35 AM Problem with CommentBoxPlus

There's something about the way this skin works that prevents the (:commentboxchrono:) action in the various CommentBox recipes from working for non-authenticated users. It would be nice to find a way to allow the CommentBox recipes to modify the page without requiring authentication. - gdb (09/02/2006)

See if it works with version 0.16.3.
--Hagan

Yes. This appears to be working correctly now. Thanks! - gdb (09/03/2006)


Problem with CommentBoxPlus

There's something about the way this skin works that prevents the (:commentboxchrono:) action in the various CommentBox recipes from working for non-authenticated users. It would be nice to find a way to allow the CommentBox recipes to modify the page without requiring authentication. - gdb (09/02/2006)

See if it works with version 0.16.3.
--Hagan

Yes. This appears to be working correctly now. Thanks! - gdb (09/03/2006)


Please change "Attachments" by "Attach" in the topmenu as it is already translated (for fr and surely others). Change also in light.tmpl the line <span id='footlastmod'>$[Page last modified on $LastModified]</span> by <span id='footlastmod'>$[Page last modified on {$LastModified}]</span> (note '{' and '}'). Thanks, jpg.

Sorry, I didn't catch these in time because I didn't see your request, which was in my navy-blue reply div.
--Hagan

Ready for 0.16.3? ;-) jpg

I made the change to the last-modified line, but I still like "Attachments" better than the verb. Would it be much trouble to add a translation for "Attachments" to the XLPage?
--Hagan

For me, it can be as you want! ;-) Attachments=Attachements in french.

Edit - History - Print - Recent Changes - Search
Page last modified on May 22, 2007, at 02:57 PM