Re: [xwiki-users] Create document from many template
Sergiu Dumitriu-2 wrote:
roberto colferai wrote:
Sergiu Dumitriu-2 wrote:
roberto colferai wrote:
cut
We're planning to do something like this in the future by default, but
not very soon.
A way to implement this now is to:
- create the templates as wiki documents
- create a redirector page that accepts two URL parameters, document
name and template name, and does a redirect with:
$response.sendRedirect($xwiki.getURL($request.documentName, 'edit',
template=${request.templateName}))
- create a panel with a text input field for the document name and a
select (drop down) list for choosing from the templates, which submits
these fields to the redirector page from above
The above redirect works like this:
- 'edit' will display the document in edit mode (works well for
unstructured wiki documents); you can use 'inline' for structured
(form-based) documents.
- the template= parameter instructs the wiki to use another document
as a template for the edited document.
Sergiu, thank you for your answer and for your speed!
I have IT experienc from twenty years ago but only in mainframe host
system
(ibm-cobol-db2) and I have some difficult to understand completely how
you
tell.
I try to show you if I understand.
1) create the templates making one wiki-page for every templates (es. pag
template1, template2 etc)
2) create a redirect page that, I think, every users never see but works
hide. How can I make it? How can I make a page that accepts two URL
parameters?
3) create a panel (Is like create a page? I think no but I don't know
exatly
what is panel in this world). Is possibile make it with normal edit-mode
or
is an activity for developer? In this case what kind of skill I must
find?
Java programmer is enough?
In XWiki, everything is a document. And in a document you can have
plain text, wiki formatting, HTML markup, and scripting. The default and
recommended scripting language is Velocity, a really small programming
language, backed up by the XWiki API, which provides access to the data
model, the current request/response, and to other important
functionalities. This forms the unstructured part of a document. On top
of it, wiki documents can contain a data type definition (like a blog
post, an access right rule, a comment, etc), and instances of different
such structured data. Combining structured and unstructured data with
scripts you can obtain in-wiki applications, like the ones you can find
on http://code.xwiki.org/xwiki/bin/view/Applications/
The templates will be regular wiki document, with the content reflecting
the predefined information you want to see in your documents. If you
want more advanced functionalities you can define data types and instead
of unstructured content you can make full-fledged applications, but this
is harder to master.
The redirect page is another wiki document that contains as text exactly
the line of code that I wrote above. Of course, this is the quick and
dirty version, without any error handling, like missing or malformed
arguments.
The panel is a structured document, you can easily create one by going
to the Panels space and fill in the name of the new panel in the little
form that's in there, and look (edit) at the other panels for examples.
There's no need for an advanced java programmer, as our goal is to make
application development as easy as possible (we're not quite there yet,
but close enough).
I know we lack detailed tutorials, but we're busy on the implementation
with little time for documentation. You can advance by:
- looking at the other documents in the wiki, the examples on
http://code.xwiki.org/, the guides from
http://platform.xwiki.org/xwiki/bin/view/DevGuide/ and the tutorials
from http://platform.xwiki.org/xwiki/bin/view/DevGuide/Tutorials
- looking at the Velocity documentation (velocity.apache.org) and our
javadoc for the API (
http://maven.xwiki.org/site/xwiki-core-parent/xwiki-core/apidocs/com/xpn/xwiki/api/package-summary.html
)
- posting questions on IRC or the users mailing list
- getting payed support from www.xwiki.com (the best way to support
XWiki and its development)
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Wow Sergiu, you're very helpful and friendly.
Thank you very much.
Now, I have some thing to study... :-)
Best Regards
Roberto
-
ICT Area-responsable
Assimoco spa
Segrate, MI
Italy
--
View this message in context:
http://n2.nabble.com/Create-document-from-many-template-tp2424398p2428145.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
Re: [xwiki-users] Create document from many template
Hi,
made something similar not using a redirect page but the copy function and
adapted the code provided here
http://code.xwiki.org/xwiki/bin/view/Snippets/SelectDocumentToCopySnippet
First question:
Whats the better way to create pages per template? (copy or redirect)
With that code all users need programming rights to create pages as copies
from templates, is that an error in the code and is that different with the
redirect page.
Thanks
hel.
Sergiu Dumitriu-2 wrote:
roberto colferai wrote:
Sergiu Dumitriu-2 wrote:
roberto colferai wrote:
cut
We're planning to do something like this in the future by default, but
not very soon.
A way to implement this now is to:
- create the templates as wiki documents
- create a redirector page that accepts two URL parameters, document
name and template name, and does a redirect with:
$response.sendRedirect($xwiki.getURL($request.documentName, 'edit',
template=${request.templateName}))
- create a panel with a text input field for the document name and a
select (drop down) list for choosing from the templates, which submits
these fields to the redirector page from above
The above redirect works like this:
- 'edit' will display the document in edit mode (works well for
unstructured wiki documents); you can use 'inline' for structured
(form-based) documents.
- the template= parameter instructs the wiki to use another document
as a template for the edited document.
Sergiu, thank you for your answer and for your speed!
I have IT experienc from twenty years ago but only in mainframe host
system
(ibm-cobol-db2) and I have some difficult to understand completely how
you
tell.
I try to show you if I understand.
1) create the templates making one wiki-page for every templates (es. pag
template1, template2 etc)
2) create a redirect page that, I think, every users never see but works
hide. How can I make it? How can I make a page that accepts two URL
parameters?
3) create a panel (Is like create a page? I think no but I don't know
exatly
what is panel in this world). Is possibile make it with normal edit-mode
or
is an activity for developer? In this case what kind of skill I must
find?
Java programmer is enough?
In XWiki, everything is a document. And in a document you can have
plain text, wiki formatting, HTML markup, and scripting. The default and
recommended scripting language is Velocity, a really small programming
language, backed up by the XWiki API, which provides access to the data
model, the current request/response, and to other important
functionalities. This forms the unstructured part of a document. On top
of it, wiki documents can contain a data type definition (like a blog
post, an access right rule, a comment, etc), and instances of different
such structured data. Combining structured and unstructured data with
scripts you can obtain in-wiki applications, like the ones you can find
on http://code.xwiki.org/xwiki/bin/view/Applications/
The templates will be regular wiki document, with the content reflecting
the predefined information you want to see in your documents. If you
want more advanced functionalities you can define data types and instead
of unstructured content you can make full-fledged applications, but this
is harder to master.
The redirect page is another wiki document that contains as text exactly
the line of code that I wrote above. Of course, this is the quick and
dirty version, without any error handling, like missing or malformed
arguments.
The panel is a structured document, you can easily create one by going
to the Panels space and fill in the name of the new panel in the little
form that's in there, and look (edit) at the other panels for examples.
There's no need for an advanced java programmer, as our goal is to make
application development as easy as possible (we're not quite there yet,
but close enough).
I know we lack detailed tutorials, but we're busy on the implementation
with little time for documentation. You can advance by:
- looking at the other documents in the wiki, the examples on
http://code.xwiki.org/, the guides from
http://platform.xwiki.org/xwiki/bin/view/DevGuide/ and the tutorials
from http://platform.xwiki.org/xwiki/bin/view/DevGuide/Tutorials
- looking at the Velocity documentation (velocity.apache.org) and our
javadoc for the API (
http://maven.xwiki.org/site/xwiki-core-parent/xwiki-core/apidocs/com/xpn/xwiki/api/package-summary.html
)
- posting questions on IRC or the users mailing list
- getting payed support from www.xwiki.com (the best way to support
XWiki and its development)
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
-
hel.
h...@hel.at
--
View this message in context:
Re: [xwiki-users] Create document from many template
Hi Helmut,
On Thu, Mar 5, 2009 at 11:32 AM, hel-o h...@hel.at wrote:
Hi,
made something similar not using a redirect page but the copy function and
adapted the code provided here
http://code.xwiki.org/xwiki/bin/view/Snippets/SelectDocumentToCopySnippet
First question:
Whats the better way to create pages per template? (copy or redirect)
Both ways work fine. Using the redirect might be more transparent for the
user but it doesn't change much in the end. Mostly a personal preference
here ;-)
What you could do is write a manual list of documents to use as templates as
the input (instead of showing all spaces / pages).
With that code all users need programming rights to create pages as copies
from templates, is that an error in the code and is that different with the
redirect page.
This sounds weird. Programming rights are checked when rendering a page.
This means that your page has to be saved by an user with programming
rights. However, it doesn't mean that every single user who uses the page
has to have programming rights. An user with the edit right should be able
to use the snippet. This should be the same in both the redirect and the
copy modes.
Guillaume
Thanks
hel.
Sergiu Dumitriu-2 wrote:
roberto colferai wrote:
Sergiu Dumitriu-2 wrote:
roberto colferai wrote:
cut
We're planning to do something like this in the future by default, but
not very soon.
A way to implement this now is to:
- create the templates as wiki documents
- create a redirector page that accepts two URL parameters, document
name and template name, and does a redirect with:
$response.sendRedirect($xwiki.getURL($request.documentName, 'edit',
template=${request.templateName}))
- create a panel with a text input field for the document name and a
select (drop down) list for choosing from the templates, which submits
these fields to the redirector page from above
The above redirect works like this:
- 'edit' will display the document in edit mode (works well for
unstructured wiki documents); you can use 'inline' for structured
(form-based) documents.
- the template= parameter instructs the wiki to use another document
as a template for the edited document.
Sergiu, thank you for your answer and for your speed!
I have IT experienc from twenty years ago but only in mainframe host
system
(ibm-cobol-db2) and I have some difficult to understand completely how
you
tell.
I try to show you if I understand.
1) create the templates making one wiki-page for every templates (es.
pag
template1, template2 etc)
2) create a redirect page that, I think, every users never see but works
hide. How can I make it? How can I make a page that accepts two URL
parameters?
3) create a panel (Is like create a page? I think no but I don't know
exatly
what is panel in this world). Is possibile make it with normal edit-mode
or
is an activity for developer? In this case what kind of skill I must
find?
Java programmer is enough?
In XWiki, everything is a document. And in a document you can have
plain text, wiki formatting, HTML markup, and scripting. The default and
recommended scripting language is Velocity, a really small programming
language, backed up by the XWiki API, which provides access to the data
model, the current request/response, and to other important
functionalities. This forms the unstructured part of a document. On top
of it, wiki documents can contain a data type definition (like a blog
post, an access right rule, a comment, etc), and instances of different
such structured data. Combining structured and unstructured data with
scripts you can obtain in-wiki applications, like the ones you can find
on http://code.xwiki.org/xwiki/bin/view/Applications/
The templates will be regular wiki document, with the content reflecting
the predefined information you want to see in your documents. If you
want more advanced functionalities you can define data types and instead
of unstructured content you can make full-fledged applications, but this
is harder to master.
The redirect page is another wiki document that contains as text exactly
the line of code that I wrote above. Of course, this is the quick and
dirty version, without any error handling, like missing or malformed
arguments.
The panel is a structured document, you can easily create one by going
to the Panels space and fill in the name of the new panel in the little
form that's in there, and look (edit) at the other panels for examples.
There's no need for an advanced java programmer, as our goal is to make
application development as easy as possible (we're not quite there yet,
but close enough).
I know we lack detailed tutorials, but we're busy on the implementation
with little time for documentation. You can advance by:
- looking at the other documents in the wiki, the examples on
http://code.xwiki.org/, the guides from
Re: [xwiki-users] Killer App for xwiki
Hernández Cuchí wrote: Hello, In my organization we are debating between XWiki and Sharepoint. There is a functionality that makes sharepoint different from many alternatives, and it is to create forms in an easy way. I've been searching the documentation of xwiki, and even though I found that there are forms, I hadn't found a way of making them in a simple way, I mean, with a form to create the forms. Then, displaying the structured data and being able to copy paste to the office suite. So here comes the question, is there any easy way to create a formular? I mean that if there isn't, if someone knowing the technology could do it I would just be awesome. There is no public form designer for the moment, although there was an attempt to do this a few years ago (still in the sandbox), and we do know that this is a Must Have feature, but there's no volunteer for it at the moment. Technically, this shouldn't be that difficult to do for an experienced developer (either in JS or in GWT), but our GWT developers are pushing on the new WYSIWYG editor, and our JS developers are busy on other things. And I didn't see any Summer of Code candidate good enough to handle this project, maybe this year we'll have one. Another alternative for the moment is to use the class sheet found in XE, as it creates a basic automatic form for a class, one that simply lists all properties and displays them in order. So in summary, we're planning to have this as soon as we find resources or volunteers to work on it. -- Sergiu Dumitriu http://purl.org/net/sergiu/ ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Killer App for xwiki
I think you referring to sharepoint lists, which I agree and very useful and powerful, but they are not exactly form. I don't know of an easy way to customize sharepoint lists to support any business rules. I also don't know of any easy way to query data from sharepoint list. Sharepoint is very powerful and with the right level of training you can create powerful solutions quickly with it. XWiki, I believe is a different category of application. I would recommend you look into combining Xwiki with the eXo platform or Liferay, to have something similar to Sharepoint. Also look into creating portlets inside Liferay , I am not familiar with portlets, but I know that many Java frameworks allows you to create and integrate with the portlets standards. On Thu, Mar 5, 2009 at 1:50 PM, Hernández Cuchí, Francisco Ricardo francisco.hernan...@oepm.es wrote: Hello, In my organization we are debating between XWiki and Sharepoint. There is a functionality that makes sharepoint different from many alternatives, and it is to create forms in an easy way. I've been searching the documentation of xwiki, and even though I found that there are forms, I hadn't found a way of making them in a simple way, I mean, with a form to create the forms. Then, displaying the structured data and being able to copy paste to the office suite. So here comes the question, is there any easy way to create a formular? I mean that if there isn't, if someone knowing the technology could do it I would just be awesome. thanks -- Francisco Hernández Cuchí ** IMPORTANTE: El contenido de este correo y ficheros adjuntos es confidencial y está dirigido únicamente para el destinatario/s. Si Ud recibe este correo por error, por favor póngase en contacto con su administrador de correo o con el emisor immediatamente y no difunda su contenido a nadie ni haga copias. *** Este correo ha sido escaneado de virus y contenido malicioso *** ** ___ 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] Killer App for xwiki
Sergiu Dumitriu wrote: Hernández Cuchí wrote: Hello, In my organization we are debating between XWiki and Sharepoint. There is a functionality that makes sharepoint different from many alternatives, and it is to create forms in an easy way. I've been searching the documentation of xwiki, and even though I found that there are forms, I hadn't found a way of making them in a simple way, I mean, with a form to create the forms. Then, displaying the structured data and being able to copy paste to the office suite. So here comes the question, is there any easy way to create a formular? I mean that if there isn't, if someone knowing the technology could do it I would just be awesome. There is no public form designer for the moment, although there was an attempt to do this a few years ago (still in the sandbox), and we do know that this is a Must Have feature, but there's no volunteer for it at the moment. Technically, this shouldn't be that difficult to do for an experienced developer (either in JS or in GWT), but our GWT developers are pushing on the new WYSIWYG editor, and our JS developers are busy on other things. And I didn't see any Summer of Code candidate good enough to handle this project, maybe this year we'll have one. Another alternative for the moment is to use the class sheet found in XE, as it creates a basic automatic form for a class, one that simply lists all properties and displays them in order. So in summary, we're planning to have this as soon as we find resources or volunteers to work on it. Alternatively, since you're planning on spending some money, you can go to www.xwiki.com for payed support, and you can support the development of this feature. It is better to invest in Open Source than to keep feeding the MS monopoly. -- Sergiu Dumitriu http://purl.org/net/sergiu/ ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Killer App for xwiki
Thanks for the info people! The problem is that I give only technical advice, I do not make the decisions. If that would be possible, and then listing the objects with all the properties, it would rock. -Mensaje original- De: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] En nombre de Sergiu Dumitriu Enviado el: jueves, 05 de marzo de 2009 13:21 Para: XWiki Users Asunto: Re: [xwiki-users] Killer App for xwiki Sergiu Dumitriu wrote: Hernández Cuchí wrote: Hello, In my organization we are debating between XWiki and Sharepoint. There is a functionality that makes sharepoint different from many alternatives, and it is to create forms in an easy way. I've been searching the documentation of xwiki, and even though I found that there are forms, I hadn't found a way of making them in a simple way, I mean, with a form to create the forms. Then, displaying the structured data and being able to copy paste to the office suite. So here comes the question, is there any easy way to create a formular? I mean that if there isn't, if someone knowing the technology could do it I would just be awesome. There is no public form designer for the moment, although there was an attempt to do this a few years ago (still in the sandbox), and we do know that this is a Must Have feature, but there's no volunteer for it at the moment. Technically, this shouldn't be that difficult to do for an experienced developer (either in JS or in GWT), but our GWT developers are pushing on the new WYSIWYG editor, and our JS developers are busy on other things. And I didn't see any Summer of Code candidate good enough to handle this project, maybe this year we'll have one. Another alternative for the moment is to use the class sheet found in XE, as it creates a basic automatic form for a class, one that simply lists all properties and displays them in order. So in summary, we're planning to have this as soon as we find resources or volunteers to work on it. Alternatively, since you're planning on spending some money, you can go to www.xwiki.com for payed support, and you can support the development of this feature. It is better to invest in Open Source than to keep feeding the MS monopoly. -- Sergiu Dumitriu http://purl.org/net/sergiu/ ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ** IMPORTANTE: El contenido de este correo y ficheros adjuntos es confidencial y está dirigido únicamente para el destinatario/s. Si Ud recibe este correo por error, por favor póngase en contacto con su administrador de correo o con el emisor immediatamente y no difunda su contenido a nadie ni haga copias. *** Este correo ha sido escaneado de virus y contenido malicioso *** ** ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] XWiki and Kerberos SSO: authorization checks fail
Same happens with AppServerTrustedKerberosAuthServiceImpl - user gets created (I've checked in xwikidoc table), edit right is passed as parameter to createEmptyUser method (not sure where to check in the db if right has actually been applied), but still all the pages including main home page report error You are not allowed to view this document or perform this action.. Maybe it has to do with fact that user is first created (automatically just by visiting) and only after that I import initial content (xwiki-enterprise-wiki-1.8-rc-1.xar). Authentication page in admin guide mentions authkerb.jar - this jar is nowhere to be found, but also seems not to be required. One other issue is if instead empty I configure xwiki.authentication.createuser=ldap, when obtaining user details plugin wrongly tries to bind only with principal/username - binding with admin account then search should be tried as well, just like XWikiLDAPAuthServiceImpl seems to work/fallback to. If just empty user would work I'd be satisfied. I've checked out source but can not find what is wrong. Btw, source code doesn't look to be in good shape - XWiki class is huge, XWikiLDAPAuthServiceImpl has some important TODOs, XWikiRightServiceImpl's checkRight and hasAccessLevel methods are very long, lots of non externalized messages, magic values, ... Any thoughts on where to look for solution to this access rights issue would be appreciated. Thanks in advance! Regards, Stevo. On Thu, Feb 26, 2009 at 5:21 PM, Stevo Slavić ssla...@gmail.com wrote: Hello all, I'm trying to configure Kerberos SSO using AppServerTrustedAuthServiceImpl. I'm using latest xwiki, 1.8 rc 1 and to the contrary of what Admin Guide for Authentication states, this class is included in xwiki-core module. Nevertheless, I've configured application server well and set AppServerTrustedAuthServiceImpl to be used. Problem is that user authorization checks fail. In debug log I saw that user creation was started but auth_createuser context param was empty/null and thus not equal to string empty which createUser of XWikiAuthServiceImpl expects, so user wouldn't actually get created and thus when XWikiRightServiceImpl. To set auth_createuser parameter to empty I've adjusted xwiki.cfg by adding xwiki.authentication.createuser=empty. If this is what really has to be done, it would be good that Admin Guide gets updated with this information. After setting createuser to empty, debug log changed but just a little bit (see attached log archive). Now it seems that user is being created but it still has no access rights. Does someone have any ideas how to configure this to work? Thanks in advance! Regards, Stevo. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Killer App for xwiki
Just yet another idea, if somemody collect ones: I time from time thinking about embedding JasperReports in xwiki to receive analog of Crystal Reports ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Translation Volunteers needed
Hi, i decided to review all german translations because i found they are not really consistent. So i used the View All option, but when i save one result page i have to get back to the View All again and (i'm not sure) but i think the terms are not in the same order when i call the same result page twice (very bad for reviewing all terms). Whats the best way to edit and review all translation terms of a language? Thanks hel. Ludovic Dubost-2 wrote: Henning Sprang a écrit : On Mon, Feb 23, 2009 at 12:02 PM, Guillaume Lerouge guilla...@xwiki.com wrote: A XWiki Glossar would be a good thing. Good idea ! ;) ... Having something in the real translation tool where a wiki page with discussions and comments from translaters can be listed and checked would be interesting, I think. Well each language has a wiki page. http://l10n.xwiki.org/xwiki/bin/view/XE/XEXWikiCoreResources_667368132_xe-statistics-alltime_en http://l10n.xwiki.org/xwiki/bin/view/XE/XEXWikiCoreResources_667368132_xe-statistics-alltime_de http://l10n.xwiki.org/xwiki/bin/view/XE/XEXWikiCoreResources_667368132_xe-statistics-alltime_fr And comments can be used. The big question is how to make people realize there are comments. And maybe also, in the same place, a link to a place in the wiki in the language of choice where the string is used, so it can be seen in context. Including the english version for comparison ;) That would be nice but it's not so easy to know on which url the string is used.. We could find the template or wiki page and provide a URL to the source. But right now this is too much work for the translation tool developer (which happened to be me until now) Ludovic Henning ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users - hel. h...@hel.at -- View this message in context: http://n2.nabble.com/Translation-Volunteers-needed-tp2362141p2429301.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
Re: [xwiki-users] XWiki and Kerberos SSO: authorization checks fail
Just found what was the problem. Importing XAR, as Import-Export page of Admin Guide documents, alters rights: At this stage your rights might have been changed as the import may have imported different rights. You may need to log out and log in again. Problem is that log out and then log in solution for some reason doesn't work for user previously authenticated/created over kerberos. I believe this is because user is not being updated/synchronized after it has been created using AppServerTrustedKerberosAuthServiceImpl. My solution, with clean/fresh xwiki (database), was to access xwiki first with kerberos disabled (either in xwiki configuration, or just temporarly adjust browser, in my case firefox, not to trust xwiki service), then import initial content as not-logged in user, then reenable kerberos, and finally try accessing xwiki - upon that user will be created and it will have appropriate access rights. Not sure how, but I believe AppServerTrustedKerberosAuthServiceImpl should be altered to better handle this situation. Other issue with xwiki.authentication.createuser=ldap not binding/searching well for user details is still present - would be nice to have it fixed. Mentioning of authkerb.jar in Authentication page of Admin Guide should be removed, it's not needed and might be misleading. Regards, Stevo. 2009/3/5 Stevo Slavić ssla...@gmail.com Same happens with AppServerTrustedKerberosAuthServiceImpl - user gets created (I've checked in xwikidoc table), edit right is passed as parameter to createEmptyUser method (not sure where to check in the db if right has actually been applied), but still all the pages including main home page report error You are not allowed to view this document or perform this action.. Maybe it has to do with fact that user is first created (automatically just by visiting) and only after that I import initial content (xwiki-enterprise-wiki-1.8-rc-1.xar). Authentication page in admin guide mentions authkerb.jar - this jar is nowhere to be found, but also seems not to be required. One other issue is if instead empty I configure xwiki.authentication.createuser=ldap, when obtaining user details plugin wrongly tries to bind only with principal/username - binding with admin account then search should be tried as well, just like XWikiLDAPAuthServiceImpl seems to work/fallback to. If just empty user would work I'd be satisfied. I've checked out source but can not find what is wrong. Btw, source code doesn't look to be in good shape - XWiki class is huge, XWikiLDAPAuthServiceImpl has some important TODOs, XWikiRightServiceImpl's checkRight and hasAccessLevel methods are very long, lots of non externalized messages, magic values, ... Any thoughts on where to look for solution to this access rights issue would be appreciated. Thanks in advance! Regards, Stevo. On Thu, Feb 26, 2009 at 5:21 PM, Stevo Slavić ssla...@gmail.com wrote: Hello all, I'm trying to configure Kerberos SSO using AppServerTrustedAuthServiceImpl. I'm using latest xwiki, 1.8 rc 1 and to the contrary of what Admin Guide for Authentication states, this class is included in xwiki-core module. Nevertheless, I've configured application server well and set AppServerTrustedAuthServiceImpl to be used. Problem is that user authorization checks fail. In debug log I saw that user creation was started but auth_createuser context param was empty/null and thus not equal to string empty which createUser of XWikiAuthServiceImpl expects, so user wouldn't actually get created and thus when XWikiRightServiceImpl. To set auth_createuser parameter to empty I've adjusted xwiki.cfg by adding xwiki.authentication.createuser=empty. If this is what really has to be done, it would be good that Admin Guide gets updated with this information. After setting createuser to empty, debug log changed but just a little bit (see attached log archive). Now it seems that user is being created but it still has no access rights. Does someone have any ideas how to configure this to work? Thanks in advance! Regards, Stevo. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Create a tree navigation
Hi, I have a space where I want to make navigation easier. So inside this space I want to create a navigation panel, containing only the Table of contents, is it possible? The best situation would be to create tree view, like a file explorer. Does anyone know how can it be done? Thanks - Roney ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Create a tree navigation
Hi, we're currently working on a customizable treeview widget allowing to browse wikis/spaces/pages/attachments. It will be available soon, starting with XE 1.8. Thanks, JV. On Thu, Mar 5, 2009 at 4:02 PM, CASTRO roney roney.cas...@gemalto.com wrote: Hi, I have a space where I want to make navigation easier. So inside this space I want to create a navigation panel, containing only the Table of contents, is it possible? The best situation would be to create tree view, like a file explorer. Does anyone know how can it be done? Thanks - Roney ___ 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] Killer App for xwiki
For a static PPT file, the office importer seems to do reports quite nicely already: http://nielsmayer.com/xwiki/bin/view/Sandbox/Spreadsheet Niels http://nielsmayer.com On Thu, Mar 5, 2009 at 4:42 AM, r...@gradsoft.com.ua wrote: Just yet another idea, if somemody collect ones: I time from time thinking about embedding JasperReports in xwiki to receive analog of Crystal Reports ___ 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] [ANN] XWiki Enterprise 1.8 Release Candidate 2 released
The XWiki development team is pleased to announce the release of XWiki Enterprise 1.8 RC 2. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This is the second Release Candidate for the 1.8 version. Changes from 1.8RC1: Main changes: * new useravatar macro for 2.0 syntax * Improvements on 1.0-2.0 syntaxes convertion * Add ability to configure xwiki to use the XWiki Syntax 2.0 as default when creating new pages * Bugs fixed in XWiki 2.0 syntax rendering. * Upgrade to groovy 1.6 final. * Update french translations * Update german translations * Update spanish translation Important bug fixes: * XWIKI-3228 - Error while saving xwiki 2.0 documents containing anchor links * XWIKI-3242 - Entering an empty link makes the rendering blow up * XWIKI-3252 - Cannot view documents in other languages than the default when in multilingual mode and when using XWiki Syntax 2.0 For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise18RC2 Note that general goals for XWiki Enterprise 1.8 are: * Office Importer * New Blog * REST API * Finish new rendering/syntax * Finish new WYSIWYG * French XE * MediaWiki import Thanks -The XWiki dev team ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] What's new page with new Blog App?
I have installed the new blog application but my What's new page (Main/Dashboard) doesn't have any of my blog articles. The code says div id=webhomeblogdisplay style=float:left; width: 49.9%; div style=padding-right:20px; h3Blog a href=$xwiki.getURL(Main.BlogRss, view, xpage=rdf) style=img src=$xwiki.getSkinFile(icons/black-rss.png) alt=rss icon//a/h3 #set($nbstart = $request.nbstart) #set($category = Default) #set($nbitems = 3) #includeTopic(Blog.Topics) /div But that doesn't seem to work. Something else I'm supposed to use besides Blog.Topics? Thanks, -Dave -- Dave Mangot Terracotta Inc. 650 Townsend St. Suite 325 San Francisco, CA 94103 USA +1 415 738 4059 dman...@terracottatech.com This e-mail incorporates Terracotta's confidentiality policy, which is online at http://www.terracottatech.com/emailconfidentiality.shtml ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Killer App for xwiki
We've been thinking about this for a while. It is possible to script XWiki to achieve what you say but we haven't made it easy. We are actually close to it and do not even need a form designer as was suggesting Sergiu. We just need to be able to focus one developer probably for about a month just on this and we can get something very cool. I perfectly agree.. It's a killer app we should have and we are close to it. If some users that know both sharepoint and XWiki well can list us what makes XWiki great compared to Sharepoint it would really help. We are often asked how to differentiate. Ludovic Hernández Cuchí a écrit : Hello, In my organization we are debating between XWiki and Sharepoint. There is a functionality that makes sharepoint different from many alternatives, and it is to create forms in an easy way. I've been searching the documentation of xwiki, and even though I found that there are forms, I hadn't found a way of making them in a simple way, I mean, with a form to create the forms. Then, displaying the structured data and being able to copy paste to the office suite. So here comes the question, is there any easy way to create a formular? I mean that if there isn't, if someone knowing the technology could do it I would just be awesome. thanks -- Francisco Hernández Cuchí ** IMPORTANTE: El contenido de este correo y ficheros adjuntos es confidencial y está dirigido únicamente para el destinatario/s. Si Ud recibe este correo por error, por favor póngase en contacto con su administrador de correo o con el emisor immediatamente y no difunda su contenido a nadie ni haga copias. *** Este correo ha sido escaneado de virus y contenido malicioso *** ** ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Killer App for xwiki
Needless to say that if any company wants to sponsor this we can find people to implement it. Ludovic Ludovic Dubost a écrit : We've been thinking about this for a while. It is possible to script XWiki to achieve what you say but we haven't made it easy. We are actually close to it and do not even need a form designer as was suggesting Sergiu. We just need to be able to focus one developer probably for about a month just on this and we can get something very cool. I perfectly agree.. It's a killer app we should have and we are close to it. If some users that know both sharepoint and XWiki well can list us what makes XWiki great compared to Sharepoint it would really help. We are often asked how to differentiate. Ludovic Hernández Cuchí a écrit : Hello, In my organization we are debating between XWiki and Sharepoint. There is a functionality that makes sharepoint different from many alternatives, and it is to create forms in an easy way. I've been searching the documentation of xwiki, and even though I found that there are forms, I hadn't found a way of making them in a simple way, I mean, with a form to create the forms. Then, displaying the structured data and being able to copy paste to the office suite. So here comes the question, is there any easy way to create a formular? I mean that if there isn't, if someone knowing the technology could do it I would just be awesome. thanks -- Francisco Hernández Cuchí ** IMPORTANTE: El contenido de este correo y ficheros adjuntos es confidencial y está dirigido únicamente para el destinatario/s. Si Ud recibe este correo por error, por favor póngase en contacto con su administrador de correo o con el emisor immediatamente y no difunda su contenido a nadie ni haga copias. *** Este correo ha sido escaneado de virus y contenido malicioso *** ** ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
