[opencms-dev] empty context menu
Technology Operations
techops at thedoleco.com
Thu Apr 2 19:47:32 CEST 2009
Hello,
I am very new to opencms. I have followed the online documentation and the
wdogsystems article to create a simple xsd content definition. i am able to
see my content type in the "create new" menu in the admin console. i am also
able to create the content itself. however, when i right click on the name,
the context-menu that is supposed to show me the options turns up blank....
no options at all! i have turned on debug logging on however, i dont see any
logs! i am totally at a dead end as to what to do next! pleae help. followed
below is my opencms-modules.xml, my content definition and logging
properties...
<module>
<name>com.redo.poc.xmlcontent</name>
<nicename><![CDATA[POC for XML Content]]></nicename>
<class />
<description />
<version>0.1</version>
<authorname />
<authoremail />
<datecreated />
<userinstalled />
<dateinstalled />
<dependencies />
<exportpoints>
<exportpoint
uri="/system/modules/com.redo.poc.xmlcontent/lib/"
destination="WEB-INF/lib/" />
<exportpoint
uri="/system/modules/com.redo.poc.xmlcontent/classes/"
destination="WEB-INF/classes/" />
</exportpoints>
<resources>
<resource uri="/system/modules/com.redo.poc.xmlcontent/" />
</resources>
<parameters />
<resourcetypes>
<type name="image"
class="org.opencms.file.types.CmsResourceTypeXmlContent"
id="2500">
<properties/>
<param
name="schema">/system/modules/com.redo.poc.xmlcontent/content-defs/image.xsd</param>
</type>
</resourcetypes>
<explorertypes>
<explorertype name="image" key="fileicon.image"
icon="xmlcontent.gif">
<newresource
uri="newresource_xmlcontent.jsp?newresourcetype=image"
order="2500" page="structurecontent" />
<accesscontrol>
<accessentry principal="ROLE.WORKPLACE_USER"
permissions="+r+v+w+c" />
</accesscontrol>
</explorertype>
</explorertypes>
</module>
xsd:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:include schemaLocation="opencms://opencms-xmlcontent.xsd" />
<xsd:element name="Images" type="OpenCmsImages" />
<xsd:complexType name="OpenCmsImages">
<xsd:sequence>
<xsd:element name="ImageType" type="OpenCmsImageType"
minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="OpenCmsImageType">
<xsd:sequence>
<xsd:element name="Title" type="OpenCmsString" minOccurs="0"
maxOccurs="1" />
<xsd:element name="Caption" type="OpenCmsString"
minOccurs="0" maxOccurs="1" />
<xsd:element name="ImageFile" type="OpenCmsVfsFile"
minOccurs="0" maxOccurs="1" />
</xsd:sequence>
<xsd:attribute name="language" type="OpenCmsLocale" use="required"
/>
</xsd:complexType>
</xsd:schema>
logging:
# What follows is the default OpenCms log4j configuration.
# OpenCms uses the "commons-logging" component to detect the available
logging implementation.
# A recent log4j.jar is shipped with the default OpenCms installation and
thus log4j is used.
# To use another logging mechanism, delete the shipped log4j.jar in
/WEB-INF/lib.
# You must then provide the configuration of the logging mechanism you want
to use by
# environment settings or startup parameters of the servlet engine.
# OpenCms provides a special variable ${opencms.logfile} to the environment,
which contains
# the log file path. The location of this file is calculated relative to
this
# "log4j.properties" file on OpenCms startup. If this file is located in the
folder "${classes}",
# then the log is written to "${classes}../logs/opencms.log".
# To disable this mechanism, you must set ${opencms.set.logfile} to "false".
In this case
# you must configure the log output file manually.
opencms.set.logfile=true
opencms.logfile=opencms_init.log
# Per default we use WARN debug level and just one appender
log4j.rootLogger=\
ERROR,\
OC
# ,CONSOLE
# Optional CONSOLE appender for logging on the system console (good for
debugging during development)
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
# CONSOLE uses PatternLayout.
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
#log4j.appender.CONSOLE.layout.ConversionPattern=%5p [%25.25C:%4L] %m%n
log4j.appender.CONSOLE.layout.ConversionPattern=%5p [%100C:%4L] %m%n
# Set levels for all default channels available in OpenCms
log4j.logger.com.opencms=DEBUG
log4j.logger.org.opencms=DEBUG
log4j.logger.org.opencms.flex=ERROR
log4j.logger.org.opencms.i18n=ERROR
log4j.logger.com.opencms.db.generic=ERROR
log4j.logger.org.opencms.db.generic=ERROR
log4j.logger.org.opencms.init=INFO
log4j.logger.org.opencms.monitor=DEBUG
log4j.logger.org.opencms.scheduler=DEBUG
log4j.logger.org.opencms.search=INFO
log4j.logger.org.opencms.staticexport=DEBUG
log4j.logger.org.opencms.jsp.CmsJspLoginBean=DEBUG
log4j.logger.org.opencms.db.mysql3.CmsProjectDriver=DEBUG
log4j.logger.org.opencms.db.mysql.CmsProjectDriver=DEBUG
log4j.logger.org.opencms.db.oracle8.CmsProjectDriver=DEBUG
log4j.logger.org.opencms.db.oracle.CmsProjectDriver=DEBUG
log4j.logger.org.opencms.workplace.tools=WARN
# This default appender configuration simply writes all OpenCms channels in
one log file
# A OpenCms 'channel' directly translates into a 'logger' in the log4j lingo
log4j.appender.OC=org.apache.log4j.RollingFileAppender
# In a default Tomcat installation, this should place the log file in the
Tomcat log directory
# Adjust this path in case you want to log in another directory
log4j.appender.OC.File=${opencms.logfile}
# Limit log size to 5mb, then rotate
log4j.appender.OC.MaxFileSize=2mb
# Keep 5 backup files
log4j.appender.OC.MaxBackupIndex=5
# This specifies the logfile layout
log4j.appender.OC.layout=org.apache.log4j.PatternLayout
log4j.appender.OC.layout.ConversionPattern=%d{DATE} %5p [%C:%4L] %m%n
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20090402/925b0596/attachment.htm>
More information about the opencms-dev
mailing list