| Author |
Message |
|
|
I have a page on my site that I allow a user to update some information about themselves. Only they can manage the content on this page.
The page is not part of the CMS but is part of the site itself.
The page consists of the textarea and other data that needs to be submitted. I have the form submitting fine, I'd just like to enable the WYSIWYG functionality on the textarea to make input nicer for the user.
|
 |
|
|
Hi Chris,
How are you defining your postToUrl?
If it is a property, you will need to define the property in the Component Properties section of your component, it sounds to me as if you need a string value which will allow you to specify a URL change the Property Type to textfield.
Once you have defined the property you need to do the following in the code, change the propertyName value to whatever the name of your property is:
Wherever you want the value of this property to be display do the following:
So for example if you wish to display this in a form action do:
The only other thing you need to do is to edit the page in the Structure Tool and set the property value by right clicking on the component on the page and selecting Properties (if you can't identify which component it is easily I suggest that you select Page Structure, find the component and then right click and choose Properties).
Cheers,
Mark.
|
 |
|
|
I have a textarea field on a form that collects input from a user. Is it possible to integrate the WYSIWYG editor functionality into this text area so that the user can format their input?
If this is possible can someone please provide an example of what needs to be included on the page, i.e. JavaScript and how the textarea field should be configured.
Thanks,
Mark.
|
 |
|
|
That sorted it! I'm not certain what I had before but I overwrote the taglib declarations and everything else at the top of the component and it now works.
Thanks, I knew it would be something simple, I just didn't know what.
Mark.
|
 |
|
|
Jaric,
This is really strange, the Site Map demo does work, when I trap the setInput method on the SortPagesTag the value being passed in is an expression to be evaluated, i.e.
When I debug my own code the input property is being set with the already evaluated expression, i.e.
Any thoughts?
Mark.
|
 |
|
|
Jaric,
I total agreed with your deductions and had come to the same conclusion, and the code in my version 2.9.7.3 is the same.
When I output the debug message I get:
As should be expected!
Mark.
|
 |
|
|
The following code creates a new site node under parentSiteNodeId 55 using a template that I created (which has a content id of 151).
The following code creates a piece of content under parentContentId 121.
The only problem I had with the above code is that I needed to change the infoglue tld files to allow me to pass in evaluated values.
|
 |
|
|
|
There is no difference. It fails in exactly the same way, when trying to set the 'input' property in SortPagesTag - failing with the conversion to type List!
|
 |
|
|
I have been happily using the ChildPages tag and the JSTL c:forEach tag, now that I've tried to integrate the SortPages tag things are falling apart.
My code is as follows:
If I remove the sortPages tag this code works perfectly, I've also changed the id for the sortPages to sortedChildPages and it still doesn't work. The issue appears to be with the output of the childPages tag. I'm getting the following stacktrace:
I've tried stepping through the sortPages tag in debug and this is happening on the setInput method.
Any thoughts?
Thanks,
Mark.
|
 |
|
|
Jaric,
Thanks for the question, but 'no' I need it to be part of the URL for marketing and SEO purposes.
I've worked out how to create new Site Nodes using that method described earlier (I'll document that later in this thread for anyone else looking to do the same thing). I'm now looking to see if I can publish the page that I've just created. The source code has a section to do this, but it is commented out. I'm going to play around and see if I can get it working (it seems to work for Content).
Mark.
|
 |
|
|
I've managed to find an undocumented tag, remoteSiteNodeService, in the structure tld file, but I'm not exactly certain how this works.
I've tried the following:
But this gives me the following stacktrace:
Anyone any ideas? If I find anything I'll keep you posted.
|
 |
|
|
Hi,
I know it is possible to create Content within the content tool using the , that works really well. Although I have noticed that the examples in the developers manual show that you can use the following contentTypeDefinitionId="${ctd.id}", but when I actually come to do this I have to use static values.
What I'd actually like to do is dynamically create a new site node. Is this possible?
I would like to dynamically create a profile page for each new user that registers on my site, so they can view their profile on a URL like . I don't want to have to create the page manually. If this is possible how do I do it, and at that point I'll need to set up the components on the page to make sure it has the correct layout, etc?
Can anyone help?
Thanks,
Mark.
|
 |
|
|
Karl,
I have reconfigured Tomcat/InfoglueCMS so that infoglueDeliverLive is served through the ROOT web app, running on port 80. This way user can simply go to http://www.mydomain.com/ and see the live web site.
Thanks,
Mark.
|
 |
|
|
Just to confirm, I have placed my custom_error.jsp file in the tomcat/webapp/ROOT folder and not within Infoglue. Is this correct?
Thanks,
Mark.
|
 |
|
|
I haven't posted on this issue in a long time, but the problem is still present.
When I first install infoglue into the live environment I installed infoglueCMS, preview, working and live all under one Tomcat instance. This mirrored the development environment, where there are no problems (at least not like this).
In the early hours of the this morning I split the CMS, preview and working onto a completely different server and configured the CMS so that it could publish to live on the original server. I believed that this would clear up the issue.
It might be worth noting now that I have a custom error page configured.
This morning when I split infoglue up I did extensive testing, i.e. making sure I could publish, etc. This went smoothly without error.
My client has today attempted a published, nothing major just a few templates. As soon as this was done the live server stopped serving infoglue pages and only served the custom error page (the custom error page has reference to image assets and css within the site, these are not being served, simply the plain HTML of the custom error page). The only way to resolve this situation is to restart Tomcat. When the site when down today I did not get a chance to see if the CMS or Working were serving pages and whether it was just the live server that was down.
The log file entry is as follows:
javax.servlet.ServletException: File "/custom_error.jsp" not found
at org.apache.jasper.servlet.JspServlet.handleMissingResource(JspServlet.java:335)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:48
at org.infoglue.deliver.applications.actions.ErrorPageAction.doExecute(ErrorPageAction.java:166)
at org.infoglue.cms.applications.common.actions.WebworkAbstractAction.execute(WebworkAbstractAction.java:113)
at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:131)
at webwork.dispatcher.ServletDispatcher.service(ServletDispatcher.java:174)
at org.infoglue.deliver.portal.dispatcher.DeliveryServletDispatcher.service(DeliveryServletDispatcher.java:66)
at org.infoglue.deliver.portal.dispatcher.PortalServletDispatcher.service(PortalServletDispatcher.java:176)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:43
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:415)
at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:342)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:29
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:58
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Unknown Source)
Any help in this area would be much appreciated.
Thanks,
Mark.
|
 |
|
|