The render method of the panels_views_plugin_row_fields class modifies the value of $view->field value, that causes other modules to not be able to work as expected (e.g. views_slideshow).
Actually I think it is only errors in variable names, because the code tries to restore the original value of $view->field.
Comments
Comment #1
b-prod commentedThe patch below corrects the described bug.
Comment #2
osopolarThe patch from #1 seems to be correct. I applied the same changes to the panels 7.x-3.x-dev. This fixes my problem in #1116648: Pager doesn't work with Panel Fields. Would be nice to have some more reviews.
d7 version of above patch!
Comment #3
osopolarFixed typo in #2, changed patch name to be more clear, that it is fr d7.
d7 version of patch in #1!
Comment #4
osopolarComment #5
Letharion commentedAssigning to merlin for review.
Comment #6
mandreato commented#1 worked for me with Panels 6.x-3.x-dev
Comment #7
mandreato commented#3 worked for me with Panels 7.x-3.x-dev
Please commit both.
Comment #8
mandreato commentedLatest 7.x-3.x-dev fixes a part of the problem:
It remains the part of the foreach loop, which I fixed with the attached patch.
Comment #9
b-prod commentedThis is a very old issue, that can be easily fixed, so I set it as critical.
Patch tested successfully with Views Slideshow module, because this module uses the rendered fields in its theme function.
To clearly identify the bug, here are the steps to reproduce:
When displaying the view, you get a lot of error messages (depending of the number of fields set in the pager), caused by the pager fields not available in the $view->field array.
Comment #10
japerryFixed in Drupal 7!
http://drupalcode.org/project/panels.git/commit/f253afb
Comment #12
b-prod commented@japerry: for your information, there are some basic rules about commit messages:
https://drupal.org/node/52287
Comment #13
osopolar@B-Prod: Wondering what is wrong with japerry's commit message.
Comment #14
japerrylol I was wondering the same. I think I missed a comma? Oh well.... ;)