Messages posted by: Carbonize

No but you can add the human verification mod to help prevent the spam.

Whats the address of your guestbook ?

You need to set base_url in config.inc.php to http://www.meinhpname.at/guestbook

All the images show fine here so hard for me to figure out the problem.

I only have the files for Lazarus and Advanced Guestbook 2.2 to hand but if you look in lib/comment.class.php it says

1 - Whats the link to your guestbook

2 - The base_url needs to be set to http://YOURDOMAIN.COM/guestbook
where guestbook is the folder the guestbook is in.

Try setting the base_url variable found in the config.inc.php file.

1 - The function used to encrypt the password was changed recently by the makers of MySQL and as such the old stored password suddenyl became incorrect after an upgrade.

2 - The password stored in the config file is the password to access your database and has nothing to do with the guestbooks password. I only request it in the reset script as a layer of security in case the script is left on the server.

3 - Sounds like somebody has edited your lang/english.php file.

You can easily upgrade. Just replace your existing guestbook files with the new ones EXCEPT the config.inc.php file found in the admin folder.

There is a limit of about 45 characters on the AIM input if I remember correctly.

Advanced Guestbook is FREE and you can do with it as you wish.

Well first I'd write a nasty letter to GoDaddy about installing old and exploitable scripts for their users. I guarantee they would blame you if anything happened. the current version is 2.3.4

Anyway this has been discussed before and your best bet is to lter one of the existing fields such as AIM.

It is just the standard MySQL encryption. You can do it using phpMyAdmin but remember ot select PASSWORD from the function list.

Ok just tested and yes the originating IP is your servers IP.

No it would just stop the server being able to post in your guestbook which wouldn't happen anyway. I may be wrong, as I said I have never really paid that much attention.

This is a known bug in PHP 4.4.1. I wrote a username/password reset script and it can by found at http://carbonize.co.uk/Lazarus/Smf/index.php?topic=8.0 and this will bypass that page. Just remember to delete it when done.

I am not aware if Chi Kien Uong is aware of this problem so feel free to email him about it.

Comments should be covered by the anti flood function already.