Messages posted by: Carbonize

Hmm the code should not change as the code is passed in the post using a hidden tag. Get the latest version of the script from www.carbonize.co.uk/verification.zip and make sure that every instruction was followed, particularly those to do with add.class.php.

The post tag is right as it points to your script. I think the fault lies in the location you have supplied for where the text file is stored. this is why I posted my variations. Try putting the links folder in the HTML folder.

or it could be /home/refresh2/domains/cafedesire.com/public_html/cgi-bin/links

I just submitted my site twice on cafedesire.com and it said successful but never appeared but no error messages. Then realised I was using your old links script

Anyway the problem is that you are trying to put the files in the cgi-bin and it's not letting you. Try changing

to

Ok after reading some old old threads ( from 2002 ) I decided to grab a copy of the 2.2 session.class.php file ( thanks JTD ). Anyway I think I have a quick fix for 2.2. users but need it to be tested.

THIS FIX HAS BEEN TESTED AND WORKS

Open your lib/session.class.php and locate

and replace it with

Cheers

UPDATE: You can now download a prepatched copy of the sessions.class.php file from www.carbonize.co.uk/AG

change the file that the script writes to. Chmod links_id.txt to 777 and try again.

I was just doing a search of the forums to see when the last time the script writer actually posted was and I discovered that the SQL injection exploit was actually discovered in 2002 and reported to him, It also affected 2.3 which I assume is why he released 2.3.1. I wonder if I can't just edit the session.class.php file to fix the exploit in 2.2 and save people having to upgrade.

Somebody send me the session.class.php file from 2.2 please. Email is at the bottom of this post or on my website.

You need to make the links directory writable from what I can see. Check your FTP program on how to change a files/folders permissions and change the folder to 766 or if that doesn't work 777.

In the verify.php are all of the 8 numbers set at the start?

The date is stored as a unix timestamp. I'll rewrite the script to allow the timestamp to be formatted when I get chance.

Also, having just browsed your site, I would say that you could easily integrate the guestbook into your current site design. As your site uses the same banner and menu on every page you could make them a single file and have every page call that file using the include function of PHP. Same for the copyright at the bottom. Only having a single file for the menu and banner means it is easier to update as and when necessary. I have given brief instructions elsewhere in this forum and I am in the process of writing a tutorial on it for my site.

Yes there was another site that only displayed 7 characters but if it still works then let it be, simply change the message about entering the 8 characters.

As to using an image for the background you will find the head section and I believe the <BODY> tag in the templates/header.php file. You can either use the background="image.gif" attibute in the body tag or add

in the style section.

Which image is supposed to be not appearing?

Oh and green text on a green background doesn't work

Anonymous wrote:I soo stupid. But I learn

No stupid is when you don't learn from your mistakes. It takes intelligence to admit you were wrong.

Trevor wrote:Talking about the Googlebot...

It's supposed to be denied from my guestbook by a robots.txt file and also noindex nofollow meta-tags but it's still indexing the pages. I thought Googlebot was supposed to be well behaved and follow orders. Any suggestions for blocking it and other bots.

Trevor

There is no guarantee it was really googlebot. I myself have spoofed the googlebot useragent when testing various sites and I know some people always spoof it. The real googlebot will honour any orders placed in a robots.txt file as will most bots. Email harvesters wont honour this though. The only 100% certain way to block bots is by writing a php script that gets the user agent string and recognises every known bot. Upon recognising a bot stop loading the page. Place this in every page and the bots will just leave your site.