cancel
Showing results for 
Search instead for 
Did you mean: 

Prevent WPC_article file from being overwritten on server restart in NW 7.31 SP12

former_member183915
Active Contributor
0 Kudos

Hi,

We have modified wpc_article.xsl and wpc_article.xml . Once we upload the file to portal when we take portal server restart, the custom file gets replaced with SAP standard file.

Is there any way to prevent this issue? We are facing this issue after upgrading portal  to NW 7.31 SP12. It was working fine till SP4.

Any inputs

Changes done :

In Portal goto Portal Content Administration > KM Content > root > etc > wpceditor > styles

select context menu for wpc_article.xsl

Edit Locally

Opens notepad

<!-- Comment out back to top Lee Lewis

     <div class="wpcbacktotop">

      <a class="wpca" href="#" onclick="javascript:window.location.reload(false)">

       <xsl:value-of disable-output-escaping="yes"

        select="wpc:getString('xsl.xmsg.back_to_top', string(/document/@locale))" />

      </a>

     </div>

     -->

Regards,

Navya

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member183915
Active Contributor
0 Kudos

Hi,

Any inputs??

rohit_singhal
Active Contributor
0 Kudos

Hi Navya,

As per my understanding, we should not modify the standard forms instead, if any customization is required, we edit a copy of the standard.

Why not create a custom form (change the name of the updated form to a custom one), and its corresponding XSL?

You will then have to maintain following configurations in System Admin:

  1. Delta copy standard WPC form template at path pcd:portal_content/com.sap.pct/templates/pcc.templates/content/com.sap.portal.pcc.article_default_iview, and paste the new iView in the folder where you want to maintain all the form templates.
  2. Update the following iView properties with the custom form name:
    • com.sap.nw.wpc.WebContentType
    • com.sap.portal.ContentTemplate
  3. Perform the following mapping in System Administration:
    1. Maintain Document Types: Content Management-->Web Page Composer-->Editor-->Document Types-->Document Types-->Document Types. This configuration is done to map the XML form with the corresponding XSL and Resource Bundle file.
    2. Maintain Document Styles: Content Management-->Web Page Composer-->Editor-->Stylesheets-->Stylesheets-->Document Styles. This configuration is done to define XSL.
    3. Maintain Stylesheet Groups: Content Management-->Web Page Composer-->Editor-->Stylesheets-->Stylesheet groups-->Document Style Groups. This configuration is done to define the stylesheet group.
    4. Maintain Web Content Types: Content Management-->Web Page Composer-->Web Content Types-->Web Resource Type-->Web Resource Type. This configuration is done to map XML form to the template iView created in Step a.

Best Regards,

Rohit Singhal