Hello XWiki developers,
I would like to know if there’s any in-built feature in XWiki that can
allow us to show a user’s page-edit history.
I am aware of the activity-stream application. However, it only shows
recent changes. Our requirement is that a user, say Joe, is able to see his
entire edit history (say from past two years) in the form of a list where
each item in the list shows the page-title, timestamp of the edit, and any
‘version summary’ he might have entered for that edit. The list should
display as paginated if it has more than 20 results. The other requirement
is that this application has to be performant as we can expect a few
hundred people to access their contribution-history every hour.
Is there something already built into XWiki that can give us this
information? Or will we have to build a new application to return this data.
Thank you for your help,
Chetan
Hi,
This is a idea proposal for an Administration Overview that:
A. Provides generic/global information about the instance like 'version',
'instance id', etc.
B. Provides a summary of usage listing count of major entities (wikis,
users, pages, extensions, etc.)
C. Lists demo content installed in the wiki
D. Provides a way for administrators to subscribe to the XWiki Community
I'm curios which of the above section sounds interesting to you and would
like to see inside the product. Also maybe you have other ideas of what is
missing or could be represented better.
Thanks,
Caty
Thank you for your quick reply,
please excute my late one ;)
Thank you, that did indeed help with the issue of configuration.
Skins do not seem to work that way though, since there are
unevaluated expressions smeared all over the page when I use a linked skin.
We updated to version 8.4.2 for this, due to EOL of the 7.4 branch in
January. Should there be any idea how to use linked skins, I would be
very happy, if not I'll just use the second approach (which is using
a separate volume for the skins)
Hi Xwiki Team,
it seems as if there is a small bug in the "Menu Application"extension
(version 8.2). Every time a user, that is not in the XWikiAdminGroup,
does some changes on the menu page in edit mode, the menu crashes and is
no longer visible. To fix that an admin user of XWikiAdminGroup has to
edit and save the page. It is important that a small change has to be
done by the admin user.
Best regards
Alina
We use computed field in a class
We would like that the sheet, that creates a xform for this class, displays these fields always in a 'disabled' mode (read-only)
Using $doc.display('computedField') currently presents the field Editable when the user is creating a new object or edits the existing object of class
We tried using $doc.display('computedField','view') but this has no effect on the computedFields; funny enough $doc.display('normalField', 'view') does put the field in 'view' (read-only) mode.
We would actually prefer that it will just a 'disabled' tag to the form field
Gerritjan Koekkoek
Vader van Rai Koekkoek (cdls) en voorzitter vereniging CdLS
Visit our website<http://www.cdlsworld.org>
Facebook<https://www.facebook.com/gerritjan.koekkoek>
email<gerritjan(a)cdlsworld.org>
Hi again,
I am using an XWiki Enterprise 8.4.2 in a docker container and use the
external data in a persisted volume. At this point, I am using no extra
database for storing the entries, so I assume that an embedded database
is used.
I am trying to import content from a MediaWiki using MediaWiki XML,
which works surprisingly well. However, none of the created pages appear
in my navigation panel. I tried creating a new page, this did also not
appear in navigation lists.
Since I imported into a sub-wiki, i changed back to the unchanged
main xwiki, but there are no pages there as well - not even the default
pages.
Skimming google for this kind of problem, I have often been sent to
Extension:Navigation-Pages, and documents about hoe hidden pages are
not displayed in said navigational tree - but as far as I can see, I
am creating regular pages which are not hidden and non-terminal as
well.
Is there anything known about this issue and maybe how to resolve it?
You must tell us what is this file?
A custom file per user? where did this file come from? Do you want this file attached to profile user?
Etc.
Your file is in your ldap ilike users photo:?
#-# [Since 8.1M2, XWikiLDAPAuthServiceImpl]
#-# On every login update photo from LDAP to XWiki avatar otherwise photo will not be updated.
#-# - 0: never
#-# - 1: at each authentication
#-# The default is 0
# xwiki.authentication.ldap.update_photo=0
Anyway you can add custom velocity code here:
/bin/edit/XWiki/XWikiUserProfileSheet?editor=wiki
(I don't know it it is a clean way, it depend of your use case desired)
--------------------------------------------
En date de : Mar 29.11.16, mh(a)ow2.org <mh(a)ow2.org> a écrit :
Objet: Re: [xwiki-users] API/Scripting : create user and attach some files to its profile
À: "XWiki Users" <users(a)xwiki.org>
Date: Mardi 29 novembre 2016, 9h00
Hi Pascal,
Thanks for the tip :)
It answers to the "how to add a
field" part of my question. But it
doesn't answer about attaching file to the
profile. The main issue I see
here is the
account is created on login. Or maybe there might be a
hook
system so we can trigger something when
the account is created( ie, to
attach files
to the profile) ?
Cheers,
Le
28/11/2016 à 08:46, Pascal BASTIEN a écrit :
> Hello,
>
> I added some others attributes (I
don't know if you can do the same with file)
> Add some attributes here:
/bin/edit/XWiki/XWikiUsers?editor=class
>
e.g. myaddress
> (disabled it to prevent
your user modified it)
>
> Add this field "myaddress" on
the sheet: /bin/view/XWiki/AdminUserProfileSheet
> and finally add it in xwiki.cfg:
> #-# retrieve the following fields from
LDAP and store them in the XWiki user object
(xwiki-attribute=ldap-attribute)
>
xwiki.authentication.ldap.fields_mapping=last_name=sn,first_name=givenName,email=xxxxx....cut....,myaddress=street
> and choose a value for this setting:
> #-# On every login update the mapped
attributes from LDAP to XWiki otherwise this happens only
once when the XWiki
> #-# account is
created.
> #-# - 0: only when creating
user
> #-# - 1: at each authentication
> #-# The default is 0
>
xwiki.authentication.ldap.update_user=1
>
>
> (eventually add
a XWiki.TranslationDocumentClass to translate myaddress
attribute)
>
>
> Pascal BASTIEN
>
>
--------------------------------------------
> En date de : Ven 25.11.16, mh(a)ow2.org <mh(a)ow2.org> a écrit
:
>
> Objet:
[xwiki-users] API/Scripting : create user and attach some
files to its profile
> À:
"XWiki Users" <users(a)xwiki.org>
> Date: Vendredi 25 novembre 2016,
12h37
>
> Hi,
>
> I'm working
on a registration system around xwiki.
>
> The basic
workflow is the user is created in a LDAP
> directory at
>
registration time. Then the user can login to xwiki.
> It's only upon the first successful
login to xwiki that the
> user's
xwiki
> profile is created in xwiki
database.
>
> Now
here is my point : how could I prepare the user profile
> *before* he
> gets
connected ? For example I would be able to attach some
> files to
>
XWiki.<username> and why not some others
attributes.
>
>
Is anyone already achieved this ?
>
> Cheers
>
_______________________________________________
> users mailing list
> users(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>
>
Hello,
I am new to xwiki (though like it a lot already...), I have installed the
release notes extension (1.3.1) but I have a problem with the
{{releasenotechanges}} macro. I may not use it properly, but I can't get my
changes appear in the release note page. I changed the default macro to use
the {{changes...}} macro instead, and it works better (but i need to
manually enter the product, version etc...) which is less convenient.
Once again I think I may not be using the extension correctly, but if
someone could point me to the documentation that could help me understand
how it works it would be much appreciated. (of course i have read this page
http://extensions.xwiki.org/xwiki/bin/view/Extension/Release+Notes+Applicat…
)
Also is there a way to change the default template of the RN to adapt it to
different context (for instance different languages)?
Regards,
Yann
Hello,
I am trying to create a docker container (based on tomcat:jre8) for
xwiki which keeps configuration and skins in volumes. So far, I have
made enough
progress that the xwiki is being deployes and the configuration
is accepted. My skins, however, are not.
I am using /var/local/xwiki/ as environment.PermanentDirectory
and I have 3 extras stored in there -
xwiki.cfg, xwiki.properties and a customSkin-directory.
I already tried to create symlinks in the container, pointing
to the files at the mount point, this was not working as the
properties file was simply ignored and the symlink was not followed.
I understood this concerning the properties file, I do not quite
understand why the cfg seems to be ignored as well (since several
template files were not loaded at all). So I had a workaround for this.
My problem is, that the symlink to the custom skin directory is present,
working, and it SHOULD work, but whenever I add ?skin=mySkin to the
current page URL (and the folder is named mySkin), my browser displays
the flamingo skin.
Is there another place, or another way, to keep the skins persisted, in
a volume to be mounted on docker?
Thanks in advance
This is the scenario that we would like to implement:
A page (we'll call it the master page) that contains a dashboard like interface that contains other objects in which the master page will keep history for all the objects that are attached. Each individual object that is added to the dashboard can be edited and saved from the master page in which the history of the master page is updated.
The operation is very similar to how the current dashboard macro works but instead of using the display gadget to only display a page it would actually allow the editing of the objects on the page. The history of the page would keep track of any edits made to the different objects.
I was wondering if there is any recommended direction to head in implementing this or if there is already a way to do such a thing. We are currently using XWiki Enterprise version 7.4.4.
Thanks,
Steve