Node Specific Custom HTML?

I've run into a roadblock today when I discovered that variables such as ${nodename} don't work the Custom HTML or Text resource. Below is an example of what I'm trying to do, but doesn't work with variables.

What you get

servername/.../campic.jpg

Does anyone have a creative idea of how I could include some node specific custom HTML to the node details page?

Find more posts tagged with

node_details_custom_html

Accepted answers

All comments

FormerMember

Is this a change fro 8.1? Is there a bug we need to open?

jds

Yes to both. I've opened a ticket with support on this issue and they said they will open a bug. The case is #17100. I have not heard back from support in a couple of weeks.

mark_wiggans

JDS- the ticket # you referenced is closed. The last entry from the rep was

"Worked with customer via a goto meeting, and problem appears to be an Orion 8.5 bug, was able to resolve via changing of permissions."

If this is not the case and you wish to re-open the ticket send an email to the ticket and the rep will get it.

jds

Huh, well at least a bug has been reported with 8.5. I was never told about the resolution of "changing permissions".

I'll send an email to the ticket to try to find out what is going on.

Thanks

aLTeReGo

Is this a change fro 8.1? Is there a bug we need to open?

Denny, I'm not sure if this is a new bug, an existing bug, or not a bug at all. I've never tried using Orion variables in the custom HTML/TEXT resource. I was just sad to see that it didn't work. If this isn't a bug, and is by design I'll be happy to report it as a feature request. In the meantime I'm sure it can be overcome with the use of ASP code. I'm just not sure how to go about coding something like that. Ideas anyone?

chris.conway

It's something I reported way back in V7.

The Custom HTML resource is just that, HTML only. No ASP code will work in it.

It's the reason I took to writing my own resource files as it was the only way to get custom HTML/ASP working together.

FormerMember

Is this a change fro 8.1? Is there a bug we need to open?

Denny, I'm not sure if this is a new bug, an existing bug, or not a bug at all. I've never tried using Orion variables in the custom HTML/TEXT resource. I was just sad to see that it didn't work. If this isn't a bug, and is by design I'll be happy to report it as a feature request. In the meantime I'm sure it can be overcome with the use of ASP code. I'm just not sure how to go about coding something like that. Ideas anyone?

Got it. I wouldn't write anything in ASP. Our direction is ASP.net. We will discontinue backward compatibility with ASP at some point.

aLTeReGo

I'm still confused, is the inability to use Orion variables in a custom HTML/Text resource a bug or a feature...um, I mean by design?

Denny, I appreciate you pointing me in a general direction but I'm even more out of my league in ASP.NET.