Pager Notices in /tracker

In general you should have read http://drupal.org/node/571990 as it's explained in the issue creation form :)

Anyway can you provide an export which allows to reproduce this easy? This would really help!
Just from screenshots you can't get really all informations afaik.

I encountered the same problem. After week of search in code. I found some mistake. views_plugin_pager_full.inc in method set_current_page. Problem in the way how determined pager ID (if it is nonzero) for render.
Find string

$pager_page_array = isset($_GET['page']) ? explode(',', $_GET['page']) : array(0);

And replace it into

          if(isset($_GET['page']))
		  $pager_page_array = explode(',', $_GET['page']);
	  else {
		  $pager_page_array[0]=0;
		  $pager_page_array[$this->options['id']]=0;
	  }

Here is the written email, because the person doesn't know how to use the contact form/drupal.org

Just in general, only because i linked a handbook page doens't mean that you don't miss all informations.
Just assume that we are not in front of your pc/...

> 
> Hi.
> ich hätte nicht ein ticket auf gemacht wenn ich was gefunden hätte oder
> ähnliches
> 
> chekliste
>   •Is this really a Views issue? (It could be a Drupal, CCK or other
> module's issue.)
> yes
>   •Are you using the latest version of Views? Is the problem fixed in the
> development version?
> yes und no
>   •Is it a duplicate? Have you searched?
> no und yes
>   •Do not hijack other issues (if you have to change the title you should
> probably open a new issue)
> keine ahnung ich denke der title ist aus sage kräftig oder nicht?
>   •Issues should be specific. Broad topics are better in the forums.
> weis nicht was du da mit sagen möchtest ist ein bug von views
>   •Do not post issues that can be fixed with CSS.
> kein css problem
>   •Describe, in detail, the steps to reproduce the issue.
> gut habe nicht an den export gedacht
>   •Try to reproduce your problem using a Drupal core theme and turning off
> as many modules as possible.
> habe ich gemacht
>   •Screenshots are always helpful
> nun hast nen einstellungs shot  hatt wohl nicht gereicht
> 
> •Questions you should be able to answer:
>   1.How often does this happen?
> Standig repruduzierbar
>   2.What is the exact, complete error message? Copy and paste it into the
> issue.
> haste oben stehn
>   3.List every step you took to create the problem. Each click, each menu
> item. Reproducibility is the key to solving issues.
>   habe ich geschrieben  bis auf den export
>   4.Other modules that may be interacting.
>   kein anderes module in mit leiden schaft gezogen auch ohne andere module
>   5.Completely describe exactly what you are attempting to accomplish. If
> your issue is only one or two sentences long, you have almost certainly not
> described the problem in enough detail.
> ich denke es ist ausführlich genug gewesen.
> 
> sorry aber ich muss es sagen und musste es los werden
> das das wieder typisch deusch von dir rüber kam
> 
> das neue was ich gefunden habe ist das nurn weis ich nicht, da es bis jetzt
> nur in verbindung mit xml sitmap auf tritt,
> ob es sich lohnt es als issue bei dir zu machen.
> 
> •Notice: Undefined offset: 0 in theme_pager() (Zeile 337 von
> /var/www/web909/html/CMS/includes/pager.inc).
> •Notice: Undefined offset: 0 in theme_pager_next() (Zeile 528 von
> /var/www/web909/html/CMS/includes/pager.inc).
> •Notice: Undefined offset: 0 in theme_pager_last() (Zeile 564 von
> /var/www/web909/html/CMS/includes/pager.inc).
> •Notice: Undefined offset: 0 in theme_pager() (Zeile 359 von
> /var/www/web909/html/CMS/includes/pager.inc).
> 
> this i get
> if i have
> XML sitemap             7.x-2.0-beta3
> XML sitemap custom
> XML sitemap engines
> XML sitemap menu
> XML sitemap node
> XML sitemap taxonomy
> XML sitemap user
> enabled
> you get this first if go to admin/config/search/xmlsitemap/engines then
> admin/config/search/xmlsitemap/custom
> if the block disabled in this pages then the notice is not shown maybe a
> problem od xml sitemap or not ?
> 
> gruss alyx

> you get this first if go to admin/config/search/xmlsitemap/engines then
> admin/config/search/xmlsitemap/custom
> if the block disabled in this pages then the notice is not shown maybe a
> problem od xml sitemap or not ?
> 

This was really valuable informations, let's move first to xml sitemap because it seems to be a bug of them.

Just in general, please calm down.

now i understood why you sent me this in private, sorry about my confusion.
That's valuable because as davereid told me xmlsitemap doesn't use views.

So this seems to be a general drupal issue from my perspective or a bug of xmlsitemap and views together.
Let's move back.

So i'm wondering is this still the case for the current dev version?

Recently some fix to remove notices from pager came in, so this might have helped here as well.

I came across almost the same problem. somehow my pager was missing and i gave it another pager ID, but then I had a lot of warnings. with the fix in 2, the warnings were gone.

I noticed, that this bug is gone in the newest dev version.