Full page webskins are designed so that the look of a content item can be completely changed by switching webskin. That means that all full page webskins need to include appropriate header/footer html themselves.
At this point only navigation has built in access restriction. If you need to do that for other types try the CheckPermission tag in the security tag library. Code between the start and end tag will only be shown to users who have the correct permissions. I can't really comment on the structure you've set up or the FUs since you've left out a lot. For example how are are articles / sections associated with a navigation node? How are you generating the FUs? Blair On Nov 14, 2007 9:56 AM, tilespace <[EMAIL PROTECTED]> wrote: > > So we still have a problem with our members section. > > Our current process is this: > - Log into the admin > - Click on "Issues" tab > - Choose one of the following: > - Manage Issues > - Manage Sections > - Manage Articles > * All three are custom types with 2 custom rules - > ruleCurrentIssue and ruleIssueArchives > > If we add an issue, the front-end displays properly displaying the > most recent issue when the "Current Issue" is clicked and displaying a > list of all others when "Archived Issues" is clicked. Both of these > work properly in that you have to be logged in to view them. The > current issue only displays the sections that have articles in them. > Each section is a link and each article is a link. When you click on a > section, it should be displaying all articles for that issue (whether > current or archived) and when you click on an article (whether through > the issue display page or through the sections) it should be > displaying the full article. > > But here are the problems that exist: > - when you click on a section or article link, it pulls up the > information without any branding > - if you type in the FU directly, you can access it without having > to log in > - based on a previous reply, I created navigational items for > sections and articles thinking I could create rules that would display > them properly but that doesn't want to work AND now those items are > appearing in the subnav when using the skin:genericNav tag > (by "doesn't want to work" what I mean is that when you go to /go/ > members/sections/ you get an empty page and when you go to /go/members/ > sections/*sectionname* - which is what we really want - you get an > empty) > > I've read the articles by Jake at CFWebTools that were referred to me > and they didn't really apply to my issue (I don't think anyways, > unless I misread them). > > I'm dying here... Does anyone have any suggestions on a better way to > do it? We have to be able to give the data entry people the ability to > add issues, sections and articles at will and have them display > properly on the front-end. Has anyone tackled something similar to > this before? > > *sigh* > > Thanks guys :) > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" 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/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
