Is there a way to customize an the COE form in 8.5?

Hi,

I was just wondering if there is an extension point to customize the COE in 8.5? In v7, you could customize the jsp of the form. Where is that in 8.5? Or, is it gone?

Thanks,

Eric

Find more posts tagged with

Comments

Although it is not something we made explicitly public, it is possible and rather easy. There are two things you have to do:

<![if !supportLists]>1. <![endif]>Override the editor jsp page by setting the new jsp in the spring theme config file. You will use the current editor jsp “contentInstance.jsp” as the starting point for your customization

<![if !supportLists]>2. <![endif]>If your customization requires to address each single widget on the page youy might wish to take a look at some existing overridden editors we have in the product (such as linkForm.jsp, but you will find plenty of them by taking a look in the spring theme xml file)

The question is why you need to customize the editor ? I would suggest to keep it as is …..

-m

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: venerdì 5 settembre 2014 16:25
To: eLink Recipient
Subject: Is there a way to customize an the COE form in 8.5?

Is there a way to customize an the COE form in 8.5?

Posted byeborisow@us.imshealth.com (Borisow, Eric) On 09/05/2014 10:21 AM

Hi,

I was just wondering if there is an extension point to customize the COE in 8.5? In v7, you could customize the jsp of the form. Where is that in 8.5? Or, is it gone?

Thanks,

Eric

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Thanks Mario. I'll have to check that out.

As for the reason, we previously had a customization in 8.0 that would allow us to create a content instance that contained a list of attributes (and hence widgets) that should be hidden when the COE page loads. For example, System Title should not appear because we use a separate attribute called Display Title and a listener populates the System Title on save. That's just one example, but we have a few others. Essentially, the COE jsp code would skip over any attributes defined in the other Content Instance.

Regards,

Eric

Mario,

We're finally getting back to this. So, we grabbed the contentInstance.jsp from the vcm-ui.war file and put it into one of our custom projects. After deploying it and updating our theme, we're receiving an error message on the front-end. In the browser, it's throwing this error:

json is undefined

It happens at line #269 of vui.js which is this line:

var json=vui.secure_eval(_24f);
_24a.metadata=json.xapi.metadata;

Is there something I'm missing about the deployment? Do I need to deploy the file into the vcm-ui.war file directly?

Thanks,

Eric