On Sun, Mar 21, 2010 at 10:46 PM, cd34 <mcd...@gmail.com> wrote: > Something else is considerably broken with my upgraded installation. > webhelpers pager() on pages that were previously working and have been > untouched are also throwing the 'Internal Server Error'
Again, please post the traceback. If it says anything about 'routes.url_for()', it may be related to another issue, it may be related to another issue we're dealing with. In short, I'm checking whether Paginate needs to be updated to accommodate the new version of Routes and Pylons, and whether it's necessary to do this now or after 1.0. (In detail, Paginate uses url_for(), which depends on a singleton in Routes. Something in Routes 1.12 threw off one of the webhelpers.paginate unittests. Meanwhile, Pylons now has an option to not use the singleton. (Not using the singleton means url_for() won't work; which is why we're migrating to pylons.url. But Paginate doesn't have access to pylons.url.) Changing Paginate to not use the singleton would require the user to pass in a callback function to generate a URL to the other pages. So I'm checking whether it's necessary to do this for WebHelpers 1.0 or whether it will affect only future apps that use this option.) -- Mike Orr <sluggos...@gmail.com> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-disc...@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
