Re: [xwiki-users] wiki editor doesn' t work
Dayong Sun wrote: > Thanks again, Marius. > > I couldn't remove Xerces-J 2.6.2 from our server. > But I installed Xerces-J 2.6.2 on my own machine. > XWiki on my machine still works well. In the > same way I tried BeanUtil. Is Xerces-J 2.6.2 or Xerces-J 2.8.1 detected on the (2.2.1) XWiki instance running on your local machine? If it's still Xerces-J 2.8.1 after you installed Xerces-J 2.6.2 then this doesn't prove anything. If your local XWiki instance runs indeed with Xerces-J 2.6.2 then the problem must be in some other place. The exception you get (java.lang.NoSuchFieldError: fFeatures) is precisely related to Xerces though. > > In fact today I downloaded all .jar files from > our server/tomcat/shared/lib and copied > to my machine/xwiki/WEB-INF/lib one by one. > And still, XWiki works well. Same comment as above. Did the detected version of Xerces change after you copied the jars from the Tomcat lib? Hope this helps, Marius > > Then I tried re-install XWiki on our server > and this time I use Hibernate. The error > is still there! > > This thing really drives me crazy. > > > > On Mon, Jan 25, 2010 at 4:02 AM, Marius Dumitru Florea < > mariusdumitru.flo...@xwiki.com> wrote: > >> jackyork wrote: >>> I have posted a few questions here and I really appreciated your replies. >> I >>> just received the 1,000,001 error from this XWiki program when I was >> trying >>> to switch editor from WYSIWYG to WIKI. This error must be a result of >> some >>> old version libs. I have excluded beanutil.jar and xercesImpl.jar. >> What do you mean by excluded? Is "Xerces-J 2.8.1" detected as pointed >> out in http://lists.xwiki.org/pipermail/users/2010-January/018949.html ? >> This library is needed so don't remove entirely, just make sure the >> right version is loaded (i.e. remove only the jars that correspond to an >> older/incorrect version). >> >> Hope this helps, >> Marius >> >>> Again the error info: >>> >>> Jan 24, 2010 10:46:38 PM org.apache.tomcat.util.http.Parameters >>> processParameters >>> WARNING: Parameters: Invalid chunk ignored. >>> 2010-01-24 22:46:38,351 [] >>> [ >> http://secure10.olemiss.edu/xwiki/bin/edit/Main/WebHome?editor=wiki&&$param >> ] >>> ERROR [/xwiki].[action] - Servlet.service() for servlet >> action >>> threw exception >>> java.lang.NoSuchFieldError: fFeatures >>> at >>> org.apache.xerces.parsers.XML11NonValidatingConfiguration.(Unknown >>> Source) >>> at >>> org.apache.xerces.parsers.XML11NonValidatingConfiguration.(Unknown >>> Source) >>> at >> sun.reflect.GeneratedConstructorAccessor116.newInstance(Unknown >>> Source) >>> at >>> >> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) >>> at >> java.lang.reflect.Constructor.newInstance(Constructor.java:494) >>> at java.lang.Class.newInstance0(Class.java:350) >>> at java.lang.Class.newInstance(Class.java:303) >>> at >>> >> org.xwiki.xml.internal.DefaultXMLReaderFactory.createXMLReader(DefaultXMLReaderFactory.java:81) >>> at >>> >> org.xwiki.rendering.internal.util.XWikiXMLReaderFactory.createXMLReader(XWikiXMLReaderFactory.java:50) >>> at >>> >> org.xwiki.rendering.internal.parser.WikiModelXHTMLParser.createWikiModelParser(WikiModelXHTMLParser.java:154) >>> at >>> >> org.xwiki.rendering.internal.parser.wikimodel.AbstractWikiModelParser.parse(AbstractWikiModelParser.java:86) >>> at >>> >> org.xwiki.rendering.internal.parser.WikiModelXHTMLParser.parse(WikiModelXHTMLParser.java:111) >>> at >>> >> com.xpn.xwiki.wysiwyg.server.converter.internal.DefaultHTMLConverter.fromHTML(DefaultHTMLConverter.java:100) >>> at >>> >> com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:117) >>> at >>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) >>> at >>> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) >>> at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:117) >>> at >>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) >>> at >>> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) >>> at >>> >> com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68) >>> at >>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) >>> at >>> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) >>> at >>> >> com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:295) >>> at >>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) >>> at >>> >> org.apache.catalina.core.ApplicationFilte
Re: [xwiki-users] wiki editor doesn' t work
Thanks again, Marius. I couldn't remove Xerces-J 2.6.2 from our server. But I installed Xerces-J 2.6.2 on my own machine. XWiki on my machine still works well. In the same way I tried BeanUtil. In fact today I downloaded all .jar files from our server/tomcat/shared/lib and copied to my machine/xwiki/WEB-INF/lib one by one. And still, XWiki works well. Then I tried re-install XWiki on our server and this time I use Hibernate. The error is still there! This thing really drives me crazy. On Mon, Jan 25, 2010 at 4:02 AM, Marius Dumitru Florea < mariusdumitru.flo...@xwiki.com> wrote: > jackyork wrote: > > I have posted a few questions here and I really appreciated your replies. > I > > just received the 1,000,001 error from this XWiki program when I was > trying > > to switch editor from WYSIWYG to WIKI. This error must be a result of > some > > old version libs. I have excluded beanutil.jar and xercesImpl.jar. > > What do you mean by excluded? Is "Xerces-J 2.8.1" detected as pointed > out in http://lists.xwiki.org/pipermail/users/2010-January/018949.html ? > This library is needed so don't remove entirely, just make sure the > right version is loaded (i.e. remove only the jars that correspond to an > older/incorrect version). > > Hope this helps, > Marius > > > > > Again the error info: > > > > Jan 24, 2010 10:46:38 PM org.apache.tomcat.util.http.Parameters > > processParameters > > WARNING: Parameters: Invalid chunk ignored. > > 2010-01-24 22:46:38,351 [] > > [ > http://secure10.olemiss.edu/xwiki/bin/edit/Main/WebHome?editor=wiki&&$param > ] > > ERROR [/xwiki].[action] - Servlet.service() for servlet > action > > threw exception > > java.lang.NoSuchFieldError: fFeatures > > at > > org.apache.xerces.parsers.XML11NonValidatingConfiguration.(Unknown > > Source) > > at > > org.apache.xerces.parsers.XML11NonValidatingConfiguration.(Unknown > > Source) > > at > sun.reflect.GeneratedConstructorAccessor116.newInstance(Unknown > > Source) > > at > > > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > > at > java.lang.reflect.Constructor.newInstance(Constructor.java:494) > > at java.lang.Class.newInstance0(Class.java:350) > > at java.lang.Class.newInstance(Class.java:303) > > at > > > org.xwiki.xml.internal.DefaultXMLReaderFactory.createXMLReader(DefaultXMLReaderFactory.java:81) > > at > > > org.xwiki.rendering.internal.util.XWikiXMLReaderFactory.createXMLReader(XWikiXMLReaderFactory.java:50) > > at > > > org.xwiki.rendering.internal.parser.WikiModelXHTMLParser.createWikiModelParser(WikiModelXHTMLParser.java:154) > > at > > > org.xwiki.rendering.internal.parser.wikimodel.AbstractWikiModelParser.parse(AbstractWikiModelParser.java:86) > > at > > > org.xwiki.rendering.internal.parser.WikiModelXHTMLParser.parse(WikiModelXHTMLParser.java:111) > > at > > > com.xpn.xwiki.wysiwyg.server.converter.internal.DefaultHTMLConverter.fromHTML(DefaultHTMLConverter.java:100) > > at > > > com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:117) > > at > > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) > > at > > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > > at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:117) > > at > > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) > > at > > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > > at > > > com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68) > > at > > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) > > at > > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > > at > > > com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:295) > > at > > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) > > at > > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > > at > > > com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) > > at > > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) > > at > > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > > at > > > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > > at > > > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) > > at > > > org.apache.catalina.core.Standard
Re: [xwiki-users] Problem with a Downloaded Macro (RSSAggregator)
Jerome Velociter wrote: > Hello Rick, > > You need to save the macro document (Macros.RssAggregatorMacro IIRC) > with a user that has the programming access level granted. > > Hi Jerome, I saved it as the Admin user - it didn't have Program access, but I added it afterward. Do I have to re-install the macro? If so how do I accomplish that? Rick ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Problem with a Downloaded Macro (RSSAggregator)
Hello Rick, You need to save the macro document (Macros.RssAggregatorMacro IIRC) with a user that has the programming access level granted. Jerome. Rick Hadsall wrote: > I'm getting this after installing the RssAggregator macro XAR and using it in > a page: > >> Failed to execute macro: groovy >> >> org.xwiki.rendering.macro.MacroExecutionException: You don't have the right >> to execute this script >> at >> org.xwiki.rendering.macro.script.AbstractJSR223ScriptMacro.execute(AbstractJSR223ScriptMacro.java:134) >> at >> org.xwiki.rendering.macro.script.AbstractJSR223ScriptMacro.execute(AbstractJSR223ScriptMacro.java:50) >> at >> org.xwiki.rendering.internal.transformation.MacroTransformation.transformOnce(MacroTransformation.java:175) >> etc... >> > > Ideas? > > Rick > > ___ > users mailing list > users@xwiki.org > http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Problem with a Downloaded Macro (RSSAggregator)
On Mon, Jan 25, 2010 at 15:49, Rick Hadsall wrote: > I'm getting this after installing the RssAggregator macro XAR and using it in > a page: > >> >> Failed to execute macro: groovy >> >> org.xwiki.rendering.macro.MacroExecutionException: You don't have the right >> to execute this script >> at >> org.xwiki.rendering.macro.script.AbstractJSR223ScriptMacro.execute(AbstractJSR223ScriptMacro.java:134) >> at >> org.xwiki.rendering.macro.script.AbstractJSR223ScriptMacro.execute(AbstractJSR223ScriptMacro.java:50) >> at >> org.xwiki.rendering.internal.transformation.MacroTransformation.transformOnce(MacroTransformation.java:175) >> etc... Looks like a script macro (groovy i guess) is used without programming right (i.e. the page where this macro is has been saved by someone that don't have programming right) >> > > Ideas? > > Rick > > ___ > users mailing list > users@xwiki.org > http://lists.xwiki.org/mailman/listinfo/users > -- Thomas Mortagne ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Problem with a Downloaded Macro (RSSAggregator)
I'm getting this after installing the RssAggregator macro XAR and using it in a page: > > Failed to execute macro: groovy > > org.xwiki.rendering.macro.MacroExecutionException: You don't have the right > to execute this script > at > org.xwiki.rendering.macro.script.AbstractJSR223ScriptMacro.execute(AbstractJSR223ScriptMacro.java:134) > at > org.xwiki.rendering.macro.script.AbstractJSR223ScriptMacro.execute(AbstractJSR223ScriptMacro.java:50) > at > org.xwiki.rendering.internal.transformation.MacroTransformation.transformOnce(MacroTransformation.java:175) > etc... > Ideas? Rick ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Problems with links
ndreher wrote: > Hello, > it seems to be a problem with the Internet Explorer. > The whole time I worked with Firefox no problem appeares. > > Can you tell me if there is an analog Debug-Tool for the IE as you told me > for the Firefox-Browser ? There is Internet Explorer Developer Toolbar ( http://tinyurl.com/dkmm9 ) but I doesn't show the AJAX requests and thus you can't detect what HTML is send to the server when you switch to Source tab. Hope this helps, Marius > > IE-Version: 7.0.5730.13CO > > Thanks > Norbert ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Problems with links
Hello, it seems to be a problem with the Internet Explorer. The whole time I worked with Firefox no problem appeares. Can you tell me if there is an analog Debug-Tool for the IE as you told me for the Firefox-Browser ? IE-Version: 7.0.5730.13CO Thanks Norbert -- View this message in context: http://n2.nabble.com/Problems-with-links-tp4435123p4453765.html Sent from the XWiki- Users mailing list archive at Nabble.com. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Problems with links
Hello, it seems to be a problem with the Internet Explorer. The whole time I worked with Firefox no problem appeares. Can you tell me if there is an analog Debug-Tool for the IE as you told me for the Firefox-Browser ? IE-Version: 7.0.5730.13CO Thanks Norbert -- View this message in context: http://n2.nabble.com/Problems-with-links-tp4435123p4453761.html Sent from the XWiki- Users mailing list archive at Nabble.com. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] REST services access to spaces & tags
Hello friends, I am facing some unexpected behavior with RESTful services in private wiki instance: Issue: Spaces, Tags entities can be accessed publicly through REST URL, eventhough XWiki is run in private wiki mode. Description: One of the XWiki 2.1.1 instance is setup in a private wiki mode. Guests are not allowed to register or view any page on this instance. I am also making use of authenticated services (RESTful services & XMLRPC services) for connecting 3rd party applications to this xwiki instance. However, when I access REST URLs for spaces, tags, etc there is no authentication check from XWiki. This data is publicly available. When I access a page URL, I am blocked off for authentication. Couldn't find a JIRA for this one. Could we consider this as an non-consistent behavior in terms of xwiki REST authentication where one resource is blocked while others are not. Has anyone else faced this before or has a work-around to this issue. Thank you for your time & consideration friends. Environment: XWiki : 2.1.1 stable Tomcat: 6.0.20 MySql: 5.0.45 community JDK: 1.5 (Apparently, REST services do not work for me through JDK 1.6. This could be just me facing this issue though J) ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] [ANN] XOffice 1.1 M1 Released!
The XWiki development team is pleased to announce the release of XWiki Office 1.1 Milestone 1. Go grab it at: http://www.xwiki.org/xwiki/bin/view/Main/Download#HXWikiOffice Summary of changes: - support for on page style extensions - more powerful text formatting - fixed encoding issues Updating: - active instances of 1.1 snapshots are automatically updated - the 1.1 new features updates will be pushed when version 1.1 final will be available - the 1.0 bugfixes will be pushed during the 1.1 development cycle. View detailed release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXOffice11M1 For more information about XOffice visit: http://xoffice.xwiki.org/xwiki/bin/view/Main/WebHome Thanks, -The XWiki dev team ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] wiki editor doesn' t work
jackyork wrote: > I have posted a few questions here and I really appreciated your replies. I > just received the 1,000,001 error from this XWiki program when I was trying > to switch editor from WYSIWYG to WIKI. This error must be a result of some > old version libs. I have excluded beanutil.jar and xercesImpl.jar. What do you mean by excluded? Is "Xerces-J 2.8.1" detected as pointed out in http://lists.xwiki.org/pipermail/users/2010-January/018949.html ? This library is needed so don't remove entirely, just make sure the right version is loaded (i.e. remove only the jars that correspond to an older/incorrect version). Hope this helps, Marius > > Again the error info: > > Jan 24, 2010 10:46:38 PM org.apache.tomcat.util.http.Parameters > processParameters > WARNING: Parameters: Invalid chunk ignored. > 2010-01-24 22:46:38,351 [] > [http://secure10.olemiss.edu/xwiki/bin/edit/Main/WebHome?editor=wiki&&$param] > ERROR [/xwiki].[action] - Servlet.service() for servlet action > threw exception > java.lang.NoSuchFieldError: fFeatures > at > org.apache.xerces.parsers.XML11NonValidatingConfiguration.(Unknown > Source) > at > org.apache.xerces.parsers.XML11NonValidatingConfiguration.(Unknown > Source) > at sun.reflect.GeneratedConstructorAccessor116.newInstance(Unknown > Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:494) > at java.lang.Class.newInstance0(Class.java:350) > at java.lang.Class.newInstance(Class.java:303) > at > org.xwiki.xml.internal.DefaultXMLReaderFactory.createXMLReader(DefaultXMLReaderFactory.java:81) > at > org.xwiki.rendering.internal.util.XWikiXMLReaderFactory.createXMLReader(XWikiXMLReaderFactory.java:50) > at > org.xwiki.rendering.internal.parser.WikiModelXHTMLParser.createWikiModelParser(WikiModelXHTMLParser.java:154) > at > org.xwiki.rendering.internal.parser.wikimodel.AbstractWikiModelParser.parse(AbstractWikiModelParser.java:86) > at > org.xwiki.rendering.internal.parser.WikiModelXHTMLParser.parse(WikiModelXHTMLParser.java:111) > at > com.xpn.xwiki.wysiwyg.server.converter.internal.DefaultHTMLConverter.fromHTML(DefaultHTMLConverter.java:100) > at > com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:117) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:117) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at > com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at > com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:295) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at > com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) > at > org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200) > at > org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) > at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773) > at > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703) > at > org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:895) > at > org.apache.tomcat.util.threads.ThreadPool$Con
Re: [xwiki-users] [myxwiki] new wiki request
On Fri, Jan 22, 2010 at 07:32, Morin Maxim wrote: > > Hi, > > my friend and I are stuying in science teaching and we have to build a wiki > for a school project. For this project, I will like to have a wiki name : > lamaisonverte. > > My username is p0825828. Here is your new wiki: http://lamaisonverte.myxwiki.org > > Thanks, > > Maxim > ___ > users mailing list > users@xwiki.org > http://lists.xwiki.org/mailman/listinfo/users > -- Thomas Mortagne ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Blog: Showing teasers inline on a wiki page
Hi there, Vincent Massol wrote: > Hi Rick, > > On Jan 24, 2010, at 7:50 PM, Rick Hadsall wrote: > >> Guillaume Lerouge wrote: >>> Yes, definitely. The blog actually used to do this but we changed it some >>> time ago because when content got truncated sometimes markup was no longer >>> closed properly, which led to wome weird display on the blog homepage (half >>> of the text getting underlined, stuff like that). >>> >>> With the new rendering engine, it could be possible to write a "smart" >>> snippet algorithm that would cut the markup in the right place. In the >>> default version, you'll notice that if you manually fill the "summary" field >>> of a blog post it gets displayed on the blog homepage instead of the actual >>> article content, which I believe is close to the behavior you're looking >>> for. If that's what you want to do, follow the indications on >>> http://code.xwiki.org/xwiki/bin/view/Applications/BlogApplication to create >>> a blog out of any page. >>> >> OK. I'll give this a try. In theory the engine could be smart enough >> to know if it is going to truncate in the middle of markup and adjust >> accordingly, but having people provide a summary is a decent alternative. >> >> But what I'm trying to do is create the blogs, but then be able to list >> the blogs on another regular wiki/content page - either in a list or a >> summary format. I don't want to force the user to go to the "blog" page >> to get the teasers for that content - I'd like to be able to tease the >> content on another page or two (where relevant, by category, or blog, >> etc) and let them click to read the full thing. >>> By the way, I'd be interested in hearing your feedback about XWiki as >>> compared to Confluence. Specifically, if you were to name one thing you like >>> best in XWiki vs Confluence and one thing you like best in Confluence >>> compared to XWiki, what would those be? > > First let me thank you a lot for the feedback, that's really useful for us. > >> Well, it's probably too soon to tell as I'm very new with XWiki and very >> comfortable with Confluence. My sense is that XWiki has a long way to >> go - Confluence's markup language is excellent, > > In term of markup language, we had XWiki syntax 1.0 which was close to > confluence's syntax (since both depended on Radeox). However we've seen lots > of limitations and have created XWiki Syntax 2.0 which we believe is the most > powerful markup language (basically we can do back and forth from HTML and > not loose content which isn't true for the other syntaxes we know of). > > The new syntax is described here: > http://platform.xwiki.org/xwiki/bin/view/Main/XWikiSyntax > > I'd be happy to know if you still think there are things better done in the > confluence syntax and that xwiki's syntax cannot do (I believe the opposite > is true). > > Also, to be noted, is that XWiki is polyglot ie it supports several syntaxes, > amongst which Confluence syntax (although if you use it you won't be able to > use our new WYSIWYG editor since right now it only supports XWiki Syntax 1.0). Correction: the new WYSIWYG editor works best with XWiki Syntax 2.0 but it's not restricted to this syntax. The WYSIWYG editor understands and produces annotated XHTML thus it can work with any syntax that has a parser from and a renderer to annotated XHTML. Of course, if the storage syntax is less powerful than XHTML you'll loose information during page save. The editor can be adjusted to restrict some XHTML constructs in order to reduce the information loss. > >> and you can do pretty >> much anything you want with the macros they provide and the parameters >> for them. > > I agree that confluence has an edge in term of number of macros. Where XWiki > catches up I believe is with the ability to write velocity/groovy/ruby/python > scripts directly in pages along with a powerful API accessible from theses > scripting language which makes it relatively easy to script any missing > macro. However this is no substitute for more macros since standard users may > not have the skills to write such scripts. > >> For example with the blog issue you simply use the blog macro >> on any page and pass it the parameters for which blogs you want >> (category, space, date ranges, what kind of listing, etc) and voila. > > I remember using the confluence blog a long time ago (around 2005) and I > didn't like it because it was something part of the Confluence core and you > couldn't modify it to your needs. For example it had not ability to modify > the date of a post (that's probably been added since then) and there was no > way I could add it (except to go in java dev mode and rewrite the blog > provided I had access to the sources). In XWiki the blog application is > contained in wiki pages and you can edit them and modify them to suit your > exact needs, where needed. > > In due time we'll probably make the most obvious features avail
Re: [xwiki-users] Is it possible to programatically change xwiki class properties
hi Radek,
On 01/25/2010 07:21 AM, Radek Rekas wrote:
> Hi,
>
> I am trying to change the values for a static list field in a wiki class
> programatically but so far I have only figured out how to display them. Is it
> possible to set class property values for static list fields programatically
> through velocity or groovy code?
yes, it is possible but you will need programming rights for that.
>
> The code that I'm using to display the values is pasted below:
> #set($classdocname = "Test.TestClass")
> #set($classdoc = $xwiki.getDocument($classdocname))
> #foreach($field in $classdoc.getxWikiClass().properties)
> * $field.prettyName
why iterating here? You should just
#set($field = $classdoc.getxWikiClass().get("name of your static list property
here"))
see http://platform.xwiki.org/xwiki/bin/view/DevGuide/API for the API (the
'core' part)
> $doc.displayEdit($field.xWikiClass.get("values"), "${field.name}_" , $field)
I couldn't say I really understand how this line displays the values of the
property...
However, in order to change them, you need to use the protected PropertyClass
(com.xpn.xwiki.objects.classes.PropertyClass) of the $field, namely:
$field.propertyClass
which will be of type com.xpn.xwiki.objects.classes.StaticListClass if your
field is a static list. Then you just play around with its values using:
$field.propertyClass.values
(for display) and
#set($field.propertyClass.values = "val1|val2|val3")
for edit.
Happy hacking,
Anca
> #end
>
> Thanks,
>
>
> Radek
> ___
> users mailing list
> users@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Lucene defaultpage fails
On Mon, Jan 25, 2010 at 10:00, Petteri Karttunen
wrote:
> Hello,
> I've been running xwiki with "log4j.logger.com.xpn.xwiki.plugin.lucene=debug"
> now for some days. The problem has occurred several times but I've nothing in
> my logs. Is there something else I could do/debug?
As i said i doubt "log4j.logger.com.xpn.xwiki.plugin.lucene=debug"
bring anything since Lucene plugin does not print any debug log (or
almost nothing and not useful here).
Only part of the code i see where it's possible to have the variable
null (which makes it produce a nullpointerexception) are supposed to
be covered by an error log at some point (not when you look at the
page but before). I can't see how you could have this issue if nothing
goes wrong and is then logged.
> -Pete
>
> -Alkuperäinen viesti-
> Lähettäjä: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] Puolesta
> Thomas Mortagne
> Lähetetty: 20. tammikuuta 2010 19:28
> Vastaanottaja: XWiki Users
> Aihe: Re: [xwiki-users] Lucene defaultpage fails
>
> On Wed, Jan 20, 2010 at 17:12, Petteri Karttunen
> wrote:
>> I wish there was more info in my logs...I paused actively watching and
>> debugging this one few weeks ago because of the workaround (reinitializing
>> the plugin when needed in a groovy try{...getQueueSize()...} catch -block on
>> a search page). As far as I can remember there wasn't any lucene-errors in
>> my logs at the time and the search clearly returned 0 hits according to
>> logs. To be sure I'll put the debugging options on again and let you know
>> the results as soon as the problem occurs again. Are these enough?:
>>
>> log4j.logger.com.xpn.xwiki.plugin.lucene.IndexData=debug
>> log4j.logger.com.xpn.xwiki.plugin.lucene.DocumentData=debug
>> log4j.logger.com.xpn.xwiki.plugin.lucene.IndexUpdater=debug
>> log4j.logger.com.xpn.xwiki.plugin.lucene.IndexRebuilder=debug
>> log4j.logger.com.xpn.xwiki.plugin.lucene.LucenePlugin=debug
>> log4j.logger.com.xpn.xwiki.plugin.lucene.SearchResults=debug
>> log4j.logger.com.xpn.xwiki.plugin.lucene.SearchResult=debug
>
> You can use
>
> log4j.logger.com.xpn.xwiki.plugin.lucene=debug
>
> I think but AFAIK there is almost no debug log in Lucene plugin.
>
>>
>> I haven't examined the code thoroughly so probably a missed shot but is
>> there any chance that this could be a method synchronization issue with
>> searchers and writers?
>> -Pete
>>
>> -Alkuperäinen viesti-
>> Lähettäjä: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] Puolesta
>> Thomas Mortagne
>> Lähetetty: 20. tammikuuta 2010 17:14
>> Vastaanottaja: XWiki Users
>> Aihe: Re: [xwiki-users] Lucene defaultpage fails
>>
>> On Wed, Jan 20, 2010 at 16:01, Petteri Karttunen
>> wrote:
>>> Everything I could find was this one problem in closing the writer:
>>>
>>> 23:00:06,242 [Lucene index updating thread] [Lucene Index Updater] WARN
>>> lucene.IndexUpdater - Failed to close writer.
>>>
>>> I forgot to mention another symptom suggesting index reading problems: when
>>> the situation is on I can do Lucene-queries (custom search page wo
>>> getQueueSize()) but it just doesn't return anything. So the plugin kind of
>>> "works" but "seems" not to be able to read indexes properly.
>>
>> As far as i can see in the code all search* methods in the public api
>> are "protected" from any Exception and return null when something
>> wrong happen. But it also log the error so when you do a failing
>> search you should have something in the log.
>>
>>> -Pete
>>>
>>>
>>> -Alkuperäinen viesti-
>>> Lähettäjä: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org]
>>> Puolesta Thomas Mortagne
>>> Lähetetty: 20. tammikuuta 2010 15:48
>>> Vastaanottaja: XWiki Users
>>> Aihe: Re: [xwiki-users] Lucene defaultpage fails
>>>
>>> For your informations: as far as i can see in the code there is only
>>> one way to have the IndexUpdater to null (whichgenerate a
>>> nullpointerexcetion in #getQueueSize) is when during the init the
>>> index can't be opened. In this case you should find a log looking like
>>> this:
>>>
>>> "Failed to open the index directory: " followed with a message
>>> detailing a little why it can't open index directory.
>>>
>>> (so indeed it could be caused by the fact that no more inode can be
>>> used on linux for example).
>>>
>>> Could you look if you can find this error anywhere in the log ?
>>>
>>> On Tue, Jan 19, 2010 at 13:48, Thomas Mortagne
>>> wrote:
On Tue, Jan 19, 2010 at 13:26, Petteri Karttunen
wrote:
> Hello,
>
> My issues seem to happen randomly but not at startup. Plugin works well
> from some hours to some days but I'm not sure what triggers this. I
> haven't been able to debug anything of interest in plugin's logs.
>
> Only potential clue I have is that plugin is leaving index files open
> which -at least- leads Tomcat finally to "too many files open" -error at
> some point. lsof | grep "lucene" gives me a bunch of these:
>
>
Re: [xwiki-users] Lucene defaultpage fails
Hello,
I've been running xwiki with "log4j.logger.com.xpn.xwiki.plugin.lucene=debug"
now for some days. The problem has occurred several times but I've nothing in
my logs. Is there something else I could do/debug?
-Pete
-Alkuperäinen viesti-
Lähettäjä: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] Puolesta
Thomas Mortagne
Lähetetty: 20. tammikuuta 2010 19:28
Vastaanottaja: XWiki Users
Aihe: Re: [xwiki-users] Lucene defaultpage fails
On Wed, Jan 20, 2010 at 17:12, Petteri Karttunen
wrote:
> I wish there was more info in my logs...I paused actively watching and
> debugging this one few weeks ago because of the workaround (reinitializing
> the plugin when needed in a groovy try{...getQueueSize()...} catch -block on
> a search page). As far as I can remember there wasn't any lucene-errors in my
> logs at the time and the search clearly returned 0 hits according to logs. To
> be sure I'll put the debugging options on again and let you know the results
> as soon as the problem occurs again. Are these enough?:
>
> log4j.logger.com.xpn.xwiki.plugin.lucene.IndexData=debug
> log4j.logger.com.xpn.xwiki.plugin.lucene.DocumentData=debug
> log4j.logger.com.xpn.xwiki.plugin.lucene.IndexUpdater=debug
> log4j.logger.com.xpn.xwiki.plugin.lucene.IndexRebuilder=debug
> log4j.logger.com.xpn.xwiki.plugin.lucene.LucenePlugin=debug
> log4j.logger.com.xpn.xwiki.plugin.lucene.SearchResults=debug
> log4j.logger.com.xpn.xwiki.plugin.lucene.SearchResult=debug
You can use
log4j.logger.com.xpn.xwiki.plugin.lucene=debug
I think but AFAIK there is almost no debug log in Lucene plugin.
>
> I haven't examined the code thoroughly so probably a missed shot but is there
> any chance that this could be a method synchronization issue with searchers
> and writers?
> -Pete
>
> -Alkuperäinen viesti-
> Lähettäjä: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] Puolesta
> Thomas Mortagne
> Lähetetty: 20. tammikuuta 2010 17:14
> Vastaanottaja: XWiki Users
> Aihe: Re: [xwiki-users] Lucene defaultpage fails
>
> On Wed, Jan 20, 2010 at 16:01, Petteri Karttunen
> wrote:
>> Everything I could find was this one problem in closing the writer:
>>
>> 23:00:06,242 [Lucene index updating thread] [Lucene Index Updater] WARN
>> lucene.IndexUpdater - Failed to close writer.
>>
>> I forgot to mention another symptom suggesting index reading problems: when
>> the situation is on I can do Lucene-queries (custom search page wo
>> getQueueSize()) but it just doesn't return anything. So the plugin kind of
>> "works" but "seems" not to be able to read indexes properly.
>
> As far as i can see in the code all search* methods in the public api
> are "protected" from any Exception and return null when something
> wrong happen. But it also log the error so when you do a failing
> search you should have something in the log.
>
>> -Pete
>>
>>
>> -Alkuperäinen viesti-
>> Lähettäjä: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] Puolesta
>> Thomas Mortagne
>> Lähetetty: 20. tammikuuta 2010 15:48
>> Vastaanottaja: XWiki Users
>> Aihe: Re: [xwiki-users] Lucene defaultpage fails
>>
>> For your informations: as far as i can see in the code there is only
>> one way to have the IndexUpdater to null (whichgenerate a
>> nullpointerexcetion in #getQueueSize) is when during the init the
>> index can't be opened. In this case you should find a log looking like
>> this:
>>
>> "Failed to open the index directory: " followed with a message
>> detailing a little why it can't open index directory.
>>
>> (so indeed it could be caused by the fact that no more inode can be
>> used on linux for example).
>>
>> Could you look if you can find this error anywhere in the log ?
>>
>> On Tue, Jan 19, 2010 at 13:48, Thomas Mortagne
>> wrote:
>>> On Tue, Jan 19, 2010 at 13:26, Petteri Karttunen
>>> wrote:
Hello,
My issues seem to happen randomly but not at startup. Plugin works well
from some hours to some days but I'm not sure what triggers this. I
haven't been able to debug anything of interest in plugin's logs.
Only potential clue I have is that plugin is leaving index files open
which -at least- leads Tomcat finally to "too many files open" -error at
some point. lsof | grep "lucene" gives me a bunch of these:
...
java.bin 10095 tomcat 666r REG 104,1 60931511 15634869
/srv/www/DATA/xwiki/lucene/_5r7.cfs (deleted)
java.bin 10095 tomcat 667r REG 104,1 60931507 15634870
/srv/www/DATA/xwiki/lucene/_5r9.cfs (deleted)
java.bin 10095 tomcat 668r REG 104,1 60931507 15634871
/srv/www/DATA/xwiki/lucene/_5rb.cfs (deleted)
...
>>>
Also, xwiki gets the plugin object normally during the malfunctional state
but it seems it just cannot read index. Could it be that the plugin
becomes unusable not before a deleted index file becomes overwritten by
the
