[release] pun_antispam (Page 1 of 3)

I just installed fresh 1.3RC and this extension.
On registration page, there is a box for entering captcha but there is no picture
Same on post by Guest.
On change password page, there is no captcha at all
(of course I did set it in Administration, Settings, Festures...)

Did I missed something?
I unzipped file in Extensions directoru, and installed it from administration panel.

Thanks for this, a captcha extension is an unfortunately necessary extension straight off!

Quick request:
- Support ReCaptcha as captcha source option (http://www.recaptcha.net).

It is a smart captcha solution and in wide use, and all entered text goes to helping computers understand printed text better (for things like book scanning).

Ahh good to know and I will take a look. If I do manage it, where shall I post the changes?

Just installed 1.3 final (clear install).
Installed antispam (via PunBB Repository ext).

Same problem as before few weeks:
On registration page, there is a box for entering captcha but there is no picture
Same on post by Guest.
On change password page, there is no captcha at all
(of course I did set it in Administration, Settings, Festures...)

Verison of antispam system installed:1.2

This extension requires your PHP to have the GD image manipulation library installed. Maybe that's missing with your installation of PHP. What does your PHPinfo say on this matter? (Under Administration > Environment > Show Info, usually).

I just figured that if I manually download pun_antispam.zip form repository (or trunk doesn't matter), extract and install, it work fine.
If I install it via the pun_repository extension it doesn't work.

I compared all files in extensions\pun_antispam between manual and repository extension installation and all files are same.

Bingo !
If permissions for pun_antispam folder are set to 755 it work
If permissions are 777 it don't work

Repository extension set permissions to 777

Pun repository gives permissions 644 to image.php on my server (and all other files in entire forum folder tree, including all files in extensions folder, have 644 permissions).
All folders in extensions folder (entire tree) have 777 permissions if installed via repository. If installed manually folders have 755 permissions and files have 644.

I just did what you wrote in your previous post, but no luck.
I tried every possible combination of permissions on image.php. Nothing.

so there are combinations that work:
pun_antispam folder: 755
image.php: 655, 755, 644, 744, 455, 444

don't work
pun_antispam folder: 777
image.php: any

don't work
pun_antispam folder: 755
image.php: x6x, xx6, x7x, xx7

If you need any other info just ask. This is test instalation so we can play with it. I testing 1.3 becouse I considering to move one exixting 1.2.15 forum to 1.3 (and also change provider to new one, so I put test instalation on new server).

I did it exactly the same way before.
Any way just for check I did it again.
After step 3. there is error when i open image.php (and there is no picture in forum but without any error):

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@xxx.xxx and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

After I changed permissions on pun_antispam to 755 everything work fine.

Anyway, seems that it's pun_repository's problem.
Anatoly and I will continue to work with PunBB next week (because of circumstances). Then we'll fix it (if somebody doesn't fix it before ).

Do you have problems with these extensions? Or they are functioning fine?

pun_repository intentionally sets permissions to 777. This enables users to delete downloaded files manually (for example, via FTP).

BTW
I'm little confused here.
If I understand it well, 777 mean that everyone have full permissions on file.
On the other hand 755 mean that Group (what ever this is) and World (as I understand it was literally anyone), do not have write permissions on folder/file.
Why more permissions make the problem?

Giving 777 permissions so user can manually delete files look little bit strange to me.
I can't figure situation where I will give ftp (or any other kind of direct access) to any user (owner of site of course have access via cpanel, FTP or some other way depending on provider).