Extension talk:Header Footer/Archive

How do you use this extension?
How do you use this extension? What would an example look like?
 * I have now included some examples. Jean-Lou Dupont 17:03, 26 May 2007 (UTC)

Header/Footer not showing:
I've installed the extension using PEAR, along with StubManager. Everything seemed fine.

I accessed the page "www.mydomain.com/wiki/index.php/MediaWiki:Hf-nsheader-Main" and added some "test test" message in there by editing the page. However, nothing shows. Isn't this supposed to show the "test test" message in all pages in the Main namespace in my wiki? Solution: use instead "www.mydomain.com/wiki/index.php/MediaWiki:Hf-nsheader-" for the Main namespace.

A few suggestions to include in the documentation page

 * Since the extension depends on the StubManager extension, you should note in the installation instructions that StubManager must be installed and the "require_once" statement for StubManager must occur above the "require_once" statement for HeaderFooter in the LocalSettings file.
 * It appears that for pages that are subjected to both a hf-nsheader- and a hf-header-, both headers are rendered and the namespace header occurs first. You might include a description of what happens for pages that have multiple header and footer influences.

Thanks, Furboy 04:10, 7 April 2008 (UTC)

A few bugs

 * Confirm Delete Page:When deleting a page from a namespace that has a corresponding hf-nsheader- or hf-nsfooter- the header and/or footer are rendered on the delete confirm page.
 * Right-aligned table conflict:If a table with the parameter align="right" is the last wikitext on a page, the table gets covered up by the hf-nsfooter. You can work around the problem by adding enough tags to get the table to move up, or by simply adding some text after the table.
 * __NOHEADER__ and __NONSHEADER__ not working:__NOHEADER__ and __NONSHEADER__ are not working for me. The documentation page says to use the magic words on "edit protected pages", which I assume means that the headers will be disabled on pages that include the magic words and that are protected.  That's how I have it set up and it doesn't work.

Thanks, Furboy 04:10, 7 April 2008 (UTC)
 * Many thanks for the detailed bug reports. Could you use my project's issues tracking facility to document these? One has much higher chances of seeing resolutions this way. Thanks again. Jean-Lou Dupont 10:09, 7 April 2008 (UTC)

Wish List

 * hf-header- trumps hf-nsheader-: It appears that for pages that are subjected to both a hf-nsheader- and a hf-header-, both headers are rendered and the hf-nsheader- occurs first. For my own application, I would rather see the hf-nsheader- header get rendered in all instances where there is not a hf-header-, but that when there are both a hf-nsheader- and a hf-header-, that the hf-header- is rendered and the hf-nsheader- is not.  I suppose that I could use a __NONSHEADER__ to force the override, but I haven't been to get my __NONSHEADER__ to work.  Ideally, I would like to be able to put a __NONSHEADER__ in my hf-header- or a __NOHEADER__ in my hf-nsheader- to force the appropriate overrides.
 * Custom parameters: It would be nice to be able to pass a parameter from a page to its corresponding hf-header- page, similar to the way you can pass parameters to templates. One way might be with a hook like parameter name|parameter value that could be retrieved in the hf-nsheader- from a variable like .
 * Evaluate Cite.php: Cite.php is a citation reference extension that collects text enclosed by &lt;ref> tags and inserts the text as a footnote in a section indicated with the placeholder tag &lt;references/>. Some of the shortcomings of Cite.php include 1) the editor must actually remember to include the &lt;references/> tag, 2) placing the &lt;references/> tag is an additional task for the editor - a task that must be repeated on each page that has such references, and 3) many editors means that the location and formatting of the reference footnotes are not likely to be similar.  If there was a way for HeaderFooter.php to evaluate whether a page included &lt;ref></tt> tags, a standard footer could be developed to the &lt;references/></tt> tag conditionally.

thanks, Furboy 04:10, 7 April 2008 (UTC)
 * Could you also add these the my project's issues/features tracking facility? Thanks. Jean-Lou Dupont 10:11, 7 April 2008 (UTC)

Thanks
Thanks for pointing me to it, works fine for me. --Subfader 09:30, 16 May 2008 (UTC)

Automatically appending categories to pages
On my wiki I have at home, I've set up this extension (and all works great). However, I have one question: how would I write the code so that when a certain header is applied to all pages of a namespace, those pages are automatically added to a certain category? For example, I have a header that goes at the top of every page in the User namespace, and I want all those pages to be in "Category:User Pages", but when I add something to the page MediaWiki:Hf-nsheader-User along the lines of  </tt>, nothing happens (except that the header page is added to that category). The same if I use  </tt> tags or if I don't use tags around it at all. What should I do to fix this? ~Signed &Omega;mega234 &Dagger; talk to me 02:32, 17 June 2008 (UTC)
 * Hi - the header and footer text are processed outside of the scope of the current page; hence, what you are trying to do won't work. You may file a feature request on GoogleCode and maybe ... ;-) Jean-Lou Dupont 02:42, 17 June 2008 (UTC)
 * I second this request. Would be a real killer feature :-) -- Thoralf 16:44, 28 August 2008 (UTC)

__NOHEADER__ and __NONSHEADER__ not working - my solution (NOT AN ISSUE)
Hello.

__NOHEADER__ and __NONSHEADER__ only work on pages that are protected from editing. I edited this part of HeaderFooter.body.php:

if ($disable && $protect) return null; return $content;

And deleted "&& $protect".

Works fine for me.

Many thanks to the author! 19:03, 4 July 2008 (UTC)
 * Hi - note that the magic words are working... but not the way you wanted. Jean-Lou Dupont 01:16, 5 July 2008 (UTC)

Header & Footer position
Hi first of all thanks for your -very useful- extension. Is it possible to change the position of the elements and to move them for example outside of ?