Mike 's Bookmarks tagged pmwiki →  View Popular

How to add "title" attributes to all links?

Description

Attach:linktitles.phpΔ

Link titles are displayed in a small tooltip when the mouse cursor passes over a link. It can be used to provide additional information and/or URL and is a usability recommended feature (*).

To use this script, download itΔ, place it into the cookbook/ folder and add the line

 include_once('cookbook/linktitles.php');

to a local customization file (local/config.php).

Then you can add a link title by placing it in parentheses after the link text:

• [[Main/HomePage|Home (Go to the site home)]] prints "Home" (and title "Go to the site home")
  
• [[ My website (Blog and freeware stuff) -> http://5ko.free.fr ]] prints "My website" (and title "Blog and freeware stuff")

What I would like to see is a "last edited by" block that includes everybody who had a hand in developing the page. It would be nice to show who originally started the page. Maybe add a block of text to PmWiki pages showing the last editor and all previous editors, such as:

Questions answered by this recipe

• How can I require authors to provide a name when they edit pages?
  
• Can I force PmWiki to use an authenticated login name as the author name?
  

Answer

Add the line

    $EnablePostAuthorRequired = 1;

This recipe provides a way to automatically keep a list of the pages each author has edited by producing an "Author Contributions" page with a name of Profiles.<author's name>-Contrib for each author that has a page in the Profiles group.

Contributions by authors without profile pages are placed in a single Profiles.Other-Contrib page.

Description

Download authorcontrib.phpΔ and place it to your cookbook/ directory, then insert the following line in your local/config.php file:

if ($action == 'edit' || $action == 'comment') {
include_once("$FarmD/cookbook/authorcontrib.php"); }

Armin, how did you manage to get the Google adwork running on a wiki page. I tried that before but don't know where to add the Google code. Thanks, Oliver

I guess, I've added the Google Adsense lines to the .tmpl file, for the skin I'm using. Have to check source code at home.Armin

Suppose an admin wants to have a simple "(:example:)" markup that will always produce a fixed HTML string in the output, such as for a webring, Google AdSense display, or Javascript. The Markup() call to do this would be:

Markup('example', 'directives',
  '/\\(:example:\\)/',
  Keep("<div class='example'><p>Here is a 
    <a target='_blank' href='http://www.example.com">link</a> to
    <em>example.com</em></p></div>") );

• The first argument is a unique name for the markup ("example").
  
• The second argument says to perform this markup along with other directives.
  
• The third argument is the pattern to look for "(:example:)".
  
• The fourth argument is the HTML that "(:example:)" is to be replaced with. We use the Keep() function here to prevent the output from being further processed by PmWiki's markup rule -- in the above example, we don't want the http://www.example.com url to be again converted to a link.
  

Define a markup to call a custom function that returns content

An 'e' option on the $pattern parameter will cause the $replace parameter to be treated as a PHP expression to be evaluated instead of replacement text. Thus, a markup to produce a random number between 1 and 100 might look like:

Markup('random', 'directives',
  '/\\(:random:\\)/e',
  "rand(1, 10)");

This calls the PHP built-in rand() function and substitutes the directive with the result. Any function can be called, including functions defined in a local customization file.

Arguments can also be passed by using regular expression capturing parentheses, thus

Markup('randomargs', 'directives',
  '/\\(:random (\\d+) (\\d+):\\)/e',
  "rand('$1', '$2')");

will cause the markup (:random 50 100:) to generate a random number between 50 and 100.

For a PmWiki function to help with parsing arbitrary sequences of arguments and key=value pairs, see Cookbook:ParseArgs.

<< Custom InterMap | Documentation Index | Custom WikiStyles >>

• 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

1. Download the latest version of PmWiki as a zip archive (pmwiki-latest.zip) or a gzipped tarball (pmwiki-latest.tgz) from http://www.pmwiki.org/pub/pmwiki/.

2. Unpack the archive (tar zxvf pmwiki-latest.tgz or unzip pmwiki-latest.zip). This will create a pmwiki-x.y.z directory containing the PmWiki software. For example, the current "latest" should unpack to a directory named "pmwiki-2.0.13". The files in this directory include:

    COPYING            The GNU General Public License
    local/             A directory for local configuration scripts
    pmwiki.php         Main PmWiki script
    pub/               Directory of publicly accessible files
      css/             Directory for generic .css files
      skins/           Directory of layout templates (skins)
    sample-config.php  A sample configuration file
    scripts/           Some scripts that extend the possibilities of PmWiki
    wikilib.d/         Directory containing some default PmWiki files
    cookbook/          A directory for recipes obtained from the Cookbook.

3. The pmwiki-x.y.z directory needs to be placed into a location accessible by your webserver (e.g., in a public_html directory of some sort). You can place files and directories using a number of methods -- FTP, or a Unix mv or cp command generally does the job.

4. Open a web browser to the pmwiki.php script on the server (i.e., not the one on your local computer or accessed using a file://... URL). PmWiki will then analyze your system configuration and provide instructions (if needed) for creating the wiki.d/ directory which will be used to hold the pages created for your site. Usually there are two ways to achieve this:

        chmod 2777 .

5. After establishing directory permissions, try opening a browser to the pmwiki.php script again. If all is well, the wiki.d directory will have been created and you'll see the default home page.

Important: If you used method 4b, you should reset permissions by executing "chmod 755 ." in the directory containing pmwiki.php.

6. Check out Initial Setup Tasks for other tasks you may want to perform to begin customizing your PmWiki installation. You might also want to peruse the Release Notes for further information.

7. If you want to use PmWiki in a different language download the international language pack as zip archive (i18n.zip) or as gzipped tarball (i18n.tgz) from http://www.pmwiki.org/pub/pmwiki/. Then extract it and copy the files into the wikilib.d/ directory as described above

Most PmWiki configuration is performed in a file called local/config.php. Some configuration is done on special pages in the Site group, such as the Site.SideBar menu.

Modifying config.php

When you first install PmWiki, the local/config.php file does not exist. Copy the sample-config.php file (in the same directory as pmwiki.php) to local/config.php and use it as a starting point. You could create local/config.php from scratch, but sample-config.php is already populated with many of the options you might want to adjust.