Hello again,
after due consideration, the removal of onclick is not such a problem,
it even allows for cleaner HTML code. I added the following Javascript
and it solved the problem for me:
$('#${prefix}pager a').click(function () {
var partial_url = this.href +
2/ Unicode characters such as « and » (angled double quotes) were
not accepted in symbol_previous and symbol_next, so I kept the defaults
( and ).
This one can be solved easily, too: in file paginate/__init__.py, change
line 541 from :
tag_string += '{0}/{1}'.format(text, tag)
to:
I have a NewRequest subscriber that's added in main() via
config.add_subscriber(). Exceptions thrown in this subscriber aren't caught
by pyramid_debugtoolbar. Is this behavior expected?
--
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To
Without more info I can say it's not expected on anything after Pyramid 1.0
where NewRequest subscribers explicitly did not support exceptions.
On Wed, Feb 13, 2013 at 12:45 PM, Wyatt Baldwin wyatt.lee.bald...@gmail.com
wrote:
I have a NewRequest subscriber that's added in main() via
I'm using Pyramid 1.4. pyramid_debugtoolbar is included via the
pyramid.includes settings. I'm not using any other includes or tweens. The
subscriber is set up like this:
def main(global_config, *settings):
config = Configurator(settings=settings)
def callback(event):
Exceptions
Oh.. that.. yeah. Without providing any useful information, I can just say
that I tend to avoid NewRequest subscribers like the plague now that
config.add_request_method exists.
This sounds like a more fundamental issue with the toolbar. It historically
causes all sorts of odd problems that some
