I don't think that will be possible by tricking the CMS. If your requirement gets a little more complex than edit via form, I suggest you create your own ASP page with all the elements on it, and use a combination of ASP, Javascript, and RQL to save all the values that you need. It should not be a difficult thing to do.
On Dec 23, 7:20 pm, "[email protected]" <[email protected]> wrote: > Cool, I will try this, also just as we can fill in the content > elements using Edit elements via form, can we manage to do the same > for Structural elements on a page, I want to have a single form from > which content editors populate all the content. One form for all > elements, anyone did such a thing, is it possible? > > On Dec 23, 3:02 pm, bushland25 <[email protected]> wrote: > > > > > I would suggest not routing toeditviaform. To do so, you have to > > set a session variable that is the page guid. Once you do that, RedDot > > gets a little confused if you try toeditelements on the existing > > page (not the page you editedviaform) and you could cause some > > issues. Of course, if you manage it correctly, it should be fine. Here > > is what I used: > > > I had an ASP file created with the following that just opens up a > > window for editingviaform. > > > Session("EditPageGuid") = Request("editpageguid") > > %> > > <script> > > window.open('/CMS/ioRDLevel1.asp? > > Action=GetElementsPageFormData&CalledFromRedDot=1&DummyRefreshTime=1226367506390', > > 'LaunchViaForm', 'width=650,height=550'); > > </script> > > <% > > > To set the page guid, I had this in my content class (the page from > > which I wanted to launcheditviaformwithout going to the following > > page). > > > <a href="javascript:window.open('/CMS/Plugins/ExecuteRQL.asp? > > action=LaunchViaForm&editpageguid=<%info_pageguid%>', 'LaunchViaForm', > > 'width=650,height=550');void(0);">[editviaform]</a> > > > Hope that helps! > > > On Dec 23, 7:36 am, "Henry Lu, Sun Certified Java Programmer" > > > <[email protected]> wrote: > > > With simple RQL, you can automate the process of creating and connecting > > > the > > > page to a structural element on another page and route the editor to the > > > newly created page with its status opened. > > > > I have not done routing the editor to the "EditElementviaAForm" and I > > > would think it is doable. > > > > Henry Lu > > > > On Tue, Dec 23, 2008 at 10:14 AM, [email protected] > > > <[email protected] > > > > > wrote: > > > > > Hey, I am wondering if you guys figured this out, I want to use this > > > > in my project. Any help is great. > > > > > On Nov 19, 6:16 am, abdn_webteam <[email protected]> wrote: > > > > > It bugs us that the 'creation' of a page is a two-step process: give > > > > > the page a headline, then select the page andeditits > > > > > placeholderelements. > > > > > > 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 > > > > > 'EditElementsviaForm' interface?- 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 "RedDot CMS Users" 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/RedDot-CMS-Users?hl=en -~----------~----~----~----~------~----~------~--~---
