Hi,
Been using Zenphoto for a few years now on the same sites and have always kept up to date with the latest release, currently running 1.3.1.2 [5831]. Until this week I have never had a problem with spam in the comments. This week I am suddenly getting lots of spam even though I have the simple spam filter enabled with CAPTCHA as well as name & email enabled.
Any thoughts? For now I have disabled comments as the sites are currently quiet regarding real comments.
Thanks
Steve
Comments
OK thanks for that, I'll look in to Akisment and maybe give it a go, I guess I have just been lucky up till now!
Steve
I know this should be obvious to me, but I thought switching comments off on the admin/album page would disable comments for the individual images within that album as well as the album, but it dosen't. Is there another way to bulk disable comments for all the images within an album other than clicking the check box on each individual image?
Yes I woke up to more spam this morning!
Thanks
Steve
Steve
Regarding Akisment, I am actually at a bit of a loss how to implement it as there is no specific plugin for zenphoto. I am probably just missing the obvious.
Maybe I should just make all the users register?
Thanks
Steve
There is an Akisment plugin on the Zenphoto WEB plugin pages. But it is written by a user so unless he visits here you will be pretty much on your own using it. Also, unfortunately, I have no idea of how to locate it. (I have always had problems with the site serach!)
http://www.zenphoto.org/2009/11/spamfilter-akismet/
As well there's a few other spam filter plugins for zp here:
http://www.zenphoto.org/tag/spam/
I use akismet myself and it seemed to work fine while using the zen comments
I have started experimenting but have 3 problems with the registration plugin:
1) On the user registration that is created, I am getting HTML code visible around the text 'passwords must be at least 6 characters long and contain at least one character from each of the following groups:'
2) On the verification email that is sent only the domain is created as a link all the code after the link is just plain text, so to verify one needs to highlight the whole link and text and then cut/paste in to the browser.
3) When the verify is initiated in the browser it works but at the top of the page there are warnings (I have removed the actual server path:
Warning: pack() [function.pack]: Type H: illegal hex digit . in /path/zp-core/zp-extensions/register_user.php on line 150
Warning: Cannot modify header information - headers already sent by (output started at /path/register_user.php:150) in /path/index.php on line 120
Warning: Cannot modify header information - headers already sent by (output started at /path/zp-core/zp-extensions/register_user.php:150) in /path/index.php on line 121
Warning: Cannot modify header information - headers already sent by (output started at /path/zp-core/zp-extensions/register_user.php:150) in /path/index.php on line 122
Warning: Cannot modify header information - headers already sent by (output started at /path/zp-core/zp-extensions/register_user.php:150) in /path/themes/zenpage/register.php on line 3
I am using the zenpage theme
Thanks
Steve
2) I would guess your mail client is insterting line breaks on long lines. (A common problem.) Not much we can do about that on our end.
3) Probably related to #2? If the link is "damaged" it will not work. A line break in the link would constitute an invalid hex character.
1) On the user registration page that is created, I am getting HTML code visible around the text 'passwords must be at least 6 characters long and contain at least one character from each of the following groups:'
I'll look for that code you mention, I presume its in the zp extenstions folder somewhere? User registration I guess?
Steve
Regarding the the possible line breaks in the verification email link, I have taken the line into BBedit to look at it but cannot see any line breaks. It actually ceases to be a link right after the domain, so in the message you get `http://www.domain.net` as the link but /index.php? onwards is just text. Any you sure something isn't going wrong in the generation of the link?
Thanks
Steve
Steve