// you’re reading...


Debugging inline template scripts inside the RedDot CMS server

Good morning folks. Just a short article on how to get(debug) errors if you are using PreExecutes inside your CMS template (which you have to do to get the HTML result as a published page)

The problem with getting the error

First of all, if you develop something using scripts inside RedDot it’s hard to get errors.. The CMS takes your script code and then processes it and then it just returns the result. If there is an error inside your code it returns what? The error? No, the answer is: nothing.

How to get rid of these?

If you want to develop some script stuff directly on your RedDot CMS server,
(Or if you just have to, because you have to do it directly inside your template..)
then you should enable the “debug” option via flags.
To get behind that use the flags setting in your RDServer.ini as mentioned in my older blog

What’s next?

By now you will be able to:

  • Write code into your template
  • Open the page in CMS
  • Look into your /[RD-Install]/ASP folder and sort the files by date
  • Take the latest preexecute file (if you are developing on a live system this could be tricky, because other users by clicking in the RedDot CMS are producing files too..)
  • Once you found out which file it is you can open this file in a new browser window with:
  • The filename is based on the GUID so it should be unique and wont change, so you only have to find out once per page

Your browser should spit out the nasty little errors if you have some.

Aloha-Contest! Which other flag settings do you know?

The best three entries will get a picture of me in my hawaiian party dress.. hula!

(This post was a reply to a question from the google groups)

Share and Enjoy:
  • Print
  • email
  • Twitter
  • Digg
  • Reddit
  • StumbleUpon
  • Google Bookmarks
  • del.icio.us
  • MisterWong
  • Facebook
  • LinkedIn

No related posts.

About the author:

Markus Giesen Markus Giesen is a Solutions Architect and RedDot CMS Consultant, formerly based in Germany. Travelling around the world to find and offer solutions for a better world (in a very web based meaning). He just found a way to do this as part of a Melbourne based online consultant house. On this blog Markus shares his personal (not his employers) thoughts and opinions on CMS and web development. In his spare time you will find him reading, snowboarding or travelling. Also, you should follow him on Twitter!


5 comments for “Debugging inline template scripts inside the RedDot CMS server”

  1. There’s also a plugin available from Reddot (either the UK community site, or via your local account manager) that does pretty much the same thing, but means you don’t need to go poking around for the right log yourself.

    Posted by Paul Smith | November 27, 2008, 2:48 pm
  2. Oh. I win the photo!! GO ME!

    0 = Navigation manager OFF, Persist Pre-execute scripts OFF

    256 = Navigation Manager OFF, Persist Pre-Execute scripts ON

    1024 = Navigation Manager ON, Persist Pre-Execute scripts OFF

    1280 = Navigation Manager ON, Persist Pre-Execute scripts ON

    this does mean that people need to be aware whether they need to set the flag to 256 or to 1280 though

    Posted by Paul Smith | November 27, 2008, 2:53 pm
  3. Nope, these I already mentioned before in the link above to this page:

    Ok, maybe you’ll get it anyway.. You deserve it for sure ^^

    Posted by Markus Giesen | November 27, 2008, 2:56 pm
  4. ah, so you did. I missed the teeny tiny text. I should learn to read things more carefully!! Nice shirt ;)

    Posted by Paul Smith | November 27, 2008, 4:36 pm
  5. There’s always the USERLIMITS flag in the user import part of RDAccountSystem.xml?

    Posted by Paul Smith | November 27, 2008, 4:54 pm

Post a comment

Stay up to date! - Get notified about followup comments

If you don't feel the urge to comment but wish to stay in the loop:
Just enter your email and subscribe to new comments.

Subscribe without commenting

Recent Tweets

  • RT @AirKraft: Transport Canada breakout: they manage 80K pages and 300K assets with WSM(RedDot). Wow! #OTCW 2010-11-11
  • The RedDot usergroup session 'Future of WCM' is in National Harbor 7, now. See you there! #otcw 2010-11-11
  • RT @yttergren: @AirKraft: Calling all WSM(RedDot) devs: share your solutions on http://bit.ly/bgPIof EVERY solution can win an iPad #OTCW 2010-11-10
  • Come to the Solution Exchange session. Enhance your (#reddot) CMS project! Chesapeake 12, 3:20pm #otcw Looking forward to see you there! 2010-11-10
  • More updates...