Override features doesn't work!!!!

I come from the good ol' days of Builder and not at all comfortable in the new world of CSIDE. What should I do to make override work in CSIDE other than orphaning and editing the script in your own ospace? What am I missing? I assume there is no step-by-step guide which guides you on how to do so. Pleaseeee help.

Find more posts tagged with

Comments

David Templeton

What do you want to override? In CSIDE if you have an object that you orphaned and want to override there is a menu item to list the features and scripts. In your object, Source -> Override features.

Shruti_Mishra

Hi David,

Thanks for your reply.

I am trying to override the WebLingo::WebScript RunFileWithArglist() script. I did the above steps but still the control is going to the original core script. Is there anything else that I need to do as well?

Thanks,

Shruti

David Templeton

Ok, huge red flags now appear 😊 Why do you need to override RunFileWithArglist?

Shruti_Mishra

Here is a small snippet that I need to add to the RunFileWithArglist():

*********************************************

Dynamic newFile
if ($Kernel.OSpaceUtils.IsOSpace('htmlmap'))
   newFile = $HTMLMap.HTMLMaps.( srcfile )
elseif ($Kernel.OSpaceUtils.IsOSpace('customizationsrt'))
   newFile = $CustomizationsRT.HTMLMaps.( srcfile )
else
   newFile = $MyCustomModule.HTMLMaps.( srcfile )
end

if IsDefined( newFile )
srcFile = newFile
end

*********************************************

As you can clearly understand from here, I am trying to replace the Core WebLingo file with one of my own. We don't have CustomizationsRT or HTMLMap installed, just including it for the future purpose. The approach we are going for is the third one basically.

Chris Meyer

*.kc { font-family: Helvetica , arial , sans-serif; font-size: 16.0px; line-height: 1.6; background-color: rgb(255,255,255);}*.kc a { color: rgb(65,131,196);}*.kc a.absent { color: rgb(204,0,0);}*.kc a.anchor { display: block; padding-left: 30.0px; cursor: pointer; top: 0; left: 0; bottom: 0;}*.kc h1, *.kc h2, *.kc h3, *.kc h4, *.kc h5, *.kc h6 { margin: 20.0px 0 10.0px; padding: 0; font-weight: 700;}cursor:text {}position:relative {}*.kc h1:hover a.anchor, *.kc h2:hover a.anchor, *.kc h3:hover a.anchor, *.kc h4:hover a.anchor, *.kc h5:hover a.anchor, *.kc h6:hover a.anchor { text-decoration: none;}*.kc h1 code, *.kc h1 tt { font-size: inherit;}*.kc h2 code, *.kc h2 tt { font-size: inherit;}*.kc h3 code, *.kc h3 tt { font-size: inherit;}*.kc h4 code, *.kc h4 tt { font-size: inherit;}*.kc h5 code, *.kc h5 tt { font-size: inherit;}*.kc h6 code, *.kc h6 tt { font-size: inherit;}*.kc h1 { font-size: 28.0px; color: rgb(0,0,0);}*.kc h2 { font-size: 24.0px; border-bottom: 1.0px solid rgb(204,204,204); color: rgb(0,0,0);}*.kc h3 { font-size: 20.0px;}*.kc h4 { font-size: 18.0px;}*.kc h5 { font-size: 16.0px;}*.kc h6 { color: rgb(119,119,119); font-size: 16.0px;}*.kc blockquote, *.kc dl, *.kc li, *.kc ol, *.kc p, *.kc pre, *.kc table, *.kc ul { margin: 15.0px 0;}*.kc hr { border: 0 none; color: rgb(204,204,204); height: 4.0px; padding: 0;}*.kc body > h2:first-child { margin-top: 0; padding-top: 0;}*.kc body > h1:first-child { margin-top: 0; padding-top: 0;}*.kc body > h1:first-child + h2 { margin-top: 0; padding-top: 0;}*.kc body > h3:first-child, *.kc body > h4:first-child, *.kc body > h5:first-child, *.kc body > h6:first-child { margin-top: 0; padding-top: 0;}*.kc a:first-child h1, *.kc a:first-child h2, *.kc a:first-child h3, *.kc a:first-child h4, *.kc a:first-child h5, *.kc a:first-child h6 { margin-top: 0; padding-top: 0;}*.kc h1 p, *.kc h2 p, *.kc h3 p, *.kc h4 p, *.kc h5 p, *.kc h6 p { margin-top: 0;}*.kc li p.first {}*.kc li { margin: 0;}*.kc ol, *.kc ul { padding-left: 30.0px;}*.kc ol *:first-child, *.kc ul *:first-child { margin-top: 0;}*.kc dl { padding: 0;}*.kc dl dt { font-size: 16.0px; font-weight: 700; font-style: italic; padding: 0; margin: 15.0px 0 5.0px;}*.kc dl dt:first-child { padding: 0;}*.kc dl dt > *:first-child { margin-top: 0;}*.kc dl dt > *:last-child { margin-bottom: 0;}*.kc dl dd { margin: 0 0 15.0px; padding: 0 15.0px;}*.kc dl dd > *:first-child { margin-top: 0;}*.kc dl dd > *:last-child { margin-bottom: 0;}*.kc blockquote { border-left: 4.0px solid rgb(221,221,221); padding: 0 15.0px; color: rgb(119,119,119);}*.kc blockquote > *:first-child { margin-top: 0;}*.kc blockquote > *:last-child { margin-bottom: 0;}*.kc table { padding: 0; border-collapse: collapse;}*.kc table tr { border-top: 1.0px solid rgb(204,204,204); background-color: rgb(255,255,255); margin: 0; padding: 0;}

Hi,

Ok, huge red flags now appear ðŸ˜Š Why do you need to override RunFileWithArglist?

This goes back many years as a technique for overriding a core weblingo file with a replacement in a custom module. Customers often want to change a look or behaviour of core functionality, and sometimes changing a core weblingo file is necessary. This approach allows a developer to remap a weblingo file to another location, which doesn't require modifying the original file.

I don't know a better way of doing this in Content Server. I've seen other frameworks (e.g., Django) make it a standard feature, but with Content Server we have to do it ourselves. I believe htmlmap and CustomizationsRT both use this approach.

If you know a better way of doing this then please share. I'm always looking for ways to improve how I do things.

I am trying to override the WebLingo::WebScript RunFileWithArglist() script. I did the above steps but still the control is going to the original core script. Is there anything else that I need to do as well?

As with Builder you still need to patch the parent object you're overriding. This means adding something like the following to your __Init function:

function Void __Init()    Object parent = OS.Parent(this)    if parent        parent.RunFileWithArglist = .RunFileWithArglist    endend

This can be generalised, but you get the idea.

Shruti_Mishra

Thanks Chris! The below worked for me:

WEBLINGO::WebScript.RunFileWithArglist = $MyModule.WebScript.RunFileWithArglist

Greg Griffiths

another option is to patch the .fHTMLFile and .fHTMLPathPrefix of the Request Handler you need it for to point to your custom module's folder structure.

AftabShaikh

Hi Greg,

Can you show us an example on how to override weblingo file on RH level?

Quoted Greg Griffiths on 02/25/2019 12:15 PM:

another option is to patch the .fHTMLFile and .fHTMLPathPrefix of the Request Handler you need it for to point to your custom module's folder structure.

Greg Griffiths

you just set the features that control the WebLingo, like fHTMLFile etc, in your Orphan/Override of that Request Handler.

Dont forget to review and update the change with each patch/upgrade etc to keep it functional, correct and secure.

John Simon

It may be helpful to look at your RH's GenerateOutput script and/or GenerateHTML script to understand which RH settings to override and which ones take precedence.

Cheers...