Wokflow for dynamically generated page
I have dynamically generated pages that are driven from external database - therefor there are no actual pages. The fields in database are modified through FCKEditor and asp. No standard fields are used or referenced to the database fields. In result of this the pages are not placed in draft status. However I need to have these pages to be submitted to the workflow. Does anyone have any idea how it can be accomplished? --~--~-~--~~~---~--~~ 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
If you weren't opposed to writing positive articles about RedDot, your blog would probably be really great and I'd read it regularly. If you used your real name, it would have a legitimacy to it that your anonymous blog can never have. Adam Boyle On Wed, Nov 19, 2008 at 7:28 PM, Gavin Cope <[EMAIL PROTECTED]> wrote: > I've been reading this post with great interest. Not to discount anything > you've said because they're all valid points but nothing you've said in your > blog is a big secret. Any potential customer that talks to a reference site > will more than likely find about the cons of RedDot. Indeed I know from > experience that we have lost bids to other CMS products due to a customer's > requirements around say usability. So the information is there for any > company that does it's due diligence. On the flip side, other customers > "love" the product and have been using it for years, it meets their needs > and the misgivings of the product are either small enough not to worry about > or there are sufficient work arounds. So in a nutshell, I agree with what > you're saying in your blog in principle. I would also encourage you to keep > writing your blog because the more information gets out there, the more > likely we'll reach a critical mass where a few interested people snowball > into a caring, sharing developer community. I would however also encourage > you to write some articles on what you LIKE about RedDot as well. So without > sounding like a sales person, I think your blog would benefit from a > balanced dicussion because at the end of the day, you're positive and > negative opinions as a customer TO a potential customer mean more than any > sales person's spiel. > > Cheers, > > Gavin > > 2008/11/20 [EMAIL PROTECTED] <[EMAIL PROTECTED]> > > >> I am blogging about some of the negative sides of RedDot to counter >> balance the positives put forward by, among others, the RedDot sales >> team themselves. I would not suggest anyone take either my or their >> comments in isolation. I'm focussing on RedDot because that is the CMS >> I've been forced to work with. I would be utterly astounded if an >> existing RedDot customer read my blog and decided to stop using the >> software purely based on its content. I merely wish to give all the >> relevant information for potential customers, who have no opportunity >> to trial the software themselves, and no other means of evaluating it. >> >> On Nov 19, 8:38 pm, "Adam Boyle" <[EMAIL PROTECTED]> wrote: >> > Blogging exclusively about bugs and flaws isn't helpful to those who >> might >> > be evaluating RedDot. >> > >> > It's not fair to write about only the negative stuff without also >> mentioning >> > some of the positive things that RedDot does too. >> > >> > If you were honestly trying to foster a debate about what features a CMS >> > should have, then why did you name your blog RedDotGripes? >> > >> > Isn't it more honest to say that you created your blog in the hopes that >> it >> > will pursuade current and/or potential RedDot customers against using >> > RedDot? >> > >> > Isn't that the real purpose of your blog? >> > >> > Adam >> > >> > On Wed, Nov 19, 2008 at 2:29 PM, [EMAIL PROTECTED] < >> > >> > [EMAIL PROTECTED]> wrote: >> > >> > > I'm trying to publicise some bugs, design flaws, and usability issues >> > > relating to RedDot, for those who might be evaluating it. I'm trying >> > > to foster debate about what kinds of features a modern day CMS needs >> > > and how they might be implemented. I'm trying to gauge public opinion >> > > - to what extent am I on my own here, and how much do others share my >> > > thoughts? I'm trying to let off some steam. >> > >> > > On Nov 19, 7:15 pm, "Adam Boyle" <[EMAIL PROTECTED]> wrote: >> > > > I don't think you've really answered Morgan's first question. >> > >> > > > You're interested in the comments, but what are you trying to >> achieve >> > > with >> > > > your blog? >> > >> > > > What purpose do you hope the comments generated by your blog will >> serve? >> > >> > > > Adam >> > >> > > > On Wed, Nov 19, 2008 at 2:00 PM, sayno more < >> [EMAIL PROTECTED]> >> > > wrote: >> > > > > 1. I'm interested in the comments, as evidenced - I think - by my >> > > responses >> > > > > to them. I'd like responses to my blog posts which are not "how do >> I do >> > > > > this" type questions, which would obviously not be appropriate in >> a >> > > blog >> > > > > format, by critical evaluations of a piece of software, and its >> design. >> > >> > > > > 2. I'll be interested to see how many of the gripes have been, or >> will >> > > be, >> > > > > addressed. As you point out, some of these gripes are genuine >> flaws of >> > > the >> > > > > software as it stands right now, and will be useful information >> for >> > > those >> > > > > who are considering adopting RedDot for their website. >> > >> > > > > 3. This sounds quite positive, so we'll all wait and see what the >> > > outcome >> > > > > is. >> > >> > > >
Re: File Upload from a form:
If I were to do it, I would add an ASP.NET project to the RedDot project and create the upload functionality in ASP.NET. They have some built-in controls that let you easily upload files and tutorials are available in a lot of places. On Nov 19, 1:49 pm, mave <[EMAIL PROTECTED]> wrote: > Hi, > > Can I upload a file to the Reddot CMS via a webform? If yes can you > please let me know how to do that? > > Thanks, > Mave. --~--~-~--~~~---~--~~ 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
I've been reading this post with great interest. Not to discount anything you've said because they're all valid points but nothing you've said in your blog is a big secret. Any potential customer that talks to a reference site will more than likely find about the cons of RedDot. Indeed I know from experience that we have lost bids to other CMS products due to a customer's requirements around say usability. So the information is there for any company that does it's due diligence. On the flip side, other customers "love" the product and have been using it for years, it meets their needs and the misgivings of the product are either small enough not to worry about or there are sufficient work arounds.So in a nutshell, I agree with what you're saying in your blog in principle. I would also encourage you to keep writing your blog because the more information gets out there, the more likely we'll reach a critical mass where a few interested people snowball into a caring, sharing developer community. I would however also encourage you to write some articles on what you LIKE about RedDot as well. So without sounding like a sales person, I think your blog would benefit from a balanced dicussion because at the end of the day, you're positive and negative opinions as a customer TO a potential customer mean more than any sales person's spiel. Cheers, Gavin 2008/11/20 [EMAIL PROTECTED] <[EMAIL PROTECTED]> > > I am blogging about some of the negative sides of RedDot to counter > balance the positives put forward by, among others, the RedDot sales > team themselves. I would not suggest anyone take either my or their > comments in isolation. I'm focussing on RedDot because that is the CMS > I've been forced to work with. I would be utterly astounded if an > existing RedDot customer read my blog and decided to stop using the > software purely based on its content. I merely wish to give all the > relevant information for potential customers, who have no opportunity > to trial the software themselves, and no other means of evaluating it. > > On Nov 19, 8:38 pm, "Adam Boyle" <[EMAIL PROTECTED]> wrote: > > Blogging exclusively about bugs and flaws isn't helpful to those who > might > > be evaluating RedDot. > > > > It's not fair to write about only the negative stuff without also > mentioning > > some of the positive things that RedDot does too. > > > > If you were honestly trying to foster a debate about what features a CMS > > should have, then why did you name your blog RedDotGripes? > > > > Isn't it more honest to say that you created your blog in the hopes that > it > > will pursuade current and/or potential RedDot customers against using > > RedDot? > > > > Isn't that the real purpose of your blog? > > > > Adam > > > > On Wed, Nov 19, 2008 at 2:29 PM, [EMAIL PROTECTED] < > > > > [EMAIL PROTECTED]> wrote: > > > > > I'm trying to publicise some bugs, design flaws, and usability issues > > > relating to RedDot, for those who might be evaluating it. I'm trying > > > to foster debate about what kinds of features a modern day CMS needs > > > and how they might be implemented. I'm trying to gauge public opinion > > > - to what extent am I on my own here, and how much do others share my > > > thoughts? I'm trying to let off some steam. > > > > > On Nov 19, 7:15 pm, "Adam Boyle" <[EMAIL PROTECTED]> wrote: > > > > I don't think you've really answered Morgan's first question. > > > > > > You're interested in the comments, but what are you trying to achieve > > > with > > > > your blog? > > > > > > What purpose do you hope the comments generated by your blog will > serve? > > > > > > Adam > > > > > > On Wed, Nov 19, 2008 at 2:00 PM, sayno more <[EMAIL PROTECTED] > > > > > wrote: > > > > > 1. I'm interested in the comments, as evidenced - I think - by my > > > responses > > > > > to them. I'd like responses to my blog posts which are not "how do > I do > > > > > this" type questions, which would obviously not be appropriate in a > > > blog > > > > > format, by critical evaluations of a piece of software, and its > design. > > > > > > > 2. I'll be interested to see how many of the gripes have been, or > will > > > be, > > > > > addressed. As you point out, some of these gripes are genuine flaws > of > > > the > > > > > software as it stands right now, and will be useful information for > > > those > > > > > who are considering adopting RedDot for their website. > > > > > > > 3. This sounds quite positive, so we'll all wait and see what the > > > outcome > > > > > is. > > > > > > > 4. I've done just that with a dedicated follow-up post. Thanks. > > > > > > > 2008/11/18 theHam <[EMAIL PROTECTED]> > > > > > > >> 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 s
Re: RedDot gripes
I am blogging about some of the negative sides of RedDot to counter balance the positives put forward by, among others, the RedDot sales team themselves. I would not suggest anyone take either my or their comments in isolation. I'm focussing on RedDot because that is the CMS I've been forced to work with. I would be utterly astounded if an existing RedDot customer read my blog and decided to stop using the software purely based on its content. I merely wish to give all the relevant information for potential customers, who have no opportunity to trial the software themselves, and no other means of evaluating it. On Nov 19, 8:38 pm, "Adam Boyle" <[EMAIL PROTECTED]> wrote: > Blogging exclusively about bugs and flaws isn't helpful to those who might > be evaluating RedDot. > > It's not fair to write about only the negative stuff without also mentioning > some of the positive things that RedDot does too. > > If you were honestly trying to foster a debate about what features a CMS > should have, then why did you name your blog RedDotGripes? > > Isn't it more honest to say that you created your blog in the hopes that it > will pursuade current and/or potential RedDot customers against using > RedDot? > > Isn't that the real purpose of your blog? > > Adam > > On Wed, Nov 19, 2008 at 2:29 PM, [EMAIL PROTECTED] < > > [EMAIL PROTECTED]> wrote: > > > I'm trying to publicise some bugs, design flaws, and usability issues > > relating to RedDot, for those who might be evaluating it. I'm trying > > to foster debate about what kinds of features a modern day CMS needs > > and how they might be implemented. I'm trying to gauge public opinion > > - to what extent am I on my own here, and how much do others share my > > thoughts? I'm trying to let off some steam. > > > On Nov 19, 7:15 pm, "Adam Boyle" <[EMAIL PROTECTED]> wrote: > > > I don't think you've really answered Morgan's first question. > > > > You're interested in the comments, but what are you trying to achieve > > with > > > your blog? > > > > What purpose do you hope the comments generated by your blog will serve? > > > > Adam > > > > On Wed, Nov 19, 2008 at 2:00 PM, sayno more <[EMAIL PROTECTED]> > > wrote: > > > > 1. I'm interested in the comments, as evidenced - I think - by my > > responses > > > > to them. I'd like responses to my blog posts which are not "how do I do > > > > this" type questions, which would obviously not be appropriate in a > > blog > > > > format, by critical evaluations of a piece of software, and its design. > > > > > 2. I'll be interested to see how many of the gripes have been, or will > > be, > > > > addressed. As you point out, some of these gripes are genuine flaws of > > the > > > > software as it stands right now, and will be useful information for > > those > > > > who are considering adopting RedDot for their website. > > > > > 3. This sounds quite positive, so we'll all wait and see what the > > outcome > > > > is. > > > > > 4. I've done just that with a dedicated follow-up post. Thanks. > > > > > 2008/11/18 theHam <[EMAIL PROTECTED]> > > > > >> 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 reg
File Upload from a form:
Hi, Can I upload a file to the Reddot CMS via a webform? If yes can you please let me know how to do that? Thanks, Mave. --~--~-~--~~~---~--~~ 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: option list basic question
Hi, an option list is just a kind of placeholder and It does what its name means. You can edit different values, hide and show for your example. Anthony On 19 nov, 15:30, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > When someone says "create an option list" how do I do that? For > instance I am trying to implement > this:http://blog.markusgiesen.de/2008/07/27/playing-peek-a-boo-hiding-page... > > but my option list isn't working. What would an option list look like > for this? > > thanks for helping > > James --~--~-~--~~~---~--~~ 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
by the way: I like it that we discuss it here, that shows, that there is a need for discussions :) On 19 Nov., 20:29, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I'm trying to publicise some bugs, design flaws, and usability issues > relating to RedDot, for those who might be evaluating it. I'm trying > to foster debate about what kinds of features a modern day CMS needs > and how they might be implemented. I'm trying to gauge public opinion > - to what extent am I on my own here, and how much do others share my > thoughts? I'm trying to let off some steam. > > On Nov 19, 7:15 pm, "Adam Boyle" <[EMAIL PROTECTED]> wrote: > > > I don't think you've really answered Morgan's first question. > > > You're interested in the comments, but what are you trying to achieve with > > your blog? > > > What purpose do you hope the comments generated by your blog will serve? > > > Adam > > > On Wed, Nov 19, 2008 at 2:00 PM, sayno more <[EMAIL PROTECTED]> wrote: > > > 1. I'm interested in the comments, as evidenced - I think - by my > > > responses > > > to them. I'd like responses to my blog posts which are not "how do I do > > > this" type questions, which would obviously not be appropriate in a blog > > > format, by critical evaluations of a piece of software, and its design. > > > > 2. I'll be interested to see how many of the gripes have been, or will be, > > > addressed. As you point out, some of these gripes are genuine flaws of the > > > software as it stands right now, and will be useful information for those > > > who are considering adopting RedDot for their website. > > > > 3. This sounds quite positive, so we'll all wait and see what the outcome > > > is. > > > > 4. I've done just that with a dedicated follow-up post. Thanks. > > > > 2008/11/18 theHam <[EMAIL PROTECTED]> > > > >> 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,
Re: RedDot gripes
I work with RedDot since 2001/2002. And it definetly was state of the art at this time. I can agree that there are a lot of open source CMS out there, like TYPO3 which back in the days was not that good but since now made some great efforts. But still I'm ore than sure, that RedDot has it's place in the enterprise cms world. The bugs and how they manage them is definetly something to discuss, but I think another blog which only figures out the negative sites or maybe negative ones is the wrong platform. Better publish some articles in a forum, I think even the google group is not the final solution for reddot related information. On 19 Nov., 20:29, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I'm trying to publicise some bugs, design flaws, and usability issues > relating to RedDot, for those who might be evaluating it. I'm trying > to foster debate about what kinds of features a modern day CMS needs > and how they might be implemented. I'm trying to gauge public opinion > - to what extent am I on my own here, and how much do others share my > thoughts? I'm trying to let off some steam. > > On Nov 19, 7:15 pm, "Adam Boyle" <[EMAIL PROTECTED]> wrote: > > > I don't think you've really answered Morgan's first question. > > > You're interested in the comments, but what are you trying to achieve with > > your blog? > > > What purpose do you hope the comments generated by your blog will serve? > > > Adam > > > On Wed, Nov 19, 2008 at 2:00 PM, sayno more <[EMAIL PROTECTED]> wrote: > > > 1. I'm interested in the comments, as evidenced - I think - by my > > > responses > > > to them. I'd like responses to my blog posts which are not "how do I do > > > this" type questions, which would obviously not be appropriate in a blog > > > format, by critical evaluations of a piece of software, and its design. > > > > 2. I'll be interested to see how many of the gripes have been, or will be, > > > addressed. As you point out, some of these gripes are genuine flaws of the > > > software as it stands right now, and will be useful information for those > > > who are considering adopting RedDot for their website. > > > > 3. This sounds quite positive, so we'll all wait and see what the outcome > > > is. > > > > 4. I've done just that with a dedicated follow-up post. Thanks. > > > > 2008/11/18 theHam <[EMAIL PROTECTED]> > > > >> 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, m
Re: RedDot gripes
Blogging exclusively about bugs and flaws isn't helpful to those who might be evaluating RedDot. It's not fair to write about only the negative stuff without also mentioning some of the positive things that RedDot does too. If you were honestly trying to foster a debate about what features a CMS should have, then why did you name your blog RedDotGripes? Isn't it more honest to say that you created your blog in the hopes that it will pursuade current and/or potential RedDot customers against using RedDot? Isn't that the real purpose of your blog? Adam On Wed, Nov 19, 2008 at 2:29 PM, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > > I'm trying to publicise some bugs, design flaws, and usability issues > relating to RedDot, for those who might be evaluating it. I'm trying > to foster debate about what kinds of features a modern day CMS needs > and how they might be implemented. I'm trying to gauge public opinion > - to what extent am I on my own here, and how much do others share my > thoughts? I'm trying to let off some steam. > > On Nov 19, 7:15 pm, "Adam Boyle" <[EMAIL PROTECTED]> wrote: > > I don't think you've really answered Morgan's first question. > > > > You're interested in the comments, but what are you trying to achieve > with > > your blog? > > > > What purpose do you hope the comments generated by your blog will serve? > > > > Adam > > > > On Wed, Nov 19, 2008 at 2:00 PM, sayno more <[EMAIL PROTECTED]> > wrote: > > > 1. I'm interested in the comments, as evidenced - I think - by my > responses > > > to them. I'd like responses to my blog posts which are not "how do I do > > > this" type questions, which would obviously not be appropriate in a > blog > > > format, by critical evaluations of a piece of software, and its design. > > > > > 2. I'll be interested to see how many of the gripes have been, or will > be, > > > addressed. As you point out, some of these gripes are genuine flaws of > the > > > software as it stands right now, and will be useful information for > those > > > who are considering adopting RedDot for their website. > > > > > 3. This sounds quite positive, so we'll all wait and see what the > outcome > > > is. > > > > > 4. I've done just that with a dedicated follow-up post. Thanks. > > > > > 2008/11/18 theHam <[EMAIL PROTECTED]> > > > > >> 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
option list basic question
When someone says "create an option list" how do I do that? For instance I am trying to implement this: http://blog.markusgiesen.de/2008/07/27/playing-peek-a-boo-hiding-pages-with-the-navigation-manager/#comment-1925 but my option list isn't working. What would an option list look like for this? thanks for helping James --~--~-~--~~~---~--~~ 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: 'Last 5 updates' component
Hi Brett, I think you need to use RQL to do it. A page search with today's modified pages as argument seems enough, just sort your results by modified date then display the five first result. Don't forget to convert the date, RedDot encodes it. You will find all you need in RQL documentation, It is on redDot community website. Anthony On 19 nov, 06:47, Brett <[EMAIL PROTECTED]> wrote: > Hi All, > > Is there a publicly available component that shows the last 5 updated > pages in RedDot? We are only using the CMS at the minute and aren't > using LiveServer until Feb '09. > > Thanks, > Brett --~--~-~--~~~---~--~~ 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
I'm trying to publicise some bugs, design flaws, and usability issues relating to RedDot, for those who might be evaluating it. I'm trying to foster debate about what kinds of features a modern day CMS needs and how they might be implemented. I'm trying to gauge public opinion - to what extent am I on my own here, and how much do others share my thoughts? I'm trying to let off some steam. On Nov 19, 7:15 pm, "Adam Boyle" <[EMAIL PROTECTED]> wrote: > I don't think you've really answered Morgan's first question. > > You're interested in the comments, but what are you trying to achieve with > your blog? > > What purpose do you hope the comments generated by your blog will serve? > > Adam > > On Wed, Nov 19, 2008 at 2:00 PM, sayno more <[EMAIL PROTECTED]> wrote: > > 1. I'm interested in the comments, as evidenced - I think - by my responses > > to them. I'd like responses to my blog posts which are not "how do I do > > this" type questions, which would obviously not be appropriate in a blog > > format, by critical evaluations of a piece of software, and its design. > > > 2. I'll be interested to see how many of the gripes have been, or will be, > > addressed. As you point out, some of these gripes are genuine flaws of the > > software as it stands right now, and will be useful information for those > > who are considering adopting RedDot for their website. > > > 3. This sounds quite positive, so we'll all wait and see what the outcome > > is. > > > 4. I've done just that with a dedicated follow-up post. Thanks. > > > 2008/11/18 theHam <[EMAIL PROTECTED]> > > >> 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 top
Re: RedDot gripes
I don't think you've really answered Morgan's first question. You're interested in the comments, but what are you trying to achieve with your blog? What purpose do you hope the comments generated by your blog will serve? Adam On Wed, Nov 19, 2008 at 2:00 PM, sayno more <[EMAIL PROTECTED]> wrote: > 1. I'm interested in the comments, as evidenced - I think - by my responses > to them. I'd like responses to my blog posts which are not "how do I do > this" type questions, which would obviously not be appropriate in a blog > format, by critical evaluations of a piece of software, and its design. > > 2. I'll be interested to see how many of the gripes have been, or will be, > addressed. As you point out, some of these gripes are genuine flaws of the > software as it stands right now, and will be useful information for those > who are considering adopting RedDot for their website. > > 3. This sounds quite positive, so we'll all wait and see what the outcome > is. > > 4. I've done just that with a dedicated follow-up post. Thanks. > > 2008/11/18 theHam <[EMAIL PROTECTED]> > > >> 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
Re: RedDot gripes
1. I'm interested in the comments, as evidenced - I think - by my responses to them. I'd like responses to my blog posts which are not "how do I do this" type questions, which would obviously not be appropriate in a blog format, by critical evaluations of a piece of software, and its design. 2. I'll be interested to see how many of the gripes have been, or will be, addressed. As you point out, some of these gripes are genuine flaws of the software as it stands right now, and will be useful information for those who are considering adopting RedDot for their website. 3. This sounds quite positive, so we'll all wait and see what the outcome is. 4. I've done just that with a dedicated follow-up post. Thanks. 2008/11/18 theHam <[EMAIL PROTECTED]> > > 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
Re: Pagination of list items...
P.S. There's potential for the list (of several hundred items) to include an image per item, so the javascript method is not really appropriate. Although I could do some dynamic image loading based on which items are actually showing, I guess. But those without JS would not see the images, and I'm not sure that's good enough. On Nov 19, 3:59 pm, bobbykjack <[EMAIL PROTECTED]> wrote: > Yup, I too have had to resort to a complex combination of RedDot + > PHP, but it's just about working. I have a RedDot page that contains a > list of other pages (the items in the final list). Certain data is > transferred from each item into the top-level page. The top-level page > is then published as a PHP file containing all that data in an array. > A separate PHP page includes the first, then manipulates the data as > it sees fit. > > Would be a lot easier and a LOT cleaner with a standard PHP/database > setup, so I'm weighing up options to decouple it from RedDot. > > - Bobby > > On Nov 19, 11:12 am, abdn_webteam <[EMAIL PROTECTED]> wrote: > > > Just a quick note to say we tried this method and it worked fine, > > though we baulked at the idea of having a thousand news stories > > rendered on one page. We therefore tried an alternative method of > > combining PHP comment tags and conditional statements to simply > > discard the unshown pages, and created a multi-pass to show the next/ > > previous pages. Works well, with little overhead. > > --~--~-~--~~~---~--~~ 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: Pagination of list items...
Yup, I too have had to resort to a complex combination of RedDot + PHP, but it's just about working. I have a RedDot page that contains a list of other pages (the items in the final list). Certain data is transferred from each item into the top-level page. The top-level page is then published as a PHP file containing all that data in an array. A separate PHP page includes the first, then manipulates the data as it sees fit. Would be a lot easier and a LOT cleaner with a standard PHP/database setup, so I'm weighing up options to decouple it from RedDot. - Bobby On Nov 19, 11:12 am, abdn_webteam <[EMAIL PROTECTED]> wrote: > Just a quick note to say we tried this method and it worked fine, > though we baulked at the idea of having a thousand news stories > rendered on one page. We therefore tried an alternative method of > combining PHP comment tags and conditional statements to simply > discard the unshown pages, and created a multi-pass to show the next/ > previous pages. Works well, with little overhead. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
just click view the add earn $6800 per month
just click view the add earn $6800 per month other details log on to » You click 12 ads per day = $60 » 20 referrals click 12 ads per day = $240 » Your daily earnings = $240 » Your weekly earnings = $1680 » Your monthly earnings = $6800 http://www.bux2ads.com/adsplus/?r=subuu http://www.bux2ads.com/adsplus/?r=subuu http://www.bux2ads.com/adsplus/?r=subuu *** --~--~-~--~~~---~--~~ 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: The 'create' part of Create and Connect Page...
Hey The only way to do this would be to create an RQL plugin that strings together the relevant instructions. It's something we've wanted to do here, but havn't had the time to piece together. Paul -Original Message- From: RedDot-CMS-Users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of abdn_webteam Sent: Wed, November 19,2008 11:17 To: RedDot CMS Users Subject: The 'create' part of Create and Connect Page... It bugs us that the 'creation' of a page is a two-step process: give the page a headline, then select the page and edit its placeholder elements. Is there a method for joining these two steps together, so when a user clicks 'Create and Connect Page' they are automatically taken to the 'Edit Elements via Form' interface? UCB Celltech is the UK branch of UCB Pharma S.A., a company registered in Belgium with registered offices at Allee de la Recherche 60, 1070 Brussels, Belgium, KBO/BCE nr. 0403.096.168, RPR/RPM Brussels. UCB Celltech's UK branch registration number is BR009137 and its UK representative office is at 208 Bath Road, Slough, Berkshire SL1 3WE. Legal Notice: This electronic mail and its attachments are intended solely for the person(s) to whom they are addressed and contain information which is confidential or otherwise protected from disclosure, except for the purpose for which they are intended. Dissemination, distribution, or reproduction by anyone other than the intended recipients is prohibited and may be illegal. If you are not an intended recipient, please immediately inform the sender and return the electronic mail and its attachments and destroy any copies which may be in your possession. UCB screens electronic mails for viruses but does not warrant that this electronic mail is free of any viruses. UCB accepts no liability for any damage caused by any virus transmitted by this electronic mail. (Ref: #*CUK0308) --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
'Last 5 updates' component
Hi All, Is there a publicly available component that shows the last 5 updated pages in RedDot? We are only using the CMS at the minute and aren't using LiveServer until Feb '09. Thanks, Brett --~--~-~--~~~---~--~~ 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: Set page not to publish
Thanks! On Nov 17, 6:29 pm, RedDot in Toronto <[EMAIL PROTECTED]> wrote: > You can do it at the template level... Content Class (you don't want > to publish) -> Tempates -> Assign Project Variants... be careful with > this feature, one of the problems I've experienced in the past is if > it is directly connected to a page that you do want to publish it can > cause publication weirdness. > > On Nov 17, 11:07 am, Brett <[EMAIL PROTECTED]> wrote: > > > Can anyone refresh my memory of how not to publish a page? > > > Thanks, > > Brett --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
The 'create' part of Create and Connect Page...
It bugs us that the 'creation' of a page is a two-step process: give the page a headline, then select the page and edit its placeholder elements. Is there a method for joining these two steps together, so when a user clicks 'Create and Connect Page' they are automatically taken to the 'Edit Elements via Form' interface? --~--~-~--~~~---~--~~ 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: Pagination of list items...
Just a quick note to say we tried this method and it worked fine, though we baulked at the idea of having a thousand news stories rendered on one page. We therefore tried an alternative method of combining PHP comment tags and conditional statements to simply discard the unshown pages, and created a multi-pass to show the next/ previous pages. Works well, with little overhead. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Database Content placeholders and forms in RedDot CMS
Hi, I'm looking at creating forms to update a database table using RedDot CMS, and I've fallen at the first hurdle. In my first form, I happen to want to write the values "1", "2" and "3" to the database but display the labels "Not important", "Quite important" and "Very important" respectively. The textbook approach is to reference a Standard Text Field (which has a red dot) to a Database Content placeholder (which is bound to a database column). I would like to reference an Option List placeholder to the Database Content placeholder but RedDot does not allow me to do this (Selected element(s) in clipboard are not valid for this action). So is this do-able? Using ASP? Using ASP+RQL? (No doubt on other occasions I'll want to have checkboxes, radio buttons, etc etc. Clearly input validation will be non-trivial too) Really my question is bigger - can I create robust and usable database editing forms in RedDot, or am I better off moving it out of RedDot and into a tried-and-tested web development technology? thanks, Jonathan --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
