Club Drupal

    <!--

    See comment about $closure in main module.

    print $closure;

    -->

; Information added by Drupal.org packaging script on 2015-05-25

version = "7.x-1.3"

datestamp = "1432557782"

      'system' => array(

        'table' => 'system',

        'columns' => array('name' => 'name'),

      ),

 *

 * Strings in hook_help() should not be run through t().

  $help_exists = module_exists('help') ? TRUE : FALSE;

  if ($help_exists) {

    // Add tabs to core Help page to access Advanced Help.

    $items['admin/help/tab1'] = array(

      'title' => 'Help',

      'type' => MENU_DEFAULT_LOCAL_TASK,

      'weight' => 0,

    );

    $items['admin/help/ah'] = array(

      'title' => 'Advanced Help',

      'type' => MENU_LOCAL_TASK,

      'weight' => 2,

    // Make Advanced Help the normal help.

    $items['admin/help/ah'] = array(

      'type' => MENU_NORMAL_ITEM,

  $items['help/ah/search/%'] = array(

    $path = explode('/', $_GET['q'], 4);

    $return = count($path) == 4 ? $path[3] : $keys;

  $breadcrumb[] = advanced_help_l(t('Advanced help'), 'admin/help/ah');

    $breadcrumb[] = advanced_help_l(t('Advanced help'), 'admin/help/ah');

        $items[] = advanced_help_l($name, "admin/help/ah/$module");

    drupal_set_title(t('Advanced help'));

          '#href' => "admin/help/ah/$module",

  $form = search_form($form, $form_state, 'admin/help/ah', $keys, 'advanced_help', t('Search help'));

    $form_state['redirect'] = array('help/ah/search/' . $keys, array('query' => array('popup' => 'true')));

    $form_state['redirect'] = 'help/ah/search/' . $keys;

  $breadcrumb[] = advanced_help_l(advanced_help_get_module_name($pmodule), "admin/help/ah/$pmodule");

  $breadcrumb[] = advanced_help_l(t('Help'), "admin/help/ah");

        $readme = '';

        if ('md' == $ext) {

          $readme .=

            '<p>' .

	    t('If you install the !module module, the text below will be filtered by the module, producing rich text.',

	    array('!module' => l(t('Markdown filter'),

	    'https://www.drupal.org/project/markdown',

	    array('attributes' => array('title' => t('Link to project.')))))) . '</p>';

	}

        $readme .=

          '<div class="advanced-help-topic"><pre class="readme">' . check_plain($output) . '</pre></div>';

	$output = $readme;

        $up = "admin/help/ah/$module";

  // There has never been a theme hook for closure (going back to

  // first release 2008-04-17).  Unable to figure out its purpose.

  // $variables['closure']           = theme('closure');

  border: 1px solid #ccc;

.advanced-help-topic p.bob {

  background: #f1f1f1;

  border: 1px solid #ccc;

  display: block;

  margin: 1em;

  padding: .4em;

}

.help-leftalign {

  text-align: left;

}

<p>The help texts can be marked up with standard HTML. They will be

rendered using your site's theme.</p>

<p>If the module or theme author does not make use of the

<em>Advanced help</em> HTML-framework, but if there is a

<p>The help texts may appear in a popup or not as the project prefers.

<p>The help texts may be made searchable. If advanced help search is

<p>When you enable the module, a new tab with the legend “Advanced

help” will show up under “Help”:

<div class="ta-center">

<img class="help-img-center" alt="ahelp_tab.png" src="&path&ahelp_tab.png" width="661" height="225" border="1" />

</div>

<!--

-->

<li><a href="https://www.drupal.org/u/gisle">gisle</a> (current maintainer, D7)</li>

<li><a href="https://www.drupal.org/u/gnuget">gnuget</a> (current maintainer, D8)</li>

<p>To translate a help-file indexed by <strong>Advanced help</strong>,

first create a directory

<code>translations/help/<em>language</em></code> in the project's 

root directory. The <em>language</em>  is the language code that

appears on the <em>Languages</em> page in the administrative UI.</p>

<p>Then, copy the <code>.ini</code> file and all

the <code>.html</code> files from the help directory into this.  If

you need to alter an image to use it in a translation, you may also

put the altered image there.</p>

<p>In the topics section, the <code>.ini</code> file only needs to

keep the topic names (unaltered) and titles (translated). If there is

<code>.ini</code> file may be discarded or ignored.</p>

<p>Each <code>.html</code> file should then be translated in place.</p>

<p>When translating a <code>.html</code> file, you will find that

the <code>&amp;path&amp;</code> keyword (used for images and links)

will lead to the original directory. If you must translate items that

are linked, such as images containing text,

use <code>&amp;trans_path&amp;</code> instead, which will lead to the

translated directory. This will allow you to pick and choose which

linked items, if any, will be translated.</p>

<p>If a topic is not tranlated, the default (untranslated) version

will be shown instead.</p>

<h2>Translating Advanced help's help files</h2>

<p>If you want to help with the translation of

<strong>Advanced help</strong> help texts for a particular language, look for an issue named named “Translation to XXX” (where

“XXX” is the language you want to translate the help texts to) in the <a href="https://www.drupal.org/project/issues/advanced_help">issue queue for Advanced help</a>.

If such an issue does not exist, please can create it.

Choose <em>Category</em>   “Task”,

<em>Status</em> “Needs review” and

<em>Component</em>  “Documentation”.

Upload translated files as an attachment (change the file type from <code>.html</code> to <code>.txt</code> to be allowed to upload). </p>

<p>Uploaded translations will be included in the next version if

reviewed and approved by other users (i.e. gets to status “RTBC”).</p>

site.  Although the <strong>Advanced help</strong> does not provide

general help by itself, it provides a powerful and easy framework that

modules and themes may use to provide their own help.</p>

<p>This file defines five help topics (inside the square brackets), and

<p>To reference items within the help directory, such as images you wish to embed  within the help text, use:</p>

<p>The <code>trans_path</code> keyword refers to a translated version of the image in the translation directory and may be used it differs from the original.</p>

<code>topic</code>, <code>path</code>, and <code>base_url</code>.

This is currently still supported, but will be removed in a future

<p>It as the responsibility of the site manager to make sure this type

of protection is in place if the site has help files that merits

protection from direct access.</p>

<p>To enable advanced help search, navigate to

<em>Administration → Configuration → Search and metadata → Search settings</em>.

Scroll down to <em>Active search modules</em> and tick the box to the

left of “Advanced help”.  The search form will appear on the top of

the advanced help index pages.</p>

navigate to <em>Administration → Reports → Status report</em> and

click the link “run cron manually”.</p>

<a href="http://en.wikipedia.org/wiki/Image:Lerdorf.jpg" class="image" title="Rasmus Lerdorf, who wrote the original Common Gateway Interface binaries"><img alt="Rasmus Lerdorf, who wrote the original Common Gateway Interface binaries" src="&path&180px-Lerdorf.jpg" width="180" height="270" border="0" /></a>

<div><a href="http://en.wikipedia.org/wiki/Rasmus_Lerdorf" title="Rasmus Lerdorf">Rasmus Lerdorf</a>, who wrote the original <a href="http://en.wikipedia.org/wiki/Common_Gateway_Interface" title="Common Gateway Interface">Common Gateway Interface</a> binaries.</div>

<a href="http://en.wikipedia.org/wiki/Image:Andi_Gutmans_1.jpg" class="image" title="Andi Gutmans, who, along with Zeev Suraski, rewrote the parser that formed PHP 3"><img alt="Andi Gutmans, who, along with Zeev Suraski, rewrote the parser that formed PHP 3" src="&path&180px-Andi_Gutmans_1.jpg" width="180" height="244" border="0" class="thumbimage" /></a>

<div class="help-leftalign"><a href="http://en.wikipedia.org/wiki/Andi_Gutmans" title="Andi Gutmans">Andi Gutmans</a>, who, along with <a href="http://en.wikipedia.org/wiki/Zeev_Suraski" title="Zeev Suraski">Zeev Suraski</a>, rewrote the <a href="http://en.wikipedia.org/wiki/Parsing#Parser" title="Parser">parser</a> that formed PHP&nbsp;3.</div>

<p class="attribution">This excerpt is adapted from <a href="http://en.wikipedia.org/wiki/PHP#History">Wikipedia: PHP - history</a>. It is used here under a <a href="http://en.wikipedia.org/wiki/Wikipedia:Text_of_Creative_Commons_Attribution-ShareAlike_3.0_Unported_License">Creative Commons BY-SA 3.0</a> license. 

Picture of Rasmus <a href="http://en.wikipedia.org/wiki/File:Lerdorf.jpg" title="Link to work">Lerdorf</a> by Jud Dagnall, available under <a href="http://creativecommons.org/licenses/by-sa/3.0/deed.en" title="Link to license">Creative Commons BY-SA 3.0</a>.

Picture of <a href="http://en.wikipedia.org/wiki/File:Andi_Gutmans_1.jpg" title="Link to work">Andi Gutmans</a> by <a href="https://www.flickr.com/people/81342178@N00" title="Link to author">Jim Winstead</a>, available under <a href="http://creativecommons.org/licenses/by/2.0/deed.en" title="Link to license">Creative Commons BY 2.0</a>.</p>

; Information added by Drupal.org packaging script on 2015-05-25

version = "7.x-1.3"

datestamp = "1432557782"

[readme]

title = LESMEG

[using-advanced-help]

title = Bruk av Avansert hjelp

[translation]

title = Oversettelse av Avansert hjelp

[ini-file]

title = Avansert hjelp .ini-filformat

[why-advanced-help]

title = Hvorfor Avansert hjelp?

<p>The advanced help configuration file is in simple .ini file format.

It has an optional section for global settings that might be inherited

for each help file, followed by sections for each help file.</p>

<p>Global settings may be put into a section named <code>[advanced help

settings]</code>.  This means that this name is reserved and it cannot

be a help file in any module or theme. The following settings may be

set in this section, with the default value (if any) in brackets.</p>

<dl>

<dt><code>line break</code> (FALSE)</dt>

<dd>If set, the line break filter will be applied to all help files

defined by this module or theme, unless that help file specifically is

set otherwise.  The line break converts line breaks

into <code>br</code> and <code>p</code> tags automatically.</dd>

<dt><code>navigation</code> (TRUE)</dt>

<dd>If set, this navigation will be displayed at the end of the topic:

<em>previous topic</em>, Up (parent), <em>next topic</em>.</dd>

<dt><code>css</code></dt>

<dd>Specify a css file that will be used for all help files (unless

overridden), including the .css extension. This .css file must reside

in the help directory along with the .html files, and will not be

affected by translation.</dd>

<dt><code>name</code></dt>

<dd>May be set to override the module or theme name as displayed in

both the module/theme index as well as the navigation and breadcrumb

trail. Usually, this is not set, but for some projects you may want to

use a more friendly name than appears in the project's .info file.</dd>

<dt><code>index name</code></dt>

<dd>This may be set to change the name of the module or theme in the

module/theme index. It overrides the <code>name</code> setting above,

as well as the project's name in its .info file.</dd>

<dt><code>hide</code> (FALSE)</dt>

<dd>This may be used to hide a module or theme in the module/theme

index. This is particularly useful for modules who insert their help

files into the hierarchy of another module or theme, as might be done

by modules that extend <strong>Views</strong> or derived themes that

extend base themes like <strong>Zen</strong>. By setting this to TRUE

the project will not appear as its own entry.</dd>

</dl>

<p>Each section after that will correspond to a single help file for a

single topic.  It starts with the topic name in square brackets

(e.g. <code>[ini-file]</code>).  The following settings may be set for

each file/topic, with the default value (if any) in brackets.</p>

<dl>

<dt><code>title</code></dt>

<dd>The title of the topic, presented to the user and used in

links. If you have special characters in your title, be sure to

enclose it in quotes.  (This setting is currently not optional.)</dd>

<dt><code>file</code> (topic name)</dt>

<dd>The filename, without the .html extension, used for the file with

the help text for the topic. This is optional; if not specified, the

topic name wil be the file name.</dd>

<dt><code>weight</code> (0)</dt>

<dd>The weight, used for sorting topics on the administration

page. The default is 0 (zero) if unspecified. Items with the same weight

are sorted alphabetically.</dd>

<dt><code>parent</code></dt>

<dd>The topic ID to use in a hierarchy; children will be listed

beneath parents in the topic list, and will have the parent in their

breadcrumb trail. You may parent this topic to a topic in another

module or theme by using <code>module%topic</code>

or <code>theme%topic</code> as the identifier,

where <code>module</code> or <code>theme</code> is the project's short

name. For example if parent is set to, '<code>views%display</code>',

the topic will be regarded as a child of the

<code>display</code> topic in the <strong>Views</strong> module.</dd>

<dt><code>line break</code> (FALSE)</dt>

<dd>Set the line break filter for this topic. Set to FALSE to disable

the line break filter if this has been turned on in the global

settings.</dd>

<dt><code>css</code></dt>

<dd>Specify a css file that will be used for this file. This .css file

must reside in the help directory along with the .html files. This

will override any .css file added by the global settings.</dd>

<dt><code>popup width</code> (500)</dt>

<dd>The width in pixels of the popup window.</dd>

<dt><code>popup height</code> (500)</dt>

<dd>The height in pixels of the popup window.</dd>

</dl>

<p>For example, here is a version of the <code>advanced_help.help.ini</code> file:</p>

<pre>

[readme]

title = README

weight = -11

[using-advanced-help]

title = Using advanced help

weight = -10

[translation]

title = Translating advanced help

[ini-file]

title = Help .ini file format

line break = FALSE

[why-advanced-help]

title = Why advanced help?

line break = TRUE

</pre>

<h2>Om denne oversettelsen</h2>

<p>Dette er en (delvis) oversettelse til <em>norsk</em> (bokmål) av

hjelpeteksene for <strong>Avansert hjelp</strong>.  Den er i første

rekke laget for å vise hvordan en oversettelse av hjelpetekstene ser

ut.</p>

<h2 id="project-description">Synopsis</h2>

<p>Modulen <strong>Avansert hjelp</strong> tilbyr et rammeverk som gjør

det mulig for modul- og theme-utviklere å integrere hjelpetekster i et

Drupal-nettsted.</p>

<p>Disse hjelpetekstene lagres som vanlige <code>.html</code>-filer

som lever i filsystemet (ikke i databasen).  Disse filene distribueres

fra prosjektes repo på Drupal.org i den samme pakken som prosjektets

øvrige filer, og plasseres i en en underkatalog med navnet

<code>help</code> i prosjektets katalog.  Det innebærer at

hjelpetekstene på en enkel måte kan holdes synkronisert med det

prosjektet hjelpen er knyttet til, men også at tilgangen til disse

filene ikke er underlagt de tilgangsbegrensningene som Drupal

administrerer.</p>

<p>Hjelpetekstene kan bruke standard HTML-markeringer De vil bli vist

med ditt nettsteds theme.</p>

<p>Dersom prosjektets forfatter ikke bruker HTML-rammeverket for

<em>Avansert hjelp</em>, men det finnes en 

<code>README.md</code> eller <code>README.txt</code> i pakken,

så vil innholdet av den filen vises i stedet.</p>

<p>Hjelpetekstene kan vises i et sprettopp-vindu eller ikke, ut fra

prosjektets preferanser.  Ved å fjerne tilgangen til å se

sprettopp-vinduer kan nedstedet skjule sprettopp-vinduer fra

brukere.</p>

<p>Hjelpetekstene kan organiseres hierarkisk, noe som gjør det mulig

og navigere fra toppen av og nedover for hjelp.</p>

<p>Hjelpetekstene kan gjøres søkbare.  Dersom søk av avansert hjelp er

slått på, vil all hjelpetekst indekseres. Dette innebærer at alt

innhold på sidene med avansert hjelp er søkbart med nøkkelord.</p>

<h2 id="use">Bruk av modulen</h2>

<p>When you enable the module, a new tab with the legend “Advanced

help” will show up under “Help”:

<div class="ta-center">

<img class="help-img-center" alt="ahelp_tab.png" src="&path&ahelp_tab.png" width="661" height="225" border="1" />

</div>

<p>By itself, this module doesn't do much.  The <strong>Avansert

hjelp</strong> assists other modules and themes in showing help texts.

Nothing will show up until you enable at least one other module that

makes use of the advanced help framework or comes with a file

named <code>README.md</code> or <code>README.txt</code>.  However, it

comes with a small companion demo module named

<strong>Eksempel på hjelp</strong> to demonstrate how it works.

For more extensive example of use of the advanced help features, see

the <strong>Views</strong> project.</p>

<!--

<h2 id="project-recommended">Anbefalte moduler</h2>

<ul>

<li><a href="https://www.drupal.org/project/markdown">Markdown filter</a>:<br>

When this module is enabled, display of any <code>README.md</code> the

module shows will be rendered with markdown.</li>

<li><a href="https://www.drupal.org/project/attributions">Attributions</a>:<br>

When this module is enabled, attributions of third party content used

by the project (i.e. some text from Wikipedia) will be available in an

attribution block and on an atribution page.</li>

</ul>

-->

<h2 id="support-status">Status for oppfølging</h2>

<p>Reported bugs for the Drupal 7 branch will be fixed in a timely

manner.  Bugs in the issue queue for the Drupal 6 branch will only be

fixed if accompanied with a patch, after the patch has been reviewed

and tested by the community.  No Drupal 8 version is currently under

development.  Post a message in

the <a href="https://www.drupal.org/node/1928218">issue queue</a> if

you're interested in managing a port of the project to to Drupal

8. Older versions are no longer supported.</p>

<p>Community support in the form of patches are very welcome for both

Drupal 6 and Drupal 7 versions, and will be given priority. For QA,

the project needs community support in the form of reviews of patches,

development versions and releases.</p>

<p>The primary goal of the module is to remain <strong>light-weight

and simple</strong>.  This means that not all feature requests will be

implemented, even if they are a good idea.  Feature requests

accompanied by patches are more likely to make it into a release.</p>

<p>The maintainer hopes that the community is willing to help out by

answering &amp; closing support requests.</p>

<!--

<h2 id="project-problems">Kjente problemer</h2>

-->

<h2 id="project-maintainers">Kreditering</h2>

<ul>

<li><a href="https://www.drupal.org/u/merlinofchaos"">merlinofchaos</a> (52 commits, opprinnelig forfatter)</li>

<li><a href="https://www.drupal.org/u/redndahead">redndahead</a> (8 commits)</li>

<li><a href="https://www.drupal.org/u/dmitrig01">dmitrig01</a> (3 commits)</li>

<li><a href="https://www.drupal.org/u/amitgoyal">amitgoyal </a> (5 commits)</li>

<li><a href="https://www.drupal.org/u/gisle">gisle</a> (nåværende administrator, D7)</li>

<li><a href="https://www.drupal.org/u/gnuget">gnuget</a> (nåværende administrator, D8)</li>

</ul>

<p>For å oversette en hjelpe-fil indeksert av <strong>Avansert hjelp</strong>

må du først opprette en katalog

<code>translations/help/<em>språk</em></code> i prosjektets rotkatalog der

<em>språk</em> er språkkoden som vises på siden <em>Språk</em> i det

administrative grensesnittet.</p>

<p>Deretter kopierer du <code>.ini</code>-fila og alle

<code>.html</code> filene fra den opprinnelige hjelpe-katalogen

katalogen til denne katalogen. Om du trenger å endre et bilde for å

bruke det i en oversettelse, kan du også plassere det endrede bildet

her.</p>

<p>I emne-delen av <code>.ini</code>-fila trenger du bare å beholde

emnenavnene (uendret) og titlene (oversatt). Hvis det finnes

en <code>name</code> eller <code>index name</code> innstilling i

'advanced help settings'-delen, bør disse beholdes. Alle innstillinger

som beholdes skal oversettes. Resten av dataene i

<code>.ini</code>-filen kan fjernes eller ignoreres. </p>

<p>Hver enkelt <code>.html</code>-fil skal deretter oversettes uten å

endre navn eller plassering.</p>

<p>Når du oversetter en <code>.html</code>-fil, vil du finne at

nøkkelordet <code>&amp;path&amp;</code> (brukes for bilder og linker)

vil føre til den opprinnelige katalogen. Hvis du må oversette

elementer som er lenket, for eksempel bilder som inneholder tekst,

bruke <code>&amp;trans_path&amp;</code> i stedet. Dette nøkkelordet

vil peke på den oversatte katalogen. Dette vil tillate deg å velge

hvilke lenkede elementer, om noen, som vil bli oversatt.</p>

<p> Hvis et emne ikke er oversatt, så vil den uoversatte versjonen

vil bli vist i stedet.</p>

<h2>Oversettelse av hjelpetekstene til Avansert hjelp</h2>

<p>Dersom du ønsker å hjelpe til med å oversette

hjelpetekstene til <strong>Avansert hjelp</strong> til et bestemt språk

kan du se etter en tråd i <a href="https://www.drupal.org/project/issues/advanced_help">sporingskøen for Advanced help</a>

med navnet “Translation to XXX” (der

“XXX” språket du ønsker å oversette hjelpetekstene til).

Dersom en slik tråd ikke eksisterer kan du opprette den.

Velg <em>Category</em>  “Task”,

<em>Status</em>  “Needs review” og

<em>Component</em>  “Documentation”.

Last opp filer med oversatte hjelpetekster som

vedlegg (endre filtype fra <code>.html</code> til <code>.txt</code> for å få lov til å laste opp).</p>

<p>Oversettelser som lastes opp vil bli inkludert i neste versjon dersom de godkjennes av andre brukere (ved at de oppnår status “RTBC”).

<p>Modulen <strong>Avansert hjelp</strong> tilbyr et rammeverk som gjør

det mulig for modul- og theme-utviklere å integrere hjelpetekster i et

Drupal-nettsted.  Selv om <strong>Avansert hjelp</strong> ikke selv

inneholder generell hjelp tilbyr den et kraftig og enkelt rammeverk som

prosjekter kan benytte for å tilby egen hjelp.</p>

<p>Prosjekter som benytter <strong>Avansert hjelp</strong> må

ha en underkatalog med navnet <code>help</code> i sin rotkatalog

I denne katalogen opprettes filen

<em>MODULNAVN</em>.help.ini (evt. <em>THEMENAVN</em>.help.ini).

Formatet på denne fila framgår av følgende eksempel:</p>

<pre>

[about-php]

title = About PHP

file = about-php

weight = -10

[history]

title = History of PHP

parent = about-php

[usage]

title = Usage of PHP

weight = 1

[security] 

title = Security of PHP

weight = 2

[syntax]

title = PHP syntax

parent = usage

</pre>

<p>Lag alltid den engelske versjonen av disse temaene først.  Ønsker

du å ha temaene oversatt til et annet språk følger du anvisningene i

<a href="&topic:advanced_help/translation&">Oversettelse av

Avansert hjelp</a>.</p>

<p>Denne fila definerer fem hjelpe-emner (i firkant-parenteser), og

noen innstillinger for dem.

Se: <a href="&topic:advanced_help/ini-file&">Avansert hjelp .ini-filformat</a> for

en liste over definerte innstillinger.</p>

<p>Alle emner er beskrevet av det prosjektet som tilbyr

emnet, og av emne-id.  For å produsere en themet lenke til et

sprettopp-vindu om et emne, bruk et format etter mønster fra følgende

eksempel:</p>

<!-- D6

<pre>

$output = theme('advanced_help_topic', 'help_example', 'about-php');

$output .= ' ' . t('Click the help icon!');

</pre>

-->

<!-- D7 -->

<pre>

$output = theme('advanced_help_topic', array(

  'module' => 'help_example',

  'topic' => 'about-php',

));

$output .= ' ' . t('Click the help icon.');

</pre>

<p>Ikke oversett strengen inne i <code>t()</code>. Bruk alltid engelsk, og benytt Drupals lokaliserings-modul til å oversette.</p>

<p>Forutsatt at strengene er korrekt oversatt (ved hjelp av Drupals lokaliserings-modul) genererer dette følgende markeringer:</p>

<pre>

<a class="advanced-help-link" title="Om PHP"

  onclick="var w=window.open(this.href, 'advanced_help_window',

  'width=500,height=500,scrollbars,resizable');

  w.focus(); return false;"

  href="/help/help_example/about-php?popup=1">

<span>Hjelp</span>

</a>

 Klikk på hjelpe-ikonet.

</div>

</pre>

<p>Dette produserer et klikkbart hjelpe-ikon lik det som vises under:</p>

<div class="ta-center">

<img class="help-img-center" alt="klikkbart ikon" src="&trans_path&click_icon.png" width="180" height="90" border="0" />

</div>

<p>Inne i en hjelpe-fil kan du lenke til andre hjelpe-emner ved å

bruke dette formatet:</p>

<pre>

<a href="&topic:module/topic&">topic</a>

</pre>

<p>Ved å bruke dette formatet i stedet for standard-lenker vil sprettopp-status være konsistent når man trykker på lenker.</p>

<p>For å referere til andre elementer som befinner seg i

hjelpe-katalogen, som bilder som du ønsker å bake inn i teksten,

bruk:</p>

<pre>

<img src="&path&example.png"/>

<img src="&trans_path&example.png"/>

</pre>

<p>Nøkkelordet <code>trans_path</code> vil peke på en oversatt versjon

av bildet i oversettelse-katalogen og kan benyttes dersom du ønsker å

vise et bilde med oversatt tekst i stedet for originalen.</p>

<p>For å peke på en normal sti på nettstedet, bruk:</p>

<pre>

<a href="&base_url&admin/settings/site-configuration">anchor text</a>

</pre>

<p><strong>NB: </strong> I tidligere versjoner av <strong>Advanced

help</strong> var det ikke nødvendig å benytte &amp;-tegn rundt

<code>topic:</code>, <code>path</code>, og <code>base_url</code>.

Dette fungerer fortsatt, men kan bli fjernet i en senere versjon.

Ved å bruke &-tegn for å markere disse nøkkelordene kan de

brukes overalt, og ikke bare som parametere til 

<code>href=""</code> og <code>src=""</code>.</p>

<h2 id="access-control">Adgangskontroll</h2>

<p>Når denne modulen er installert vil brukere med tillatelsen

<code>view advanced help index</code>

se indeks-siden for <strong>Avansert hjelp</strong> ved å gå til

<em>Administrasjon &rarr; Advanced Help</em>

(sti: <code>admin/advanced_help</code>). Øvrige tillatelser

<code>view advanced help topic</code>  og

<code>view advanced help popup</code>

gir brukere adgang til de aktuelle hjelpe-sidene og sprettopp-vinduer.</p>

<p>Hjelpeteksten er lagret som vanlige <code>.html</code>-filer og

kan, med mindre de beskyttes, bli sett av alle som kjenner deres URL.

Dersom du ønsker å beskytte dem kan du beskytte dem mot innsyn ved å

plassere følgende fire linjer i en fil med navn

<code>.htaccess</code> i katalogen <code>help</code> i prosjektkatalogen:</p>

<pre>

<Files *\.html>

Order Allow,Deny

Deny from all

</Files>

</pre>

<p>Det er nettstedsansvarlig som har ansvaret for at denne typen

beskyttelse er på plass dersom nettstedet har hjelpe-filer som må

beskyttes fra direkte innsyn.</p>

<p>Se også denne tråden i prosjektets sporings-kø:

<a href="https://www.drupal.org/node/1980936">#1980936 Typing complete path to .html help files in module bypasses user permissions</a>.</p>

<h2 id="search">Søk</h2>

<p>For å skru på søk for <strong>Avansert hjelp</strong>, naviger til

<em>Administrasjon → Oppsett → Søk og metadata → Søkeinnstillinger</em>.

Rull ned til feltet <em>Aktive søkemoduler</em> og kryss av feltet til venstre for

“Advanced help”.  Søkefeltet vil deretter dukke opp på toppen av indekssidene for

<strong>Avansert hjelp</strong>.</p>

<p>Dersom modulen <strong>Search</strong> i core er skrudd på, vil alt

innhold på hjelpesidene bli indeksert av cron.  Dersom du installerer

og skrur på nye prosjekter og ønsker å indeksere deres

hjelpetekster umiddelbart kan du navigere til <em>Administrasjon →

Rapporter → Status</em> og klikke på lenken for å “kjøre cron

manuelt.”.</p>

The <strong>Advanced help</strong> framework was designed to replace the original Drupal help system, which has several flaws that make it hard to create new help, hard to maintain existing help, and particularly hard to access help.

The primary goal, then, is to increase the accessibility of help, meaning the ability of both the user and the help text author to access the needed tools to use, create, maintain and translate the help.

This system is completely separate from Drupal's <code>hook_help()</code>. In Drupal 6 and 7, it actually co-exists with it; in the future, it is hoped that it will completely replace it allowing <code>hook_help()</code> to be deprecated and removed.

Messages added to the top of a page are not really “help”. Often these messages are an introduction to a form or a short blurb telling a user what to do with a particular page. The problem is, these messages are always there, they are easily ignored, and they come before the actual page. In general, when users are learning, they want to see the page first, then ask questions. The reverse order is much less conducive to actually teaching a user how to use something. By allowing help to be available on request, the system conforms more naturally to how most people work.

<h2>Advanced help er organisert etter emner</h2>

With the <code>hook_help()</code> method, help text is organized by URL path. This is fine if you have help text describing how to use a particular page or what a particular page does, but ultimately is limiting because manuals and documentation are usually grouped by topic, and those topics are determined by the material itself.

<strong>Advanced help</strong> allows the documentation author to organize topics as he or she sees fit; the only restriction, really, is that each individual chunk of text needs to stand on its own as a discrete topic.

What's more, modules and themes can insert their topics into another's hierarchy. This would allow the Drupal core to create a task based help navigation system which allows modules and themes to insert topics into that navigation fluidly. This allows modules and themes to continue to keep their systems separate, yet integrate into the main system.

<h2>Advanced help-emner er behandlet som HTML i egne filer</h2>

This separation makes it easy to find and modify. Currently, everything is lumped together in <code>hook_help()</code> in PHP strings that are run through <code>t()</code>, and there is a fair amount of PHP code necessary in this system that actually gets in the way of writing good, explanatory text.

In fact, requiring a documentation author to understand PHP at all is a detriment. The idea that documentation writers need to have PHP development as a skill seriously reduces the number of available contributors. HTML, on the other hand, is a much more common skill, is relatively easy to learn, and the amount of HTML needed to write documentation is only a little bit more than the HTML used in forum posts.

Another benefit to not using PHP is that the files themselves are safe. They are filtered to escape malicious script code that could take over the server or do worse things. This means that these files can be used relatively easily on Drupal.org itself. It also means that descriptions of the project pulled from the project's help pages or README.txt or README.md can be made on the project's Drupal.org without the need to download the module or theme to look at the contents of these files.  This also simplifies maintenance, as the files can be corrected easily by patches, which are updated by tyhe maintainer and pushed to git.

By moving all docymentation into help files, we could, if we wanted, package the Drupal.org handbooks, or a subset of them, directly into a Drupal distribution, or a Drupal add-on, so that Drupal administrators can have Drupal help without needing to visit Drupal.org. This can be valuable in locked down corporate environments and on planes. But more importantly, the handbooks can be made version aware much more easily than the current method on Drupal.org.

The downside to this method is that these books can't easily be made dynamic. Though the use of alter hooks could allow a module or theme to make modifications to the help as needed, doing this could make the help files less useful when you take them out of context.

<h2>Advanced help-filer oversettes som en fullstendig fil</h2>

It is actually not easy to translate documents as strings, particularly when the language being used is very much unlike English. In fact, when translating a document, the organization of the sentences may change drastically. It is also a burden on the CPU to do this, as you are indexing on very long strings.

Translators have a much better time translating a document as a unit, because of the presence of the entire context.

<h2>Advanced help har sitt eget navigasjons-system</h2>

By making use of a navigation system specified in a .ini file (which is not PHP code and therefore safe to use), the help can be structured like a book, which is typical of online manuals. This is familiar to users, can be organized (and re-organized) and allows a module or theme to include significantly richer text without burdening the PHP code with having its help loaded unnecessarily.

This book can be navigated hierarchically as well, making it easy to keep related topics together.

<h2>Advanced help indekseres av nettstedets søkemotor</h2>

An important goal of this system was to add searchability to the help. By being able to enter keywords into the search box and find relevant topics, we come up with a system that resembles the kind of help that comes with many operating systems. This is very valuable when searching through manuals trying to find out how to do a particular thing.

This search is specific to the help, meaning that the help will not be mixed in with the global node search. This can be considered both an advantage and a disadvantage. For the most part, this help system is meant to provide help to site administrators, and content searches should not find it. The disadvantage, of course, is when you want to use it for end user help, you will not be able to.

<h2>Hjelp for en bestemt side kan hentes inn via sprettopp-vinduer</h2>

In addition to the manual-like hierarchical navigation, <strong>Advanced help</strong> can also provide context-sensitive additional help through a popup. While popups are controversial, the argument for using them is that when getting help while on a form, <i>a popup will not throw away a user's data.</i> Browsers are not very friendly to input forms if they are not submitted, and navigating away from the form can be dangerous. There are various other solutions to this problem, but each one has a drawback. The drawbacks to popups are well known, but mostly it is the irritation of having new windows. When getting help, though, a popup is usually invited. Help should not interfere with what the operation the user is trying to complete. It differs greatly from the uninvited popup, which are usually ads or popups meant to prevent users from navigating away from a site.

Popups can be added to a page with plain text links or themed icon links.

      'value' => '<?php print "this is a custom field"; ?>',

 * Alter fields defined by Display Suite.

 *

 * This function is called for each entity type.

; Information added by Drupal.org packaging script on 2015-05-21

version = "7.x-2.10"

datestamp = "1432195683"

        'length' => 64,

        'length' => 64,

        'length' => 64,

/**

 * Increase the view_mode storage length to 64

 */

function ds_update_7203() {

  db_change_field('ds_field_settings', 'view_mode', 'view_mode',

    array(

      'description' => 'The name of the view_mode.',

      'type' => 'varchar',

      'length' => 64,

      'not null' => TRUE,

      'default' => '',

    )

  );

  db_change_field('ds_layout_settings', 'view_mode', 'view_mode',

    array(

      'description' => 'The name of the view_mode.',

      'type' => 'varchar',

      'length' => 64,

      'not null' => TRUE,

      'default' => '',

    )

  );

  db_change_field('ds_view_modes', 'view_mode', 'view_mode',

    array(

      'description' => 'The machine name of the view mode.',

      'type' => 'varchar',

      'length' => 64,

      'not null' => TRUE,

      'default' => '',

    )

  );

}

  // Load the ds file that handles ds call of hook_ds_fields_info, otherwise it

  // doesn't get loaded

  module_load_include('inc', 'ds', 'ds.ds_fields_info');

  $disable_css = FALSE;

  if (!empty($layout['settings']['layout_disable_css'])) {

    $disable_css = TRUE;

  }

  if (!$disable_css && isset($layout['css']) && !isset($loaded_css[$layout['path'] . '/' . $layout['layout'] . '.css'])) {

      $bundle = strtr($vars['elements']['#bundle'], '-', '_');

      $vars['theme_hook_suggestions'][] = $layout['layout'] . '__' . $vars['elements']['#entity_type'] . '_' . $bundle;

      $vars['theme_hook_suggestions'][] = $layout['layout'] . '__' . $vars['elements']['#entity_type'] . '_' . $bundle . '_' . $vars['elements']['#view_mode'];

        if (module_exists('token') && isset($var[$object])) {

      if (isset($vars[$object])) {

        $vars['layout_attributes'] .= ' ' . token_replace($layout['settings']['layout_attributes'], array($object => $vars[$object]), array('clear' => TRUE, 'sanitize' => TRUE));

      }

      else {

        $vars['layout_attributes'] .= ' ' . $layout['settings']['layout_attributes'];

      }

    if (module_exists('token') && isset($var[$object])) {

    $value = $field['properties']['code']['value'];

    // Token support - check on token property so we don't run every single field through token.

    if (isset($field['properties']['use_token']) && $field['properties']['use_token']) {

      $value = token_replace($value, array($field['entity_type'] => $field['entity']), array('clear' => TRUE));

    }

      $value = ds_format_php_eval($value, $field['entity'], isset($field['build']) ? $field['build'] : array());

      $value = check_markup($value, $format);

      if (isset($field['entity']->language)) {

        $language = $field['entity']->language;

      }

      else {

        $language = LANGUAGE_NONE;

      }

                $terms_loaded[$item['tid']] = $term;

        $content .= '<' . check_plain($title_wrapper) . ' class="title">' . $data->title . '</' . check_plain($title_wrapper) . '>';

        if (module_exists('i18n_taxonomy')) {

          $term = i18n_taxonomy_localize_terms($term);

        }

        if (module_exists('i18n_taxonomy')) {

          $term = i18n_taxonomy_localize_terms($term);

        }

          $item_display = l($term->name, $uri['path'], $uri['options']);

      if ($value != 0 && $key == $value) {

    // Additional settings

    if (isset($form_state['values']['additional_settings']['preview']['info']['settings']['disable_css'])) {

      $record->settings['layout_disable_css'] = $form_state['values']['additional_settings']['preview']['info']['settings']['disable_css'];

    }

      $suggestions .= '<ul><li>' . implode('.tpl.php</li><li>', $suggestions_array) . '.tpl.php</li></ul>';

      $form['additional_settings']['ds_layouts']['preview']['info'] = array(

        '#type' => 'container',

        '#attributes' => array(

          'class' => array('ds-layout-preview-suggestion'),

        ),

      );

      $form['additional_settings']['ds_layouts']['preview']['info']['suggestions'] = array(

        '#markup' => '<p>' . $selected . '</p><p>' . t('!suggestions', array('!suggestions' => strtr($suggestions, '_', '-'))) . '</p>',

      if (!empty($chosen_layout['css'])) {

        $disable_css = FALSE;

        if (isset($layout->settings['layout_disable_css'])) {

          $disable_css = $layout->settings['layout_disable_css'];

        }

        if (isset($form_state['values']) && $disable_css !== $form_state['values']['additional_settings']['ds_layouts']['preview']['info']['settings']['disable_css']) {

          $disable_css = $form_state['values']['additional_settings']['ds_layouts']['preview']['info']['settings']['disable_css'];

        }

        $form['additional_settings']['ds_layouts']['preview']['info']['settings']['disable_css'] = array(

          '#type' => 'checkbox',

          '#title' => t('Disable layout CSS styles'),

          '#default_value' => $disable_css,

        );

      }

  $values = $form_state['values'];

  if (isset($values['additional_settings']['preview']['info']['settings']['disable_css'])) {

    $disable_css = $values['additional_settings']['preview']['info']['settings']['disable_css'];

  }

  else {

    $disable_css = FALSE;

  }

  $record = db_select('ds_layout_settings')

    ->fields('ds_layout_settings')

    ->condition('entity_type', $values['ds_entity_type'])

    ->condition('bundle', $values['ds_bundle'])

    ->condition('view_mode', $values['ds_view_mode'])

    ->execute()

    ->fetchObject();

  $record->settings = unserialize($record->settings);

  $record->settings['layout_disable_css'] = $disable_css;

  drupal_write_record('ds_layout_settings', $record, array('id'));

  $url = $base_url . '/' . $values['layout_changed_url'];

; Information added by Drupal.org packaging script on 2015-05-21

version = "7.x-2.10"

datestamp = "1432195683"