As far as I know "LDAP service is not available" error message is only
displayed in LDAP UI extension and indicate that it cannot find the
service that is supposed to be located in xwiki-platform-ldap-api
("XWiki Platform - LDAP - API" extension) jar. Either you installed it
by hand last time and
Hello,
Is it possible not to import an existing document in a XAR Package ?
because I have 350 documents in that package and i really don't want to
check if every document exists...
Regards,
Quentin
--
View this message in context:
Hi!
Yes. To make sure I copied xwiki.cfg from old to new version again and
restart xwiki.
In xwiki.cfg in LDAP section uncommented only next strings
xwiki.authentication.authclass=com.xpn.xwiki.user.impl.LDAP.XWikiLDAPAuthServiceImpl
xwiki.authentication.ldap.server=127.0.0.1
Hi Quentin,
There's no such option in the import UI but a developer can add it
relatively easy:
* add a "new" link to the "select none, all" options using JavaScript
* catch the click event on the "new" link and send an AJAX request to
a wiki page, passing the selected documents
* in that wiki
Hi Quentin,
Also feel free to report a jira issue at http://jira.xwiki.org to suggest
adding this feature if you feel the need is a generic need.
Thanks
-Vincent
On 9 Sep 2015 at 11:48:42, Marius Dumitru Florea
(mariusdumitru.flo...@xwiki.com(mailto:mariusdumitru.flo...@xwiki.com)) wrote:
>
Thank you! It is our situation, we installed "XWiki Platform - LDAP - API" in
extension manager on new version and error message disappeared.
--
View this message in context:
http://xwiki.475771.n2.nabble.com/LDAP-service-is-not-available-after-update-from-6-4-2-to-7-1-2-tp7595928p7595945.html
Thanks Marius, I will try it.
--
View this message in context:
http://xwiki.475771.n2.nabble.com/Do-not-import-existing-document-tp7595939p7595941.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
___
users mailing list
2015-09-05 3:17 GMT-06:00 vinc...@massol.net :
> ok, I understand what you mean now: you’d like the ability to lock down
> existing applications, i.e. prevent users of them from making structural
> changes to them.
>
> That’s a valid use case and we support it :)
>
>