sebas5384 [sebas5384]

Hello, and thank you for applying for a CVS account.

As per requirements, the motivation should include more than two sentences (the exact words are few paragraphs) that describe the module features, and compare the proposed module with the existing solutions.

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.

If we are playing some kind of game, I am sorry but I win. :-)

Please change only the status of the report, when you add an updated version of the module.

See also my comment #3, which has been left without any answer.

So basically what this module does is create a context specified for 1 node based on its NID. When the node is created its possible to edit the context.

First I did not succeed to edit the context because it was made invisible. That was for good reason I remember out of our IRC discussion. When a lot of nodes create a context it would get a little to much. Now what I did was add a link to the context by node fieldset on the edit form of the node. This makes it possible to go to the context from the node.

Also I cleaned up some tabbing in the code that is against coding standards.

@sebas5384 I'll take a look at it but please when you post a new update give a short explanation about what you changed. Now I should go a look if I see the change? So please leave a post about your changes.

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.

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.