[xwiki-users] Tag cloud with only 'viewable' tags
I'm not sure if this is possible in the current configuration: My issue is this: A (anonymous) user can see tags used only in 'private' pages, e.g. pages the current user has no view acces to. If he clicks a tag, he can see the page Tags?do=viewTagtag=DeadlyIncidents showing him no pages with this tag. The problem is threefold: - The tagcloud is cluttered with tags that are of no use to the current user - The user can become confused if he tries to look for a page with that tag - Information existing in a page is leaked. A tag is just a tag, but it can tells something about information on one or more pages. In my opinion, the user should only be able to see tags that are used in pages he has view right to. I can imagine it would put a heavy load on a system to check for every tag if it's used in viewable pages, though. Any thoughts? Sincerily, Joris ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Workspace manager free default pages set + 2 new ideas
Hi Dmitry, I understand your concerns about programming rights. It has been and it still is a subject of debate. However, please note that you do not need programming rights to do velocity scripting inside XWiki (whether it is on the main wiki or on a subwiki). You need PR only for groovy scripting (since it has access to the core java layer) and for some velocity methods that request access to the same core java layer that you should normally not need to access. Even so, there are rare times when you want to do some complex stuff that *really* needs groovy or privileged velocity APIs, so you can not completely escape the need of PR. I`m not sure the PR wiki-level encapsulation you desire is easy to perform, since PR (as they are currently defined) are too powerful to be contained inside a wiki and generally tend to have access to everything. The current PR would need serious rethinking and maybe redefinition in order to obtain that, but it's good to have this encapsulation in consideration when it will come to that. My 2 cents on the issue :) Thanks, Eduard On Wed, Feb 1, 2012 at 8:42 AM, Haru Mamburu haru_mamb...@mail.ru wrote: Hi, Eduard, Sorry to be unclear first time. Let's end it up: E.g. I set up my workspace AND I need to do some scripting on it. If I got everything right, looks not possible without GLOBAL programming rights. Programming rights actually should work even without admin rights. For now we have no tool to encapsulate programming rights of user with programming rights niether inside his own workspace (as a global user), nor inside virtual wiki. Ideal XWiki world runs everything independently. It's how I understand words platform and engine. So, this encapsulation engine is another new feature request. I'd like to ask. Is it easy to implement? Finally: http://jira.xwiki.org/browse/XEM-207 - second level of virtualization http://jira.xwiki.org/browse/XEM-208 - programming rights incapsulation inside workspaces and virtual wikis Hope, it helps. Kind Regards. Dmitry 30 января 2012, 18:21 от Eduard Moraru enygma2...@gmail.com: Hi Dmitry, I`m not sure I fully understand your proposal or concerns. 1. You are saying that global admins are dangerous because they can get programming rights and kill everything. They don`t need programming rights to kill everything if they have global admin rights :) They just use the UI to delete everything. Also, I don`t think XWiki`s scope is to protect you from yourself or from your trusted people. If you assign global admin rights to someone, you`d better do it carefully. The same goes with every collaborative system. 2. You are describing a usecase where only subwikis/workspaces are launched in production and that the main wiki is restricted to regular users, in an attempt to avoid global admins. Well... sure, but how is this different from you being the only main wiki admin and the other users to be only subwiki admins (at best)? I`m not sure it's ok to impose such a usecase to users instead of applying it only when needed. Workspaces is already designed to fulfil this usecase by not assigning any main wiki admins. It allows global users to create their own workspaces (subwikis) and play as they wish inside them, no programming rights or global admins involved. 3. I`m not sure I understand the proposed flexible solution. If by virtual wiki 2 - workspaces - workspaces (probably) you mean to allow subwikis to be created inside subwikis, then this, indeed is the new feature request that I was referring to when suggesting that you create a new jira. The idea is more general than your particular use case and can be applied to various usecases. Though I still think that one level of virtualization is enough for XWiki (as things are working right now), I accept the idea that some people might need more complex scenarios. Thanks, Eduard On Sat, Jan 28, 2012 at 7:41 PM, Haru Mamburu haru_mamb...@mail.ru wrote: Hi Eduard, Thanks for explnation. I'm very happy to issue a new idea, but idea itself is a bit wider and deeper, then described below. I would like to point out some reasons and effects to be more clear before jiraing it :-) Security leak XE/XEM Usecase XE/XEM + Workspace Manager. One main Wiki and let's say, hundreds of workspaces. To be more real we'd add Wiki Manager and tens of virtual wikis running on the same engine (something like XWiki.com running) As my humble experience shows, nearly never in natural way XWiki would have only one User with Admin Rights on the Wiki level. It's human to be all the time in a hurry and meanwhile XWiki becomes messy inside. It's not the big problem yet. :-) As an Admin User on wiki level, I can easily gain programming rights. For now, it's completely uncontrolled and will run unnoticed. So, let's imagine that all stars in solar system lined up in a bad way and one Admin became an AngryAdmin with a revenge as a
Re: [xwiki-users] How programming rights works in xwiki?
Hi Mohit As you cited from the doc with programming rights you are allowed to execute arbitrary java, but not modify it during runtime. An example for the use of programming rights would be if you create a page where an XWikiGuest user can save something without having edit rights on the page by using $doc.saveWithProgrammingRights(). In this example the script calling this method would need to be saved from a user with programming rights. Generally spoken, without programming rights you are only allowed to use Api classes and the mayor part of their methods. With programming rights you are allowed to use all methods of Api classes or even to get background classes (e.g. XWikiDocument instead of only the api class Document). Hope this clarifies how it works. Edo On Wed, Feb 1, 2012 at 12:12 PM, mohit gupta motgu...@gmail.com wrote: Below is the statement given at http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Access+Rights A programmer is allowed to execute arbitrary java code in the wiki and can thus gain control of the system user which the wiki is running under. Could you give me some example how xwiki admin can modify existing java class. when it will be compile and deployed? Assume i want to add a new method in XWikiAuthServiceImpl.java . How should i go with this provided i am having programming rights.Thanks. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Workspace manager, WYSIWYG editor + 3-rd new idea
Hi, All, As we have now workspaces in addition to virtual spaces, it looks logic to provide following scenario in UI of WYSIWYG editor: select virtual wiki/workspace - Space - Page - Anchor It would help much in multiworkspace environment. Is it difficult to implement? Please, vote if it looks useful for you at http://jira.xwiki.org/browse/XEM-209 Kind Regards, Dmitry 01 февраля 2012, 15:36 от Eduard Moraru enygma2...@gmail.com: Hi Dmitry, I understand your concerns about programming rights. It has been and it still is a subject of debate. However, please note that you do not need programming rights to do velocity scripting inside XWiki (whether it is on the main wiki or on a subwiki). You need PR only for groovy scripting (since it has access to the core java layer) and for some velocity methods that request access to the same core java layer that you should normally not need to access. Even so, there are rare times when you want to do some complex stuff that *really* needs groovy or privileged velocity APIs, so you can not completely escape the need of PR. I`m not sure the PR wiki-level encapsulation you desire is easy to perform, since PR (as they are currently defined) are too powerful to be contained inside a wiki and generally tend to have access to everything. The current PR would need serious rethinking and maybe redefinition in order to obtain that, but it's good to have this encapsulation in consideration when it will come to that. My 2 cents on the issue :) Thanks, Eduard On Wed, Feb 1, 2012 at 8:42 AM, Haru Mamburu haru_mamb...@mail.ru wrote: Hi, Eduard, Sorry to be unclear first time. Let's end it up: E.g. I set up my workspace AND I need to do some scripting on it. If I got everything right, looks not possible without GLOBAL programming rights. Programming rights actually should work even without admin rights. For now we have no tool to encapsulate programming rights of user with programming rights niether inside his own workspace (as a global user), nor inside virtual wiki. Ideal XWiki world runs everything independently. It's how I understand words platform and engine. So, this encapsulation engine is another new feature request. I'd like to ask. Is it easy to implement? Finally: http://jira.xwiki.org/browse/XEM-207 - second level of virtualization http://jira.xwiki.org/browse/XEM-208 - programming rights incapsulation inside workspaces and virtual wikis Hope, it helps. Kind Regards. Dmitry 30 января 2012, 18:21 от Eduard Moraru enygma2...@gmail.com: Hi Dmitry, I`m not sure I fully understand your proposal or concerns. 1. You are saying that global admins are dangerous because they can get programming rights and kill everything. They don`t need programming rights to kill everything if they have global admin rights :) They just use the UI to delete everything. Also, I don`t think XWiki`s scope is to protect you from yourself or from your trusted people. If you assign global admin rights to someone, you`d better do it carefully. The same goes with every collaborative system. 2. You are describing a usecase where only subwikis/workspaces are launched in production and that the main wiki is restricted to regular users, in an attempt to avoid global admins. Well... sure, but how is this different from you being the only main wiki admin and the other users to be only subwiki admins (at best)? I`m not sure it's ok to impose such a usecase to users instead of applying it only when needed. Workspaces is already designed to fulfil this usecase by not assigning any main wiki admins. It allows global users to create their own workspaces (subwikis) and play as they wish inside them, no programming rights or global admins involved. 3. I`m not sure I understand the proposed flexible solution. If by virtual wiki 2 - workspaces - workspaces (probably) you mean to allow subwikis to be created inside subwikis, then this, indeed is the new feature request that I was referring to when suggesting that you create a new jira. The idea is more general than your particular use case and can be applied to various usecases. Though I still think that one level of virtualization is enough for XWiki (as things are working right now), I accept the idea that some people might need more complex scenarios. Thanks, Eduard On Sat, Jan 28, 2012 at 7:41 PM, Haru Mamburu haru_mamb...@mail.ru wrote: Hi Eduard, Thanks for explnation. I'm very happy to issue a new idea, but idea itself is a bit wider and deeper, then described below. I would like to point out some reasons and effects to be more clear before jiraing it :-) Security leak XE/XEM Usecase XE/XEM + Workspace Manager. One main Wiki and let's say, hundreds of workspaces. To be more real we'd add Wiki Manager and tens of virtual wikis running on the same
Re: [xwiki-users] Background color for a livetable
Hi Stéphanie, a solution for this use case was posted here: http://extensions.xwiki.org/xwiki/bin/view/Extension/Background+color+for+a+livetable Hope this helps, Guillaume 2012/1/24 Stéphanie stephanie.roull...@gmail.com Hello everyone, I have a livetable build like every livetable : #livetable(allapps $collist $ colprops $options) My livetable is build using a class and one of the field of this class is state. This field can have three value : new, in progress, closed. I want to put a background color for each line depending of this field state. I want the background colors like this : - new - background color = green - in progress - background color = orange - closed - background color = red Is there a possibility to define this somewhere ? And if yes, where exactly ? In the options of my livetable ? I hope this possibility exists because I really need it. Have a good day, Stéphanie -- View this message in context: http://xwiki.475771.n2.nabble.com/Background-color-for-a-livetable-tp7219650p7219650.html Sent from the XWiki- Users mailing list archive at Nabble.com. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Not able to delete the page ?
Hi All, i am logged in as admin user who has all possible rights at wiki administration level . i have a space with the name MySpace. Now i created the page AppPage1 by mistake. i want to delete this page. But when i go for deletion , it gives me the message Are you sure you wish to move this document to the recycle bin? i clicked yes but then it gives the some run time error saying Wrapped Exception: com.jnetdirect.jsql.JSQLException: Cannot insert the value NULL into column 'XDD_ID', table 'WikiActualData.dbo.xwikirecyclebin'; column does not allow nulls. INSERT fails. at com.jnetdirect.jsql.JSQLException.makeFromDatabaseError(JSQLException.java:85) at com.jnetdirect.jsql.IOBuffer.processPackets(IOBuffer.java:547) at com.jnetdirect.jsql.JSQLStatement.getNextResult(JSQLStatement.java:2645) Complete stack trace is attached with this mail. I have tried my level best to delete this page but everytime it gives me the same error . I am not getting how to delete this page. Detailed information: Error number 0 in 3: Exception while hibernate execute Wrapped Exception: could not insert: [com.xpn.xwiki.doc.XWikiDeletedDocument] com.xpn.xwiki.XWikiException: Error number 0 in 3: Exception while hibernate execute Wrapped Exception: could not insert: [com.xpn.xwiki.doc.XWikiDeletedDocument] at com.xpn.xwiki.store.XWikiHibernateBaseStore.execute(XWikiHibernateBaseStore.java:1097) at com.xpn.xwiki.store.XWikiHibernateBaseStore.executeWrite(XWikiHibernateBaseStore.java:1143) at com.xpn.xwiki.store.XWikiHibernateRecycleBinStore.saveToRecycleBin(XWikiHibernateRecycleBinStore.java:70) at com.xpn.xwiki.XWiki.deleteDocument(XWiki.java:4298) at com.xpn.xwiki.XWiki.deleteDocument(XWiki.java:4284) at com.xpn.xwiki.XWiki.deleteAllDocuments(XWiki.java:6175) at com.xpn.xwiki.XWiki.deleteAllDocuments(XWiki.java:6164) at com.xpn.xwiki.web.DeleteAction.action(DeleteAction.java:93) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:227) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:116) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:128) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:144) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:217) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:109) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at
Re: [xwiki-users] Not able to delete the page ?
Can you delete other pages? Hope this helps, Marius On Wed, Feb 1, 2012 at 7:09 PM, mohit gupta motgu...@gmail.com wrote: Hi All, i am logged in as admin user who has all possible rights at wiki administration level . i have a space with the name MySpace. Now i created the page AppPage1 by mistake. i want to delete this page. But when i go for deletion , it gives me the message Are you sure you wish to move this document to the recycle bin? i clicked yes but then it gives the some run time error saying Wrapped Exception: com.jnetdirect.jsql.JSQLException: Cannot insert the value NULL into column 'XDD_ID', table 'WikiActualData.dbo.xwikirecyclebin'; column does not allow nulls. INSERT fails. at com.jnetdirect.jsql.JSQLException.makeFromDatabaseError(JSQLException.java:85) at com.jnetdirect.jsql.IOBuffer.processPackets(IOBuffer.java:547) at com.jnetdirect.jsql.JSQLStatement.getNextResult(JSQLStatement.java:2645) Complete stack trace is attached with this mail. I have tried my level best to delete this page but everytime it gives me the same error . I am not getting how to delete this page. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] WYSIWYG on demand
Does anyone have a working example of loading the WYSIWYG editor on-demand with velocity? Would love to see how you implemented it...I'm having some trouble with porting the code on the xwiki site. Thanks, aaron ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] How to customize the default skin and default stylesheet?
Under the presentation section of look and feel, i see skin as XWiki.DefaultSkin and DEFAULT STYLESHEET as style.css. If i want to replace both of these with my customized skin and stylesheet, how should i go about this? where should i put my both these new docs? ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] How to customize the default skin and default stylesheet?
Hi Mohit, you can override both of those by adding a XWiki.XWikiSkins object in a document and adding the name of that document in the Skin field of the presentation section of the administration. Guillaume On Thu, Feb 2, 2012 at 8:19 AM, mohit gupta motgu...@gmail.com wrote: Under the presentation section of look and feel, i see skin as XWiki.DefaultSkin and DEFAULT STYLESHEET as style.css. If i want to replace both of these with my customized skin and stylesheet, how should i go about this? where should i put my both these new docs? ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
