I am doing a Drupal 7 version of Anonymous Publishing.

Please use this issue queue to post reviews and bug rapports about the Drupal 7 code base.

Comments

gisle’s picture

Issue summary: View changes

Removed obsolete comments.

gisle’s picture

Issue summary: View changes

typo

gisle’s picture

Issue summary: View changes

update

Gastonia’s picture

Gisle, thanks for reviving this project, and thanks for your feedback on the topics of anon publishing on drupal.se (here are the links for anyone wanting to join the threads there: 1) http://drupal.stackexchange.com/questions/53470/how-can-anonymous-users-... 2) http://drupal.stackexchange.com/questions/25194/use-email-to-validate-po...)

I had a couple questions about your direction of the future of the module, and also if you would like help to develop.

First, I use Domain Access extensively, and many of my DA projects are what I am trying to have this functionality for. A_P may not be the solution if it has to be a node access module as well.

I looked through the code and saw the reference to the node access functions at the end of the .module file. When you ressurected the module, was node access already a part of it? I could not see why or how the architecture of the module necessitated it being a NA module. Do you think that could be factored out?

I don't want to reinvent the wheel. I would like to discuss more your thoughts on the future of the module. If our goals and needs are similar, then I would much rather contribute to this product than start my own. Skype, email, and even getting an active thread with the community going here would be great.

Thanks!

gisle’s picture

Yes, the node access integration is part of the original design. Unfortunately, it must be in there to grant the anonymous user the right to preview/manage his yet unpublished node (it will not become published until he authenticates). You can't just let Anonymous view unpublished content, as this setting would apply to all anonymous users whether they created the content or not.

I agree that making Anonymous Publishing incompatible with other node access modules is probably a too severe restriction. Drupal's node access system is designed to allow more than one node access module be installed (each node access module is assigned its own realm and should in principle work without interfering with others). However, in reality, things does not work out exactly like that. I've spent countless hours with DNA trying to figure out what is really goes on when two node access modules clash.

I put the caveat about it not being compatible with other node access modules to make testers aware of this potential problem. I'll relax the language a bit.

gisle’s picture

Version: 5.x-1.x-dev » 7.x-1.x-dev
Status: Active » Needs review

Stable release 7.x-1.0-alpha2 is now available. Please review.

gisle’s picture

Version: 7.x-1.x-dev » 7.x-1.0-alpha3
Assigned: gisle » Unassigned

Stable release 7.x-1.0-alpha4 is now available. Please review.

IMPORTANT:
If you have installed a previous version of this module disable and uninstall it (use the "Uninstall" tab on the Modules administration page) before installing this version. Just disabling it will not work.

gisle’s picture

Issue summary: View changes

shortened it

gisle’s picture

Version: 7.x-1.0-alpha3 » 7.x-1.0-alpha5
Issue summary: View changes

Stable release 7.x-1.0-alpha5 is now available. Please review.

gisle’s picture

Version: 7.x-1.0-alpha5 » 7.x-1.0-alpha7

Stable release 7.x-1.0-alpha7 is now available. Please review.

Release note for 7.x-1.0-alpha7.

gisle’s picture

Version: 7.x-1.0-alpha7 » 7.x-1.0-rc1
Issue summary: View changes

A release candidate of Anonymous publishing is now available for download on the project page.

Changes since tagged release 7.x-1.0-alpha7:

  • Moved admin GUI from 'content' to 'people' to be consistent with most other anti-spam modules.
  • Adding an 'unverified' tab to spot manual spammers.
  • Renamed 'blocked' tab to 'verified'.
  • Added autodeletion of personal information (by cron).
  • Deleted duplicate "claim" module left over from refactoring the project.

After upgrading, you must run the database upgrade script.

After running the database update script, please re-examine the configuration settings for this module to verify that they're still correct.

Notices about versions:

If you're upgrading from something older than the alpha7 release, please note that the project has now been been split into three different submodules. Each submodule provides one of the three major features of the project.

After downloading and installing the upgrade, you must visit the module administration page and enable the submodule (or submodules) you want. You need to have the parent module and at least one submodule activated for it to have any effect on your site.

If you're upgrading from the alpha2 release you need to disable and uninstall it (use the "Uninstall" tab on the Modules administration page) before installing a new development snapshot. Just disabling it will result in database (PDO) exceptions. This step is not necessary if you use the alpha3 release (or later).

Link to: Release note.

thorandre’s picture

Status: Needs review » Reviewed & tested by the community

Tested both with a clean D7 installation and with a more complex D7 distribution. Works fine, neat work!
Well documented and nice interface options that fulfill needs for many different use cases.

gisle’s picture

Version: 7.x-1.0-rc1 » 7.x-1.0-rc2
Status: Reviewed & tested by the community » Needs review

I've just released RC2 of Anonymous Publishing.

It fixes a number of bug that where found during code review. There are no new features in this release.

There is also a schema change since RC1, so please make sure you run the database update script after upgrading.

Please review.

gisle’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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