Re: How do I hide Master Pages in Nav Manager?

2008-11-18 Thread Tiffany

To be honest, I used the nav manager because my editors could visual
the tree structure better in the system. For their Knowledge Base
sometimes Articles would be grouped in multi-level Categories.
Sometimes they wouldn't. And adding pages to the nav manager made the
process easier for them to understand.
However I think the inability to limit content classes is a bigger
problem.
Thank you for your helpful suggestions.


On Nov 17, 1:22 pm, El Pollo Loco [EMAIL PROTECTED] wrote:
 Unfortunately, this is not possible. Nav Mgr does not seem to pay
 attention to content class preassignments. All you can do is to not
 use Nav Mgr to create pages, and instead use the regular multilink
 reddot for your list and create pages with that. Generally speaking, I
 dont think that your editors need to access and or edit the navigation
 structure from with nav mgr.Is there a specific reason why they
 need to use Nav Mgr to create pages?

 I guess you could hack the Nav Mgr Create Page dialog and use RQL to
 get the content classes and page definitions that are preassigned, to
 then filter out the non-preassigned content classes from the choices
 of content classes for creating a page in the Nav Mgr

 On Nov 17, 12:49 pm, Tiffany [EMAIL PROTECTED] wrote:

  Thanks for the link but it's not exactly what I'm looking for. This
  article is  about hiding pages from the structure.
  I want to hide certain templates I know they won't need when users
  create a new page. (not hide after the page is created)
  Any advice?

  On Nov 17, 10:50 am, El Pollo Loco [EMAIL PROTECTED] wrote:

  http://blog.markusgiesen.de/2008/07/27/playing-peek-a-boo-hiding-page...

   On Nov 17, 10:17 am, Tiffany [EMAIL PROTECTED] wrote:

My editors use the nav manager to add new pages. When they create a
new page, how do I only show the content classes that are relevant to
their part of the project?

Thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
RedDot CMS Users group.
To post to this group, send email to RedDot-CMS-Users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/RedDot-CMS-Users?hl=en
-~--~~~~--~~--~--~---



Re: RedDot gripes

2008-11-18 Thread theHam

Hey [EMAIL PROTECTED],

1. to clarify what you are trying to achieve with these blog posts,
are you attempting to get some assistance and/or information with the
issues you are describing? I think from the amount of people that have
contributed to this post already that it should be demonstrated that
there are people here looking to help you if you want it. Or from the
sounds of your comment I cannot see how I could possibly get a
positive outcome from this software, given the flaws that, IMO, are
pretty fundamental have you made a decision and will not be
interested in the comments from people here? If you could let everyone
be aware of your position i think it will help the more passionate
people here and hopefully stop this becoming an unproductive flame war
(as these things types of threads tend to become)

2. I would love it if the RedDot engineers took some notice of these
comments. RedDot have taken notice of these comments. The next
version of  reddot coming out will be addressing your gripe #1 as the
text editor is being replaced. Gripe #2 is being addressed (i believe
around may next year) with a cms frontend rewrite based on usability
fundamentals. Yes these have not been released yet and do not address
your issues right now but based on my previous comment other gripes
like the ones you have been mentioned have in the past been
progressively acknowledged and addressed - there is hope.

3. You asked earlier whether reddot would charge for upgrades, I'm
unaware of what region you are from but from ours if you are up to
date with your software support and maintenance upgrades are generally
provided under those costs (N.B. this may be different region to
region)

4. I posted in the comments a reference to this link. If possible
could you directly edit your post to refer to this discussion? If
people do not view the comments of the post they may miss the link.

Cheers,

 - Morgan

On Nov 19, 1:01 am, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
 Thanks for the thoughtful comments, theham. I'll be dealing with a
 lot of what you say later on, but - in the meantime:

 all software is frustrating and flawed - I think this is either not
 the case, or an awful indictment of our craft if it is. I personally
 make regular use of software that is neither flawed nor frustrating;
 as I alluded to earlier, maybe that should be rephrased as all
 complex software is frustrating and flawed. I take the point, of
 course, that RedDot is not the only culprit.

 If you can please update your blog post - you beat me to it -
 thanks :)

 Why not try and get a positive outcome from your currently negative
 experience? - of course, that would be ideal. I guess I'm feeling
 pessimistic at the moment - I cannot see how I could possibly get a
 positive outcome from this software, given the flaws that, IMO, are
 pretty fundamental. So far, I've just dealt with the text editor
 creating invalid markup. As someone who has, over the last couple of
 years, really embraced web standards and clean, semantic markup, this
 DOES feel like a MASSIVE deal. However, there are other topics I'll be
 discussing which, I believe, will be more significant to some of you
 (gripe #2 - just posted - probably doesn't fall under this category,
 unfortunately). I'm talking core aspects of the RedDot CMS model which
 I consider flawed. I would love it if the RedDot engineers took some
 notice of these comments. I would also love it if an alternative CMS
 (preferably open source) could be suggested, or developed if there
 really is a gap in the market.

 On Nov 18, 11:19 am, theHam [EMAIL PROTECTED] wrote:

  Hey [EMAIL PROTECTED],

  I understand your pain and frustration. I'm a 3 y.o reddoter with a
  love/hate relationship with the wonderful world of reddot. I try to
  make sure that my clients never have to experience the hate and i deep
  down love the challenge. One thing i have noticed is that the biggest
  gripes i have with the product have been resolved progressively
  through the years.

  1. Complex workaround asp driven navigation has been replaced by (imo)
  a much flexible approach with navman
  2. user syncronisation has been significantly improved with the user
  sync templates
  3. page definitions which has simplified and sped up the building out
  of content

  A soon to be resolved issue on my gripe list will be the text editor
  which is to be replaced by the telerik asp.net/ajax driven text editor
  (i heard this month but could be wrong). Though we also have had
  success with the ephox text editor and will be sad to see it go.

  As a few people mentioned all software is frustrating and flawed.. a
  good example of this is that reddot will do things significantly
  better than other product and significantly worse than others. If
  reddot themselves don't move fast enough to bridge the gap that is
  where people on this group and consultants can assist.

  A couple of things i think a lot of people on this group would