Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Structure related fields should be customisable ? #1614

Closed
camillemonchicourt opened this issue Oct 7, 2016 · 3 comments
Closed

Structure related fields should be customisable ? #1614

camillemonchicourt opened this issue Oct 7, 2016 · 3 comments

Comments

@camillemonchicourt
Copy link
Member

camillemonchicourt commented Oct 7, 2016

Actually all the lists in the MANAGEMENT modules (paths, trail, landedges, infrastructures, signages, interventions and projects) are structure_related. It means that each structure in a same Geotrek has his own values for each list.
This is not the case for COMMUNICATION modules (treks, POIs, touristic contents and events...) where all structures have the same values in one Geotrek, in order to be able to publish a common Geotrek-rando portal.
This is interesting when 2 structures dont have the same types of signages or the same type of interventions.
But it can be a problem if they want to work on the same types for some informations.
Recently someone wanted to have to same landtypes or the same organisms...

One solution is to add CAN BYPASS STRUCTURE to some users or groups of users but it can also be a problem as it displays all values everywhere. And other users without these rights will not see the same lists...

Another idea is to be able to associate one value to 1 structure or to ALL structures.

This structure_related fields may are to think again in the near future...

@LePetitTim
Copy link
Contributor

LePetitTim commented Aug 20, 2018

#1744 : We can put none related Structure adding the possibility to work on the same element.
(Geotrek 2.20.0)

#1767 : Create a command to unset elements with structure. Check command's help.

@camillemonchicourt
Copy link
Member Author

Yes, these are some great new features.

@gutard
Copy link
Contributor

gutard commented Sep 4, 2018

Fixed in v2.21.0

@gutard gutard closed this as completed Sep 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants