On Jun 24, 2012, at 11:26 PM, Alec Taylor wrote: > > Hmm, I'm not sure. > > I'm running the latest trunk from github: > https://github.com/web2py/web2py - If that makes a difference. > > Yes, the /profile/ URL is the one giving me trouble. It could be > something on the facebook side, though I'm not sure.
I'll make one more run, with the current trunk, to see whether any recent changes might have caused a regression. Would you please try logging the result of a URL call, either in your model or controller (I tried both)? Use whatever logging mechanism is convenient for you. If those steps don't help, I'll ask you to insert some logging into the routing code itself so we can see what's going on. > > On Mon, Jun 25, 2012 at 7:04 AM, Jonathan Lundell <jlund...@pobox.com> wrote: >> On Jun 24, 2012, at 2:02 PM, Jonathan Lundell wrote: >>> >>> On Jun 24, 2012, at 1:38 PM, Jonathan Lundell wrote: >>>> >>>> On Jun 24, 2012, at 9:30 AM, Alec Taylor wrote: >>>>> >>>>> To be as clear as possible, here is a gist containing all the files I >>>>> changed (for a test-case) since creating this "simple new project": >>>>> >>>>> https://gist.github.com/61a6b9f8e71f706e4255 >>>> >>>> I installed that app under 1.99.7 (I had to disable signature=False and >>>> turn off the Facebook stuff; no libraries) and URL(f='profile') returned >>>> '/profile'. >>> >>> Ditto for the current "nightly" build (actually June 9), with >>> signature=False turned back on. >>> >>> Are you using something more current than that? I'm doubtful that the >>> presence of the FB logic would affect things one way or the other. >> >> My code: >> >> import logging >> logger = logging.getLogger("web2py.app.social") >> >> ... >> >> logger.error("db.py: %s" % URL(f='profile')) > --
