We've made a modest contribution to the cathedral: threaded comments,
committed in the xwiki-sandbox. It mainly consists in the addition of
the class "com.xpn.xwiki.util.TreeNode" used for storing a tree
structure composed of XWiki objects linked to one another via any given
property. In the case of XWikiComments, that property is the "replyto"
property. The display is managed by a CSSed list, see the addition to
xwiki.css and wiki.css, as well as a Groovy script available in
xwiki-sandbox/threaded-comments as well.
See the feature in action at this page for instance:
http://club.mandriva.com/xwiki/bin/view/Main/SpreadAcademia
Stéphane and Christophe
at your disposal for further info!
--
Stéphane Laurière
slauriere(a)mandriva.com
Mandriva Club - http://club.mandriva.com
Mandrakesoft becomes Mandriva!
I wrote a groovy script for xwiki which allows one to speed up use of
tinymce by gzipping all the javascript files into a single stream -
based on the tiny_mce_gzip.php script available from tinymce. I
wasn't sure where to put it in the wiiki, so figured I'd post it here :)
Haven't tried it with the wysiwyg stuff Pedro is working on yet, but
it will probably need some tweaking.
Matt
I took the FAQ on Rights Management and made a first-pass attempt to
improve it. It would help if someone could look at it and make sure I have
not misunderstood anything. It needs more work. This is just step one.
http://www.xwiki.org/xwiki/bin/view/AdminGuide/Rights+Management
Also, i would LOVE to rewrite the following section, but in order to do
so, i would need to see the actual code that does this routine. Does
anyone know where the code behind this part is? ...
Evaluation Order
Here 'user' means 'user or a group containing the user':
1. Check if the user has the 'admin' right at the XWiki level -> if
so continue...
2. Check if the user has the 'admin' right at the Space level -> if
so continue...
3. Check if the user is denied access to the current document through
the 'deny' right for the document -> if so drop out negatively. If not,
then if a deny right exists for others users remember it.
4. Check if the user is allowed access to the current document
through the 'allow' right in the document -> if so drop out positively. If
not, then if a deny right exists for others users remember it.
5. Check if the user is denied access to the wiki space through the
'deny' right in the WebPreferences document for that space -> if so drop
out negatively. If not, then if a deny right exists for others users
remember it.
6. Check if the user is allowed access to the wiki space through the
'allow' right in the WebPreferences document for that space -> if so drop
out positively. If not, then if a deny right exists for others users
remember it.
7. Check if the user is denied access at the XWiki level through the
'deny' right in the XWiki.XWikiPreferences document -> if so drop out
negatively. If not, then if a deny right exists for others users remember
it.
8. Check if the user is allowed access at the XWiki level through the
'allow' right in the XWiki.XWikiPreferences document -> if so drop out
positively. If not, then if a deny right exists for others users remember
it.
==================================
Cody Burleson
IBM, Business Consulting Services
On Demand Workplaces
"Simplifying access to content, applications, people and processes."
Current Client Office (Mon - Thur): (404) 828-4583
Home Office [Friday, Sat. Sun. or email a voice message]: (214) 233.3546
Cell [anytime]: (214) 537-8783
Email: cburleso(a)us.ibm.com
Hi Tim,
I missed that one.. To make xwiki cluster aware the following things
need to be worked on / checked
- Structures that are used for cache and which could contain data that
can be changed should be moved to an XWikiCache object.. I think only
the stats module currently has some data like that (it's possible to
deactivate stats also). XWikiCacheStore and XWikiGroupServiceImpl
currently use such XWikiCache structures.
- Then XWikiCache, which users OSCache, needs to be configured for
broadcasting changes on the cluster. This means looking at how OSCache
should be configured for this. I think the JGroups broadcast would be fine..
Otherwise from that, good testing should be done and check if anything
else comes up..
We can definitively provide some support if you put some developer
resources on this..
Ludovic
Tim Suter wrote:
> Hi Ludovic,
>
> If you follow the thread here, you will see I am interested in finding a
> solution for the cluster problem.
>
> Thanks,
> Tim Suter
>
>
> ------------------------------------------------------------------------
>
> Subject:
> Re: xwiki in a test cluster
> From:
> jeremi joslin <jeremi23(a)gmail.com>
> Date:
> Tue, 13 Sep 2005 18:47:25 +0200
> To:
> Tim Suter <tsuter(a)cait.org>
>
> To:
> Tim Suter <tsuter(a)cait.org>
>
>
> Ok,
> Ask on the developper list. Ludovic will help you. I have no
> experience with clusters.
> The main problem for the cluster is the document cache I think.
>
> Jérémi
> On 9/13/05, Tim Suter <tsuter(a)cait.org> wrote:
>
>> Hello,
>>
>> I saw your response. I would like to know what needs to be changed. I do
>> not have much developer experience, but where I work, there is a staff of
>> developers on hand.
>>
>> Thanks,
>> Tim Suter
>>
>
>
>
>
--
Ludovic Dubost
XPertNet: http://www.xpertnet.fr/
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost AIM: nvludo Yahoo: ludovic
I notice that you get a stack dump if you try to create a blog of the same
page name. I could create some JavaScript validation in the blog form to
reduce this, but that is not elegant. How about appending a counter before
submitting to database when pages have the same name. Or how about using
GUIDs as the key instead of the page name. anything tro avoid getting
stack dumps. Is this issue logged in JIRA yet?
==================================
Cody Burleson
IBM, Business Consulting Services
On Demand Workplaces
"Simplifying access to content, applications, people and processes."
Current Client Office (Mon - Thur): (404) 828-4583
Home Office [Friday, Sat. Sun. or email a voice message]: (214) 233.3546
Cell [anytime]: (214) 537-8783
Email: cburleso(a)us.ibm.com
Has anyone had any success using the Backup / Restore features of the
MySQL Administrative Client on an XWiki database? I get the following
errors when trying to restore (see attached)...
==================================
Cody Burleson
On 9/12/05, Matthew Conway <conway(a)tripadvisor.com> wrote:
>
> On Sep 12, 2005, at 11:58 AM, jeremi joslin wrote:
> >
> > No it's just a set of wiki document.
> >
>
> Does that mean you used xwiki's class system to implement it, or is
> it a set of first class data types?
>
I use XWiki class system and objects to store data.
Jérémi
--
portable : 06.73.20.11.49
http://www.jeremi.infohttp://www.xwiki.com - http://www.moovement.com
skype: jeremi23
Hi, Only recently I started getting the following error (I updated the
source from the repository) when I use xwiki locally (using resin). Any
help with how I can fix it ?
thanks,
Bikash
--------------- error log --------------------------------
12:51:03,411 WARN XWikiAction:154 - Uncaught exception: Error number 0
in 11: Uncaught exception
Wrapped Exception: Can't find bundle for base name ApplicationResources,
locale en
com.xpn.xwiki.XWikiException: Error number 0 in 11: Uncaught exception
Wrapped Exception: Can't find bundle for base name ApplicationResources,
locale en
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:135)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:115)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:92)
at
com.caucho.server.dispatch.ServletFilterChain.doFilter(ServletFilterChain.java:99)
at
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:127)
at
com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:70)
at
com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:163)
at
com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:208)
at
com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:259)
at com.caucho.server.port.TcpConnection.run(TcpConnection.java:363)
at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:490)
at com.caucho.util.ThreadPool.run(ThreadPool.java:423)
at java.lang.Thread.run(Thread.java:595)
I am writing a Groovy script to run in an XWiki page. It needs to output
binary data (a PDF). I know how to
response.setContentType("application/pdf");
but how do I prevent the XWiki engine from outputting the normal page
header/footer? I want to take total control of the page output. Any tips
would be appreciated!
Stephen
I've implemented support for pluggable URL factories.
It should be a fairly low impact change, as the default is to use the
current behavior.
Should I post a patch here for review before committing?
In short, there is now an XWikiURLFactoryService (also pluggable)
which is responsible for creating the XWikiUrlFactory for the given
mode (XWikiContext.getMode()) . I made XWikiURLFactoryService
pluggable as well to allow one to allow one to create the url
factories however desired, but its default implementation copies the
way they are current constructed.
Matt
Shouldn't the velocity macro $xwiki.getRequestUrl() return a url
thats been passed through a URLFactory?
I'm having a issue with the editrights.vm page creating a redirect
that goes to the wrong place.
If I'm correct on this, then should it be com.xpn.xwiki.api.XWiki
that passes it through the URLFactory, or should com.xpn.xwiki.XWiki
do it, i.e. does changing it in the impl class cause any side
effects, e.g. in Utils.prepareContext() or XWikiHibernateStore?
Matt