Pagination Bug

We meet a strange bug when we processing a document recently.
For example, one paragraph have 3 lines, 2 lines are in the page 1, and the last line is in the page 2. So we set the Widow/Orphan Lines to 2, and click Apply, then the whole paragraph will move to page 2.
But after we saving this file, close it and open it again, the first 2 lines move to page 1 again automatically. The setting in the Widow/Orphan Lines is still 2, but we must click Apply again, the whole paragraph then will move to page 2.
We have tried it many times, every time when we close and reopen the file, the pagination will be changed automatically.
BTW, it's FM 10. Anyone have meet the same bug before?

It's not intuitive, but I have seen rare pagination problems that are resolved by rehyphenating the document (which causes FM to look at every line). To try it, use Edit > Spelling Checker, then click on Dictionaries in the resulting dialog, select the Rehyphenate Document radio button, and click OK.

Similar Messages

Report - Layout and Pagination bug

Hello,
I am using Oracle 10g XE. I was trying to add pagination to a report, it is working ok but if I select for the display position "Top and Bottom" only the bottom pagination is visible.
Is this a bug?
Catalin Florean.

Hi,
There are Top and Bottom – Left and Top and Bottom – Right.
I suppose that you have something wrong in the SQL Query or in the report.
Make a new report using the wizard. Then use Report Template – Standard and Top and Bottom – Left.
Konstantin

Possible pagination bug in tabular form

Hi All,
Can someone reproduce the following test case on 1.6.1.00.02?
1. Create a tabular form via wisard
2. Set pagination type 'Row Ranges in select list (with pagination).
3. Set 10 rows per page
4. Insert 11 rows
5. Delete last row from the second page.
The form should show no rows and 'Previous' link is missed.

Hello Tauceef,
>> Now I got it, I was under impression that it will validate one by one row before insertion,
>> but it's going to check all the rows first, then do the insertion.
Just to clear things up, the APEX engine works exactly as you describe, but this is your problem.
The APEX engine do check\validate all the rows first, one row at a time, and only if all the rows pass validation, the DML processes kick in. The DML processes work on the entire Tabular Form record set (per page view, of course).
In order for your type of validation to work (the one that queries the database), as you want it, the validation and DML actions have to run together, row by row. This is not how things work, because it’s less efficient/optimal, and may lead to a situation where a certain row can fail validation, but other row(s) already been inserted/updated/deleted into/from the database. This could be a very tricky situation.
Vikram has suggested to rely on a database constraint, and control the APEX error message. This is possible, although I’m not sure that in this case, the Tabular Form will retain all the user changes, in case of validation error. You should check it.
Another option, which Marc hinted on, is to manipulate the G_Fxx arrays. In your case, you should loop through the new rows, compute their MD5, and make sure that all the rows have different MD5 values. This is on top of the current validation, which makes sure that the new rows do not already exist in the database.
Regards,
Arie.
&diams; Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
&diams; Author of Oracle Application Express 3.2 – The Essentials and More

Report pagination bug ?

Hi,
I have a sql report with 4 parameters (drop down lists) and pagination.
I run the report I got 100 lines with right pagination.
I re-run the report with different parameters. I should see 10 lines, but there's nothing, just the pagination indicating that I should see 10 records. After many tests, always the same result, if a report returns less rows than the previous execution, I just got pagination without the reports. I can see pagination changing when I click on arrows, but still no report output !
Very annoying behaviour, any idea why ?
Thank you

I reset the branch pagination, but it's not woriking. I still have that error for the two details reports when I changed the order by of the master report.

Did "Keep with following paragraph" get fixed?

In 08 if you use "Keep with following paragraph" on a paragraph (or style for a paragraph) that falls at the bottom of a page, Pages won't push it to the next page to keep it with the next paragraph.
This bug was present (and reported) since version 1.0 of Pages. So we're at what, now...3 or 4 full versions and a couple years, without a fix, for such a huge, glaring pagination bug.
I own 08 and want to upgrade to 09. Can someone please tell me if this pagination bug was fixed?
Thanks!

santranyc wrote:
In 08, the behavior is as follows:
Say Paragraph A is followed by Paragraph B.
You set Paragraph A with "Keep with following paragraph" to make sure A and B are always on the same page.
If Paragraph A falls at the bottom of a page, however, Pages does NOT push it to the next page, as it should (according to the fact that you set the attribute "Keep with following paragraph" to be turned ON for Paragraph A).
Try the following in Pages '08.
1. Fill a page with empty paragraphs.
2. On the very last line on that page, type "hello".
3. In the Inspector, set it to "Keep with following paragraph".
4. Hit return at the end of "hello", to create a new paragraph.
The new paragraph is created and hello follows it to the new page.
5. Remove "Keep with following paragraph" from "hello".
The word hello moves back to page one.
That is the behaviour. It does not cover all cases you want, but it works as it does.
Now, still in '08 do the following.
1. Three lines from the end of page 1, add three paragraphs, each with the word "hello".
2. Add a few more paragraphs of the same kind, so you spill over to next page.
3. Click on "Keep..." for all the hello-lines.
Nothing happens. I guess you expect something to happen.
Now, in '09, do the same:
1. Three lines from the end of page 1, add three paragraphs, each with the word "hello".
2. Add a few more paragraphs of the same kind, so you spill over to next page.
3. Click on "Keep..." for all the hello-lines.
Now all the hello-lines are moved over to page 2.
Is there any other case you worry about?

Keep with following paragraph

I'm trying to keep two paragraphs together. I set the check box for the paragraph above but it doesn't join the next paragraph on the page below.
Now if I edit the text on the next page, the paragraph moves down as I would like, but if I make any edits to the text above, the paragraph moves back up to the previous page.
The edits don't have to change the line counts. Just deleting and retyping a single character will do it.
FWIW, the paragraphs in question are 2 different list styles.
Any Suggestions?
TIA
Bill
Message was edited by: bleddy

Actually, some extra googling around revealed that this bug was present (and reported) since version 1.0 of Pages: http://www.betalogue.com/2007/06/25/pages-20-keep-with-following-paragraph-fails -for-consecutive-paragraphs/
That's 2 full versions and a couple years, without a fix, for such a huge, glaring pagination bug.
This just boggles the mind. And gives me to think that Pages is, in fact, nothing more than a toy application and that its developers aren't overly worried with attaining any standards of professional reliability...
Message was edited by: zedrdave

Strange pagination behaviour on detail report (BUG?)

Hi
I've the following situation:
Form on a table and below an sql report based on value of one of form fields. Everything is fine as long, as I use form's primary key for the report, but when I use any other field, pagination breaks - going to the next report page gives "no data found" in the report region. However, where I refresh entire page, I see the next page just fine.
Case:
create table master (id number primary key, num2 number, data varchar2(10));
create table detail (id number primary key, parent number);
insert into master values(1,1,'aaa');
insert into detail values (1,1);
insert into detail values (2,1);
insert into detail values (3,1);
insert into detail values (4,1);
insert into detail values (5,1);
insert into detail values (6,1);
insert into detail values (7,1);
insert into detail values (8,1);
insert into detail values (9,1);
insert into detail values (10,1);
insert into detail values (11,1);
insert into detail values (12,1);
insert into detail values (13,1);
insert into detail values (14,1);
insert into detail values (15,1);
insert into detail values (16,1);
insert into detail values (17,1);
insert into detail values (18,1);
insert into detail values (19,1);
commit;
Create a form on master table with defaults on everything and ID as primary key (my is sequence based, but it doesn't matter)
The report code is:
select * from detail where parent=:P22_ID
and everything works fine - report pagination works. But if I change the code to
select * from detail where parent=:P22_NUM2
Pagination breaks :/ Clicking next gives "no data found", entire page refresh shows report page 2
Changing "Enable partial page refresh" doesn't help
Any suggestions?
Martin

Answering my own question...
After doing some more digging I've found that on full page refresh all bind variables work, on "next" report page however only form's primary key is set, and all other page variables are nulls, so if the report's pagination is to work, it can't use anything else
Anyone knows is this a bug, or a feature??

BUG- Reports pagination

I have to post this again as it was listed under different topic-
Description: Only 15 rows are displayed even when no pagination is selected. I have tried log out/clear cookies etc. I have also set max rows to 100.
I have posted a test case to reproduce this bug
Test case link:
http://htmldb.oracle.com/pls/otn/f?p=26867:6
Run this page
Here is the description to reproduce this bug-
created a table called test-
2 columns- id and description
Has 27 rows.
Create a report. Set pagination scheme to none.
Set max rows to 100.
Run the page-
Only shows 15 rows- no matter what you do
Please let me know if there is a workaround for this as this is crtical for our application
Thanks
Kunal

Kunal,
Works now, you had the ânumber of rows (item)â attributes set to 25. This attribute requires a page item reference, typing in a number results into using the default number of rows, which is 15. This attributes also overwrites ânumber of rowsâ, so unless you want to specify the number of rows dynamically at run-time, you should keep that field set to NULL.
Regards,
Marc

Bug report? Pagination language problem?

I've been trying to find a link to submit what I think is a bug in iTunes, but if you've ever looked for such a link, you'll get dizzy from all the circles you'll go through.
Anyway, so all of you will know and may know of a way to report it, there seems to be a minor bug with pagination when getting search results within iTunes.
In English: Do a search on an artist with more than 250 songs, which is the max number of songs iTunes can list on a page. Search Frank Sinatra - he has over 2400 songs. (Be sure to click the arrow next to his artist name in the artist column, then click 'see all songs by this artist') At the bottom right of the first page, you will probably see the word mehr or something like it. That's another language word for 'more'. Click it and you'll get the next page, but the language changes, and now you'll see the word 'previous' on the bottom left in whatever language happens to be the current flavor. It seems to rotate through all available languages. And yes, I do have English set as my language in the preferences.
Again, this is minor bug (if that's what it is) and since I know what it is, there isn't any problem using iTunes. But trying to navigate Apple's support pages to find a stupid "report a bug' link leaves me frustrated. This 'bug' has been there for a while, but I thought I'd finally let them know I've noticed it and see if they want to change it.
If I've posted this in the wrong forum; my apologies. Moderator, please locate where most useful.
Best Regards,
Bob

Hey, I see those Mehr and Zurucks, too!
Here's the feedback page:
http://www.apple.com/feedback/itunesapp.html
If you lose it again, you can easily find it by going to itunes menu > Help > Provide iTunes Feedback. No dizzy circles, pretty simple!

BUG -- Column filtering bug in Apex 4.1 causing pagination error?

Hi All,
I'm getting a pagination error, when filtering from the column header in an Interactive Report.
Report error:
Invalid set of rows requested, the source data of the report has been modified.
Reset Pagination*
The steps to recreate:
1. Run an Interactive Report
2. Click the next button to go to the second page of data.
3. From the column header select a data element that will return less than 15 rows. Note -- if the there are 15 or more rows of data, the error will not occur.
The Report will fail with the error shown above.
Note that the same error does not occur if you use the filter from the Action menu. This appears to be a bug in the column filtering.
It looks like the pagination needs to be reset after the column filter, but how is this done?
I'm using the canned interactive report with no customizations. Is there a fix for this issue?
Thanks

This «bug» is known for a long time unfortunately...
I never find any solution for IR report filtering.
Maybe you can use some JQuery to change the link when clicking a value in the list, (add a code that will update pagination).
Something like :
$('#apexir_rollover_content').load(function() {
$(this).find('a').click(function(){
gReport.search('SEARCH');
});But I don't think it will work, as they already use JQuery to bind that <a> events.
In case you update your report using a button, you can simply use a "reset pagination" process called on button click.
In case you use column link you simply have to tick the «Reset Pagination» checkbox.
I hope Apex team will fix that one day.
Good luck.
Yann.

Bug in pagination CSS on these support forums

Hi
Just noticed the pagination buttons in these forums are screwed to the right side... and then i searched and found that in this file, you have a css entry .cf { } which is empty... i assume it should have { clear: both } ?
This is the css file which has it empty
http://support.cdn.mozilla.net/media/css/common-min.css?build=2e2daad
And here's a screenshot of how it looks now
http://scr.hu/screenshooter/0640523/ypubyvb
Thanks

I use this code in userContent.css to fix this issue and style that section (I like to dim stuff).
<br />
<pre><nowiki>@-moz-document domain(support.mozilla.org) {
ol.pagination {margin:5px 0!important;padding:0!important;float:right;clear:both;opacity:0.5}
ol.pagination:hover {opacity:1}
ol.pagination a {font-weight:bold;font-size:1.3em!important}
}</nowiki></pre>

CS5 Trial bug with pagination?

I have a book of about 250 pages that is composed of about 20 different files.
There is the title, copyright, TOC, chapter_01, Chapter_02, etc.
I want all pages automatically numbered starting from 1 to around 250.
This includes the title page (which does not actually show the page number),
the table of contents, etc. My intention is that reading the PDF in various readers
will have the page number agree with the 'absolute page number' in the reader
'current page number' box.
I want InDesign CS5 to automatically do the numbering for me and update the numbering
for each file (i.e. document).
I have the footer all set up (no problem there). I do NOT want 'section' numbering.
[1] The book page numbering options (with no documents selected in the Book pallet) is;
- Continue on Next page
- Insert Blank Page
- Automatically update page and section numbers
[2] Each document (file) is set up as;
- The 'Start Section' is grayed out and checked (I think this is a the bug)
- Automatic page numbering is checked
- The start page is set at 1 (this should not matter)
- Automatic chapter numbering is checked
[3] General Preferences (with no book or documents open)
- General page number = absolute numbering
What happens is that each file starts out with its own numbering system
(starting at one) which is not what I want.
I think the 'grayed out' check box for 'Start Section' (see [2] above) is a bug.
I DO NOT WANT TO START A SECTION. I want to continue paging from
the previous document.
Is there something simple I am missing?

I figured it out.
You have to set the General Preferences > Page Numbering
to
Section Numbering.
If you do not do this then the document setting seem to be 'reset'
to a non-automated way of numbering - even if you set up your
doucments to use 'automatic numbering'.

BUG: Session 0 - Report - Pagination

Hello,
the problem is as follows:
After reloading a report (pagination, next range), the session 0 gets lost.
My setting:
Apex 4.2.2.
Two pages, the first displays a report and the second the details.
The report has activated pagination.
Example for the report source:
SELECT APEX_UTIL.Prepare_Url('f?p='||:APP_ALIAS||':DETAIL:'||:APP_SESSION||'::::P11_OID:'||OID)         AS LINK
Course of events:
Open the report page with session id 0
see the url of the report links, it still has the session id 0
f?p=APEX_CON:DETAIL:0::::P11_OID:58605
Click on the pagination button 'Next'
see the url of the report links, there is a new session id and no session id 0
f?p=APEX_CON:DETAIL:9649916689018::::P11_OID:57645
Thanks,
Max

Hi Jari,
thanks for the quick response.
I tried the following:
Report source:
SELECT APEX_UTIL.Prepare_Url('f?p='||:APP_ALIAS||':DETAIL:'||:APP_SESSION_VISIBLE||'::::P11_OID:'||OID)         AS LINK
Report result:
Open the report page with session id 0f?p=APEX_CON:DETAIL:0::::P11_OID:58605
Click on the pagination button 'Next'f?p=APEX_CON:DETAIL:9649916689018::::P11_OID:57645
Report source:
SELECT APEX_UTIL.Prepare_Url('f?p='||:APP_ALIAS||':DETAIL:666666::::P11_OID:'||OID)         AS LINK
Report result:
Open the report page with session id 0f?p=APEX_CON:DETAIL:0::::P11_OID:58605
Click on the pagination button 'Next'f?p=APEX_CON:DETAIL:666666::::P11_OID:57645
Report source:
SELECT 'f?p='||:APP_ALIAS||':DETAIL:666666::::P11_OID:'||OID         AS LINK
Report result:
Open the report page with session id 0f?p=APEX_CON:DETAIL:666666::::P11_OID:58605
Click on the pagination button 'Next'f?p=APEX_CON:DETAIL:666666::::P11_OID:57645
I think the function APEX_UTIL.Prepare_Url in combination with an AJAX report refresh is the problem.

Bug 3.1: Layout of "Pagination for this page/print friendly" checkboxes

Hi,
looks like that my entry in the 3.1 feedback application has been overlooked because the production version still shows a layout issue in the builder.
On the Edit Navigation Bar Entry (4308) and the Create/Edit Breadcrumb Entry (290) page the layout of the "Pagination for this page/print friendly" checkboxes is screwed up a little bit.
Patrick
My APEX Blog: http://www.inside-oracle-apex.com/
The APEX Builder Plugin: http://builderplugin.oracleapex.info/ New
The ApexLib Framework: http://apexlib.sourceforge.net/

Hi Arie,
I thought about the same.
Yes, I really enjoyed my vacation! :-)
Patrick
My APEX Blog: http://inside-apex.blogspot.com/
The APEX Builder Plugin: http://builderplugin.oracleapex.info/ New
The ApexLib Framework: http://apexlib.sourceforge.net/

Bug report: App Builder always resetting pagination

See my earlier post about this at
Re: PPR breaks browser Back button
I thought (mistakenly, it turns out) that the PPR stuff was to blame for the App Builder main page always "resetting" to the first set of rows.
But when I created a report using a PPR template at
http://htmldb.oracle.com/pls/otn/f?p=24317:138
paginate to the 3rd set of rows, run some other page and come back to the PPR page, it does indeed properly remember which set it was on i.e. pagination is NOT reset.
But when I do the same thing in the App Builder...Go to the 3rd set of pages, run a page from there. Now when I click on the Edit Application link on the Developer Toolbar, it throws me back to the first set of pages :-(
I just realized the reason is that the Edit Application link in the Developer Toolbar is
http://htmldb.oracle.com/pls/otn/f?p=4000:1:3150046948585447489::NO:1,4150,<b>RP</b>:FB_FLOW_ID,FB_FLOW_PAGE_ID,F4000_P1_FLOW,F4000_P4150_GOTO_PAGE,F4000_P1_PAGE:24317,138,24317,138,138
It has the RP in there that does the pagination reset! Why?
The same link in Version 1.6 is
f?p=4000:1:1514638425792267178::NO:1,4150:FB_FLOW_ID,FB_FLOW_PAGE_ID,F4000_P1_FLOW,F4000_P4150_GOTO_PAGE,F4000_P1_PAGE:102,80,102,80,80
No RP there.
What is the reason for this change?
Thanks

You could delete 20 pages by just staying on the page
detail pages and hitting delete, I've done exactly
that before.Carl, not sure what you mean. I outlined my exact steps to delete a page above and how it keeps throwing me back to Page 0, etc.
What do you men by "staying on the page detail pages and hitting delete"? You click Delete once, you are taken to the Delete Confirmation page.
So how can you delete multiple pages at once?
[I had another feature request some time back about being able to export or delete "Page Groups" that would come in handy here as well]
Deleting 20 pages is an edge case lets say you had 11
pages your pagination shows 1-10 you go to page 11
and delete it you'd have the same problem. As I said, its the same thing as any email client or any software really displaying a list of items and you open an item and delete it. Where to go next? There should be options for this kind of thing.
You can be
fairly certain that there will be some sort of report
enhancement that if you try and return rows of say
20-30 and there are only 19 the report engine will
return you 10-19 so you don't get a broken report.Yup, this is a very common "newbie" mistake where there is a search filter on a report region and a branch back to the same page. If I forget to reset pagination on the Branch Attributes page, and Search 1 returns 25 and I am on 20-25 and I start another Search that returns 10 rows, the report "breaks" since it tries to display Rows 20-25 of 10!
Are you saying that the "reset pagination" checkbox on the Branch page will no longer be necessary in upcoming versions? The report engine will be smart enough to "figure out" what set of rows to return based on what rows (x to y) the page was "stuck at" before?
Thanks

Pagination Bug

Similar Messages

Maybe you are looking for