Closed (won't fix)
Project:
Forward
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Dec 2007 at 10:35 UTC
Updated:
8 Jun 2009 at 20:09 UTC
Jump to comment: Most recent file
Comments
Comment #1
promesI like to be able to set the permissions for e-postcard functionality like the forward itself. So default off.
Personaly I don't see the added plus for this option, because it will result in being used by spammers, without leaving a trace where it actually comes from. With the added problem my sites are being blocked by projects like project honeypot: www.projecthoneypot.org. See the httpbl module that helps fighting the spammers of our world.
To marafa and others who have problems with this function: go to administer - menus and disable the menu-item.
Comment #2
femrich commentedI second this. How can the e-postcard be disabled? If it takes disabling the entire Forward module, that's what I'll do. This should be a completely separate function.
Comment #3
promesSee the last sentence of my reaction #1 to know how to disable the e-postcard functionality.
Comment #4
femrich commented... except that only disables the menu link that forward currently automatically adds to the menu. It does nothing to disable the function, so far as I can tell. Doesn't take a genius to type in the URL the menu item would have pointed to. Even a newbie can figure out that workaround, eh?
Comment #5
promesI totally agree with you. But for the short time it is an option.
The real solution is to be able to disable the option by setting a permission to use it and what role can use it.
I actually used it to send a message to a spammer (with as sender e-mail addres noreply@xxxxx) so not giving my personal address nor additonal info about my provider and so on. But for me, this is the rare occasion I see to use it, unless someone doesn't have a private/business e-mail address.
Comment #6
mvcI also would like to give users access to just the 'email this page' link, and not the epostcard feature. I've created a very simple patch against version 5.x-1.12 which adds a new permission called 'access epostcard' which must be granted for users to be able to send epostcards. Apply this patch, then unless you grant that permission to a user, they will not be able to send epostcards. If you use this patch, please post a reply and change this issue's status to either 'code needs work' if you find a problem, or 'ready to be committed' if it does what you need.
Please note that user 1 will still be able to send epostcards and will still have the link present in the navigation menu.
Comment #7
fang2415 commentedWorked a treat for me, thanks mvc. Changed the status.
Comment #8
mr.j commentedYes I third or fourth this one. I upgraded a bunch of modules a few days ago and only just noticed the link now. I was thinking WTF did that come from? Definitely make it permission-based and off by default.
Comment #9
seanrFixed in CVS (DRUPAL-5) and will be in the next release. Thanks.
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #11
jenlamptonThanks for the great module, I put this on almost every one of my sites!!
I would find it beneficial if forward and epostcard were two separate modules. Has there been any thought to pulling the two apart?
Comment #12
seanrPostcard functionality can be disabled via the permissions. There are separate permissions for access forward and access epostcard. Since they can be controlled separately, I see no need to split the module in two (especially since both methods actually use the exact same code, relying only on a couple of different parameters).