CVS edit link for kbond

I have a module that optionally makes node fields read-only based on user roles. I would like to contribute it.
CommentFileSizeAuthor
#1 readonly_field.zip2.22 KBkbond

Comments

kbond’s picture

Component: Miscellaneous » miscellaneous
Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new2.22 KB
avpaderno’s picture

Component: miscellaneous » new project application
Status: Needs review » Needs work
Issue tags: +Module review

Hello, and thank you for applying for a CVS account. I am adding the review tags, and some volunteers will review the code, pointing out what it needs to be changed.

I will report here a little checklist:

  • The code needs to follow the coding standards; check in particular the format used for the control structures, and the name given to PHP variables, Drupal persistent variables, functions defined from the module.
  • Files available from third-party sites should not be included within the module/theme. This is particularly true for files that are not licensed under GPL License v2, but it is also true for files that are licensed under the same license used by Drupal.
  • The license file should not be included as well; the packaging script already include that file. In any cases, the code for modules/themes committed in drupal.org repository needs to be released under the same license used by Drupal; any compatible license is not allowed.
  • Check the code passes the Coder validation.

As per requirements, the motivation message should include more than two sentences (the exact words are a few paragraphs) that describe the project features. For themes, it should include also a screenshot of the theme (at least 640x400 pixels), and (when possible) a link to a working demo site; for modules, it should include also a comparison with the existing solutions.

kbond’s picture

Status: Needs work » Needs review

This is a module that allows certain fields of a node (title/body/cck) to be set to read-only when editing a node. This is useful for fields that you do not want changed after creation.

For example, you may have an alias field that is used by pathauto to generate the url. You do not want to have that field editable because that would change the url.

Configuration:

Once this module is enabled, it adds a "Read-only fields settings" to each content type's administration page. Options for all available fields to make read-only are displayed. When checked, the edit node form will 'grey' these fields out.

Similar modules:

The workflow_fields module does something similar but is an extension of workflow. This module is stand-alone.

zzolo’s picture

Status: Needs review » Postponed

Hi. Please read all the following and the links provided as this is very important information about your CVS Application:

Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for your application. Please read the following documentation on how this affects and benefits you and the application process:
Migrating from CVS Applications to (Git) Full Project Applications

  • The status of this application will be put to "postponed" and by following the instructions in the above link, you will be able to reopen it.
  • Or if your application has been "needs work" for more than 5 weeks, your application will be marked as "closed (won't fix)". You can still reopen it, by reading the instructions above.
avpaderno’s picture

Issue summary: View changes
Status: Postponed » Closed (won't fix)

As per previous comment, I am setting this issue to won't fix.

Since new users can now create full projects, applications have a different purpose and they are handled on a different issue queue. See Apply for permission to opt into security advisory coverage for more information.