-
I posted previously () about a Pager not working, and the “solution” was to turn off partial refresh, then it magically revealed a Command not handled Exception, which “default error page” provided additional detail for. All in all quite nice, once I stumbled upon the proper magic.
-
Now that same exact Pager randomly fails to function. Today I changed the name of the CSS Class on that XPage, so it’s hopefully more meaningful in the distant future when I have to figure out how I built this. (grin) This broke the Pager. No error (default error page is still enabled), no console message, no JS error in Firebug, nothing what-so-ever out of the ordinary anywhere, except the Pager suddenly reloads the page without changing anything.
-
I stopped http and cleared cache, I relaunched everything, I cleared cache.ndk and relaunched everything, I rebooted and relaunched everything. Nothing made any difference.
-
Until I removed partial refresh from the Pager. DING. Functions beautifully. Put partial refresh back. DING. Functions beautifully. Now it will continue to function beautifully until the next time it doesn’t. This has happened numerous times during the month or better I’ve been laboring with XPages.
-
I’d be more than delighted to provide “the exact steps to reproduce”, except there are no exact steps. It happens randomly, from what I can tell.
Thanks for your time…