Hi - back again with possibly odd questions. This time, it's the Hobo Setup 
Wizard that's puzzling me, when setting up an invite-only private site.

The implication of the text in the generator and in Hobo Central 
(http://hobocentral.net/manual/generators) is that a private site does not 
have any visible controllers. 

If I set up an invite-only private site ("ALL your site will be private"), 
then I'd expect that the most I'd get would be any static pages, and a 
login page and an acceptance of the invitation. However, if I do just the 
minimal set up, and add a single resource, that resource is visible in the 
navigation, even as a guest.

I think I'd expect that there was a check on being an active_user in order 
to display the navigation. 

e.g. 

hobo new private-site -invite-only -private-site
cd private-site
hobo g resource thing name:string
rake assets:precompile
rails s

results in being able to see a link called "Thing" in the main nav menu, 
even when not logged in. This is more content than I expected to be 
exposed. And an attempt to use the resource, results in a failure message - 
but I'd expect the resource access to fail on the grounds of not being 
logged in, long before it looks for the resource itself. 

Hobo 2.1 from github (last updated 2014/07/15 15:00 UT)
Ruby 2.1.2
Rails 4.0.5

Happy to push a project onto BitBucket or GitHub if this isn't enough to 
repro the problem.

I might start making cucumber test features for these problem/questions. 
I'm having fun with cucumber at the moment. :)

Note that if I make the site mostly private instead, the instruction to 
make a single controller private, results in nothing showing at all. i.e. 
adding to thing_controller after the hobo_controller:

   include Hobo::Controller::AuthenticationSupport

   before_filter :login_required
results in even the home page being blank (I haven't investigated, but I'll 
guess this is because there is an attempt to get the route for the 
navigation?).

I'm not sure whether/how this used to work... but it doesn't seem very 
usable, as it is? I suspect new problems from either Ruby 2.1, or Rails 4.0 
usage.

Cheers, JeremyC.

-- 
You received this message because you are subscribed to the Google Groups "Hobo 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/d/optout.

Reply via email to