Welcome to the pulse website administration
Getting started for the impatient
Open the Content-Registry on the left, navigate to CMS, en_US and create a folder for contents. Go to the newly created folder and create a content.
After you have created the content open the Sitemap. You should see the sitemap for the locale en_US with a root level node named Autogenerated Node. Click on the eye icon to make the node visible and then on the edit icon (yes, it's the small pencil). This will open a view of the Content-Registry in a tab in the center of the viewport. Select the content you have created earlier to become your starting page.
Now the starting page is available to the root user. To allow everybody to access the starting page, open the Users and Rights panel on the left and select Roles overview. You will find a role named ~Everybody, which is assigned to every visitor of your site. Edit this role by clicking the pencil and open the Permissions assorter. Add the permission named ~CMS:CMSContentDisplayer:displayCMS to grant everybody the permission to view CMS contents on your website. You should also add ~Core:HomepageRedirector:user, so the everybody may use the homepage redirector which is called by index.jsp.
That's it. Have fun exploring the rest of the administration.
Quick tips
On the left-hand side you can find different palettes for the individual parts of the administration. All editors and edit options chosen from a palette will open as a tab in the right-hand side of the administration.
Many parts of the administration will reveal additional information in tool tips, if you hover your mouse above them. Some components - such as tabs - offer additional options when being right-clicked.
For further information on the individual editors, please consult the manual.
Latest Changes
Lorem ipsum dolor sit amet
<
I use Cpanel/tomcat server on linux centos
Any help would be appreciated.
Martin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
as far as I can see from your post you have mounted pulse as the ROOT webapp, and to be honest this is a scenario we have not been testing so far. Shame on us.
The current version (0.7 pre 2) has a bug in org.torweg.pulse.service.AbstractPulseFilter which causes the version rewriting to fail when run in the root context. At the moment I am preparing a patch to be included in the next release (due this weekend).
To fix this temporarily, you can apply a simple change to WEB-INF/xsl/globals.xsl turning of the versioning (lines 58 and following):
<xsl:variablename="path.webapp"><xsl:value-ofselect="$path.webapp.unversioned"/><!-- comment the next two lines to disable versions --><!-- <xsl:text>/</xsl:text> <xsl:value-of select="$version.id"/> --></xsl:variable>
If you are using a context name other than pulse, please also adjust the URIs for the virtual file system in WEB-INF/conf/pulse.xml or you will not be able to access resources added via WebDAV (lines 40 and following):
<virtual-file-system><providerrealm="public"class="org.torweg.pulse.vfs.providers.SingleFileSystemProvider"><!-- relative paths will be resolved against the webapp root --><base-pathuri="WEB-INF/vfs-public"/><http-base-pathuri="/pulse/vfs-public"/></provider><providerrealm="private"class="org.torweg.pulse.vfs.providers.SingleFileSystemProvider"><base-pathuri="WEB-INF/vfs-private"/><http-base-pathuri="/pulse/vfs-private"/></provider></virtual-file-system>
to
<virtual-file-system><providerrealm="public"class="org.torweg.pulse.vfs.providers.SingleFileSystemProvider"><!-- relative paths will be resolved against the webapp root --><base-pathuri="WEB-INF/vfs-public"/><http-base-pathuri="/vfs-public"/></provider><providerrealm="private"class="org.torweg.pulse.vfs.providers.SingleFileSystemProvider"><base-pathuri="WEB-INF/vfs-private"/><http-base-pathuri="/vfs-private"/></provider></virtual-file-system>
If you have any further issues, please let us know.
Cheers,
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
damn, these forums definitely could use a preview function…
here is the code section that has been messed up in the previous post:
<virtual-file-system><providerrealm="public"class="org.torweg.pulse.vfs.providers.SingleFileSystemProvider"><!-- relative paths will be resolved against the webapp root --><base-pathuri="WEB-INF/vfs-public"/><http-base-pathuri="/vfs-public"/></provider><providerrealm="private"class="org.torweg.pulse.vfs.providers.SingleFileSystemProvider"><base-pathuri="WEB-INF/vfs-private"/><http-base-pathuri="/vfs-private"/></provider></virtual-file-system>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
<xsl:variable name="path.webapp">
<xsl:value-of select="$path.webapp.unversioned"/>
<!- comment the next two lines to disable versions ->
<!-
<xsl:text>/</xsl:text>
<xsl:value-of select="$version.id"/>
->
</xsl:variable>
in pulse.xml
<virtual-file-system>
<provider realm="public" class="org.torweg.pulse.vfs.providers.SingleFileSystemProvider">
<!- relative paths will be resolved against the webapp root ->
<base-path uri="WEB-INF/vfs-public"/>
<http-base-path uri="/vfs-public"/>
</provider>
<provider realm="private" class="org.torweg.pulse.vfs.providers.SingleFileSystemProvider">
<base-path uri="WEB-INF/vfs-private"/>
<http-base-path uri="/vfs-private"/>
</provider>
</virtual-file-system>
But, I can not create any content or have a index or start page for this testing website. I would appreciate if you can browse the admin and create any content as an example and publish in the site.
When I log out I have tomcat error page, how can be fixed?
Thank you very much for your support and assistance.
Martin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
somehow the administration start page does not get delivered correctly on your installation. It should look like:
So there should be some panels on the left hand side.
When I look at the source code of the administration start page (in Firefox) it ends prematurely. There should be six additional lines of JavaScript and the closing HTML tags for script, body and html.
If I use Safari 4 on Windows it is also missing parts of the page, though not as much.
I set up an installation on a stand-alone Tomcat 6, with pulse deployed as the ROOT webapp and I can access and use the viewport on my machine.
This could be a charset encoding problem, but I am really not sure (I know I had exactly the same issue once, but can't remember the cause). Please try the following:
a) In the Tomcat start script on your system (usually /etc/init.d/tomcat or similar) make sure to set
-Dfile.encoding=utf-8
as an option to the java command starting Tomcat
b) In CATALINA_HOME/conf/server.xml look for
we thank you for taking your time to check out pulse. After all it is people like you who help us to improve the software and give us helpful information on where to improve and extend our documentation.
Cheers,
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I have installed pulse at: http://www.appshost.info:8080/Pulsar/.Core.homepage../
when I log to: http://www.appshost.info:8080/login.jsp with root and password generated by the application I can only see the following text (including the simbol at the end):
Welcome to the pulse website administration
Getting started for the impatient
Open the Content-Registry on the left, navigate to CMS, en_US and create a folder for contents. Go to the newly created folder and create a content.
After you have created the content open the Sitemap. You should see the sitemap for the locale en_US with a root level node named Autogenerated Node. Click on the eye icon to make the node visible and then on the edit icon (yes, it's the small pencil). This will open a view of the Content-Registry in a tab in the center of the viewport. Select the content you have created earlier to become your starting page.
Now the starting page is available to the root user. To allow everybody to access the starting page, open the Users and Rights panel on the left and select Roles overview. You will find a role named ~Everybody, which is assigned to every visitor of your site. Edit this role by clicking the pencil and open the Permissions assorter. Add the permission named ~CMS:CMSContentDisplayer:displayCMS to grant everybody the permission to view CMS contents on your website. You should also add ~Core:HomepageRedirector:user, so the everybody may use the homepage redirector which is called by index.jsp.
That's it. Have fun exploring the rest of the administration.
Quick tips
On the left-hand side you can find different palettes for the individual parts of the administration. All editors and edit options chosen from a palette will open as a tab in the right-hand side of the administration.
Many parts of the administration will reveal additional information in tool tips, if you hover your mouse above them. Some components - such as tabs - offer additional options when being right-clicked.
For further information on the individual editors, please consult the manual.
Latest Changes
Lorem ipsum dolor sit amet
<
I use Cpanel/tomcat server on linux centos
Any help would be appreciated.
Martin
Hi Martin,
as far as I can see from your post you have mounted pulse as the ROOT webapp, and to be honest this is a scenario we have not been testing so far. Shame on us.
The current version (0.7 pre 2) has a bug in org.torweg.pulse.service.AbstractPulseFilter which causes the version rewriting to fail when run in the root context. At the moment I am preparing a patch to be included in the next release (due this weekend).
To fix this temporarily, you can apply a simple change to WEB-INF/xsl/globals.xsl turning of the versioning (lines 58 and following):
If you are using a context name other than pulse, please also adjust the URIs for the virtual file system in WEB-INF/conf/pulse.xml or you will not be able to access resources added via WebDAV (lines 40 and following):
to
If you have any further issues, please let us know.
Cheers,
Thomas
damn, these forums definitely could use a preview function…
here is the code section that has been messed up in the previous post:
The issue has been fixed in the SVN trunk and will definitely be part of the next release.
Hello Thomas,
Thank you very much for your post.
I applied the changes:
in globals.xsl
<xsl:variable name="path.webapp">
<xsl:value-of select="$path.webapp.unversioned"/>
<!- comment the next two lines to disable versions ->
<!-
<xsl:text>/</xsl:text>
<xsl:value-of select="$version.id"/>
->
</xsl:variable>
in pulse.xml
<virtual-file-system>
<provider realm="public" class="org.torweg.pulse.vfs.providers.SingleFileSystemProvider">
<!- relative paths will be resolved against the webapp root ->
<base-path uri="WEB-INF/vfs-public"/>
<http-base-path uri="/vfs-public"/>
</provider>
<provider realm="private" class="org.torweg.pulse.vfs.providers.SingleFileSystemProvider">
<base-path uri="WEB-INF/vfs-private"/>
<http-base-path uri="/vfs-private"/>
</provider>
</virtual-file-system>
Re-started tomcat and finally could log to the system, ¡great!
visit:
http://www.appshost.info:8080/login.jsp
user: root
pwd: 1234abcd
But, I can not create any content or have a index or start page for this testing website. I would appreciate if you can browse the admin and create any content as an example and publish in the site.
When I log out I have tomcat error page, how can be fixed?
Thank you very much for your support and assistance.
Martin
Hello Martin,
somehow the administration start page does not get delivered correctly on your installation. It should look like:
So there should be some panels on the left hand side.
When I look at the source code of the administration start page (in Firefox) it ends prematurely. There should be six additional lines of JavaScript and the closing HTML tags for script, body and html.
If I use Safari 4 on Windows it is also missing parts of the page, though not as much.
I set up an installation on a stand-alone Tomcat 6, with pulse deployed as the ROOT webapp and I can access and use the viewport on my machine.
This could be a charset encoding problem, but I am really not sure (I know I had exactly the same issue once, but can't remember the cause). Please try the following:
a) In the Tomcat start script on your system (usually /etc/init.d/tomcat or similar) make sure to set
as an option to the java command starting Tomcat
b) In CATALINA_HOME/conf/server.xml look for
and add the URIEncoding="utf-8", if not present yet
That will probably fix it.
BTW, the error page on log out will disappear once you have an accessible landing page.
Hope this does the trick.
Cheers,
Thomas
Hi Martin, Hi Thomas,
as far as i remember :) adding
to the JAVA_OPTS for your tomcat will fix the problem…
Bye,
Daniel
Hi Thomas, Hi Daniel,
Thank you for your support
I added/edited server.xml
<Connector port="8080" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" URIEncoding="UTF-8"/>
And after a few minutes after re-starting tomcat I could create a content and publish it ¡GREAT!
visit:
http://www.appshost.info:8080/Pulsar/en_US.CMS.displayCMS.3./pulse
or
http://www.appshost.info:8080/index.jsp
Thank you for your support.
Martin
Hi Martin,
we thank you for taking your time to check out pulse. After all it is people like you who help us to improve the software and give us helpful information on where to improve and extend our documentation.
Cheers,
Thomas