Hi Bob

Hmm, tough one...Just wondering if this approach could work...assuming your current content structure looks like this

Content
- Homepage
  - Page
  - Page
  - Page

Would it then be possible for you to move the protected content nodes to a "Protected" folder/container like

Content
- Homepage
 - Protected
   - Page
   - Page
   - Page
   - Etc.
 - Contact form

Since the rest of the pages are protected they're not indexed in search engines anyway so it should not matter to make this structure change?

Looking forward to hearing your thoughts about this.

/Jan

@Jan,

funny thing is... that is what i already had done...

Home [actually protected too]
- protected page
- protected page
  - nested, still protected

Contact Page

for some reason, it is inheriting the protections...

Even created new page.

Should note... this site is multi-lingual... has two home nodes [one spanish, one english] similar structues underneath.

any more thoughts?? 

Hi Bob

I don't think that structure is the same that I suggested with my second approach? Seems like the structure I assumed you had? :)

In my second approch I'd like to move all protected nodes into the "Protected" folder so the inheritance will not influence the Contact page. But it's of course going to be hard if you still need to protect the Homepage node of course...But if not I think it should be a viable option, no?

Regarding multi-language then I imagine it may be able to work like this

• Homepage EN (Not protected)

  • Protected (Protection set here)
    • Page (Protected)
    • Page (Protected)
      • Page (Protected)
    • Etc. (Protected)
  • Contact page (Not protected)

• Homepage ES (Not protected)

  • Protected (Protection set here)
    • Page (Protected)
    • Page (Protected)
      • Page (Protected)
    • Etc. (Protected)
  • Contact page (Not protected)

Sorry about the bad formatting but the markdown editor is falling a bit short when trying to make nested lists but hope it's clear enough to make my point :)

/Jan

Yeah, so i figured out a bit of a hack... there is somethign with the culture and hostnames that is causing the challenge...

i added two more languages and mapped them to the two new nodes in question... that appears to have made everything better...

i will take the hacky approach... as this project had tons of scope creep and a third party agency is now trying to take advantage without us getting any relationship or $$$ benefits... Thanks for talking it out with me @Jan!

Hi Bob

You're welcome mate.

Yeah, it's not pretty but sometimes it's just about getting the job done indeed :)

See you at CG15?

/Jan

ugh, still trying to work the bosses over... stay tuned!

Fingers crossed :)

is working on a reply...