No problem. We all understand about those kinds of days. :) Blair
On Nov 15, 2007 4:04 AM, tilespace <[EMAIL PROTECTED]> wrote: > > Thanks Blair... And let me say that if I came across badly in ANY way, > I sincerely apologize. Yesterday was just a bad day for us here since > our supervisor wasn't impressed by what we've done so far and was > coming down on us. If any of his frustration came out through me, > again I apologize. I greatly appreciate everything you (and everyone > else) has done and all of the advice you have given! > > My biggest issue I think is that I'm stuck in Fusebox mode (along with > PHP and Classic ASP and .NET and blah blah blah) so trying to wrap my > head around how FC does things in our imposed slightly rushed paced is > befuddling me. I need to just stop and take a step back and do a > better job at absorbing all of this lol... > > Anyways, thank you again! > > On Nov 13, 5:09 pm, "Blair McKenzie" <[EMAIL PROTECTED]> wrote: > > No, I would use individual pages for articles. > > > > WRT anchors ... I suspect buildlink doesn't support it. If you're > > comfortable adding it to buildlink yourself, make the change then submit > the > > file to the bug > > tracker<http://bugs.farcrycms.org:8080/secure/Dashboard.jspa>as an > > improvement. An alternative would be to use buildlink like this: > > <a href="<skin:buildlink urlonly="true" ... />#youranchor">stuff</a> > > > > Blair > > > > On Nov 14, 2007 11:58 AM, tilespace <[EMAIL PROTECTED]> > wrote: > > > > > > > > > > > > > Ignore that last post... I know that's not how stParameters is set up. > > > I meant to say xCode... > > > > > On Nov 13, 4:17 pm, tilespace < [EMAIL PROTECTED]> wrote: > > > > Ok so I'm cheating and throwing the issue objectid into a session > > > > variable and then using the session variable when retrieving > articles. > > > > Hopefully that works for all situations :/ > > > > > > So I guess I'm down to getting the breadcrumb working (it's just > > > > displaying home | home | sectionname no matter what I put in for > > > > parentnode) and requiring a login to view the sections/articles. > > > > > > I might wind up not using the breadcrumb feature of FC for this and > > > > just create a custom hack for the members section... I don't know > yet. > > > > It seems it might be easier to just create a "members" folder in the > > > > www directory and then create a couple of FB cfc's to handle > > > > everything that has to do with the members section but I really > don't > > > > want to scrap everything I've been doing the past week or two :/ > Argh > > > > I say, Argh. > > > > > > On Nov 13, 3:52 pm, tilespace <[EMAIL PROTECTED]> wrote: > > > > > > > ARGH! lol > > > > > Ok, so I'm *this* much closer to making it work but it feels like > I'm > > > > > trying to force a square wooden peg into a metal pipe. > > > > > > > I can get the appropriate section to display within the header/ > > > > > primarynav/footer includes now. I created a rule for the sections > and > > > > > added displayType to it. I have it retrieving all articles > assigned to > > > > > that particular section. All of that seems to work. I then > realized I > > > > > need to only display the articles that are associated with that > > > > > particular issue so I assign the issue objectid to a new navid > struct, > > > > > pass it into the skin:buildLink stParameters parameter and Voila! > I'm > > > > > locked out. It logs me out automatically and I can't login to the > > > > > front-end with any username/password combination (admin, > subscriber, > > > > > anything). I log back into the admin with my username/password, I > > > > > remove ALL security/permissions for the members directory, I open > the > > > > > front-end back up, go to the current issue, click on the section > name > > > > > (with the navid in it) and Voila! Locked out. I take the > stParameters > > > > > parameter out of skin:buildLink and it goes through without a > problem > > > > > and lists all articles for that section instead of just that > issue's > > > > > articles. > > > > > > > Friggin' fraggin'. > > > > > > > Blair - these aren't full page webskins, they're custom types that > > > > > *should* be using displayPageStandard.cfm like all of the other > custom > > > > > types we have. Or so I thought (???). > > > > > > > I understand about the navigation having the access restrictions. > I > > > > > guess my question is how do I assign custom types to a particular > > > > > navigation item (in this case "Members") when they need to be > dynamic > > > > > and controlled by the data entry people and not its' own > navigation > > > > > item? For example we shouldn't have to create a "Section A" > navigation > > > > > item when we create the "Section A" item when using the "Sections" > > > > > type. You see what I mean? > > > > > > > That's been my question I thought - how do I associate > > > issues/sections/ > > > > > articles to the Members section? The FUs are generated when I > "rebuild > > > > > friendly urls" but based on a suggestion in a previous post, I've > gone > > > > > > > in and hardcoded them so that they have "members/" in the url. So > > > > > instead of being /go/sections/sectionname they are now > /go/members/ > > > > > sections/sectionname. Which really still isn't correct since it > should > > > > > > > be /go/members/issuename/sectionname but it'll do if I can get it > > > > > working. > > > > > > > On Nov 13, 3:26 pm, "Blair McKenzie" <[EMAIL PROTECTED] > wrote: > > > > > > > > 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 :)- Hide quoted text - > > > > > > > > - Show quoted text -- Hide quoted text - > > > > > > > - Show quoted text -- Hide quoted text - > > > > > > - Show quoted text -- Hide quoted text - > > > > - Show quoted text - > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
