If i go through the Tutorial for "Writing XWiki components",
I had problem, on using it while I'm put the code for groovy on a
XWiki-site.
It returns only "null" and nothing what "HelloWorld" means.
Can someone give me a detailed description for realizing the HelloWorld
- component
from beginning with eclipse and groovy?
Me again :)
XWiki has been allocated 1 day a week to my time, that day being Monday,
so it's probably mostly Mondays that you'll hear from me.
I'm setting up our spaces, groups & users and have discovered the
following:
"Subgroups" are really confusing and apparently have no hierarchy, and
can even be shared amongst top level groups and can refer to one another
(or self!)
When I add a subgroup, then click on it, I get told that the page does
not exist. Shouldn't it be a new group to which I can add users and
subgroups?
When adding Members to a Group, the Auto-Find is really neat - but I can
add XWiki.hhulme by clicking on the suggestion as well as hhulme. The
same is true of subgroups.
By clearing the XWikiContext in the tearDown of the unit test, I can
stop the memory leak and stop running the tests in isolation. I am
proposing we apply this change because the XWikiContext is created
per test and the worst problem which can be created is tests
erroneously passing which I don't think is very likely from a change
like this.
Jira issue: http://jira.xwiki.org/jira/browse/XWIKI-4953
Patch:
http://jira.xwiki.org/jira/secure/attachment/16788/XWIKI-4496-patchTestMemo…
Patch content:
Index: core/xwiki-core/pom.xml
===================================================================
--- core/xwiki-core/pom.xml (revision 27357)
+++ core/xwiki-core/pom.xml (working copy)
@@ -823,10 +823,6 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
- <configuration>
- <!-- Prevent Out Of Memory errors resulting from tests
that do no free up the memory correctly -->
- <forkMode>pertest</forkMode>
- </configuration>
</plugin>
<!-- Publish a Core Test JAR -->
<plugin>
Index:
core/xwiki-core/src/test/java/com/xpn/xwiki/test/AbstractBridgedXWikiComponentTestCase.java
===================================================================
---
core/xwiki-core/src/test/java/com/xpn/xwiki/test/AbstractBridgedXWikiComponentTestCase.java
(revision 27357)
+++
core/xwiki-core/src/test/java/com/xpn/xwiki/test/AbstractBridgedXWikiComponentTestCase.java
(working copy)
@@ -80,6 +80,7 @@
protected void tearDown() throws Exception
{
Utils.setComponentManager(null);
+ getContext().clear();
super.tearDown();
}
Hi devs,
The Google summer of code 2010 will start soon:
http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#…
First deadline:
"March 8-29: Mentoring organizations can begin submitting applications to Google."
So we need to propose applications.
We have already listed some there:
http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/
Now we need mentors for them since we should only propose projects for which we have declared mentors.
So can all the people who want to be mentors this year please edit the projects and put themselves as Project Lead (we can have several project leads for now)?
If you can fill this for Monday 8 it would be great since we need to move these projects into google's own application and it would show to google that we are active and it'll help XWiki to be chosen as a SOC organization this year.
thanks for your help
-Vincent
Hi devs,
Jerome and I have explored using Selenium2 (see http://xwiki.markmail.org/thread/cqbxdmhqdi36kovn)
The code is in http://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/webdriver-ui-tests/
I'd like to propose to:
* Move the code in http://svn.xwiki.org/svnroot/xwiki/enterprise/trunk/distribution-test/ui-te…
* Agree that from now on *new* UI functional tests are written using Selenium2
* Slowly migrate current functional tests over time (I have almost finished migrating the login/logout tests for ex)
* Use the PageObject pattern as shown in the existing tests in http://svn.xwiki.org/svnroot/xwiki/enterprise/trunk/distribution-test/ui-te…
The pros to use selenium2 are those listed in http://xwiki.markmail.org/thread/cqbxdmhqdi36kovn:
* No more JS sandbox. In selenium1 all the selenium API is executed as JS in the browser. In Selenium2 the browsers are controlled using their native APIs (JNA).
* Faster (as a consequence of the previous point)
* Allows to do stuff such as file uploads, etc since there's no longer the issue of the JS sandbox
* No need to start a Selenium Proxy. All you need is to start XE and then you can run the tests as simple JUnit tests.
* The API is much cleaner (this is to be expected with hindsight). See http://seleniumhq.org/docs/09_webdriver.html
* There's a very fast executing HtmlUnit driver (not to be used with tests using JS though since it emulates browser JS support and thus cannot guarantee the result in the real browser)
Caveat:
* Selenium2 is still quite young so it's possible that there are cases when it'll have bugs or be instable. We should still allow using selenium1 tests when this happens.
Note: I have configured hudson to run the selenium2 tests from the sandbox to see how stable it is.
Here's my +1
Thanks
-Vincent
sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2010-03-06 02:23:19 +0100 (Sat, 06 Mar 2010)
> New Revision: 27501
>
> Modified:
> platform/web/trunk/standard/src/main/webapp/templates/informationinline.vm
> Log:
> XWIKI-4980: Backlink information is not sorted by space
> Fixed.
>
> Modified: platform/web/trunk/standard/src/main/webapp/templates/informationinline.vm
> ===================================================================
> --- platform/web/trunk/standard/src/main/webapp/templates/informationinline.vm 2010-03-06 01:20:42 UTC (rev 27500)
> +++ platform/web/trunk/standard/src/main/webapp/templates/informationinline.vm 2010-03-06 01:23:19 UTC (rev 27501)
> @@ -40,7 +40,7 @@
> </dd>
> #end
> #end
> - #set($blinks = $doc.getBacklinks())
Should getBackLinks use an "order by" clause at the database level?
I don't think any order is guaranteed at the moment in which case it would not be breaking API.
Also getChildren could be changed at the same time since documents can have children in other spaces.
> + #set($blinks = $sorttool.sort($doc.getBacklinks()))
> #if($blinks.size()>0)
> <dt>$msg.get('core.viewers.information.backlinks')</dt>
> <dd>
>
> _______________________________________________
> notifications mailing list
> notifications(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/notifications
>
The XWiki development team is pleased to announce the release of XWiki
Enterprise and XWiki Enterprise Manager 2.2.2.
This is a bug fix release for the 2.2 branches.
It fixes mainly two important regressions around documents object
handling and office importer on Internet Explorer 7 so if you are
using 2.2 or 2.2.1 you should really upgrade to 2.2.2.
Improvements:
* XAADMINISTRATION-115 - Left align check boxes in "Registration >
Customize XWiki Registration"
* XAADMINISTRATION-63 - In "Administration" -> "Users" closing the
"Add new user" pop-up causes the page to refresh
* XAADMINISTRATION-67 - In "Administration > User > Add new user"
indicate which fields are mandatory
* XAADMINISTRATION-103 - Make registration page support lightbox so
administrator can use it to add users in admin users sheet.
* Updated translations
Important Bugs fixed:
* XWIKI-4955 - Page with empty content leads to "This template does
not exist" message when viewed in plain mode
* XWIKI-4967 - Impossible to import office (copy/paste) with style using IE7
* XWIKI-4965 - Objects can no longer be retrieved relative to their document
* XWIKI-4931 - Links are badly saved on IE7
* XWIKI-4977 - AJAX behavior broken in IE6 for documents with
non-ASCII characters in the name
* XWIKI-4974 - Adding tags with non-ASCII characters fails in Internet Explorer
* XWIKI-4968 - Deleting a comment appears in the history as being
deleted by the person who made the comment instead of the deleter
* XWIKI-4971 - Header generated ids are wrong in 1.0 syntax
* XWIKI-4966 - Missing translation keys for application configuration.
* XWIKI-4590 - View Statistics increment too fast because of AJAX
features in bottom page tags and ratings
* XWIKI-4925 - When XWiki is initialized via a XMLRPC request, it is
in a wrong state and redirect-to-login URLs will be wrong
* XWIKI-3915 - XWiki.copyWiki does not copy hidden documents
* XWIKI-4954 - XWikiDocument#clone should use set/getParent instead of
set/getParentReference
* XWIKI-4555 - XWikiHibernateStore#countDocuments does not always
return the same number as would be the size of #searchDocuments for
the same query
* XWIKI-4969 - Missing translation value for key
"import_listoferrorsfiles" in new Import UI
* XWIKI-4978 - Previewing a comment for a document with non-ASCII
characters in the name uses a wrong URL
* XAADMINISTRATION-68 - In "Administration > User > Add new user"
notify the user when the passwords he types in don't match
* XAADMINISTRATION-21 - User not created when registration information
isn't correct when creating new user in new Administration UI
For more information see the Releases notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise222
and http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM222
Thanks
-The XWiki dev team
The Main.RecentChanges page is failing on myxwiki (apparently all subwikis) and I was able to get some information out of it.
The problem can be isolated to the query in this snippet, it works on my local wiki installation with postgres but fails on the incubator.
{{velocity}}
$xwiki.searchDocuments(", XWikiRCSNodeInfo as ni where doc.id=ni.id.docId and ni.id.version2=1 group by doc.space, doc.name order by max(ni.date) desc", 1, 0)
{{/velocity}}
This is the generated hql query I got from the logs on my local machine where the query succeeds.
select distinct doc.space, doc.name, max(ni.date) from com.xpn.xwiki.doc.XWikiDocument as doc , com.xpn.xwiki.doc.rcs.XWikiRCSNodeInfo as ni where (doc.hidden <> true or doc.hidden is null) and doc.id=ni.id.docId and ni.id.version2=1 group by doc.space, doc.name order by max(ni.date) desc
here is the query from the error message from trying to run the above snippet (or the RecentChanges page)
select distinct doc.space, doc.name, max(ni.date) from XWikiDocument as doc , XWikiRCSNodeInfo as ni where (doc.hidden <> true or doc.hidden is null) and doc.id=ni.id.docId and ni.id.version2=1 group by doc.space, doc.name order by max(ni.date) desc
They appear to be functionally identical, maybe the query is different from 2.1 and is disagreeing with the mysql version on myxwiki, or perhaps something is just misconfigured. It doesn't seem like the db is corrupt since it happens on multiple subwikis.
The bottom part of the stack trace.
Caused by: com.xpn.xwiki.XWikiException: Error number 3223 in 3: Exception while searching documents with SQL [select distinct doc.space, doc.name, max(ni.date) from XWikiDocument as doc , XWikiRCSNodeInfo as ni where (doc.hidden <> true or doc.hidden is null) and doc.id=ni.id.docId and ni.id.version2=1 group by doc.space, doc.name order by max(ni.date) desc]
Wrapped Exception: could not execute query
at com.xpn.xwiki.store.XWikiHibernateStore.searchGenericInternal(XWikiHibernateStore.java:2470)
at com.xpn.xwiki.store.XWikiHibernateStore.searchDocumentReferencesInternal(XWikiHibernateStore.java:2426)
at com.xpn.xwiki.store.XWikiHibernateStore.searchDocumentsNamesInternal(XWikiHibernateStore.java:2413)
at com.xpn.xwiki.store.XWikiHibernateStore.searchDocumentsNames(XWikiHibernateStore.java:2190)
at com.xpn.xwiki.store.XWikiHibernateStore.searchDocumentsNames(XWikiHibernateStore.java:2169)
at com.xpn.xwiki.store.XWikiCacheStore.searchDocumentsNames(XWikiCacheStore.java:373)
at com.xpn.xwiki.api.XWiki.searchDocuments(XWiki.java:491)
at sun.reflect.GeneratedMethodAccessor279.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:389)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:378)
at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:270)
... 80 more
Can't be too careful.
Caleb
On 03/02/2010 08:20 PM, Thomas Mortagne wrote:
> On Tue, Mar 2, 2010 at 18:25, Sergiu Dumitriu<sergiu(a)xwiki.com> wrote:
>> On 03/02/2010 05:01 PM, Joel Forsberg wrote:
>>>
>>> Greetings
>>>
>>> On my wiki using swedish characters for xwiki page titles give ugly but
>>> working entries in all panels, e.g. "Backlinks" "Recent modifications" and "My
>>> recent modifications"
>>>
>>> An example is having:
>>> "Startsidor för våra intresseområden"
>>> ...instead of the correct:
>>> "Startsidor för våra intresseområden"
>>>
>>> Another example is putting thiss wiki code on top of a page:
>>> = header that<look ugly> here =
>>>
>>> The script responsible for for the texts in the panels is as follow:
>>>
>>> <span class="panelitem">
>>> <a href="$rdoc.getURL('view')">
>>> $xwiki.getXMLEncoded($rdoc.displayTitle)
>>> </a></span>
>>>
>>> I've noticed that changing the third line into only $rdoc.displayTitle will
>>> produce a nice looking entry, and $rdoc is set via
>>>
>>> #set($rdoc = $xwiki.getDocument($docname).getTranslatedDocument())
>>>
>>> Now, can anyone see a purpose of using getXMLEncoded() for this? As far as I
>>> have seen, it only breaks things.
>>
>> This is not caused by getXMLEncoded, it merely makes the problem
>> visible. This method must be used in order to prevent other problems:
>> Invalid XML, broken layout, XSS...
>>
>> The problem is that the code inside getDisplayTitle wrongly uses a XML
>> escaping option.
>
> No, this is valid because the job of $rdoc.displayTitle is to produce
> xhtml content and theses are valid XML escapes.
Where does it say that it should produce xhtml content?
Assuming that it should produce xhtml, the behavior is inconsistent. If
the title is placed in the document.title field, then it returns
characters; if it is placed in the first heading, it returns escapes. If
we use wiki syntax in the document.title, we get back wiki syntax; if we
use wiki syntax in the first heading, we get back HTML. That is totally
inconsistent and confusing.
This is an API design problem that should be discussed further on the
dev list.
Going back to this specific problem, I think that it should be solved by
using the plaintext output syntax, since inside a panel we're not
interested in formatting or other markup inside the title, just the
textual content.
> So you don't need to
> use getXMLEncoded because any xml content is already properly escaped
> (in xwiki/2.0 syntax).
I need to use getXMLEncoded because the title doesn't always come from
the content.
> When you want a plain text version of the title you should use
> $rdoc.getRenderedTitle("plain/1.0").
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
On 4 Mar 2010, at 13:58, Stephen Dawkins wrote:
> Hi
>
> Unfortunetly there's a bug/limitation[1] in the Firefox implementation
> of that method that means you can't use a self-signed certificate to
> sign the text.
>
> I've already knocked up a patch to fix it, but it seems no one is
> particularly interested in getting it included.
I voted for it. Anyone interested should vote for it too.
While you are at it also vote for
https://bugzilla.mozilla.org/show_bug.cgi?id=396441
>
> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=403909
>
> Regards
> Stephen
>
> On 04/03/2010 09:58, Story Henry wrote:
>> On another mailing list Caleb pointed out the following:
>>
>> On 4 Mar 2010, at 00:29, Caleb James DeLisle wrote:
>>
>>> Firefox and Opera Javascript have a method crypto.signText() which apparently will support
>>> signing of form data on the client side which has a wide array of use cases including
>>> signing XWikiDocuments in so they can be imported and exported while retaining their author field.
>>> see: http://docs.sun.com/source/816-6152-10/sgntxt.htm
>>
>> This does indeed sound like it could be another very useful application of foaf+ssl.
>>
>> Henry
>>
>> _______________________________________________
>> foaf-protocols mailing list
>> foaf-protocols(a)lists.foaf-project.org
>> http://lists.foaf-project.org/mailman/listinfo/foaf-protocols
Hi,
I have built a little keygen application for Xwiki now. It is available here:
http://github.com/bblfish/keygenapp
You can download it with
$ git clone git@github.com:bblfish/keygenapp.git
then you should be able to build it with
$ mvn clean package
$ mvn dependency:copy-dependencies
You will then just need to copy two jar files over to
webapps/xwiki/WEB-INF/lib/
* target/xwiki-foafssl-component-0.2.jar
* target/dependency/bcprov-jdk16-141.jar
Because I am not yet sure how to get the XAR plugin to work, I have not automated the build yet for that piece. Please let me know how I should fix this. Essentially there are two files that need to be installed
$ ls -l1 src/main/resources/XWiki/*.xml
src/main/resources/XWiki/foafssl_RSAPubKey.xml
src/main/resources/XWiki/foafssl_create_cert.xml
the first one there is just a class, the second one is a script that will allow you to get a certificate in one click.
In order to then have that be visible to your homepage you need to replace the content of the
XWikiUserProfileSheet with the content of
src/main/resources/XWiki/XWikiUserProfileSheet.html
You will then be able to try to login to a few other services (there is a link provided on the page). I will work next on allowing Xwiki to be logged into too with foaf+ssl (as well as on fixing any bugs you let me know of)
Henry
Social Web Architect
http://bblfish.net/
Dear dev guys
I'm Giuseppe Vallarelli an Italian computer science student from Bari
(headache on irc-channel), and i would contribute to XWiki project.
I'm a new to opensource development and web application development field,
but i'm a rapid learner and a passionate person :), in my
spare time i've spent some time learning test driven development using JUnit
4.x but i'm not an expert neither in tdd nor in development
i think that to really learn about something one person should practice a
lot and overcomes obstacles :).
I'm very grateful to Sdumitriu, Vincent Massol and CalebJamesDeLisl for help
me with the build of XWiki from sources.
How can i contribute to XWiki? I would like to contribute with development,
mabye submitting patch, but the problem is that i've never submitted
a patch. I need some guidance :). I've never managed a big project like
XWiki.
Giuseppe headache Vallarelli
P.s. Of course i would like to partecipate to GSoC 2010 with XWiki nice
development team :-)
N.b. I apologize for my imperfect english, i will imporve my writing skills
with time.
Hi devs,
I've found and fixed an important bug in XE 2.2.1:
http://jira.xwiki.org/jira/browse/XWIKI-4965
I propose to release XE 2.2.2 ASAP (i.e when Thomas is available since he's the release manager of XE 2.2.x).
In addition to this bug there are several other important fixes too:
Bug
• [XWIKI-4555] - XWikiHibernateStore#countDocuments does not always return the same number as would be the size of #searchDocuments for the same query
• [XWIKI-4590] - View Statistics increment too fast because of AJAX features in bottom page tags and ratings
• [XWIKI-4925] - When XWiki is initialized via a XMLRPC request, it is in a wrong state and redirect-to-login URLs will be wrong
• [XWIKI-4931] - Links are badly saved on IE7
• [XWIKI-4954] - XWikiDocument#clone should use set/getParent instead of set/getParentReference
• [XWIKI-4965] - Objects can no longer be retrieved relative to their document
Here's my +1
Thanks
-Vincent
JV, there's a real bug out there, why have you removed it (We need it in jira somewhere so that people who have it can find it and so that we can put it as fixed in the release notes) ?
Allowing to set the host/port (or whatever else) will not remove the bug by itself.
Thanks
-Vincent
On Mar 2, 2010, at 11:50 AM, Jean-Vincent Drean (JIRA) wrote:
>
> [ http://jira.xwiki.org/jira/browse/XAADMINISTRATION-117?page=com.atlassian.j… ]
>
> Jean-Vincent Drean moved XASCH-50 to XAADMINISTRATION-117:
> ----------------------------------------------------------
>
> Project: XWiki Administration Application (was: XWiki Scheduler Application)
> Key: XAADMINISTRATION-117 (was: XASCH-50)
> Issue Type: Improvement (was: Bug)
> Affects Version/s: 1.27
> (was: 1.16)
> Component/s: Infrastructure
> (was: Plugin)
>
>> URL generated from scheduler jobs can be wrong
>> ----------------------------------------------
>>
>> Key: XAADMINISTRATION-117
>> URL: http://jira.xwiki.org/jira/browse/XAADMINISTRATION-117
>> Project: XWiki Administration Application
>> Issue Type: Improvement
>> Components: Infrastructure
>> Affects Versions: 1.27
>> Reporter: Jean-Vincent Drean
>>
>> Scheduler jobs are passed a stub request. This stub request contains the host used on the first request, URLs generated afterwards will always use this host.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators: http://jira.xwiki.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
Hi guys,
I'm an experienced software engineer but scripting XWiki still seems to
be about as clear as mud to me.
I know I could create a Form.
I know this could result in a new Page being generated.
However, I have no idea how to make this happen.
Is an event raised when I submit the form? If so, how do I attach a
handler to that event? What do I then need to do to squeeze the
user-provided data into a page generated from a template? Or into some
data store from which a templated page would be generated?
I would be incredibly grateful if someone could throw together a very
quick walk-through of doing the following from a web browser:
Creating a new form with a singular field, e.g. Name
Writing the code which takes the contents of this form and creates a new
page with title "Name's Greeting" and content "Hello, Name!"
This does raise further questions. For example: Can a user go back later
and edit the data in the form? Or would the resulting page need to be
edited instead?
Thanks - but what I was really looking for was a way to show the
*previous* version of a page until the *changes* have been approved. At
any time in the future.
I don't even necessarily want Documentation Managers to be able to edit
pages, just to read them and click a button to say "I'm happy that this
information is correct."
I really wouldn't want our Development Manager here to write any code -
but I go to him to get my changes signed off so I can install the
binaries to the live environment :)
----------------------------------
Hi Hugh,
In XWiki you can set edit rights at page level. You can create a group
for
"Documentation Managers" and only grant its members the ability to edit
a
certain page. After the page has been authorized you may change the
rights
to that page so that anyone can edit it.
Should you want to hide the page altogether until approval you may
change
the view rights as well.
You can read more about rights management here
http://platform.xwiki.org/xwiki/bin/view/Features/RightsManagement
Also see here how you can create a group in XWiki:
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Group+Management
Hope this helps.
Hi,
Search on the XWiki site appears to be broken. Otherwise I would have
done. But I'm glad to see you don't have a "Go away" policy for people
who haven't :)
I have a question, that being: Is there any mechanism in XWiki for a
person in a Documentation Management role to "Sign off" page changes
before they become available to other users?
If not, can it be done? It would obviously require the page to be locked
as soon as edit begins and not unlocked until the higher user has
authorised it.
Thanks,
- Hugh
I would like to change AddCommentAction to support captchas. the
changes I'd like to make are as follows:
xwiki-core becomes dependent on xwiki-captcha I don't like it but
xwiki-action is not ready and there is no api for adding comments.
If xpage is defined and xredirect is not and then it does not redirect.
If a user is logged in then author name is taken from the context
and the author field is ignored. This will improve security when
anonymous commenting is disallowed.
If the user is not logged in, captcha service is enabled, and
request parameter: captcha_answer is specified then a captcha
verifier is gotten with hint specified by request parameter
captcha_type and captcha_answer is verified.
If the user is not logged in, captcha service is enabled,
captcha_answer is not specified, and space preference
"guest_comment_requires_captcha" is 1 then captcha verification fails.
If captcha check fails then captchaAnswerWrong = true is placed in
the velocity context and comment isn't added.
Patch is posted here:
http://jira.xwiki.org/jira/secure/attachment/16792/XWIKI-4952-CommentAddAct…
Caleb