I have a tablefield with defaults set, and locking enabled (image 1), but end users are satill able to change the content of those fields (see image 2, data is after a save). Caches have been cleared. This is against the latest dev release but is also in the 7.x-2.4 release. If this is operator error, let's call this a support request not a bug report. :)

Other info:

  • Tablefield is on a custom EntityAPI entity.
  • Drupal core 7.41

Image 1: Locked settings.

Lock settings

Image 2: Default values changed by user.

User is still able to change defaults.  Form shown after change.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

robertwb created an issue. See original summary.

robertwb’s picture

Issue summary: View changes
jenlampton’s picture

Status: Active » Closed (cannot reproduce)

I'm unable to reproduce this problem on the latest 2.x-dev. Please update, or reopen if you are still experiencing problems.

robertwb’s picture

Component: Code » Documentation
Category: Bug report » Task
Status: Closed (cannot reproduce) » Closed (works as designed)

Thanks - I should have followed up on this - this was operator error of a sort -- users with administrator privileges are still able to edit the header line regardless of lock status. I would probably refile this as a documentation request (unless that is already part of the docs).

Thanks for your attention!