Closed (won't fix)
Project:
Drupal.org CVS applications
Component:
new project application
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Jan 2011 at 12:51 UTC
Updated:
31 Aug 2018 at 16:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
kbond commentedComment #2
avpadernoHello, 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:
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.
Comment #3
kbond commentedThis 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.
Comment #4
zzolo commentedHi. 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
Comment #5
avpadernoAs 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.