Hi Dave, Since version 9, when a crazy man name Adam C. demonstrated the idea, Eric K. finalized the idea with JQuery.
It is now the best practice in any new plugins. Advantages you asked? 1. No more run away ASP processes. This happens when invoking an ASP and then closing it, but the process still runs on the server. 2. CMS runs fast for everyone because instead of running everything server side, the processing is now client side, with their beefy dual cores. 3. Debugging javascript is 10x easier then debugging server side code in CMS. 4. RQLs runs at least 2x as fast. For short term: 1. Copy all the preexecution code into an ASP file and place it in the plugins folder 2. Using Jquery, on document.ready, call the ASP file. For long term: 1. Please see plugin at http://www.solutionexchange.info/RQLConsole.htm for implementation details -Jian On Jan 7, 10:30 am, Dave R <[email protected]> wrote: > Holy CRAP!!! > > Since when have we been able to use AJAX for RQL rather that ASP? That > was never in any of our trainings since version 5.5. This would change > a LOT. > > The main reason why I'm looking at this is that we are using RQL to > preset various values and relationships that need to be set across > entire subsections of sites within the same project. So we're > transferring content from standard fields and referencing containers > and anchors. > > The main problem we're having is triggering these scripts. Right now, > we're having to do it on page open in smartedit. Obviously, this is > annoying for those who don't typically use smartedit and confusing for > those who only use it. > > With the AJAX solution here, we could just have these scripts run > every time the page loads and it should be much faster (I would > think). We'd still be able to set a flag so these scripts run only the > first time too.. > > Anyway, thanks for pointing this out. Do you have any docs you could > point me to on converting from asp execution to AJAX? I'm just > wondering how much work the conversion would be. > > Also, is there any flaw to this given what I've described? > > David R > > On Jan 6, 3:34 pm, "Killingsworth, Chad A" > > <[email protected]> wrote: > > Pre-execution and RQL don't normally go together. During the pre-execution > > phase, you don't have access to session key or login guid information. > > You'll be required to log in a dummy account, make your change, and then > > log them back out . It's not pretty. > > > Instead, you might consider running an ajax style call, set the value, then > > reload the page if the value was changed. We've found this strategy to be > > much more robust. > > > Chad Killingsworth > > Assistant Director of Web & New Media > > Missouri State University > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of Dave R > > Sent: Thursday, January 06, 2011 11:24 AM > > To: RedDot CMS Users > > Subject: Using Asp/RQL to set content of a Standard Field > > > Hey, > > I've got a standard field that I want to change the content of when a > > pre-execute script runs. What is the easiest way to do that? > > > Example: Prior to the pre-exec script stf_name contains no content. > > After the pre-exec, stf_name should contain "Set". > > > -- > > 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 > > athttp://groups.google.com/group/reddot-cms-users?hl=en. -- 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.
