nodecam

It doesn’t come with a default blacklist, but if you look at the configuration page, it give you a URL where you can get an up to date blacklist.txt

If your server has debugging turned off, which some do, whenever your site encounters a php error you’ll get a blank white page.
I’d try putting the default index.php in place, and see if that works. If so, you’ve got some bad code in there somewhere.
Hopefully it’s as simple as that, though you might have to sort through any php files that you’ve changed.

The code for that function looks like it got messed up some – I got it from a comment posted by Justin Greer at: https://ca2.php.net/manual/en/function.imagecreatetruecolor.php

Sounds like your server doesn’t have the “gd” installed. Not much that can be done if your server doesn’t have the image manipulation libraries available to it. ??

I’ve had this problem when my “siteurl” wasn’t set in the options table.
It happened every time I upgraded from an older b2 blog to a shiny new wordpress blog. When the “siteurl” option is set to “https://” the login page doesn’t work properly. Setting it to the proper value cleared it all up.
Gotta say, it was a bit of a panic when it happened the first time.

The file “wp-blog-header.php” is usually in the same place as your index.php – it looks like you may have inadvertently put your index.php in the wp-admin directory.
Try moving your index.php file to /home/jinsan/public_html/word
You might want to replace the index.php in /home/jinsan/public_html/word/wp-admin with the one from the distribution as well.
Let me know if that fixes it.

What files need to be gotten from CVS to fix this? Is it relatively simple?

I’m afraid it’s not possible without some heavy modifications to the styleswitcher script, unless I’m missing something quite subtle in the code – I’ll admit that I’m not using it on my site (I’ve got my own custom switcher,) but having read through the code, I think I have a handle on how it’s working.
An option would be to remove the dynamic nature of the script, and hard-code your styles right into your template – probably easier than editing the script, but not nearly as easy to add new styles, or upgrade.
It all depends on how badly you really want it in multiple columns.

The output cache plugin sounds like exactly what I had planned to do – too bad that link doesn’t work, I’d like to see what is being done there.
Sounds promising anyway – I’ll send him an email to see if he’s taken it off the market, or if it’s just a bad url.

Don’t get me wrong – I think the dynamic nature of WP is great – and I will not trade it away for MT. My idea is to get the benefits of both. I’m not asking for it to become a delivered feature (which is why it’s in the “hacks” forum.) I’m planning on building it in myself.
I’m thinking that it shouldn’t be that hard to do a subset statically, and completely transparently to both the administrator/authors and the visitor.
The idea is to make WP do something that MT does well, but still retain all the flexibility of WP. Most stuff would still be 100% dynamic, but the pages that get hit the most would be pre-rendered every time a change required them to be.
The only time the entire “cache” would have to be rebuilt is if the template changed, and with the beauty of css, there’s no compelling reason to be constantly tweaking templates anymore (instead, constantly tweak the css ??
As I’ve said though – I’m not asking someone to build this for me. I’m going to build it myself – I suspect that some people would find it a valuable hack, and I was opening it up for suggestions.

I have a setup where I intentionally “mix” or cascade stylesheets – if you go to my site ( https://www.nodecam.com ) you’ll see two dropdowns in the menu – one for color, and one for layout. I actually have the code in there to customize the fonts as well, but I only have one font style at the moment.
I started out with a B2 blog, and had the same .js include there that I’m using now – haven’t changed it since Feb 2002. I had to update my styles (to use different entity ids etc) when I migrated to WordPress last week.
I thought it was a fun thing to do anyway – didn’t require a whole lot of changes to the default wordpress index.php either.