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

Attribute Table in read only mode #9180

Closed
4 tasks done
tdipisa opened this issue May 17, 2023 · 2 comments · Fixed by #9212 or #9227
Closed
4 tasks done

Attribute Table in read only mode #9180

tdipisa opened this issue May 17, 2023 · 2 comments · Fixed by #9212 or #9227

Comments

@tdipisa
Copy link
Member

tdipisa commented May 17, 2023

Description

As discussed and agreed with #7285 it is necessary to have the Attribute Table in read-only as needed for certain layers in TOC.
It is required to have the ability to make the Attribute Table read-only per layer if desired (eg. because a layer has been added to a map for consultation purposes only and not to be edited). For these layers the editing mode of the Attribute Table should be disabled at all.

Acceptance criteria

  • A new configuration property (of type boolean) will be added for WMS layers in Layer Settings as indicated here
  • If checked (and so True) the editing mode for the Attribute Table will be disabled for the layer (eg. pencil icon not available)
  • The editing functionality of the Attribute Table (plugins.FeatureEditor) can be reached also from the Identify tool if its cfg.showEdit property is set to true. That case should be managed accordingly (eg. the pencil icon in Identify panel not available) according the value of the new property in Layer Settings
  • As indicated here the context editor (who has write permission on the context) can control that option from layers settings of layers added in the context (step 2 of the wizard). The map editor (who has write permission on a map) can do the same at map level. The others cannot control that option and it should not be visible.

Other useful information

See also #9179

@tdipisa
Copy link
Member Author

tdipisa commented Jun 15, 2023

@dsuren1, @ElenaGallo, @offtherailz I have to reopen this since you missed to consider one quite relevant point I've not included previously by mistake in the AC list of this issue but it present in the original issue #7285. I've updated the AC list above.

@dsuren1
Copy link
Contributor

dsuren1 commented Jun 16, 2023

Hi @tdipisa
I will update the code to show this option only if user has write permission to map and context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment