Re: [xwiki-users] Upgrade from 1.4 to 1.6.1 and need to resave all script pages???!??
underbad wrote: Sorry being a pain.. Is there no way of avoiding this? It effectively stops me from upgrading past my current version of xwiki. You shouldn't need this at all. Why are you saying it is not working? Programming rights are lost in three cases: 1. You save the affected document with a user without programming rights (in which case you are intentionally removing rights) 2. You delete the user who provided programming rights to the document (and you just need to re-create the user, not save all the documents) 3. You delete the rights from that user (and you just need to re-add those rights) Make sure it isn't only a cache problem, try restarting the wiki after you import the new data and set the proper rights. underbad wrote: Seems when you upgrade from 1.4.1 to 1.6.1 then you need to resave all pages that have restricted calls in them? For example, I use .search() in some of my pages, but after upgrading the xwiki they won't work until I resave the pages. On upgrading, I did not import the XWiki.Admin user (this caused problems the first time I upgraded so I avoid that now). I have about 200-250 pages in this state. Can this be done in one sweep, or can it be turned off? -- Sergiu Dumitriu http://purl.org/net/sergiu/ ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Upgrade from 1.4 to 1.6.1 and need to resave all script pages???!??
Thanks, In this case I use XWiki.Admin as the user for all developments. Other than importing the XAR (did not updating standard groups and users), only change is the new xwiki war to the newer version. On Fri, Dec 12, 2008 at 11:01 AM, Sergiu Dumitriu ser...@xwiki.com wrote: underbad wrote: Sorry being a pain.. Is there no way of avoiding this? It effectively stops me from upgrading past my current version of xwiki. You shouldn't need this at all. Why are you saying it is not working? Programming rights are lost in three cases: 1. You save the affected document with a user without programming rights (in which case you are intentionally removing rights) 2. You delete the user who provided programming rights to the document (and you just need to re-create the user, not save all the documents) 3. You delete the rights from that user (and you just need to re-add those rights) Make sure it isn't only a cache problem, try restarting the wiki after you import the new data and set the proper rights. underbad wrote: Seems when you upgrade from 1.4.1 to 1.6.1 then you need to resave all pages that have restricted calls in them? For example, I use .search() in some of my pages, but after upgrading the xwiki they won't work until I resave the pages. On upgrading, I did not import the XWiki.Admin user (this caused problems the first time I upgraded so I avoid that now). I have about 200-250 pages in this state. Can this be done in one sweep, or can it be turned off? -- Sergiu Dumitriu http://purl.org/net/sergiu/ ___ 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] Upgrade from 1.4 to 1.6.1 and need to resave all script pages???!??
On Fri, Dec 12, 2008 at 12:01 PM, Sergiu Dumitriu ser...@xwiki.com wrote: underbad wrote: Sorry being a pain.. Is there no way of avoiding this? It effectively stops me from upgrading past my current version of xwiki. You shouldn't need this at all. Why are you saying it is not working? Programming rights are lost in three cases: 1. You save the affected document with a user without programming rights (in which case you are intentionally removing rights) 2. You delete the user who provided programming rights to the document (and you just need to re-create the user, not save all the documents) 3. You delete the rights from that user (and you just need to re-add those rights) It reminds me a problem I had once. When the importer overwrite a page it first delete it, and when the XWiki.Admin user is deleted its XWiki.XWikiAdminGroup membership is deleted too. In this case, when you import the XWiki.Admin user by mistake you can have to put it in the XWiki.XWikiAdminGroup again. JV. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Upgrade from 1.4 to 1.6.1 and need to resave all script pages???!??
On Fri, Dec 12, 2008 at 1:22 PM, Jean-Vincent Drean jean-vinc...@drean.org wrote: On Fri, Dec 12, 2008 at 12:01 PM, Sergiu Dumitriu ser...@xwiki.com wrote: underbad wrote: Sorry being a pain.. Is there no way of avoiding this? It effectively stops me from upgrading past my current version of xwiki. You shouldn't need this at all. Why are you saying it is not working? Programming rights are lost in three cases: 1. You save the affected document with a user without programming rights (in which case you are intentionally removing rights) 2. You delete the user who provided programming rights to the document (and you just need to re-create the user, not save all the documents) 3. You delete the rights from that user (and you just need to re-add those rights) It reminds me a problem I had once. When the importer overwrite a page it first delete it, and when the XWiki.Admin user is deleted its XWiki.XWikiAdminGroup membership is deleted too. In this case, when you import the XWiki.Admin user by mistake you can have to put it in the XWiki.XWikiAdminGroup again. The importer does not sens delete notification anymore. See http://jira.xwiki.org/jira/browse/XWIKI-2365 JV. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users -- Thomas Mortagne ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] advice on wiki structure
Ricardo (and anyone else who like me needed to do more with users and groups than xwiki provides by default), This may help you get started and save time. I have added a bunch of extra properties to users to store more information by changing XWikiUserSheet and use velocity to display the information in useable ways. Below is the basics of a page I have for simply displaying all the info for every user of the wiki, although in our case it has a bunch of custom properties. Following that is some code to show users in each group. /**Start code here**/ All Team Members on the Wiki (using velocity) #set ($sql = , BaseObject as obj where obj.name=doc.fullName and obj.className='XWiki.XWikiUsers') #set ($allUsers = $xwiki.searchDocuments($sql)) Click User name to get more information or edit profile table id=userTable class=grid sortable filterable doOddEven cellpadding=0 cellspacing=0 border=0 nowrap tr class=sortHeader thUser/th thProject/th thEmail/th thCompany/th /tr #foreach ($user in $allUsers) #set ($userdoc = $xwiki.getDocument($user)) #set ($em = $userdoc.display(email,view,$user)) tr td[$userdoc.first_name $userdoc.last_name | $userdoc] /td td $userdoc.display(other_info,view,$user)/td td[$em | mailto:$em ]/td td $userdoc.display(company,view,$user)/td /tr #end /table /**END xwiki code /**Start code here**/ Get the email of all users in a group (using velocity) #set ($sql = , BaseObject as obj where obj.name=doc.fullName and obj.className='XWiki.XWikiGroups') #set ($allGroups = $xwiki.searchDocuments($sql)) #foreach ($group in $allGroups) 1.1 $group #set ($groupdoc = $xwiki.getDocument($group)) #set ($groupMembers = $util.sort($xwiki.rightsmanager.getAllMembersNamesForGroup($groupdoc.name))) #foreach ($mem in $groupMembers) #set ($userdoc = $xwiki.getDocument($mem)) #set ($em = $userdoc.display(email,view,$mem)) $embr #end #end /**END xwiki code -Original Message- From: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] On Behalf Of [Ricardo Rodriguez] Your EPEC Network ICT Team Sent: Thursday, December 11, 2008 1:56 AM To: XWiki Users Subject: Re: [xwiki-users] advice on wiki structure Hi Graham, If you are looking for consultancy, I am sure http://xwiki.com is the right place to start with. If you are simply asking if what you are looking for is possible with XWiki, I think yes. I think it is worth you take a look to Virtual servers (http://www.xwiki.org/xwiki/bin/view/FAQ/HowToSetupVirtualWikis) and XWiki Enterprise Manager (http://manager.xwiki.org/xwiki/bin/view/Main/). XWiki has a huge number of features, many of them not obvious by now for a regular user like me, that allow fine grained access control and a complete separation between business rules, presentation and data. I think we need a better understanding of the available tools and a lot of imagination to put things together! :-) Hope this helps, Ricardo creegers wrote: I'm currently trying to measure XWIKI against some business requirements; our business are basically looking for a simple WIKI that we can use to store corporate/enterprise knowledge in a single place and make available to the public via our websites and internally to our customer service agents. For a little more background to the requirements, the business is a financial institution that provides loan products in different countries. Each country currently has their own website (served on different domains, with no obvious links to others), customers can apply for financial products and administer their accounts through the sites, the terminology used to describe the products is the same regardless of the country, however the business rules e.g. application process, interest rates is/can be different. The business want to expose the content deemed as publicly available through a FAQ/WIKI section on each website, however they don't wish other countries content to be displayed on that website. Our customer service agents should be able to search the entire WIKI when dealing with customers phone enquiries, they also wish there to be more internal information available to the agents. I'm struggling to think of a way to achieve this using XWIKI and would be grateful of any advice. Thanks in advance Graham -- Ricardo RodrÃguez Your EPEC Network ICT Team ___ 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] advice on wiki structure
Cool! Don't you think this is worth a FAQ entry? Look at http://www.xwiki.org/xwiki/bin/view/FAQ/ Thanks! Ricardo Regan Gill wrote: Ricardo (and anyone else who like me needed to do more with users and groups than xwiki provides by default), This may help you get started and save time. I have added a bunch of extra properties to users to store more information by changing XWikiUserSheet and use velocity to display the information in useable ways. Below is the basics of a page I have for simply displaying all the info for every user of the wiki, although in our case it has a bunch of custom properties. Following that is some code to show users in each group. /**Start code here**/ All Team Members on the Wiki (using velocity) #set ($sql = , BaseObject as obj where obj.name=doc.fullName and obj.className='XWiki.XWikiUsers') #set ($allUsers = $xwiki.searchDocuments($sql)) Click User name to get more information or edit profile table id=userTable class=grid sortable filterable doOddEven cellpadding=0 cellspacing=0 border=0 nowrap tr class=sortHeader thUser/th thProject/th thEmail/th thCompany/th /tr #foreach ($user in $allUsers) #set ($userdoc = $xwiki.getDocument($user)) #set ($em = $userdoc.display(email,view,$user)) tr td[$userdoc.first_name $userdoc.last_name | $userdoc] /td td $userdoc.display(other_info,view,$user)/td td[$em | mailto:$em ]/td td $userdoc.display(company,view,$user)/td /tr #end /table /**END xwiki code /**Start code here**/ Get the email of all users in a group (using velocity) #set ($sql = , BaseObject as obj where obj.name=doc.fullName and obj.className='XWiki.XWikiGroups') #set ($allGroups = $xwiki.searchDocuments($sql)) #foreach ($group in $allGroups) 1.1 $group #set ($groupdoc = $xwiki.getDocument($group)) #set ($groupMembers = $util.sort($xwiki.rightsmanager.getAllMembersNamesForGroup($groupdoc.name))) #foreach ($mem in $groupMembers) #set ($userdoc = $xwiki.getDocument($mem)) #set ($em = $userdoc.display(email,view,$mem)) $embr #end #end /**END xwiki code -Original Message- From: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] On Behalf Of [Ricardo Rodriguez] Your EPEC Network ICT Team Sent: Thursday, December 11, 2008 1:56 AM To: XWiki Users Subject: Re: [xwiki-users] advice on wiki structure Hi Graham, If you are looking for consultancy, I am sure http://xwiki.com is the right place to start with. If you are simply asking if what you are looking for is possible with XWiki, I think yes. I think it is worth you take a look to Virtual servers (http://www.xwiki.org/xwiki/bin/view/FAQ/HowToSetupVirtualWikis) and XWiki Enterprise Manager (http://manager.xwiki.org/xwiki/bin/view/Main/). XWiki has a huge number of features, many of them not obvious by now for a regular user like me, that allow fine grained access control and a complete separation between business rules, presentation and data. I think we need a better understanding of the available tools and a lot of imagination to put things together! :-) Hope this helps, Ricardo creegers wrote: I'm currently trying to measure XWIKI against some business requirements; our business are basically looking for a simple WIKI that we can use to store corporate/enterprise knowledge in a single place and make available to the public via our websites and internally to our customer service agents. For a little more background to the requirements, the business is a financial institution that provides loan products in different countries. Each country currently has their own website (served on different domains, with no obvious links to others), customers can apply for financial products and administer their accounts through the sites, the terminology used to describe the products is the same regardless of the country, however the business rules e.g. application process, interest rates is/can be different. The business want to expose the content deemed as publicly available through a FAQ/WIKI section on each website, however they don't wish other countries content to be displayed on that website. Our customer service agents should be able to search the entire WIKI when dealing with customers phone enquiries, they also wish there to be more internal information available to the agents. I'm struggling to think of a way to achieve this using XWIKI and would be grateful of any advice. Thanks in advance Graham -- Ricardo RodrÃguez Your EPEC Network ICT Team
Re: [xwiki-users] advice on wiki structure
[Ricardo Rodriguez] Your EPEC Network ICT Team wrote: Cool! Don't you think this is worth a FAQ entry? Look at http://www.xwiki.org/xwiki/bin/view/FAQ/ Or even better, a snippet on code.xwiki.org Regan Gill wrote: Ricardo (and anyone else who like me needed to do more with users and groups than xwiki provides by default), This may help you get started and save time. I have added a bunch of extra properties to users to store more information by changing XWikiUserSheet and use velocity to display the information in useable ways. Below is the basics of a page I have for simply displaying all the info for every user of the wiki, although in our case it has a bunch of custom properties. Following that is some code to show users in each group. /**Start code here**/ All Team Members on the Wiki (using velocity) #set ($sql = , BaseObject as obj where obj.name=doc.fullName and obj.className='XWiki.XWikiUsers') #set ($allUsers = $xwiki.searchDocuments($sql)) Click User name to get more information or edit profile table id=userTable class=grid sortable filterable doOddEven cellpadding=0 cellspacing=0 border=0 nowrap tr class=sortHeader thUser/th thProject/th thEmail/th thCompany/th /tr #foreach ($user in $allUsers) #set ($userdoc = $xwiki.getDocument($user)) #set ($em = $userdoc.display(email,view,$user)) tr td[$userdoc.first_name $userdoc.last_name | $userdoc] /td td $userdoc.display(other_info,view,$user)/td td[$em | mailto:$em ]/td td $userdoc.display(company,view,$user)/td /tr #end /table /**END xwiki code /**Start code here**/ Get the email of all users in a group (using velocity) #set ($sql = , BaseObject as obj where obj.name=doc.fullName and obj.className='XWiki.XWikiGroups') #set ($allGroups = $xwiki.searchDocuments($sql)) #foreach ($group in $allGroups) 1.1 $group #set ($groupdoc = $xwiki.getDocument($group)) #set ($groupMembers = $util.sort($xwiki.rightsmanager.getAllMembersNamesForGroup($groupdoc.name))) #foreach ($mem in $groupMembers) #set ($userdoc = $xwiki.getDocument($mem)) #set ($em = $userdoc.display(email,view,$mem)) $embr #end #end /**END xwiki code -Original Message- From: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] On Behalf Of [Ricardo Rodriguez] Your EPEC Network ICT Team Sent: Thursday, December 11, 2008 1:56 AM To: XWiki Users Subject: Re: [xwiki-users] advice on wiki structure Hi Graham, If you are looking for consultancy, I am sure http://xwiki.com is the right place to start with. If you are simply asking if what you are looking for is possible with XWiki, I think yes. I think it is worth you take a look to Virtual servers (http://www.xwiki.org/xwiki/bin/view/FAQ/HowToSetupVirtualWikis) and XWiki Enterprise Manager (http://manager.xwiki.org/xwiki/bin/view/Main/). XWiki has a huge number of features, many of them not obvious by now for a regular user like me, that allow fine grained access control and a complete separation between business rules, presentation and data. I think we need a better understanding of the available tools and a lot of imagination to put things together! :-) Hope this helps, Ricardo creegers wrote: I'm currently trying to measure XWIKI against some business requirements; our business are basically looking for a simple WIKI that we can use to store corporate/enterprise knowledge in a single place and make available to the public via our websites and internally to our customer service agents. For a little more background to the requirements, the business is a financial institution that provides loan products in different countries. Each country currently has their own website (served on different domains, with no obvious links to others), customers can apply for financial products and administer their accounts through the sites, the terminology used to describe the products is the same regardless of the country, however the business rules e.g. application process, interest rates is/can be different. The business want to expose the content deemed as publicly available through a FAQ/WIKI section on each website, however they don't wish other countries content to be displayed on that website. Our customer service agents should be able to search the entire WIKI when dealing with customers phone enquiries, they also wish there to be more internal information available to the agents. I'm struggling to think of a way to achieve this using XWIKI and would be grateful of any advice. Thanks in advance Graham -- Sergiu Dumitriu
