Quantum

After some helpful advice from the people on irc I have resolved my problem. The mod_security module on my hosting server was the problem. The module acts as a script firewall and blocks certain word strings. Its aim is to stop comment spam by blocking URLs that people put into the posts. It does this by processing the entered text before the main wordpress scripts store it on the site. If an blocked URL is detected the script returns a 412 Precondition fail.

This was the error I recieved when I was trying to update my black list. It was detecting the blocked URLs and stopping the list being updated. Removing the blocked URLs the list was able to process as normal and blacklist sites not covered by the mod_security module.

I hope thats somewhat clear.

I have to agree with kay9’s suggestion. After upgrading to 1.5.1 and then being told to upgrade to 1.5.1.1 there was a lack of detail about the upgrade. More detail should be given with regards to upgrading.

Change the height in #rap to be 598px, then it looks right in firefox.

I was using paBox for a while until I discovered the major security flaw.
https://www.securityfocus.com/bid/8067/exploit/
The only way to get round this is to remove the admin.php. Ideally the admin.php file needs a complete rewrite.
Does anybody know of an XHTML shoutbox that has a database backend?

A nice clear guide. Helped me to roll out a flawless installation. Thanks.

It’s miniBB, link at bottom of page.
It’s not my favorite either but it was chosen and we have to live with it.

I better get working on some better content then.

I haven’t noticed this but IE and Netscape/Mozilla do interpret the stylesheet in different ways. IE6 even interprets styles quite differently between HTML 4.01 and XHTML 1.0 doctypes as I found out recently.

Looking at the settings I thought that once you had specified Lat/Long defaults that they would be used for every post. Currently this seems not to be the case. Hopefully this can be changed as it saves time.
Blueblimp, i like your idea of the of the drop down in the sidebar. It will make the posts less cluttered.

I’m not having trouble with the posts going into the future. The Hello World example was generated with a future time stamp during the install.
If this is a feature it seems something is wrong to cause the future posts to suddenly appear during refreshes. I have not had the time to do futhur testing. I will attempt to do so though.

Right I think I have solved it. The time stamp on the Hello World post was set in the future. Changing this to the past seems to resolve the issue.
But if it appears with a future time on some occasions this still must be a bug somewhere. Will you be able to post with a future time and have it appear only after that time has elapsed?

I’m not sure quite what details your after but I have two sites hosted with 34sp.com. Each site is on a different server. I have b2 running without problems on one. WordPress on the other.
Both servers are running FreeBSD 4.4 i think.
PHP 4.2.2, MySQL 3.23.55 and Apache 1.3.27.
If you need something more specific you have only to ask.