Sorry for the double post but I've partially managed to figure this out thanks to the load issue info. I can workaround that error by adding <include gem='hobo_clean'/> to either admin or application dryml files. There is a catch tho.. that kills any styling on the admin site whatsoever (at least I can continue working on functionality before this gets resolved either by a temporary include or commit). I've tried every include order permutation within those 3 dryml files I can think of to bring the styling back (at this point any would do as reading plain text is annoying as hell, regardless if I get main or admin theme). Sadly I just don't know enough about hobo and dryml to make it work so I got either no change or some funky merge of list items from the admin and main sites.
I could do it through math and try literally every combination possible but with 3 files and over 10 lines of code even if I wrote some auto meta-programming app it would take far too long I hope that someone more knowledgeable will be able to tell me what includes I need to copy and where to get it working for now. On Apr 18, 1:15 am, Bob Sleys <[email protected]> wrote: > I've run across similar issues with 1.4 and think I've nailed down. If > what I'm going to describe next doesn't help then I guess disregard it LOL. > > The issue at least in my case came down to loading order. > > First core.dryml is loaded from the gems directly - no problems here > > Next application.dryml is loaded but it doesn't load the auto generated > rapid tags by default. However it does load all dryml files in > taglibs/application automatically. > > Next the sub site dryml file is loaded, typically either front_site.dryml > or admin.dryml. This is where the auto generated rapid dryml files are > loaded at by default. > > The issue is if you try to extend any of the auto generated tags before > they get loaded you'll get errors. This is particularly confusing because > much of the documentation states to place these tag extensions in > application.dryml but with 1.4 the auto tags haven't been loaded yet > leading to errors. > > The simplest fix is move your tags out of application.dryml and place them > either in front_site.dryml or admin.dryml. > > It's also quite confusing that all dryml files in taglibs/application are > auto loaded at the same point as application.dryml but the auto generated > files aren't which by default will typically lead to errors. > > IMHO the auto loading of taglibs/application should be discontinued OR when > front_site.dryml loads all dryml files under taglibs/front_site should load > AND all files in taglibs/admin_site should load when admin.dryml loads. IE > when a subsite loads it should load all dryml files in > taglibs/<subsite>_site. > > Of course this can be achieved by adding an <include ...> into each > subsite.dryml file to mimic the auto loading. (this is what I've done) I > then place tags into dryml files named after the model they are for in > the appropriate subsite_site dir so I can keep them organized. I really do > hate haveing too much stuff in one file and this lets me keep my tags > organized. > > Bob > > > > > > > > On Tuesday, April 17, 2012 5:18:34 PM UTC-4, Scorpio wrote: > > > Hello, > > I generated an app with an admin subsite, invite only, no email > > confirmation with at least 1 controller public > > > The page tag works fine for front controller but in the adminsubsite I > > get errors that are pretty much the same for all actions. Going to > > admin/users generates the following errors (log and full stack trace > > in pasties) > > > Log -http://pastie.org/private/mmj9yfq1om7sney4hebqdg > > stack trace -http://pastie.org/private/gueteqemakku9yydu8apng -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
