[xwiki-users] Livetable and rights or filter issues

[walach84]

Hello fellow Xwikiers,

I need your help to solve a livetable issue for my business unit wiki.

I have a Livetable displaying elements of a Class "Demandes", but only a
part of them are not visible to some users without admin or programming
rights.

Only demands from 2015 are shown despite as soon as I create a new one, it
is impossible to find it in the livetable. I checked the rights = no
restrictions, I checked the livetable Velocity code = no filters anywhere.

Is it possible that it is a trouble between database query and displaying in
the livetable ? Some kind of trouble in JSON results ?

Thank you for your help.




--
View this message in context: 
http://xwiki.475771.n2.nabble.com/Livetable-and-rights-or-filter-issues-tp7602056.html
Sent from the XWiki- Users mailing list archive at Nabble.com.

Re: [xwiki-users] [UX][Proposal] Administration Overview

[Ecaterina Moraru (Valica)]

http://design.xwiki.org/xwiki/bin/view/Proposal/AdministrationOverview

On Fri, Dec 9, 2016 at 6:04 PM, Ecaterina Moraru (Valica)  wrote:

> 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
>

[xwiki-users] [UX][Proposal] Administration Overview

[Ecaterina Moraru (Valica)]

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

Re: [xwiki-users] skins, configuration, properties and symlinks

[Thomas Mortagne]

On Fri, Dec 9, 2016 at 3:00 PM, Stefan Helmerichs  
wrote:
> 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)
>

I don't have much idea. XWiki is loading everything located in the WAR
exactly the same way (trough ServletContext API) so there is no reason
they don't behave the same.


-- 
Thomas Mortagne

Re: [xwiki-users] Menu crashes if changed by a non admin user (see menu application extension)

[Marius Dumitru Florea]

Isn't it possible to separate the two? i.e. move the part that requires PR
in a separate page where your users don't have edit right and include it
using the Include macro.

On Fri, Dec 9, 2016 at 3:19 PM, Hamster  wrote:

> Actually, it's a bit more complicated than that...
>
> It's a page which holds all bits of information, but they also make notes
> on
> that page. So they should be able to make changes. But those changes break
> the PR stuff, so I need to re-save those pages for the PR stuff to work
> again.
>
>
>
> --
> View this message in context: http://xwiki.475771.n2.nabble.
> com/Menu-crashes-if-changed-by-a-non-admin-user-see-menu-
> application-extension-tp7600481p7602043.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
>

Re: [xwiki-users] Using computed field in a class

[Eduard Moraru]

Hi,

Normally, for a computed field, you can easily control both the script and
the custom displayer. The content of the script meta property gets rendered
the same for both view and edit modes, so that`s why asking explicitly for
'view' has no effect on the output.

What you could do instead, is to use the custom displayer and specify a
simplified version that the computed field will be displayed as, for view
mode. This can either be a plain text version or it can be a form input,
but disabled, as you suggested. There`s also a list of available
bindings/variables [1] that you can use, while writing a custom displayer.

Hope this helps,
Eduard

--
[1]
https://www.xwiki.org/xwiki/bin/view/FAQ/Bindings+available+inside+the+Custom+Display+property

On Tue, Dec 6, 2016 at 3:48 PM, Gerritjan Koekkoek 
wrote:

> 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
> Facebook
> email
>
>
>
>

[xwiki-users] Pages in Navigator

[Stefan Helmerichs]

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?

[xwiki-users] skins, configuration, properties and symlinks

[Stefan Helmerichs]

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)

Re: [xwiki-users] API/Scripting : create user and attach some files to its profile

[Eduard Moraru]

Hi,

Did not follow the discussion in depth, but maybe you are interested in
adding an EventListener on either DocumentCreatingEvent [1] (before) or
DocumentCreatedEvent [2] (after).

Other, more specialized, events exist as well, such as
XObjectAdded/Updated/DeletedEvent [7][8][9] that allows you to catch a user
profile page that was just created (example usage [6]). This way you`re
avoiding to do extra work in checking the type of the created page, like
you would have to do with DocumentCreatedEvent.

The event listener [3] can be built and added either as a java component
[4], a wiki component [5] or with a custom groovy script that does things
manually.

Hope this helps,
Eduard

--
[1]
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwiki-platform-bridge/src/main/java/org/xwiki/bridge/event/DocumentCreatingEvent.java
[2]
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwiki-platform-bridge/src/main/java/org/xwiki/bridge/event/DocumentCreatedEvent.java
[3]
http://platform.xwiki.org/xwiki/bin/view/DevGuide/WritingEventListenerTutorial
[4] http://platform.xwiki.org/xwiki/bin/view/DevGuide/WritingComponents
[5]
http://extensions.xwiki.org/xwiki/bin/view/Extension/WikiComponent+Module
[6]
https://github.com/xwiki/xwiki-platform/blob/456d6149d12d36f5481e70759e7974815591a2c1/xwiki-platform-core/xwiki-platform-oldcore/src/main/java/com/xpn/xwiki/internal/event/CommentEventGeneratorListener.java#L63
[7]
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwiki-platform-oldcore/src/main/java/com/xpn/xwiki/internal/event/XObjectAddedEvent.java
[8]
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwiki-platform-oldcore/src/main/java/com/xpn/xwiki/internal/event/XObjectUpdatedEvent.java
[9]
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwiki-platform-oldcore/src/main/java/com/xpn/xwiki/internal/event/XObjectDeletedEvent.java

On Thu, Dec 8, 2016 at 2:41 PM, Hamster  wrote:

> 1) I am not cutting any post. I use Nabble.
>
> http://xwiki.475771.n2.nabble.com/Re-API-Scripting-create-
> user-and-attach-some-files-to-its-profile-td7601934.html
>
> 2) I think my example shows perfectly what you want to accomplish. You want
> to attach an PDF to something which does not yet exist.
>
> Don't be scorned, I am just putting things in perspective. Unless there's
> an
> API which allows you to attach items to pages during the creation of the
> page. Otherwise the procedure will have to be (1) check if a user profile
> exists, if "yes" then attach file, if "no" then first create the user
> profile and then attach the file.
>
>
>
> --
> View this message in context: http://xwiki.475771.n2.nabble.
> com/Re-API-Scripting-create-user-and-attach-some-files-to-
> its-profile-tp7601934p7602032.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
>

Re: [xwiki-users] Menu crashes if changed by a non admin user (see menu application extension)

[Hamster]

Actually, it's a bit more complicated than that...

It's a page which holds all bits of information, but they also make notes on
that page. So they should be able to make changes. But those changes break
the PR stuff, so I need to re-save those pages for the PR stuff to work
again.



--
View this message in context: 
http://xwiki.475771.n2.nabble.com/Menu-crashes-if-changed-by-a-non-admin-user-see-menu-application-extension-tp7600481p7602043.html
Sent from the XWiki- Users mailing list archive at Nabble.com.

Re: [xwiki-users] Menu crashes if changed by a non admin user (see menu application extension)

[Marius Dumitru Florea]

If you don't want your users to edit those pages then why do you give them
edit right?

On Thu, Dec 8, 2016 at 11:36 AM, Hamster  wrote:

> Can this issue be addressed?
>
> I have to repair pages on a daily notice because people keep changing pages
> which require PR to function OK. It's very annoying. And I keep telling
> them, "No, it's not your fault. No, you can't see at this moment if a page
> requires PR. Yes, you will break those pages if you edit them".
>
> People who have no PR should not be able to edit pages which require PR!
>
> Thanks :-)
>
>
>
> --
> View this message in context: http://xwiki.475771.n2.nabble.
> com/Menu-crashes-if-changed-by-a-non-admin-user-see-menu-
> application-extension-tp7600481p7602029.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
>