Closed (fixed)
Project:
Smart Paging
Version:
7.x-1.3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Oct 2011 at 18:31 UTC
Updated:
12 Aug 2012 at 01:21 UTC
Jump to comment: Most recent file
Comments
Comment #1
damienmckennaHere's a quick patch to do a quick check before doing the foreach() loop.
Comment #2
rickvug commentedAlso having the same problem. Patch applies cleanly, fixes the problem and makes sense. RTBC.
Comment #3
arpeggio commentedThe patch is already included in #1309516: Extended path aliases compatability which is already committed/pushed. Thanks.
Comment #5
joshua2046 commentedafter install Smart Paging module
My website report this!
Warning: Invalid argument supplied for foreach() 在 smart_paging_url_outbound_alter() (行 507 在D:\wwwroot\joshua2046\wwwroot\sites\all\modules\smart_paging\smart_paging.module).
Warning: Invalid argument supplied for foreach() 在 smart_paging_url_outbound_alter() (行 507 在D:\wwwroot\joshua2046\wwwroot\sites\all\modules\smart_paging\smart_paging.module).
Warning: Invalid argument supplied for foreach() 在 smart_paging_url_outbound_alter() (行 507 在D:\wwwroot\joshua2046\wwwroot\sites\all\modules\smart_paging\smart_paging.module).
Comment #6
rumcious commentedI'm guessing a recent update to Drupal core is causing issues with the smart paging module? I've just started to get this same error on a recent install (7.12 at time of writing +current 'live' version of smart_paging);
Comment #7
rumcious commentedLooking into this error a little bit... the number off lines the error spits out is concurrent with the number of pages available through pagination. Any movement on this or should a new topic be posted? Content does appear to paginate where indicated (not noticed any errors - there was originally due to misconfiguration, but that was sorted out once the correct parameters were set).
Comment #8
valderama commentedI also get this warning, in version 1.3 -- I guess it is only fixed in the dev version.
Would be great if you could be provide a new release which includes this fix.
Thanks
Comment #9
ivars211 commentedThe same error for me :(
Comment #10
t-readyroc commentedSeeing the same error here as well.
Comment #11
hollyh commentedany fixes?
Comment #12
arpeggio commentedHi, I have created a 1.4 version and this fix is already included. Thanks.