Closed (won't fix)
Project:
TableField
Version:
6.x-1.2
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
8 Jul 2010 at 23:53 UTC
Updated:
13 Jun 2017 at 10:54 UTC
Jump to comment: Most recent
Comments
Comment #1
zeezhao commentedsubscribing
Comment #2
danzsmith commentedSee http://drupal.org/node/764788
Comment #3
zeezhao commentedThanks. I already use that.
However, it would be nice to be able to configure all other options e.g.
- Hide "Import from CSV"
- Lock ability to edit header
etc
Comment #4
jonathan_hunt commentedTry my patch at http://drupal.org/node/764788#comment-3817136; it makes the CSV upload a per-field option.
It would be nice to be able to lock certain rows and columns also.
Comment #5
jonathan_hunt commentedI've done some further hacking on making specific cells readonly, and support for simplistic formula.
http://drupal.org/node/867574#comment-3819306
Comment #6
iantresman commentedSimplistic formula sounds like an exciting addition. Nice one.
Comment #7
jonathan_hunt commentedFYI, I've posted some code at http://drupal.org/node/867574#comment-3950696
Comment #8
bojanz commentedI have a use case (a D7 contrib module) that Tablefield might be able to solve.
The formula code sounds a bit overcomplicated to my use case, what should be the best is probably:
In field settings, provide an option to lock the table. This means no changing of numbers of rows / columns, and no changing of cells which are already filled in.
An additional option might be to allow the table to be unlocked for certain roles (a permission).
EDIT: Posted a patch that allows default values to be locked in D7 (the second part of my idea above), at #1051070: Lock default values from editing on node add/edit
Comment #9
kevin hankens commentedThanks for all of the thoughts. I'm going to commit the patch from bojanz which will take care of setting static cells: #1051070: Lock default values from editing on node add/edit
I'll try to look into the code to restrict rebuilds based on perms.
Also, thanks for being patient with the new features - got a new baby and a very fulltime job, so that slows things down :)
Comment #10
lolandese commentedClosing as "Won't fix" because the Drupal 6 version is unsupported and the issue doesn't seem to appear on Drupal 7 or 8. If you believe it does, feel free to reopen the issue and change the version as appropriate.
Of course you can also reopen the issue if you provide a patch that fixes the issue.