Name |
Comments |
|
 Sunday, 17. February 2008 13:45
Thanks for the nice guestbook.
Keep up the good work.
|
|
 Friday, 15. February 2008 21:15
just wanted to see if it works
|
|
 Friday, 15. February 2008 19:18
Well done
|
6744) |
|
Ilka  |
fewo(dot)warnemuende(at)googlemail(dot)com |
Location: Germany |
|
Very nice Guestbook. I used it on my site. Come and look.
|
6743) |
|
joy cook  |
avicennapharm(at)gmail(dot)com |
Location: RU |
|
Glad that visited your site. Found a lot of useful information. I really liked it. Thank you very much!
|
|
 Thursday, 14. February 2008 19:54

fasnacht glarus
www.fasnacht-glarus.ch
|
6741) |
|
abogadovalencia  |
abog(at)2bobo(dot)com |
Location: vlc |
|
nice guestbook!!!!
|
|
 Tuesday, 12. February 2008 18:00
Good Luck...................
,.......................
http://www.earth.lk/chat.html
|
6739) |
|
Tony Edge  |
tony(at)system-edge(dot)co(dot)uk |
Location: Macclesfield |
|
Hi I have just created the guestbook with cpanel.
The guestbook works fine until I try to include picture when previewed I get a message.
Warning: move_uploaded_file(/home/systeme/public_html/guestbook/tmp/img-1202683756.jpg) [function.move-uploaded-file]: failed to open stream: Permission denied in /home/systeme/public_html/guestbook/lib/add.class.php on line 160
Warning: move_uploaded_file() [function.move-uploaded-file]: Unable to move '/tmp/phpXelOOh' to '/home/systeme/public_html/guestbook/tmp/img-1202683756.jpg' in /home/systeme/public_html/guestbook/lib/add.class.php on line 160
Can anyone help me with this problem?
the same picture works ok in this Guestbook
|
6738) |
|
Nils  |
nils23(at)gmx(dot)de |
Location: Berlin |
|
proxy2.de rocks
|
|
 Friday, 8. February 2008 10:38
Welcome!
|
|
 Thursday, 7. February 2008 08:05

GD test
Previous version of GB created terrible thumbnails.
|
6735) |
|
Serf  |
serf(at)scratchaddict(dot)net |
Location: Balt/Wash |
|

Agreed! This is the coolest guestbook around.
The image feature is perfect!
A friend of ours has been in a coma for some time and this is a great resource to set up for friends and family to come by and post their comments.
Thanks a million!
|
|
 Tuesday, 5. February 2008 16:39

prova
|
6733) |
|
T3000  |
magkeinenspame(at)web(dot)de |
Location: Germany |
|

Danke für dieses tolle Gästebuch !!!
|
|
 Monday, 4. February 2008 19:35

denemelik bir yazı
|
|
 Monday, 4. February 2008 15:28
oieee
|
6730) |
|
Yevgeniy Andryushkin  |
abcsite(at)gmail(dot)com |
Location: New York |
|
Now I have same book, it is cool
|
6729) |
|
Jason Yerardi  |
|
Location: - |
|
 Saturday, 2. February 2008 20:36
I have been using your Guestbook for half a year now and really like it. However, I believe there a couple things you could do to improve security.
The following has happened to me several times, using version 2.4.3: Someone creates a post with a "r*fresh" or "s*ript" tag, which automatically redirects to a hacker's web site. This happens even if html and ag codes are turned off.
For some of these, I've been able to hit "Cancel" while loading the page (to keep it from reaching the suspect entry), go into EasyAdmin, and remove. However the latest one that hacked my Guestbook was more severe. I had to actually go into the database and remove the entry from the table. Good thing I know SQL!
Anyway, great product...would just be nice to see an update that prevents "r*fresh" and "s*ript" statements in the comment field.
|
6728) |
|
Jason Yerardi  |
|
Location: - |
|
 Saturday, 2. February 2008 20:29
I have been using your Guestbook for half a year now and really like it. However, I believe there a couple things you could do to improve security.
The following has happened to me several times, using version 2.4.3: Someone creates a post with a "refresh" or "script" html tag, which automatically redirects to a hacker's web site. This happens even if html and ag codes are turned off.
For some of these, I've been able to hit "Cancel" while loading the page (to keep it from reaching the suspect entry), go into EasyAdmin, and remove. However the latest script that hacked my Guestbook was more severe. I had to actually go into the database and remove the entry from the table. Good thing I know SQL!
Anyway, great product...would just be nice to see an update that prevents "refresh" and "script" statements in the comment field.
|