I'm using spaces_taxonomy, and am trying to figure out the best way for my feature to allow for variable overrides on a per-space basis. I think I may simply be lost in the documentation. Here's what I've done:
Okay, great. Now I want to override these variables on a per-space basis. I'm guessing that going "/my_space_purl_prefix/features/[my-feature]" should present me with the same-looking form, but the submission should save the variables to "spaces_overrides" rather than "variables". However, when I go to "/my_space_purl_prefix/features/[my-feature]", I simply get redirected to "/features/[my-feature]".
I'm sure I'm just mis-undersanding what the purpose of the "/features/[my-feature]" page is, but I can't seem to figure it out! Can someone please help me understand this?
Cheers
Comments
Comment #1
ryan_courtnage commentedEureka! After carefully watching the address bar in Young Hahn's screencast (http://developmentseed.org/blog/2009/dec/18/spaces-3-customize-everythin...), I was able to determine where I went wrong.
I was trying to set space-specific variable overrides by visiting "/my_space_purl_prefix/features/[my-feature]" (where "my_space_purl_prefix" is the Spaces path setting set in the Vocabulary term admin). I was simply in the wrong place.