You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hello
We use the LDAP feature on our Dokuwiki and find out some delay on pages.
After activating some tracking we've found that tag page or page with {{topic>}} or even with Tagcloud (cloud plugin using tag) were doing multiple calls to the LDAP, even if the user is not identified (from 3 to at least 40 for the cloud). Pages with simple tag don't have this issue.
When not identified, the id sent is empty.
When identified the id is the user one.
But we've found another strangest thing : when not identified, there's a last call done with the page's author id and not the user one.
We cannot let so many unnecessary calls done to our LDAP.
thanks for you help.
A.
The text was updated successfully, but these errors were encountered:
Hi,
It seems I found at leadt one issue in helper.php : the function _applyMacro is called for each tag when search linked pages, and this function is calling getUserData in place of using $INFOUSER.
I don't understand the use of this function knowing that I cannot found any documentation of using topic with a current user data or current date.
At this point I just put in comment the call to this function in _cleanTag.
hello
We use the LDAP feature on our Dokuwiki and find out some delay on pages.
After activating some tracking we've found that tag page or page with {{topic>}} or even with Tagcloud (cloud plugin using tag) were doing multiple calls to the LDAP, even if the user is not identified (from 3 to at least 40 for the cloud). Pages with simple tag don't have this issue.
When not identified, the id sent is empty.
When identified the id is the user one.
But we've found another strangest thing : when not identified, there's a last call done with the page's author id and not the user one.
We cannot let so many unnecessary calls done to our LDAP.
thanks for you help.
A.
The text was updated successfully, but these errors were encountered: