On 4/12/06, Matthew Bevan <[EMAIL PROTECTED]> wrote: > Running 0.9a1 my CMS works fine in 'setup.py develop' mode, allowing me to > create a site with a sitetemplate and start adding content. Brilliant. But > after upgrading to 0.9a4 and updating the occasional moved function > (turbogears.jsonify to turbojson.jsonify, for example), I can no longer even > run tg-admin, as it bombs with the following traceback: > > File > "/usr/lib/python2.4/site-packages/TurboGears-0.9a4-py2.4.egg/turbogears/database.py", > line 166, in set_hub > raise KeyError, "No database configuration found!" > KeyError: 'No database configuration found!' > > I've uploaded a WIP copy of my CMS at the following URL: > > 1.1MB http://www.gothcandy.com/tg-content/releases/TG-Content-0.9a4.tar.bz2 > > Previousally if the DB connection didn't exist, it just silently ignored > everything. (While working perfectly fine on a properly set up tg-admin > shell.) Why has this changed? Any difference in SVN?
I can see why it fails, but I don't know of something in the TG code that would cause this. I wonder if something has changed in SQLObject (seems surprising, though, given that there hasn't been *that* much activity that I've seen on the 0.7-bugfix branch). The set_hub implementation is basically the same that was there 300 revisions ago. If this worked in 0.9a1, it would seem that SQLObject is, for some reason, asking for the connection where it previously hadn't been. That's my initial take after a quick look at things. Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
