Modify

Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#10481 closed defect (invalid)

No Footnotes at all in Trac 1.0

Reported by: info@… Owned by: Ryan J Ollos
Priority: high Component: FootNoteMacro
Severity: major Keywords:
Cc: Trac Release: 1.0

Description

FootNoteMacro 1.03-r11767 is installed and enabled in Trac 1.0

The macro does generate a superscript index as well as the ALT text and Hyperlink, but there is no footnote at the bottom of the page.

we have<sup class="footnote"><a cannotgivehrefhere="#FootNote1" id="FootNoteRef1" title="We have of course older backups too, but these ...">1</a></sup>

Attachments (1)

Typos.png (2.3 KB) - added by Ryan J Ollos 12 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 Changed 12 years ago by anonymous

the cannotgivehref here is normally of course href, I just wanted to avoid rejection and an internal server error of trac-hacks...

comment:2 Changed 12 years ago by Ryan J Ollos

Priority: normalhigh
Status: newassigned

comment:3 Changed 12 years ago by Ryan J Ollos

Did you place [[FootNote]] at the bottom of the page? It is working fine for me when testing out this evening with Trac 1.1.1dev. If you still have no luck, please try out the example at FootNoteMacro#Example.

comment:4 Changed 12 years ago by Ryan J Ollos

(In [12232]) Refs #10481:

  • Changed to more common no-conflict mode jQuery(document).ready(function(){... syntax, replacing $(function(){...
  • Added the 3-Clause BSD license text to the source code.

comment:5 Changed 12 years ago by PetaMem

Resolution: invalid
Status: assignedclosed

Argh...

No, I hadn't the placed at the bottom of the page. Probably stopped reading the docs too early. And thought (experience from other system) this would be implicit behaviour (placing Footnotes at the foot of the document).

I can see how this implementation offers greater flexibility, but still would suggest that the FootnoteMacro should by default "flush" all pending content at the bottom of the page.

side note: after your suggestion, I placed [[Footnote]] at the bottom of the page and it still didn't work. ;-)

So: My bad. FootNoteMacro works, resolution: invalid. Maybe docs or default behaviour could be improved for more intuitive use, but so far I'm ok with it.

comment:6 Changed 12 years ago by anonymous

Oh - BTW - On my System I do not get the aforementioned error "Error: Failed to load processor Footnote" - I just get a

Footnote?

link to some nonexistant document.

comment:7 in reply to:  5 Changed 12 years ago by Ryan J Ollos

Replying to PetaMem:

I can see how this implementation offers greater flexibility, but still would suggest that the FootnoteMacro should by default "flush" all pending content at the bottom of the page.

Sure, that makes sense - append to the bottom of the page if they haven't already been flushed. I'll keep that in mind while working on t:#9037. I might get that change integrated here as well, but currently my attention is on t:#9037 when I have time to work on footnotes.

So: My bad. FootNoteMacro works, resolution: invalid. Maybe docs or default behaviour could be improved for more intuitive use, but so far I'm ok with it.

Let me know if you have some specific ideas for changing the docs, or feel free to edit the wiki page on your own.

Changed 12 years ago by Ryan J Ollos

Attachment: Typos.png added

comment:8 in reply to:  6 Changed 12 years ago by Ryan J Ollos

Replying to anonymous:

Oh - BTW - On my System I do not get the aforementioned error "Error: Failed to load processor Footnote" - I just get a

Footnote?

link to some nonexistant document.

I see the same behavior on newer versions of Trac. I think they've just gotten better about handling broken, removed or mistyped macro names.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Ryan J Ollos.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.