Views panes ignore overridden pager settings from Views3

Sorry, I don't get the point of your criticism; I have searched the issue queue, and there is exactly one issue mentioning "Views3", which is unrelated to pager settings. Searching for "Views 3" results in a large number of issues not even related to "Views 3", and there is no way of cross-referencing an meaningful expression like "issues for panels-6.x-3.9 AND views-6.x-3.0-rc3" as far as a I know.

I can't see the necessity of exports either as this is the default behaviour I'm experiencing. Imho it only makes sense to attach exports if an issue can not be reproduced with default settings and might be caused by complex interactions (like contexts) that really require an export.

However, feel free to won't fix the issue queue if you think it's necessary to kep up.

Thanks, Merlin, now I got this warm and fuzzy Drupal feeling again... and a bad conscious if I might have been to quick with the report. Thus I tried to synthesize the issue with a simple Panel and a simple View. Honestly I'm not entirely sure what I have here, that thing crashed my browser two times on a site with ~20k nodes.

The View is configured to provide a "more" link, and to use a pager with the settings: "full pager", and "limit to 25 items". The View has two displays, a block and a page. The Views' page display renders correctly with 25 records plus a full pager. The Views block is embedded into a panels pane with no other Views panes (= no pager ID conflicts). The Views pane is supposed to use different settings than the View, and to limit the display to ten items; "Use pager" is not checked (I have a "more" link in the view, pointing to a Views page, and I don't want a duplicate pager).

I was expecting to get a Panels page, listing 25 items (that was the behaviour of my "real" view). Instead I got a listing of all nodes on the site, neither limited to 10, nor to 25 items. I don't really believe this, so please someone else give it a try and confirm that my server is jinxed...

I believe, the "Use pager" setting in the Views pane's setting is the key here; if it is checked, I get a correct display of ten items in the Panel, plus full pager plus "more" link. The "more" comes from the View, the pager probably comes from the Views pane (at least it doesn't go away when I select "Display given number of elements" in the Views block display). So the Panels pager override seems to require "Use pager" checked in the Views pane settings. If you can reproduce this so far, please try next: Check "Use different settings than the View" and "Use pager", Save (result: Panels page with full pager and more link), then edit the Panel again, uncheck "Use pager", Save again, reload Panels page. Now I'm getting a Panels page with ten items, no full pager, and a "more" link pointing to the Views page. Too weird for this hour, will go through this again tomorrow...

I have checked the Panels/Views3 behaviour on a couple of other sites, and in all cases the Views panes ignored overridden pager settings. However I'm not entirely sure if this an actual bug, and if it is a Panels issue.

My theory is, that we encounter an unfortunate interaction of Panels and Views parameters; paging has changed significantly in Views, and that is where I believe the troubles to start (this applies only to my "real world" views and not to the exports provided in #4 with their freakish behaviour).

Example: After updating from Views 2 to Views 3, I get views settings that differ from those originally configured in Views 2. We have now a seemingly undefined setting, chosen randomly (?) from the four new options, e.g. "Paged output, full pager". Even if the Panels views pane setting is: "display 1 item", it displays a larger number of items in the Panels page.

The "fix" seems to go like this: Simply change the Views setting to something else, e.g. "Display a specified number of items". Save. Maybe clear the caches. Probably the View will now render properly in the Panels pane. If not, save the Views pane settings at least one time. In the cases I have checked so far this proecedure restored the behaviour from Views-2-views embedded in a Panel. Maybe changing the settings and saving a couple of times somehow "notifies" the other module of changes.