[xwiki-users] Using parseGroovyFromPage on inherited class

Hi, I have another problem. I want to use a class that extends a parent class and then use parseGroovyFromPage. But I can't work out how to do it. An example here: - page ParentObject: <% class ParentObject { def counter = 0;

Re: [xwiki-users] Using parseGroovyFromPage on inherited class

Hi I think you'll need in your User class to use $xwiki.parseGroovyFromPage("ParentObject") Before that you need to pass $xwiki to User class. public class User extends ParentObject { private xwiki = null; void setUser() { if (session.getValue("counter") != null) this.counter =

[xwiki-users] Problems while registring users / using dot in usernames

Hello, I have seen that if I am using the register user popup (click on Add User from the Users screen), and if there is some kind of validation error on one of the fields I have just entered, the popup just dissapears (without displaying any error message). Accessing the following link (non p

[xwiki-users] [myxwiki] XWiki Enterprise 1.8 Upgrade

Hello, myxwiki.org has been upgraded to XE 1.8, if you own a wiki hosted there you should have a look at : http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise18 We also strongly recommend an upgrade to the latest wiki version. To upgrade you must download XE 1.8 XAR from : http:/

[xwiki-users] Recurrent exception in Tomcat's log file

Hello, I have XWiki turning on a Tomcat server and I was surprised about de 500ko stdout log file. I have seen that there is an error that keeps repeating in this log file: [ERROR] Method checkAccess threw exception for reference $xwiki in template /templates/menuview.vm at [128,61] org.xwik

Re: [xwiki-users] Using parseGroovyFromPage on inherited class

Hi, that doesn't work. xwiki.parseGroovyFromPage("ParentObject") returns an object of the class. I only need to include the class, so that UserClass can extend it. Hi I think you'll need in your User class to use $xwiki.parseGroovyFromPage("ParentObject") Before that you need to pass $xw

[xwiki-users] New WYSIWYG Editor Error 1.8 final

Hi, When I hit save using the new WYSIWYG editor I'm getting the following Status Code 500 error: HTTP ERROR: 500 Failed to load component [com.xpn.xwiki.wysiwyg.server.filter.MutableServletRequestFactory] for hint [HTTP/1.0] RequestURI=/xwiki/bin/save/Projects/WebHome Caused by: java.lang

Re: [xwiki-users] New WYSIWYG Editor Error 1.8 final

DarthOps wrote: > Hi, > > When I hit save using the new WYSIWYG editor I'm getting the following Status > Code 500 error: > > HTTP ERROR: 500 > > Failed to load component > [com.xpn.xwiki.wysiwyg.server.filter.MutableServletRequestFactory] for hint > [HTTP/1.0] See webapps/xwiki/WEB-INF/lib

Re: [xwiki-users] New WYSIWYG Editor Error 1.8 final

Marius Dumitru Florea wrote: > DarthOps wrote: >> Hi, >> >> When I hit save using the new WYSIWYG editor I'm getting the following >> Status Code 500 error: >> >> HTTP ERROR: 500 >> >> Failed to load component >> [com.xpn.xwiki.wysiwyg.server.filter.MutableServletRequestFactory] for hint >> [H

[xwiki-users] SSL to Apache -> Reverse proxy -> Non-SSL Xwiki

Hi Folks, I am sure I'm missing something here, and I can't figure out how to get this done. I have SSL to Apache 2 set up, of which is acting as a reverse proxy to xwiki/Tomcat running non-SSL. It is fine to load xwiki's front page using "https", but this is as far as I can go. All links st

[xwiki-users] User editon detection

Hi all, Is it possible with XWiki API to know with Web 2.0 the list of users that are editing the same page? Also is it possible to know how is connected to a specific workspace? Another question, are there any synchroneous tchatche system that can be integrated in XWiki? I'm asking this question

[xwiki-users] Error while parsing velocity page

Hello again, Here's my info: Xwiki Enterprise 1.7.2 with multiple spaces. I just migrated this wiki from another organization that was using version 1.4.2 (in case that makes a difference in my question). Environment: centos 5.2/apache 2.2/tomcat 6/mysql 5.1 Yesterday, we encountered error