With the new security update for Views 6.x-2.x we have had sites updated from the 6.x-2.x-dev release dated 2011-03-23 to 6.x-2.14

In the process the drpager module (minimax pager) display is now broken. Now it will not display the simple symbols ">" and ">>" etc. Instead it is displaying as "next >" and "last >>". Changing configurations for drpager or the view itself does not solve this problem.

This may be a problem for the drpager module but it was not a problem until the views update that includes all the commits from 2011-03-23 to 2.14 and the problem may be related to something in there.

Any thoughts?

Comments

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Postponed (maintainer needs more info)

Mh this project (minimax pager/drapager) doesn't exist, so about which project do you talk exactly?

You know 6.x-2.x-dev is there since a really long time so well that's life.

izmeez’s picture

izmeez commented

Thanks for the response.

The project I am referring to is, http://drupal.org/project/drpager

This problem has arisen somewhere after the 2011-03-23 commit and now. I am wondering if it is a change that requires an update to the drpager module or reflects a problem introduced by a particular views commit.

I may have to go through a process of checking individual commits to track this down.

dawehner’s picture

dawehner
Primary language German
commented
Project: Views (for Drupal 7) » Minimax pager
Version: 6.x-2.14 » 6.x-1.x-dev

Thanks for the link, i could have bet i looked at this url.

At the first look i would say this is a bug of the drpager module, but i'm not sure.
In this case the views issue submission guidelines: http://drupal.org/node/571990 says that this bug should be reported against the other contrib module and if they can report that the root of the problem is views, be moved back. For example drpager could have missed some feature additions of views itself.

To be able to fix the issue you definitive should provide an export of your view. If you want to really help the developers try to create a view which has this bug, but can be used on any system. This means that you don't have things like cck-fields or any other custom fields, which aren't there if you just install drupal + views.

izmeez’s picture

izmeez commented

@dereine Thanks for following up on this. The issue became apparent when updating live sites which are fairly complex. And as I have looked at it closer the behavior seems to be different and related to whether or not Ajax is on. I will try to find some time to break this down into a simpler test case that can be used on any system and report back here shortly.

mattyoung’s picture

mattyoung commented

any more update to this issue?

From Mt. Emei, China

izmeez’s picture

izmeez commented

Sorry, I haven't been back to this. I guess as a module maintainer you are wondering if this can be closed. I'll try to find some time to revisit this. Thanks.