https://www.mineraliengrosshandel.com
https://www.mineral-bosse.de
https://www.edelsteine-neuburg.de
https://www.mineralbox.biz
'._('einklappen').'
 

Plugins

On this page we would like to draw your attention to the use of Plugins.

So-called plugins make it possible in a very simple manner to increase the functional possibilities of the encyclopedia. Pages can be dynamically generated and extended. It is possible to insert tables, paragraphs can be brought together as new pages and pages located. There are many other applications.

Plugins function as mini programms that can used within the context of a page to createn a more dynamic content.


Organization

Plugins are usually entered as shown:

<?plugin PluginName?>

or with the entry field:

<?plugin-form PluginName?>

The command <?plugin will start the plugin and the command ?> will end it. Anything entered / written between the two commands, will be evaluated from the plugin. A plugin should always be at the beginning of a line. It is not necessary to execute all the directions in a line between two commands.

<?plugin BackLinks
  exclude=''
  include_self=0
  noheader=1
  info=''
  page="Category/Chapter"
?>

and

<?plugin BackLinks exclude='' include_self=0 noheader=1 info='' page="Category/Chapter" ?>

have exactly the same function and produce the following results.:

In our example we have chosen the plugin Backlinks.This allows us to see very simply all the pages on the Page page= ,relevant to our example"Category/Mining" , .

Not wanting to have an endless list of terms, we have with showpage="z%" limited the results to pages which start with the letter "Z". In our example this gives us a very limited result.

with exclude='' we can remove single pages from the results.

with include_self=0 we can prevent the current page from being shown in the results.

noheader=1 prevents the number of hits being shown. with "0" we can generate a headline.

The parameter info='' defines other areas / lists which could be showm. In our example none.

If the example is copied and modified to suit individual purposes then a new perspective can be very easily gained.


Plugin within a plugin

Now and again there are special circumstances where a plugin is started within another plugin, for example the Backlinks plugin described here within a Table. The application could be an index.

In this case the end of the internal plugin should not be "?> " but "?\> " instead . Otherwise the first plugin would interperet this as an Endmarker / Command which would lead to unpredictable results.

With some plugins it is also necessary instead of using the command "<? " to use the subplugin preliminary command "<! " .The end of the subplugin will then be marked with the command "!> ".


Operational plugins


Classifications