Hey guys,
I REALLY want to get this module to work as its exactly what I need to try and secure some galleries I have, but no matter what I do, the password page never appears for me. I am using Drupal 7.14 so I know this is a dev module for this version. I initially got an error, but after looking at past issues, I realized i had to comment out line 297 of protected_node_settings.inc which was "_user_password_dynamic_validation();". This made the error go away, but if I go to a node and enable a password and then go to that node, I get a Drupal "Access is denied" as opposed to the Password form. I went into permissions and enabled "access protected content" and "view protected content" for anonymous users and that just makes the "Access Denied" message go away. I still do not ever get a password form. I also tried using a browser with all my cookies cleared. Am I missing something? Or is this just not compatible with 7.14?
THANKS
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | readme_update-1649298-15.patch | 375 bytes | grimreaper |
| #8 | add_readme-1649298-8.patch | 2.08 KB | grimreaper |
| #5 | add_readme-1649298-5.patch | 36.22 KB | grimreaper |
Comments
Comment #1
Screenack commentedI found this page while researching an issue with implementing Protected Node. There's a patch here: http://drupal.org/node/1617766 (#1, greggles) + enabling the permission you identify, allows me to see the form. At least it's working for me now. #7 suggests there may be other configuration options that, unset, cause the module to fail. I hope this helps.
Comment #2
thaddeusmt commentedI ran into this issue where anonymous users could not see the form - just the Access Denied message as you say.
Of course, it was a permissions issue, not a bug. :) I had to check that "Anonymous Users" had the "access protected content" permission, and then the form started showing up.
I hope this helps anyone else who forgets to set the permission. Maybe this should be a "sensible default" setting on installation?
Comment #3
AlexisWilke commentedSee also Drupal 6.x issue #1792832: Can't get password form to show in Drupal 6.15
Comment #4
izus commentedthe issue encountred here (check a permission) is a lack of documentation.
all what we need here is a README.txt
Comment #5
grimreaperHello,
Here is a first try to add readme.txt and install.txt files in the module.
I only copy/paste the online documentation. I don't check for errors or outdated information (I know the email support is a little outdated) because I want to know before if I should continue in this way or if what I have done is not what is expected.
In the documentation in the readme.txt file, it's impossible to add images like the online documentation.
I don't know if we should add the documentation on a drupal.org page like the media project because we can't edit the online documentation on a distant website.
I also want to make an online documentation in French on my personal website.
I also don't know if there is a standard format for the readme.txt files.
If you have any suggestions, do not hesitate to respond.
Thanks.
Comment #6
izus commentedYou can start reading https://drupal.org/node/447604 and https://drupal.org/node/161085
Notes :
- install file should only deal with the installation of the module, it shouldn't deal with evry ossible configuration. The details should go to Redme.txt
- i think that we will allway prefer an updated basic readme.txt file rather than a very detailed but outdated one.
After a general description of the module (the fact that it uses $_SESSION), you can just describe the features in words and give urls to them (email support, global password/per node ....), dressing a list of supported modules...
- you have extra spaces in the txt files, be sure to delete then and to limt the number of caracters to 80 per line whenever it is possible following the Drupal standars.
- A documentation page in drupal.org is a good idea, generally this is very used for modules that have a lot of configuration or document the way other modules can interact with them. i think that a readme.txt will be a good start, we can probabely create a page just before a staber version is there.
- in drupal.org documentation is made in english, you can of course maintain a french documentation on your website
Comment #7
grimreaperThanks for the links.
Yeah, I will make a short readme.txt, near the size (without the d6/d5 part) of the current module description.
About the documentation page on drupal.org, I don't know if it's a good or bad thing, I don't know what will be the reaction of the person who write the current online documentation on an external website even if it's mentionned in a drupal.org documentation. But if you tell me ok, let's go.
I will try to write it next weekend.
Comment #8
grimreaperHello,
Here is I think a better readme.txt.
I also started to translate the documentation in french on my website : http://assos.centrale-marseille.fr/ftorregrosa/page-de-livre/documentati...
I hesitated to make a link to the french doc in the readme.txt, I don't know if it's a good practice.
@izus, confirm me to create documentation pageS on Drupal.org. And I will copy/paste the content of the original documentation while updating it.
Thanks for the review.
Comment #9
izus commentedof course you can create a doc page on drupal.org !
Thanks
Comment #10
izus commentedEdit, added a relation to another issue that contans README.txt to be sure we commit the right version when one or the other are reviewed for merging
Comment #11
izus commentedmerged #8 as a good initial work, i belive we'll need to edit it before a stable release.
Thanks all
Comment #12
grimreaperThanks, now I can update it in the next patches for the other issue.
Comment #13
grimreaperDocumentation on drupal.org
https://drupal.org/node/2176627
Should I update the readme.txt now ?
Comment #14
izus commentedok, you can do it here.
i updated the project page documentation link.
thanks
Comment #15
grimreaperComment #16
izus commentedfixed readme with #15
thanks