Re: [xwiki-users] This object is currently locked by - section editing
HI Piotr,
On Thu, Nov 18, 2010 at 10:57 AM, Piotr Dziubecki wrote:
> Hi Joris,
>
> I think that you can accomplish your scenario partially by using the
> following macro:
>
> {{include document="TestPage2"/}}
>
> That will give you another page linked into yours in the 'in-line' mode.
> Unfortunately you cannot edit such
> page from the context of your main document.
Thanks, that's indeed the modus we are using right now. Yet it isn't
easy enough :)
> W dniu 10-11-18 00:56, Joris Dirks wrote:
>> Real-time editing would be great, but IMHO a real tough job to
>> accomplish with a complicated markup language as XWiki's. Section
>> editing is to me/us a great one, too. I'd go even further: in my frame
>> of mind, a section is nothing different from a page.
>> I see many users finnicking around, not sure if they should put
>> everything on a topic in one page with headers, or splitting the text
>> in different pages.
>>
>> As we already have hierarchy, it would make sense to me to let users
>> just create a new 'sub-page' below their current content. That
>> sub-page is, in the data model, just a child with a weight set; for
>> the original page, a property is set like: "content splitted in child
>> pages, include every child in order of ascending weight".
>
> In fact, before I migrated to XWiki I wanted to use Wiki from Liferay and
> since their implementation doesn't
> support sections at all, I had a plan to substitute them like in your idea.
> Unfortunately this cannot be
> done without an application model redesign ( like how to handle subdocument
> reindexing if you add/remove
> something from the middle of structure etc. ).
>
> What I want to say is that currently I'd opt for the simplest solutions
> because they don't need a lot of
> work with implementation :)
>
> Regards,
> Piotr
>
>>
>> Did I make any sense to you guys?
>>
>>
>> On Sat, Nov 13, 2010 at 9:50 AM, Ricardo Rodriguez [eBioTIC.]
>> wrote:
>>>
>>>
>>> Piotr Dziubecki wrote:
W dniu 10-11-04 21:28, [Ricardo Rodriguez] eBioTIC. wrote:
> Piotr Dziubecki wrote:
>
>> W dniu 10-11-04 12:13, [Ricardo Rodriguez] eBioTIC. wrote:
>>
>>
>>> Piotr Dziubecki wrote:
>>>
>>>
Hi :)
W dniu 10-11-04 11:08, [Ricardo Rodriguez] eBioTIC. wrote:
> Hi!
>
> Piotr Dziubecki wrote:
>
>
>
>> Hello :)
>>
>> I configured my XWiki instance in the following way:
>>
>>
>>
>> #-# This parameter will activate the sectional editing.
>> xwiki.section.edit=1
>>
>> #-# This parameter controls the depth of sections that have section
>> editing.
>> #-# By default level 1 and level 2 sections have section editing.
>> xwiki.section.depth=6
>>
>>
>> I have many users working on documents simultaneously and in order
>> to minimize document locking and possible
>> merging I encourage them to edit sections/paragraphs instead. I
>> noticed that when, for instance, two users
>> edit different sections within the same page, the latter gets the
>> message:
>>
>> This object is currently locked by user1
>>
>> I checked and it's possible to force editing and save both of
>> concurrent changes to that document, but the
>> message itself is a bit confusing to the users. I'm asking if it's
>> possible to change xwiki configuration to
>> not display that message when the users edit different paragraphs
>> within the same page ?
>>
>>
>>
> To the best of my understanding locking is set a document level. So,
> if
> any user edits a section, all other users will receive that message.
>
> I think what you are doing is a bit risky. I've had here some problems
> following the same problem. When an user received this message,
> although
> she/he is editing only a section, there is no way of knowing if they
> are
> in the same section or in a different one. Even more, if you edit a
> document using the same user at two different locations, you won't
> receive the locking message.
>
>
>
Yes, I came from the Media Wiki and section editing is pretty popular
way of collaborative editing (
avoiding the whole page locks ).
>>> I also arrives to XWiki from MediaWiki years ago. So, with the current
>>> MediaWiki release, is it possible to do section edition and get a
>>> warning only if two users edit the same section?
>>>
>>> Thanks!
>>>
>>>
>> To be sure, I did some tests here:
>>
>> http://www.mediawiki.org/wiki/Sandbox
>>
>> no warnings, you can even edit the same sec
Re: [xwiki-users] component manager not initialized after install
Hi Scott, On 11/18/2010 01:50 PM, Scott McMasters wrote: > Any thoughts on this problem? It looks like XWikiServletContextListener (which is responsible for initialising the component manager) is not called. Do you have it in your web.xml? Hope this helps, Marius > > Thanks, > > Scott > > > On Tue, Nov 16, 2010 at 11:30 AM, Scott McMasters> wrote: > >> Hi, Jerome, this is the only stack trace I have in my system log: >> >> Exception thrown : javax.servlet.ServletException: Component manager has >> not been initialized before lookup for >> [org.xwiki.model.reference.DocumentReferenceResolver] for hint >> [currentmixed] >> at >> org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:535) >> at >> org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:433) >> at >> org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) >> at >> org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) >> at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) >> at >> com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1143) >> at >> com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1084) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145) >> at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:129) >> at >> com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) >> at >> com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:152) >> at >> com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) >> at >> com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68) >> at >> com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) >> at >> org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:218) >> at >> com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) >> at >> org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) >> at >> com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:832) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679) >> at >> com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:587) >> at >> com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481) >> at >> com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3453) >> at >> com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267) >> at >> com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815) >> at >> com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466) >> at >> com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:119) >> at >> com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458) >> at >> com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387) >> at >> com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102) >> at >> com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) >> at >> com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) >> at >> com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) >> at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136) >> at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196) >> at >> com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751) >> at com.ibm.io.async.ResultHandler$2.run(ResultHan
[xwiki-users] [myxwiki] How do I change the logo in a skin?
Hello, To change the logo, you can either use the current color theme (see here the documentation: http://code.xwiki.org/xwiki/bin/view/Applications/ColorThemeApplication) or you can attach the logo to your skin document - XWiki.DefaultSkin by default - (see here the documentation about skins: http://platform.xwiki.org/xwiki/bin/view/DevGuide/Skins). If you use the skin document, It's better to name the logo file 'logo.png'. This way you will override the XWiki logo. Otherwise, make sure that the skin knows where to take the logo from -> edit Administration preferences and set 'logo' property as being the name of your logo. Raluca. On Thu, Nov 18, 2010 at 2:58 PM, Jonathan @ Crindau wrote: > Hi, > > I am currently using the Colibri skin and would like to change the logo. > To where do I download the new image (and how) so that I can then > reference it in the Wiki's skin 'logo' object? > > Thanks > > > > ___ > 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
[xwiki-users] [myxwiki] How do I change the logo in a skin?
Hi, I am currently using the Colibri skin and would like to change the logo. To where do I download the new image (and how) so that I can then reference it in the Wiki's skin 'logo' object? Thanks ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] component manager not initialized after install
Any thoughts on this problem? Thanks, Scott On Tue, Nov 16, 2010 at 11:30 AM, Scott McMasters wrote: > Hi, Jerome, this is the only stack trace I have in my system log: > > Exception thrown : javax.servlet.ServletException: Component manager has > not been initialized before lookup for > [org.xwiki.model.reference.DocumentReferenceResolver] for hint > [currentmixed] > at > org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:535) > at > org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:433) > at > org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) > at > org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) > at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) > at > com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1143) > at > com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1084) > at > com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145) > at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:129) > at > com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) > at > com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) > at > com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:152) > at > com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) > at > com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) > at > com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68) > at > com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) > at > com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) > at > org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:218) > at > com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) > at > com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) > at > org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) > at > com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) > at > com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) > at > com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87) > at > com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:832) > at > com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679) > at > com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:587) > at > com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481) > at > com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3453) > at > com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267) > at > com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815) > at > com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466) > at > com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:119) > at > com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458) > at > com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387) > at > com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102) > at > com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) > at > com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) > at > com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) > at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136) > at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196) > at > com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751) > at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881) > at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473) > > Thanks again, > > Scott > > > > On Sun, Nov 14, 2010 at 12:59 AM, Jerome Velociter wrote: > >> Hi Scott, >> >> Would you happen to have a full stack-trace you could point us to ? >> >> Can you see any nested error related to a DTMManager ? >> >> Thanks, >> Jerome. >> >> On Fri, Nov 12, 2010 at 8:
Re: [xwiki-users] This object is currently locked by - section editing
Hi Joris,
I think that you can accomplish your scenario partially by using the following
macro:
{{include document="TestPage2"/}}
That will give you another page linked into yours in the 'in-line' mode.
Unfortunately you cannot edit such
page from the context of your main document.
W dniu 10-11-18 00:56, Joris Dirks wrote:
> Real-time editing would be great, but IMHO a real tough job to
> accomplish with a complicated markup language as XWiki's. Section
> editing is to me/us a great one, too. I'd go even further: in my frame
> of mind, a section is nothing different from a page.
> I see many users finnicking around, not sure if they should put
> everything on a topic in one page with headers, or splitting the text
> in different pages.
>
> As we already have hierarchy, it would make sense to me to let users
> just create a new 'sub-page' below their current content. That
> sub-page is, in the data model, just a child with a weight set; for
> the original page, a property is set like: "content splitted in child
> pages, include every child in order of ascending weight".
In fact, before I migrated to XWiki I wanted to use Wiki from Liferay and since
their implementation doesn't
support sections at all, I had a plan to substitute them like in your idea.
Unfortunately this cannot be
done without an application model redesign ( like how to handle subdocument
reindexing if you add/remove
something from the middle of structure etc. ).
What I want to say is that currently I'd opt for the simplest solutions because
they don't need a lot of
work with implementation :)
Regards,
Piotr
>
> Did I make any sense to you guys?
>
>
> On Sat, Nov 13, 2010 at 9:50 AM, Ricardo Rodriguez [eBioTIC.]
> wrote:
>>
>>
>> Piotr Dziubecki wrote:
>>> W dniu 10-11-04 21:28, [Ricardo Rodriguez] eBioTIC. wrote:
>>>
Piotr Dziubecki wrote:
> W dniu 10-11-04 12:13, [Ricardo Rodriguez] eBioTIC. wrote:
>
>
>> Piotr Dziubecki wrote:
>>
>>
>>> Hi :)
>>>
>>>
>>> W dniu 10-11-04 11:08, [Ricardo Rodriguez] eBioTIC. wrote:
>>>
>>>
>>>
Hi!
Piotr Dziubecki wrote:
> Hello :)
>
> I configured my XWiki instance in the following way:
>
>
>
> #-# This parameter will activate the sectional editing.
> xwiki.section.edit=1
>
> #-# This parameter controls the depth of sections that have section
> editing.
> #-# By default level 1 and level 2 sections have section editing.
> xwiki.section.depth=6
>
>
> I have many users working on documents simultaneously and in order to
> minimize document locking and possible
> merging I encourage them to edit sections/paragraphs instead. I
> noticed that when, for instance, two users
> edit different sections within the same page, the latter gets the
> message:
>
> This object is currently locked by user1
>
> I checked and it's possible to force editing and save both of
> concurrent changes to that document, but the
> message itself is a bit confusing to the users. I'm asking if it's
> possible to change xwiki configuration to
> not display that message when the users edit different paragraphs
> within the same page ?
>
>
>
To the best of my understanding locking is set a document level. So, if
any user edits a section, all other users will receive that message.
I think what you are doing is a bit risky. I've had here some problems
following the same problem. When an user received this message,
although
she/he is editing only a section, there is no way of knowing if they
are
in the same section or in a different one. Even more, if you edit a
document using the same user at two different locations, you won't
receive the locking message.
>>> Yes, I came from the Media Wiki and section editing is pretty popular
>>> way of collaborative editing (
>>> avoiding the whole page locks ).
>>>
>>>
>> I also arrives to XWiki from MediaWiki years ago. So, with the current
>> MediaWiki release, is it possible to do section edition and get a
>> warning only if two users edit the same section?
>>
>> Thanks!
>>
>>
> To be sure, I did some tests here:
>
> http://www.mediawiki.org/wiki/Sandbox
>
> no warnings, you can even edit the same section but then you'll need to
> get through the merge phase. In that
> case you see such a message:
>
> Someone else has changed this page since you started editing it. The
> upper text area contains the page text
> as it currently exists. Your changes are shown in the lower text area.
>>>
