Hello,

I think we should refresh the project page.

If you are ok, I will submit patch and proposition for the project page.

CommentFileSizeAuthor
#3 protected_node_content_type_settings.png67.22 KBgrimreaper
#3 protected_node_node_settings.png86.05 KBgrimreaper
#3 protected_node_settings.png263.78 KBgrimreaper
#1 protected_node-update_readme-2443703-1.patch9.66 KBgrimreaper

Comments

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
Status: Active » Needs review
StatusFileSize
new protected_node-update_readme-2443703-1.patch9.66 KB

Hello,

Here is patch that update the README.txt and replace API.txt with protected_node.api.php

Below is my proposition of content for the project page. Thanks for the review.

---------------------------

With the protected node module users can restrict access to a node with a
password they provide when creating the node (or a site wide password or a per
node type password.) On node creation authorized authors can protect a node by
supplying a password and verify strength of the password via JavaScript.

People who want to view the node or download one of its private attachments are
first redirected to a password query page (/protected-node). Once the user
entered the right password, he is redirected back to the original node.
Authorizations are stored in sessions, so users don't have to enter the
password over and over again once provided (requires cookies).

Email feature: The module is capable of sending the password via unencrypted
emails. This is useful if you create a page to be viewed only by a few people
you know.

Views submodule: The module has a few extensions supporting Views. It includes
filters and output extensions.

Rules submodule: The module includes a Rules extension allowing you to act on a
protected node and test the current state of a node for the current user.

Requirements

There is no special requirement for this module.

Roadmap

  1. Stable release for the D7 version: #2105245: [META] Plan for Protected Node v7.x-1.0 release
  2. (Maybe) start a 7.x-2.x branch rewritting the module for more flexibilty and removing the legacy structure and code
  3. D8 version: #2502345: Port Protected Node to Drupal 8

Known conflicts

  • Protected Pages: Protected Pages uses the path to protect your page. So you can password protect Views pages for example.

Maintainers

Current maintainers:

izus’s picture

izus commented
Status: Needs review » Needs work

deletions are with tag and additions with []

also what can be needed here is maybe some screenshots

pour the drupal6 issues, i think that an evaluation can be done to know if we are interested is some of the feature requests (i've already heard people wanting this on their projects per example #286028: Would you consider a patch for inheriting node protections?)

With the protected node module[,] users can restrict access to a node with a
password they provide when creating the node (or a site wide password or a per
node type password.)[.]
On node creation[,] authorized authors can protect a node by
supplying a password and verifi[ying the] strength of the password via JavaScript.

People who[Users that] want to view the node or download one of its private attachments are
first redirected to a password query page (/protected-node). Once the user
entered the right password, he is They are redirected back to the original node.
Authorizations are stored in sessions, so users don't have to enter the
password over and over again once provided (requires cookies).

+++ b/protected_node.module
@@ -1175,6 +1175,17 @@ function protected_node_set_protected($param, $passwd = NULL) {
+ * If an invalid $nid is passed, an SQL error occurs or the node was not

this sentence is not very clear

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
StatusFileSize
new protected_node_settings.png263.78 KB
new protected_node_node_settings.png86.05 KB
new protected_node_content_type_settings.png67.22 KB

Thanks for the feedbacks.

Here are 3 screenshots.

I forgot to write that for the D6 branch, I will only merge patches in RTBC.

About the D6 features request that are not in the D7 branch, yes why not looking for them but the priority is to have a stable D7 version (almost done yeah!!!). And then I think to be able to handle those features requests, There will be necessary to rewrite the module in a 7.x-2.x branch.

And I don't know how I will prioritize between the 7.x-2.x and the 8.x-1.x.

While I am thinking about it, maybe we should ask the maintainer of protected_pages (and other modules like that) if we can't make only one module for D8 that will be enough generic to regroup the modules in D7.

Yeah, it was copy/pasted from the API.txt file, I will use "If an invalid $nid is passed FALSE is returned.". And I found the protected_node_unset_protected strange.

izus’s picture

izus commented

cool
screenshots may need to be reworked/cut/adpated/zoommed, as we will add them we'll see if they are visible and readable...we just need to test :)

idk for d8, actually the two modules have two strategies for two different concerns
protected_node has deep integration with node entity and its fields/view mode ?....
protected_page care only about the path

if there is an architecture to integrate both, it would be good to do that, but i have no clue for this, i need to play with drupal8 more and more !

  • Grimreaper committed a686414 on 7.x-1.x 
    Issue #2443703 by izus, Grimreaper: Update README.txt and replace API....
grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
Status: Needs work » Fixed

Hello,

This is now merged. And I have updated the project page.

Thanks for the review.

Do not hesitate to change something if you feel it need to be changed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

digitgopher’s picture

digitgopher commented
Status: Closed (fixed) » Active

I noticed a slight problem. After the update I think the 'new line' characters were pasted in from the README. For example, on the project page there two returns in the middle of the first sentence.

Aditionally, I think it would be nice to add a bit more about how this module is different from Protected Pages. I think one of the main benefits of Protected Node is that content creators can add the password as they create content, they don't have to go to another configuration page.

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
Status: Active » Fixed

Thanks digitgopher,

I refreshed the project page and refreshed the README.txt.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.