Default Skin Without Table < Skins > DropShadow   (talk? | users? | test page | RWD? | set as default | unset | validate: HTML, CSS)

1. Tab for editing, upload, viewing, attributes (idea taken from BronwynSkin)
2. Integration of a document $Group.MenuBar which is displayed ahead of the text.
3. The really special thing is: the MenuBar is displayed as drop down menu
4. Link at the bottom of the page to jump to the top of the page
5. Two additional links for directly editing the documents $Group.SideBar and $Group.MenuBar.
6. If no $Group.MenuBar exists then automatically Main.MenuBar is loaded. If none of both exist, well then nothing is loaded and displayed. You will not recognize that.
7. If the directive (:noheader:) is used the edit links for the MenuBar and SideBar disappear from the footer. This is nice for using PmWiki as CMS which has edit capabilities, that are not too obvious.
8. Menu mode selectable (compatibility mode; dropdown menu in MenuBar, dropdown menu in both SideBar and MenuBar, dropdown menu only in SideBar.
9. Highly customizable: a lot components can be removed or are switchable
10. Link bar at the bottom (BottomBar) can be customized (wiki document)

Download

This is always the latest version as there are comments in the history below. Additionally within this archive you can find a file history.txt which tells you the version.

This is the simplified version of this skin without any menu handling. If you need menu handling use a cookbook recipe (e.g. HorizontalVerticalMenu)

Installation

Copy the content of the above ZIP-file to /path/to/pmwiki/pub/skins/ and add the following code to your local configuration file:

  $Skin = 'dropdown';

If you also want to use the different print layout you also have to add:

  $ActionSkin['print'] = 'dropdown';

There is also some further functionality which could be set:

  $DropDownSkin['Version'] = 0;

 $DropDownSkin['SideBarEdit'] = 0;

 $DropDownSkin['MenuBarEdit'] = 0;

 $DropDownSkin['BottomBarEdit'] = 0;

 $DropDownSkin['LeftSearch'] = 0;

 $DropDownSkin['PrintPreview'] = 0;

 $DropDownSkin['PageLeftFmt'] = 0;

 $DropDownSkin['PageFooterFmt'] = 0;

 $DropDownSkin['PageHeaderFmt'] = 0;

 $DropDownSkin['PageTitleFmt'] = 0;

 $DropDownSkin['PageMenuFmt'] = 0;

Internals / Examples

For versions up to 13-Jan-2005 or $DropDownSkin['Version']=0 (=compatibility mode)

I had to integrate some small javascript code in the .tmpl file to get the drop down menus also working in IE (Some faulty implementation of :hover). It did already work before this "hack" with Gecko based browsers (Mozilla, FireFox). It should also work with Opera.

The document MenuBar consists of nested lists, also you need an additional style statement for the menut titles. Here is an example (taken from Main.SideBar):

 * %menutitle% Main.SideBar
 ** [[Main/Home Page]]
 ** [[Main/WikiSandbox]]
 ** [[Main/AllRecentChanges]]

 * %menutitle% [[PmWiki/PmWiki]]
 ** [[PmWiki/Installation | Download and Install]]
 ** [[PmWiki/Tips For Editing]]
 ** [[PmWiki/Documentation Index]]
 ** [[PmWiki/FAQ]]
 ** [[PmWiki/PmWikiPhilosophy]]

The style %menutitle% is again needed for proper display of the drop down menu within IE.

For versions after 13-Jan-2005

This skin is based on nested lists and uses heavily the :hover feature. Most actual browsers support this feature. IE has limitations: It only interprets a:hover (links).

I found a source in the web where this :hover functionality is activated for all HTML entities within IE. This behaviour is programmed with help of an external script csshover.htc. More Information about that can be found at Peterned. Search for whatever:hover. Known problem: For Windows XP2 the webserver has to send the type "text/x-compressed" for ".htc" files. This script is only loaded by IE.

I changed from bulleted lists to numbered lists for compatibility with existing SideBar's. So the MenuBar and SideBar could have the same layout. Just one Exception. The SideBar can hold some other text too, but I would not recommend it for the MenuBar.

 # %menutitle% Main.SideBar
 ## [[Main/Home Page]]
 ## [[Main/WikiSandbox]]
 ## [[Main/AllRecentChanges]]
 ----
 # %menutitle% [[PmWiki/PmWiki]]
 ## [[PmWiki/Installation | Download and Install]]
 ## [[PmWiki/Tips For Editing]]
 ## [[PmWiki/Documentation Index]]
 ##%menuitem%Additional submenu
 ### [[Skins/Skins]]
 #### [[Skins/DropDown]]
 #### [[Skins/Lines]]
 ### [[Cookbook/Cookbook]]
 ##%separator%-
 ## [[PmWiki/FAQ]]
 ## [[PmWiki/PmWikiPhilosophy]]
 (:searchbox:)

Above you can see several styles: %menutitle% is necessary for correct display of the Main menuentry. %menuitem% is necessary when an entry in the menu is not a link. You can use %separator% for displaying a separator line in the menu. For IE compatibility (to see a line) you have to add some text (no matter what text, but I suggest "-").

In the BottomBar the links or text should be written within a numbered list for correct display in a row. Example:

 #[[Main/SearchWiki |SearchWiki]]
 #[[{$Group}/RecentChanges |RecentChanges]]
 #[[Main/AllRecentChanges |AllRecentChanges]]
 #[[PmWiki/WikiHelp |WikiHelp]]

But you can also place here whatever text or link you like. I would recommend only to place some few useful links here, because otherwise you'll distract from the real interesting stuff: the content! When no BottomBar document exists the above sample (HTML-hard coded) is displayed.

Translations

One thing could be translated in your own language (just add this line to your local XLPage (if is does not exist yet):

  'Read Page' => '',
  'Page Attributes' => '',
  'All Recent Changes' => '',
  'Edit' => '',
  'Top' => '',
  'Go' => '',
  'SideBar' => '',
  'MenuBar' => '',
  'BottomBar' => '',
  'Main/AllRecentChanges' => '',
  '$Group/RecentChanges' => '',

Additional hints

Removing components of the skin (temporarily)

These are standard markups that work also with this skin:

 (:notitle:)

 (:noheader:)

 (:nofooter:)

Here are some markups that are available only with this skin as it provides this functionality itself.

 (:noleft:)

 (:nomenu:)

Add search to MenuBar and SideBar

Simply place the following directive in the MenuBar or SideBar, but not within the list. Do it as a simple text entry (see example above).

 (:searchbox:)

Contributor

Karl Loncarek (Klonk)

History

• 16-Dec-2004 I'm currently working on some minor design (mainly colors) issues. Release will very soon (tomorrow?) - Klonk
  Now it's finished and I uploaded it. Maybe I can create a 'MenuBar' document for showing the dropdown menu, after Pm has integrated it.
• 17-Dec-2004 Fixed a floating problem with IE (a hack was necessary, see comments below). I uploaded the fixed version :).
• 05-Jan-2005 I changed again the .CSS and the .TMPL file. The hack I did earlier introduced another problem with IE. The problem was that the right side of the layout (DIV) didn't took up the available space in IE, when the content (e.g. table) only needed e.g. 80%. Firefox worked already. Now when the browser window get too small for displaying all the content scroll bars are shown (similar to frameset). Thanks to Paul for pointing me onto this problem. I uploaded the new files. - Klonk ... Pm, could you please update the files on this site? Thanks.
  I also found an error in the Javascript within the .TMPL file when no MenuBar is used. IE should now show no error on the page anymore.
  I just updated pmwiki.org to the latest DropDownSkin, and now I'm seeing a scroll bar on the main text body (Firefox 1.0, WinXP SP2). Here's a screenshot.gifΔ that illustrates the problem (note the extra scrollbar on the right-hand site, as well as the overlapping text). --Pm

  This behaviour is correct when something of the content is too big or has a fixed width that is larger than 74,9% of the whole browser width (like in a frameset. It should only occur, when the browser window gets too small. I see the same behaviour here, as I also use Firefox 1.0 (Win2k), but only with this page. During my testing no problem occured. I'll try to find out what element is too wide.
  Even if I maximize my browser window (on a 1024x768 screen) I still see the scrollbars. --Pm

  fixed
• 06-Jan-2005 The .CSS file needed rework as a display problem occured with Firefox (Thanks Pm for pointing on that one), when a MenuBar is used. I don't know why but defining some margins on all four sides instead only on one side helped (in #menubar). Now everything should be OK. If you find any problems, please report. Thanks. The newest version is available for download. I recommend installing the latest version. Klonk
• 07-Jan-2005 I had to change the "overflow" parameter in the .CSS file again as these scrollbars also occured when a page with embedded graphics is shown (in Firefox). Reloading fixed it. It looks like Firefox thinks the page is bigger as it should be because the picture is loaded afterwards. Now it should work again. It looks like current browsers have some problems with the .CSS "overflow" parameter. Klonk
• 11-Jan-2005 NEW With this version the edit-links for the SideBar and MenuBar are removed, when the directive "(:noheader:)" is used. Klonk
• 13-Jan-2005 Removed extra </td> which I forgot in the .tmpl file.
  • found a problem in the dropdown.php. There were missing variables resulting in not working links for EditBar and MenuBar. Affect only users of version from 11-Jan-2005. Please download the newest version. -Klonk
• 17-Jan-2005 NEW and major changes! First small stuff:
  Now $EnablePathInfo is checked and then the edit links are set for compatibility reasons. Also now the text 'MenuBar' and 'SideBar' can be translated. (Thanks Isidor and other) I also added a readme.txt and history.txt to the distribution (mainly a copy of this page)
  Now the major stuff:
  Now it is possible to set the menutype depending on the variable $DropDownSkin['Version']. Depending on the selected mode the menus now allow up to 3 sublevels. (BTW: I think nobody should use more than two sublevels.) Depending on the setting of the variable you can now use also the menu in the SideBar only or in the SideBar and the MenuBar at the same time. You still can use other stuff in the SideBar that the best of all (e.g. email link or something else, even headings as before)
  Pm there is no need to update the files on your server, as then either the text in MenuBar has to be changed or the compatibility mode ($DropDownSkin['Version']=0 has to be activated.
• 19-Jan-2005 Addded variable "$DropDownSkin['SideBarEdit']" and "$DropDownSkin['MenuBarEdit']" which allow removing the edit links for the MenuBar or SideBar indiviually. When a (:noleft:) directive is used the width of the right display area is changed accordingly. Added variable "$DropDownSkin['LeftSearch']" which allows removing the searchbox within the left display area. Added CSS code for handling (:searchbox:) in the MenuBar and SideBar. Fixed some minor display problems that resulted in different display on IE and FireFox.
• 21-Jan-2005 Added variable $DropDownSkin['PageLeftFmt'], $DropDownSkin['PageFooterFmt'], $DropDownSkin['PageHeaderFmt'], $DropDownSkin['PageTitleFmt'], $DropDownSkin['PageMenuFmt'] for hiding the according areas on every wikpage. Fixed loading of styles for print preview (should not be loaded). Added wiwki-markups (:noleft:) and (:nomenu:)
• 26-Jan-2005 NEW: Possibility to edit the bottom link bar (BottomBar). Added variable $DropDownSkin['BottomBarEdit'] for hiding the edit link for the BottomBar. Added also support for loading files according to $DefaultGroup (e.g. $DefaultGroup.SideBar). Fixed some missing handling of links depending on $EnablePathInfo. Also some minor changes in layout to reflect the editable BottomBar and for getting a better cross browser display (at least it should now look the same within gecko based browsers and IE)
• 27-Jan-2005 updated to newest csshover.htc file
• 28-Jan-2005 fixed minor display problem in IE with menus in SideBar.
• 17-Feb-2005 created additional simplified version of thi skin which includes no menu handling. If you want to use menus with it you can use HorizontalVerticalMenu.
• 24-Feb-2005 updated all versions to use new SetTmplDisplay function in PmWiki 2.0beta22
• 28-Feb-2005 Added edit links for GroupHeader and GroupFooter (can be disabled the same way than the other edit links, see above)
• 04-Mar-2005 Fixed problem with PmWiki 2.0beta24, which resulted in wrong display of edit links when e.g. (:noheader:) is used.
• 10-Mar-2005 Another attempt to fix the above display problem, changed way how e.g. (:noheader:) is detected.
• 14-Mar-2005 link #Topp didn't work with IE - fixed (#!*& IE)
• 20-Sep-2006 fixed link to false Searchpage to reflect the actual structure of PmWiki

Comments (are welcome)

• 19-Jan-2005 The (:noleft:) tag is displayed in the Printable View template. - Dan East
• 19-Jan-2005 Printable View does not reflect current page being viewed (page name is not specified). I added n=$x? to dropdown.php:97 as follows to correct - Dan East. echo "<div id='print'><a href='$PageUrl?n=$x?action=print' target='_blank'>".XL("Printable View")."</a></div>";
  • I see this was already fixed in the latest version. Great job on a great skin! - Dan East
• 16-Dec-2004 WOW! Very fine job! Awesome. Darn, I hate to report this but, there are some display issues in IE 6. The main body is dropping out of sight. Sidebar stays put, but the main body drops down so far you have to scroll to see it. Refreshing the browsers was no help. - PL
  • 17-Dec-2004 Thank you very much. I know where the problem is, but I haven't found a good solution yet. The problem is the percentage in the width of the left and right area. both width in percentage sum up to 100%, but IE does not calculate the border into the width. It's set top of this. The problem should not occur, when you maximise your browser window. (behaviour is normal for floats, as I used no tables in the Skin). I'll check whether I can do something to fix this. I also added a document MenuBar to show the working menu on this page. - Klonk
• 01-Jan-2005 I have been trying to find where the main colors are located for this, but had no luck. I looked in the css and the .tmpl file and did some changing in the pmwiki.GroupHeader file (using edit text), but had not luck. Any ideas?
  • Sorry, but I don't understand what are you searching for. All formatting and color layout is done in the CSS file. Look at #right and #left - Klonk
• This is very nice. Excellent work. - GrahamL
• 04-Jan-2005 I just changed the Attribute password the the name of this skin (case sensitive) as i suspect some automated scripts to make some funny things. I hope avoiding automatic changing of edit/view-passwords with this - Klonk
• 04-Jan-2005 Hi Klonk, I notice a minor display problem with your skin when using I.E. 6. There is a wider than desirable blank space between the side bar and the main body on the home page. This space varies widely in I.E. I notice it only affects the home page at my site; other pages display well without wide spacing between the menu and the main body. Could this be because I make HEAVY use of tables in the body on the home page?
  • Hmm, very dfficult to say what causes this. For displaying the left and right part I use floats and IE behaves quit unpredictable when using floats. The sidebar is fixed on 25% width and should not change (could you check this?) When does the width of the space vary? When changing window size? Or only when displaying different text? Do you use tables with a fixed width? This skin was mainly developed with Mozilla Firefox so I did not too much testing with IE. I'll do a little bit of testing with my own test-homepage, which only contains the original PmWiki files... Klonk
  • Sorry I cannot reproduce this effect, maybe it has really something to do with the tables. I know that IE handles the boxmodel a little bit different (e.g. borderline of table is not calculated into width and stuff like this). Can you tell me the link to your homepage or give me the markup source so I can do some testing here? If you want it to mail me, just visit my homepage. There you'll find my email address. Klonk
  • fixed - Klonk
• 05-Jan-2005 Perfect Skin! Kicked mine out and installed yours. Armin
• 13-Jan-2005 I like this skin a lot, and am now using it on my site. Thanks for it! A few minor notes (none of which is great importance):
  • It isn't perfect in Konqueror (I don't expect this to be fixed, it's just a heads-up). In Konq, the border of the menus when they are pulled down tend to be a few times the width of the box, going off to the right.
  • It would be really neat to be able to have hierarchical entries, for example:
    * %menutitle% My Stuff
    ** My Subtitle
    *** A subentry
    *** Another one
    ** My subtitle 2
    *** Subentry...
    You get the drift :) As it is it works somewhat. You can go into nesting depths, but it breaks if you come back out.
  • Perhaps also allow horizontal separators?
  • If the text in the box is reasonably long, it wraps, which looks kinda ugly. Is there a way to increase the maximum width of the box? RobinS
  • I had no chance at testing with Konqueror (as I like Linux, but don't use it at the moment). I really tried hierarchical entries but found no possibility to get this working nicely with LIs (I'll try again, maybe I can come up with something). In the current version only one subentry looks good (one level less than in your example). I assume that the above would only be possible with the use of Javascript, but in that case evaluating the code in MenuBar would get really complicated. Therefore I try to avoid Javascript as far as possible. As the menu is organized as list a horizontal separator is currently not possible (at least I haven't tried it,yet) Increasing the width is quite simple. Just edit the entry #menubar ul li ul li{ in the dropdown.css and increase the width. Klonk
  • Good news: Found a possibility to increase depth of the menu, I also plan to add Dropdown capabilities to the SideBar as desired, just wait and see. :-) -Klonk
• 14-Jan-2005 Great Skin :) Translation fixes
  • SideBar & MenuBar
    Is that possible to make both SideBar & MenuBar translation Items?
    Could be done in dropdown.php
    echo "/SideBar?action=edit'>".XL("SideBar")."</a></li>
    echo "/MenuBar?action=edit'>".XL("MenuBar")."</a></li>";
    to be added also in Translation section
    • Sure, I'll add it for the next release. Thanks for pointing on that
  • Page Attributes & All Recent Changes & Edit
    are to be added in Translation section
    Isidor
    • Thanks, I included this in my local XLPage und thus didn't realize it - fixed -Klonk
• 14-Jan-2005 This is a very nice skin! Fixes for the Edit: Sidebar, MenuBar links if you don't have PathInfo enabled (it doesn't work on my server) -

From dropdown.php...
function IsHeaderShown($x) {
global $ScriptUrl,$pagename;
if ($GLOBALS['PageHeaderFmt']!='') {
echo " <li>";
echo XL("Edit");
echo ":</li>
<li class='bar'><a href='$ScriptUrl?n="; #fixed
echo FmtPageName('$Group',$pagename);
echo ".SideBar?action=edit'>SideBar</a></li> #fixed
<li class='bar'><a href='$ScriptUrl?n="; #fixed
echo FmtPageName('$Group',$pagename);
echo ".MenuBar?action=edit'>MenuBar</a></li>"; #fixed
return;}
}

• It would probably be nice if there was an if statement to see whether the PathInfo was on or off. I didn't try to do that yet.
  • Thanks, I'll add checking for the Pathinfo setting in the next version. -Klonk

• This is a fantastic skin - the one that was closest to what I was looking for to be usable "right out of the box". Using Wiki pages to create the drop downs is a great idea. I did hack it to make several changes, some of which might be worth adding as switches:
  • killed sidebar and left column (redundant with drop downs)
  • increased the body width to 99%
  • removed the "edit SideBar" button at the bottom - no sidebar to edit!!
  • put a search box in the top menu (very easy to do, but doesn't align in IE 6)
  • changed the lower search wiki link to an upload link (I guess my point is really that it would be nice if editing the bottom menu bar was as easy as the top) - later I removed it completely when I realized that one of the tabs was upload!
  • did I say this was a fantastic skin? My changes visible at http://neil.eton.ca/wiki/ NeilHerber January 16, 2005, at 12:12 PM
    • Thanks for your kind words. I'll think about a way to implement your suggestions - Klonk
    • Good news: I will implement most of your suggestions in the next version (watch the history for details), the footer will not be editable (maybe in future). - Klonk
• 16-Jan-2005 - Color / CSS problem (can't change color). A follow up on my January 1, comment. I could not locate the #right or #left tags in my PMWIKI.CSS files. I am on pmwiki-2.0-beta14. Here is the existing css.
  

[..Stuff deleted..]
Could I have the incorrect CSS? Thanks again.

• I think you are searching in the wrong place. Go to the skins directory and search for "dropdown.css" in the "dropdown" subdirectory. Within this .CSS file you will find the desired sections - Klonk

• 20-Jan-2005: A really minor tweak I made was to centre the logo. left-aligned looks OK for texty logos, but a plain graphical one perhaps should be centred or it looks odd. For anyone interested, it was just a matter of wrapping <center>...</center> around the <a href=.. line that displays the logo. One ultra-minor thing about doing this is that it aligns to the centre of the column, rather than the sidebar. Can you think of how I might make it centre-align to the sidebar? (If it requires more than 20 seconds thinking, don't bother. It's only 10 pixels out, just enough to notice if you look for it.) --RobinS
  • Update: worked it out myself. Easier than I thought, just made a minor CSS change:

 #logo{
        /* margin: 5px 0 5px 20px; */
        margin: 5px 5px 5px 5px
} 

• --RobinS

• 21-Jan-2005: I knew I will install this skin only when I saw this one. I have installed PmWiki since 2 days only and not a PHP programmer but can understand most code if can not modify. I have passwords problem another one is where to add javascript code of my 'google adsense' to get it displayed in all pages.

ask for edit password or lets attr set form open without asking for attr password. As I have to put wiki on heavy traffic pages, there may be many vandals also visiting and without it asking for passwords they will mess the whole wiki including navigation links also as left panel is also wide open to edit :( --Raj

• First of all you should put your javascript code (if it normally resides in the HTML head section) into the same section within dropdown.tmpl. Alternatively (which might be nicer) add $HTMLHeaderFmt[] = "....your Javascript code, embedded in HTML..."; to your lokal config.php.
  The passwords have nothing to do with this skin, but nevertheless I'll try to help. The password are set only for one specific page (that one you had displayed before). If you want to set it site wide, you have to do this in your config.php. (see also example config.php and PmWiki/PasswordsAdmin ) - Klonk

• 30-Jan-2005 I have a dumb question: how to narrow the sidebar? -- Danil
  • Open the dropdwon.css file and edit the width in the section #left. Don't make it too narrow otherwise the menu might be wider. - Klonk
• 15-Feb-2005 Menubaritems are all equal width with $DropDownSkin['Version'] = 2;

• 15-Feb-2005 In HorizontalVerticalMenu you wrote that there is an "advanced version of the DropDown. Is the version here the "advanced"? newmy
  • Well, HorizontalVerticalMenu uses the same technique, I used for this skin. It is advanced as it supplies an own markup for building the menu. You can use it also with this skin. But there you run into the same "width" problem described above. Another solution would be the use of the Cookbook/FlexiSkin and the "DropDownSkin" emulation (see alternative Layouts). - Klonk
  • Do you think it makes sense to integrate the same markup etc. from HorizontalVerticalMenu in this skin? - Klonk
    • It's like a "coin with three sides - upper - lower and flanging (don't know what M¨¹nzrand is in Englisch)". I think it would be clearer what to use for what purpose. otherwise we have new markups we (may) not (really) need. I wish it would be included. newmy
      • Hmm, again such a havy change in this skin. Don't like this very much. I think I'll create a version without menus at all and then just HorizontalVerticalMenu could be used additionally. - Klonk
        • I agree with you. good solution. newmy
• 20-Feb-2005 Problem when using MarkupExtensions.
  

• 22-Feb-2005 suggestion for dropdown.php using $DefaultGroup.AllRecentChanges instead of Main.AllRecentChanges analouge to $Group.RecentChanges
  

• 22-Feb-2005 Problem with images e.g. [(approve links) edit diff]
  

 $WikiStyle['imgleft']['align'] = 'left'; $WikiStyle['imgleft']['hspace'] = '10px'; 
 $WikiStyle['imgright']['align'] = 'right';$WikiStyle['imgright']['hspace'] = '10px'; 

• 24-Feb-2005 please include additional Edit-Links for GroupHeader and GroupFooter newmy
  • I would suggest just editing the BottomBar and changing it accordingly e.g. (You have to change the links for the german version, write them down before changing the BottomBar): - Klonk
    
  *Main/SearchWiki *[[Recent Changes]] *[[Main/All Recent Changes]] *PmWiki/WikiHelp *'''Edit:''' *%bar%[[GroupHeader?action=edit|GroupHeader]]%% *%bar%[[GroupFooter?action=edit|GroupFooter]]%%

  • right but the wrong place. I don't want to put this in the ButtonBar, because when i'm using the Cookbook/AuthenticatedAsConditional in conjunction with an (:if ! authenticated edit:) (:noheader:) (:notitle:) (:if:) in the GroupHeader, then the Menus are not visible to the "normal unauthenicated user" but the ButtonBar _is_ visible. So it would be better to put this "inside" the code near the edit-actions of the "SideBar, MenuBar and BottomBar". Please think about this ... newmy
    • done -Klonk
      • The $GroupHeader-Line in dropdownskinsimple.zipΔ seems to be corrupt ... newmy
        • Fixed, thanks for noticing that - Klonk
• 03.Mar-2005After update to 2.24/5 the Constellation (Cookbook/AuthenticatedAsConditional, DropDownSkin with the markup (:if ! authenticated edit:) (:noheader:) (:notitle:) (:if:) in GroupHeader) only the header is hidden when a unauthenticated user opens the page. The edit-line in the button is always shown. In 2.23 the edit-line will be hidden (as described in the "manual"). newmy
  • fixed, see history - Klonk
    • now, if im authenticated to edit, the edit-menu on top and buttom are _not_ shown. better that if i'm once authenticated the edit-functions will be shown until i close the windows or logout with Cookbook/FakeLogout. newmy
      • Try the latest version, should work now - Klonk
• 13.Mar-2005 #TOPP-Link is not working with IE but with FireFox. Is ist able to solve this? newmy
  • fixed, it seems like IE needs some text for the anchor to work - Klonk
• 14.Mar-2005 another strange behaviour with IE ... Its not really possible to mark text on a page for C&P (e.g. for past in another program). With FireFox - no problem. newmy
  • I get the same thing on my wiki (www.srekel.net). This page works fine in IE though, so it might be some local css-change I've made. /Srekel
    • @Srekel: what includes do you use? newmy
    • @newmy: I've tried to use the smileys plugin but didn't get it to work. But even when I tried to reset everything, I got the same result. So it doesn't seem to be any changes I've made, strangely enough.
• 03/17/2005 Please excuse me if this is not the right place to ask a question. I am new to PHP, Wikis & PMWiki. I have started to create one using DropDownSkin. I really like what it has to offer. I have been trying to create a drop down menu at the top similar to what you have on this page. When I copy the code from menuBar & put it in my menubar I get a long & ugly bulleted list rather than a drop down menu. Is there something I need to put in config.php to enable this functionality? Or elsewhere?
  • As default the new Markup is used. Therefore you should use "#" (numbered list) instead of "*" - Klonk
  • As a separate question, is it possible to use "pagelist" or some other function to dynamically create the menus rather than having to hard code them? For example, in the pmWiki.org site, there is a sidebar with a menu which has "documentation index" as 1 topic. When you go to that topic, you get all of the pages in it. But I would like to have a list like that (documentation index) available in the menu under the topic & have pages automatically added if a user adds one. Is it possible to put this in the menu bar?
    • This won't work, I think, as (:pagelist:) creates direct HTML output, and for the menu to work you need wiki markup - Klonk
  • Thanks for any help you can offer. If there is a better place to ask my question, please let me know.
    • You're welcome - Klonk
• 03/17/2005. Thanks for the quick response. In preparing to write back & insert a sample showing that it didn't work w/#'s, I discovered the problem--the #s were not at the left margin! Moved them to the left margin & it's fine.
• 08/11/2005. Very nice!
  But when I want to edit page attributes ( action=attr) where I use
  id: ..... containing more users then the sidebar overlaps the edit window and I can't reach the begining of the lines. What a pitty !
  Would you be so kind to take a care of it?
  Jiri August 11, 2005, at 06:09 AM
• 2006-03-28 For the sidebar to be comatible with PmWiki 2.1, make the following changes
  1. In the template file (dropdown.tmpl) change Main.SideBar to $SiteGroup.SideBar.
  2. Also make a change in the stylesheet file (dropdown.css)

Before
#sidebar h1 {

After
#sidebar h1, .sidehead {

• 23April2006 The syntax for including a header only in edit mode, listed in the 03March2005 entry above is wrong. Tt should be this:

(:if ! auth edit:) Not authenticated to edit (:noheader:) (:nofooter:) (:notitle:) (:ifend:)

This is a great skin.

• 27 June 06. Great skin and I'm trying to adapt it to my site. One think that doesn't work are most of the access keys such as Alt (Windows) or Control (Mac) e for editing. These work fine if I change to another skin. Thanks for hints on how to fix this.

• 15 Aug 06: I can't use the SearchWiki field. There is an error message "The page "Main/SearchWiki" doesn't exist. (Create Main.SearchWiki)". I'm trying to use a complete fresh installation (pmwiki + dropdown skin) but it's the same error message. What is the matter?
  
  

I do not use that skin anymore, but as far I remember the page Main/SearchWiki is not used anymore. Now its Site/Search. I'll change this. - Klonk September 20, 2006, at 02:52 AM

Try to add this line to the search area in your tmpl file : <input type='hidden' name='action' value='search' />