Description: When I configure footnotes numbering per page and insert a footnote in two different cells of a table, the numbering goes to 0. Oddly, when I restart the program, the numbering is corrected. I have tested when the table doesn't cross the page, and the problem appears not happen. This error is similar to the error 155306, indicated by myself too previously. Steps to Reproduce: 1. Open the document given below. 2. Go to the page 48 (using number page in status bar, type 48). 3. In the table in the end of page, insert a footnote after the word "Nehemías", and the error occur. Actual Results: The result, in the file below, is 0. Expected Results: In the file below, the expected result should be the footenote number 3, but 0 is got. If the file is saved and reopen, the error is corrected mysteriously. Reproducible: Always User Profile Reset: No Additional Info: None.
Created attachment 187795 [details] File in which the error occur. See the file attached above, in which the error occur, and do the steps indicated also above, to see the error occurring.
I have tested the problem with stable version 7.4.7.2, and it seems that the problem does not occurr anymore.
I'm sorry for the anterior comment (disconsider it), but the problem apparently occurrs when the paragraph within the table crossing to the next page. For test, try to insert a footnote in the sample file above in the last column table crossing from the page 33 to the page 34 (within a table). The problem occurrs.
Created attachment 188478 [details] File with problem in the footnotes.
I've identified the problem. When, in the page 33 of the attachment annexed above this comment, I put two footnotes, one of them in the last line of the page 33, the Writer presents the problem, because the line should go to next page, but the footnote doesn't fit in the page of its occurrence. The program confound the numbering with position of footnote.
Thanks Hudson! Sounds like the same issue as bug 78303, so marking as a duplicate. Please let me if I missed a difference! *** This bug has been marked as a duplicate of bug 78303 ***