Yea, that was my fault, I got hard-core about the feature freeze only after I first encouraged adding the new feature. In my defense, I wanted that new feature ;) And also in my defense, we needed to respect the feature freeze and get 2.0 out the door so we can start adding features like this to 2.1!.
Fortunately, there's a simple update to your quickstart that re-enables support for tgext.pages. You just have to break websetup out into two functions, one which initializes your db, and another which bootstraps your data. --Mark On Mon, Mar 23, 2009 at 10:54 PM, Jorge Vargas <[email protected]> wrote: > > On Mon, Mar 23, 2009 at 3:59 PM, dimazest <[email protected]> wrote: >> >> >> >> On Mar 23, 1:18 pm, Florent Aide <[email protected]> wrote: >>> On Mon, Mar 23, 2009 at 12:35 PM, [email protected] <[email protected]> >>> wrote: >>> >>> > Hello, >>> >>> > I'm interested in a TurboGears CMS development for this GSOC. >>> >>> I would suggest you join forces with >>> thishttp://bitbucket.org/jon1012/tgextpages/ >>> which is a light CMS we are working on and which extends any >>> TurboGears application. >> >> I tried to setup tgext.pages for a newly created project. I used >> virtualenv with --no-site-packages, installed TurboGears version >> 2.0b7. >> Then I installed tgext.pages by doing python setup.py develop. >> >> First, I tried to install pages model to the project by Paster Script >> (easy), but I got the following message >> >> Adding Pages Database Definition to your TG Project >> =================================================== >> This does not appear to be a TurboGears2 application >> >> I ran it from the directory where development.ini, setup.cfg and >> setup.py are located. >> > right, due to a misundestanding pages paster command depends on a > feature that was pushed into 2.1 so the automatic install doesn't > works anymore. We are going to have to change the docs for 2.0.x. See > the huge thread currently going on about "DB Creation" > >> Having no luck with script I added required lines to the files, as >> described in the Manual (harder) section, now I get the ImportError: >> No module named i18n exception ( full traceback >> http://paste.turbogears.org/paste/39891 >> ) >> >> How can i get the tg.i18n module? >> > currently pages requires TG2.0rc1 > >> Dima >> > >> > > > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
