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
On Feb 28, 2010, at 5:46 PM, Jerome Velociter wrote:
> On 2/28/10 5:32 PM, vmassol (SVN) wrote:
>> Author: vmassol
>> Date: 2010-02-28 17:32:49 +0100 (Sun, 28 Feb 2010)
>> New Revision: 27370
>>
>> Added:
>> contrib/sandbox/webdriver-ui-tests/src/test/it/org/xwiki/it/ui/AbstractAdminAuthenticatedTest.java
>> Removed:
>> contrib/sandbox/webdriver-ui-tests/src/test/it/org/xwiki/it/ui/AbstractAdminAuthenticatedTest.java
>> Modified:
>> contrib/sandbox/webdriver-ui-tests/src/test/it/org/xwiki/it/ui/AbstractTest.java
>> contrib/sandbox/webdriver-ui-tests/src/test/it/org/xwiki/it/ui/ImportTest.java
>> contrib/sandbox/webdriver-ui-tests/src/test/it/org/xwiki/it/ui/LoginTest.java
>> contrib/sandbox/webdriver-ui-tests/src/test/it/org/xwiki/it/ui/elements/AdministrationPage.java
>> contrib/sandbox/webdriver-ui-tests/src/test/it/org/xwiki/it/ui/elements/BasePage.java
>> contrib/sandbox/webdriver-ui-tests/src/test/it/org/xwiki/it/ui/elements/HistoryPane.java
>> contrib/sandbox/webdriver-ui-tests/src/test/it/org/xwiki/it/ui/elements/HomePage.java
>> contrib/sandbox/webdriver-ui-tests/src/test/it/org/xwiki/it/ui/elements/ImportPage.java
>> contrib/sandbox/webdriver-ui-tests/src/test/it/org/xwiki/it/ui/elements/LoginPage.java
>> contrib/sandbox/webdriver-ui-tests/src/test/it/org/xwiki/it/ui/elements/RegisterPage.java
>> Log:
>> Testing Selenium 2.0 (merge with WebDriver).
>> * Make sure the package is deleted before the test if it's there
>> * Added license headers
>> * Minor refactorings
>>
>>
>> - public void selectOptionReplaceHistory()
>> + public void toggleReplaceHistoryOption()
>> {
>> getDriver().findElement(By.xpath("//input[@name='historyStrategy' and @value='replace']")).click();
>> }
>
> I don't think toggle is the right word here. Toggle usually refers to a
> 2-states switch
>
> Mabye "selectReplaceHistoryOption" would better fit.
The reason I've used toggle is because you had added a method called unselectOptionReplaceHistory() and its implementation was the same as selectOptionHistory.
Are you sure it's not a toggle, i.e if I click twice on it, it's not in the same state as initially?
Thanks
-Vincent
The XWiki development team is pleased to announce the release of XWiki
Enterprise and XWiki Enterprise Manager 2.2.1.
This is a bug fix release for the 2.2 branches.
It fixes mainly too important regressions around documents parents
handling and xar import so if you are using 2.2 you should really
upgrade to 2.2.1.
New features
* XWIKI-4922 - XWiki translation into catalan language
* XWIKI-4938 - Provide an action for sub queries
Improvements:
* XWIKI-4926 - Finish covering DocumentAccesBridge with new
DocumentReference and AttachementReference
* XWIKI-4884 - Hide the first and last new line when editing a
standalone macro
* XWIKI-4909 - Upgrade to Pygments 1.2.2
* XAADMINISTRATION-113 - Make registration page configurable from
administration sheet
* Updated translations
Important Bugs fixed:
* XE-607 - Cannot use Main.Dashboard as a space dashboard of a
blacklisted space
* XE-605 - Documentation about html macro is wrong in XWikiSyntax page
* XE-604 - Link to RSS feed on dashboard when used as space
dashboard points to global RSS feed
* XWIKI-4929 - XWikiDocument#getParent and setParent does not
serialize/resolve the reference based on the document but on the
current context
* XWIKI-4907 - Can't link to recently modified pages
* XWIKI-4856 - Charset errors on macro insertion
* XWIKI-4878 - Code macro 2.0 - extra newline inserted
* XWIKI-4915 - Code macro 2.0 - inline language=none uses non-monospace font
* XWIKI-4948 - DocumentModelBridge should not contain any set methods
* XWIKI-4672 - Freestanding image/links should be protected in
xwiki/2.0 renderer when before or after word that could break it when
parsed
* XWIKI-4413 - Livetable does not properly empty its cache when
sorting order change
* XWIKI-3899 - The LiveTable does not filter correctly documents
when the + character is used in the filter key
* XSCOLIBRI-199 - Syntax highlighting uses non-monospace font
* XSCOLIBRI-194 - In inline mode, the fullscreen UI doesn't use
the current theme
For more information see the Releases notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise221
and http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM221
Thanks
-The XWiki dev team
Hi,
Yesterday I wanted to add some functional tests for Create page/space actions and I found that the Selenium version we're using doesn't work on Snow Leopard (my OS) so I started looking at issues and found that the pb was fixed in Selenium2/WebDriver. Since I had wanted to explore it for a while I took the time to do a quick exploration...
Selenium2 is the merge of Selenium and WebDriver.
Pros of Selenium2:
* 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)
Now Selenium2 also recommends to use the PageObject pattern which IMO is a very good pattern that we should use. More here:
http://code.google.com/p/selenium/wiki/PageObjects
In order to get a feel of it, I've committed a first test in the sandbox using the PageObjects pattern:
http://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/webdriver-ui-tests/
To run the test:
* Start a local XE on port 8080
* Open the project in your IDE and run LoginTest as a JUnit test
Let me know what you think.
My opinion
* We should test it more, on Ajaxy web pages to verify it's stable and working well enough
* If that works well enough then we could make it our default way of writing functional UI tests and start migrating existing tests one by one + write new ones in it
Thanks
-Vincent
On 2/26/10 6:01 PM, jvelociter (SVN) wrote:
> Author: jvelociter
> Date: 2010-02-26 18:01:09 +0100 (Fri, 26 Feb 2010)
> New Revision: 27315
>
> Modified:
> platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/plugin/packaging/Package.java
> platform/core/trunk/xwiki-core/src/main/resources/ApplicationResources.properties
> Log:
> XWIKI-4937 Importing a new document with 'add new version to existing history' loses first version of the document
>
> Fixed. Integration tests (w/ Selenium2) will follow shortly - too much http://tinyurl.com/ydyooyd in this module :)
>
>
> Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/plugin/packaging/Package.java
> ===================================================================
> --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/plugin/packaging/Package.java 2010-02-26 16:44:31 UTC (rev 27314)
> +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/plugin/packaging/Package.java 2010-02-26 17:01:09 UTC (rev 27315)
> @@ -618,24 +618,34 @@
>
[snip]
>
> Modified: platform/core/trunk/xwiki-core/src/main/resources/ApplicationResources.properties
> ===================================================================
> --- platform/core/trunk/xwiki-core/src/main/resources/ApplicationResources.properties 2010-02-26 16:44:31 UTC (rev 27314)
> +++ platform/core/trunk/xwiki-core/src/main/resources/ApplicationResources.properties 2010-02-26 17:01:09 UTC (rev 27315)
> @@ -2266,7 +2266,7 @@
> xe.rss.blog=Blog RSS feed:
> xe.rss.blog.description=this feed displays blog posts from this wiki.
> xe.rss.blog.feed=Blog RSS Feed
> -xe.rss.space.description=RSS feed for document changes on space '{0}'
> +xe.rss.space.description=RSS feed for document changes on space "{0}"
Oups, meant to commit that separately, it fixes a bug for XE-604
> xe.rss.search.description=It is possible to subscribe to a search on a specific query term. To do this, got to the {0}, run a search on a keyword and then click on the RSS icon.
> xe.rss.tags.description=It is possible to subscribe to a feed for a specific tag or for all existing tags. To do this, got to the {0} and click on the RSS feed icon you wish to use.
> xe.rss.tags.feed=Tags RSS Feed
>
> _______________________________________________
> notifications mailing list
> notifications(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/notifications