5
 Followers
42
 Likes

Site properties shared between multiple eSpaces

Backend
On our radar

It would be useful to have, what we could call, site properties that would be shared between multiple eSpaces. This would avoid the replication of site properties with the same value over multiple eSpaces.
Created on 7 Sep 2010
Comments (12)
The solution to this is to create a public user action that only returns the value a site property, and is consumed by other espaces.
Although, if site properties could be made public, that way it would be easier to share site properties among espaces.
Good suggestion.

@Tiago, yes, but the problem with that is, you have to republish the consumers espace when a site-property is updated.
because the property is cached in the consumers-espace.
which imho, is not correct!


Maybe you could store the properity into a database table and enable caching on the query.

Get the information from the database, use it in any eSpace you wish.




Joost,
Don't know exactly what you mean when you say you have to republish the consumer espace when the site property is updated.
In 5.1 tried the following test, and it works ok, as I expected:
1-Consumer espace consumes action that returns the value of a site property.
2-In consumer espace displayed the current value of the site property. Ok.
3-In producer espace updated the value of the site property.
4-In consumer espace displayed the current value of the site property. Ok, displayed the new value.
No republication was needed of the consumer espaces.

Good suggestion.

@Tiago, yes, but the problem with that is, you have to republish the consumers espace when a site-property is updated.
because the property is cached in the consumers-espace.
which imho, is not correct!


very good

Merged this idea with 'Public/Private site properties' (created on 27 Oct 2016 13:37:00 by bfcantante)

Instead of have duplicate site properties in all espaces why not share? I speak about for example the Currency, DecimalSeparator, GroupSeparator.



This comment was:
- originally posted on idea 'Public/Private site properties' (created on 27 Oct 2016 by bfcantante)
- merged to idea 'Site properties shared between multiple eSpaces' on 08 Nov 2018 11:09:37 by Kilian Hekhuis
Merged this idea with ''Site properties' and 'Session Variables' with 'public' property' (created on 05 Sep 2018 13:45:07 by Huarlem Lima)

Would be of good help if 'Site properties' and 'Session Variables' had 'public' property.



This comment was:
- originally posted on idea ''Site properties' and 'Session Variables' with 'public' property' (created on 05 Sep 2018 by Huarlem Lima)
- merged to idea 'Site properties shared between multiple eSpaces' on 08 Nov 2018 11:10:18 by Kilian Hekhuis

Why?


You can create action-wrappers for them?




This comment was:
- originally posted on idea ''Site properties' and 'Session Variables' with 'public' property' (created on 05 Sep 2018 by Huarlem Lima)
- merged to idea 'Site properties shared between multiple eSpaces' on 08 Nov 2018 11:10:18 by Kilian Hekhuis

Precisely to avoid this work.



This comment was:
- originally posted on idea ''Site properties' and 'Session Variables' with 'public' property' (created on 05 Sep 2018 by Huarlem Lima)
- merged to idea 'Site properties shared between multiple eSpaces' on 08 Nov 2018 11:10:18 by Kilian Hekhuis

Changed the category to Backend




This comment was:
- originally posted on idea ''Site properties' and 'Session Variables' with 'public' property' (created on 05 Sep 2018 by Huarlem Lima)
- merged to idea 'Site properties shared between multiple eSpaces' on 08 Nov 2018 11:10:18 by Kilian Hekhuis
views
842
Followers
5