WCM Tutorial

[rbramley]

I've been working my way through the tutorial, but the PR Form wasn't displaying correctly.

So I followed the instructions from the Caution note on page 32:

CAUTION: If your PR Form does not have a selection of radio buttons for the included
footer, and instead has a WYSIWYG field, your form callout has not been properly initialized
by the Virtualization Server. To correct, click Cancel in the Create Form wizard and click the
Preview icon next to the file get_company_footer_simple_type.jsp in the
/ROOT/media/releases directory. If this file returns a list of the company footers you have
created, the callout has been properly initialized and you are ready to restart the content
creation process using the PR Form.

However, previewing this jsp caused the following exception:

org.apache.jasper.JasperException: The class org.alfresco.web.pr.Util specified in TLD for the function pr:getCompanyFooters cannot be found: org.alfresco.web.pr.Util
‍‍‍

and the main Tomcat window had the following warning:

[Warning] :3:151: schema_reference.4: Failed to read schema document 'http://www-alfresco-www--bob.avm.127-0-0-1.ip.alfrescodemo.net:8180/media/releases/get_company_foote...', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>

Has anyone else had this problem?

Thanks,

Robin

[rbramley]

There was another error on the Tomcat console:

[Error] :19:112: src-resolve: Cannot resolve the name 'alfresco:company-footer' to a(n) 'type definition' component.

As a workaround I've removed the following line from press-release.xsd and the form now displays as expected (minus the company footer radio group).

<xs:element name="include_company_footer" type="alfresco:company-footer" minOccurs="1" maxOccurs="unbounded" />
‍‍‍

[kvc]

Try stopping and restarting the Virtualization Server.  This error is due to the Virtualization Server starting before Tomcat fully initializes.

Kevin

[rbramley]

Thanks Kevin - bouncing the virtualisation server fixed it.

Btw. I'd followed the README and waited until the console displayed the message 'INFO: Server startup in nnnnn ms'…

Cheers,

Robin

[kvc]

Thanks Kevin - bouncing the virtualisation server fixed it.

Btw. I'd followed the README and waited until the console displayed the message 'INFO: Server startup in nnnnn ms'…

Cheers,

Robin

EXCELLENT!!!!!!!!!!!


Kevin