Sergiu,
I think it would be beneficial to document below that the filters must
be run on this order and explain why. WDYT?
Thanks
-Vincent
On Jun 24, 2008, at 2:00 PM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2008-06-24 14:00:10 +0200 (Tue, 24 Jun 2008)
> New Revision: 10662
>
> Modified:
> xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/web.xml
> Log:
> XWIKI-891 and XWIKI-1771: Fix regression caused by wrong filter
> order (non-ASCII chars in ISO-8859-1 are lost).
>
>
> Modified: xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/
> web.xml
> ===================================================================
> --- xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/
> web.xml 2008-06-24 10:52:43 UTC (rev 10661)
> +++ xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/
> web.xml 2008-06-24 12:00:10 UTC (rev 10662)
> @@ -9,15 +9,6 @@
> <display-name>xwiki</display-name>
> <description>XWiki Application</description>
>
> - <!-- A filter that allows requests to be saved and reused later.
> For example when the current request contains an expired
> - authentication token, and the authorization module redirects
> to the login page, all the information sent by the
> - client would be lost; this filter allows to save all that
> information, and after a successful login, injects the
> - saved data in the new request. -->
> - <filter>
> - <filter-name>RequestRestorer</filter-name>
> - <filter-class>com.xpn.xwiki.web.SavedRequestRestorerFilter</
> filter-class>
> - </filter>
> -
> <!-- Filter that sets a custom encoding to all requests, since
> usually clients don't specificy
> the encoding used for submitting the request, so by default
> containers fall back to the
> encoding globally configured in their settings. This allows
> XWiki to use a custom encoding,
> @@ -41,12 +32,21 @@
> </init-param>
> </filter>
>
> + <!-- A filter that allows requests to be saved and reused later.
> For example when the current request contains an expired
> + authentication token, and the authorization module redirects
> to the login page, all the information sent by the
> + client would be lost; this filter allows to save all that
> information, and after a successful login, injects the
> + saved data in the new request. -->
> + <filter>
> + <filter-name>RequestRestorer</filter-name>
> + <filter-class>com.xpn.xwiki.web.SavedRequestRestorerFilter</
> filter-class>
> + </filter>
> +
> <filter-mapping>
> - <filter-name>RequestRestorer</filter-name>
> + <filter-name>Set Character Encoding</filter-name>
> <url-pattern>/*</url-pattern>
> </filter-mapping>
> <filter-mapping>
> - <filter-name>Set Character Encoding</filter-name>
> + <filter-name>RequestRestorer</filter-name>
> <url-pattern>/*</url-pattern>
> </filter-mapping>
hi Vincent/Fabio,
*According to my knowledge partitions should not be overlap.But the XDOM
model is nested.
I think this might be a problem. The sample plugin I have made is also
base on partitioning the entire document to non overlapping reagents so each
partition can be then subjected to syntax coloring.
*I tried to use the existing api(rule bale partitions) to nested syntax as
well .But it turned out difficile
*I need help on this.
*WDUT ?
Thanks
-Malaka
--Malaka Ekanayake
CSE UOM
I configured my Chinese Wiki, but in the wysiwyg editor I can only select
some English font-family. What can I do if I want to add some Chinese
font-families? Should I modify some .js files in tinymce.
Please anyone knows that give me some suggestion, thanks a lot.
--
View this message in context: http://www.nabble.com/How-to-add-new-font-family-to-XWiki-tinymce-tp1805443…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi XWikiers,
I'd like to release XE 1.5M2 tomorrow with XWIKI-2401 included.
Please note that the new administration application has been commited,
the more testers we can have before the release, the better.
Here's my +1.
Thanks,
--
Jean-Vincent Drean
Environment:
We are using Enterprise 1.4
Scenario:
Created XYZSpace
Created XYZUser
Created XYZGroup and added XYZUser
Gave XYZGroup global view rights for XYZSpace
XYZUser can view XYZSpace
Created GlobalViewer user
Gave GlobalViewer global view rights
GlobalViewer can view main
GlobalViewer can not view XYZSpace
My question is:
How is a GlobalViewer created? Intuitively is seemed like going
to the global rights tab and granting the GlobalViewer view rights would
work everywhere. But oddly, the GlobalViewer did not have rights in
XYZSpace when specific view rights had been granted to another user in
the XYZSpace. Is there some interaction between global view rights and
space view rights?
I am grateful for your help!
Thanks
Satya
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
Hi Guys:
I have been reading everywhere and I can't find a solution that fits my
problem.
I have 2 users
- Admin (Standard).
- User1 (All possible rights for Space called Test).
Now I acces Test.WebPreferences And I get 2 Tabs:
- Space Prefs.
- Space Rights.
(So far so good)
But when I press the Space Rights Tab the Ajax table that should show my
users and groups doesnt show any names... The Only correct information it
displays is how many of each existe.
In the meanwhile When I log in as Admin and access the Administration area
everything works fine both tables on global rights and space rights work
fine.
Can anybody help me out? Or give me a hint to where I should look to solve
this problem.
Im using the Xwiki enterprise 1.5 milestone.
And the link is
http://localhost:8080/xwiki/bin/admin/XX/WebPreferences?editor=spacerights&…
Every time I enter the link above the follwoing messages appear besides
others of course.
17:28:19,529 INFO [XWikiRightServiceImpl] Access has been denied for
(xwiki:XWiki.test,XWiki.canUsee,view): global level (restricting right was
found)
17:28:19,529 INFO [XWikiRightServiceImpl] Access has been denied for
(xwiki:XWiki.test,XWiki.canUsee,view): access manager denied right
17:28:19,561 INFO [XWikiRightServiceImpl] Access has been denied for
(xwiki:XWiki.test,XWiki.teste,view): global level (restricting right was
found)
17:28:19,561 INFO [XWikiRightServiceImpl] Access has been denied for
(xwiki:XWiki.test,XWiki.teste,view): access manager denied right
17:28:19,592 INFO [XWikiRightServiceImpl] Access has been denied for
(xwiki:XWiki.test,XWiki.XWikiAdminGroup,view): global level (restricting
right was found)
17:28:19,592 INFO [XWikiRightServiceImpl] Access has been denied for
(xwiki:XWiki.test,XWiki.XWikiAdminGroup,view): access manager denied right
17:28:19,608 INFO [XWikiRightServiceImpl] Access has been denied for
(xwiki:XWiki.test,XWiki.XWikiAllGroup,view): global level (restricting right
was found)
17:28:19,608 INFO [XWikiRightServiceImpl] Access has been denied for
(xwiki:XWiki.test,XWiki.XWikiAllGroup,view): access manager denied right
Firebug finds error here in usersandgroups.js in the function
displayUsersAndGroups(row, i, table, idx):
->>>>>var userurl = row.userurl;
var uorg = table.json.uorg;
var allows = row.allows;
var denys = row.denys;
--
View this message in context: http://www.nabble.com/Space-Admin-Space-Rights-tp18095953p18095953.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hello,
I sent an early version of MailAuth earlier, no response at all?
I don't mean to be pushy, but I'm beginning to have doubts if my
involvement is needed and/or welcome at all. And I'd really prefer to
work out with you some kind of patch that can be applied to XWiki
instead of creating a de-facto private fork version. I admit I'm a lousy
team player, but this is getting frustrating, to say the least.
Greetings, Lilianne E. Blaze
Hello devs,
Short note to inform you I'm about to create a 1.1 branch for the
spacemanager plugin. I will backport XPSM-10, XPSM-11 and XPSM-12 in it.
I need it for XWiki Workspaces 1.1 branch (it can't rely on
1.2-SNAPSHOT/trunk, since this last has dependencies on core 1.5 now).
Curriki could need it too when it will upgrade to XWiki 1.4.
Regards,
Jerome.