gpiper

Same behavior for me (i.e., the 1/2 screen of whitespace that comes & goes as “tied to” the left-hand dashboard/column), in FF (3.0.4 Win & Mac) and Safari (3.2.1 Mac).

I must admit that I didn’t see the expand/contract handle at first either. Now that I know about it, I can live with the odd whitespace behavior a little easier…

Try checking your default category. I had mine set to ‘asides’ which is what I was using in order to facilitate posting asides via a Netvibes module; however, it started causing problems with newly created pages because of how WP2.1 “brands” pages with the default category.

Once I changed the default category & then created new pages, Sideblog stopped causing the ‘404’ error/problem.

Kates will still need to fix the plugin somehow, but at least now there’s a somewhat reasonable workaround.

I’m having the same problem. Strangely enough, though, it didn’t start right away, but only after I’d successfully added a few widgets into the mix, and then deleting the most recently installed widgets didn’t fix the problem.

I’ve also tried adding the scriptaculous directory to the wp-includes/js directory, and that didn’t help. It should be noted that this was done after things had worked without it in that location.

Also of note is that this was/is on a fresh install of 2.0.3.

It’s very frustrating!

UPDATE:

It turns out that, unbeknownst to me, my admin-header.php file got zeroed out. So, all of the problems I was running into were due to the absence of any code in that file.

When I restored admin-header.php from a recent backup, things started working correctly again.

-ghp

Yes, indeed, I see that I do have some compliancy problems, per the output from https://validator.w3.org for my main page.
103 errors are listed, after fixing the encoding mismatch you mention. I’m now going to work on fixing the rest of them, although I must admit tthat I’m not exactly sure just why they’re problems. The HTML code itself looks fairly reasonable to me. But, then, I’m not the swiftest coder around… ;^)
-ghp

I went through a lot of back & forth about which software to use, before and after having narrowed it down to WP & b2evo. My saga is described here.
A very helpful source of info that I found for comparing the various CMSes was Owen Winkler’s Blogware Choice posting, along with his nifty comparison chart.
-ghp

Yup, I’ve tried two others, so far — the FCKEditor-based plugin from https://www.moiblog.com, and the HTMLArea-based hack from https://mudbomb.com/archives/2004/05/29/wysiwyg-hack-for-wordpress/
Unfortunately, neither has been completely satisfactory in terms of working 100% correctly and/or to my liking. TinyMCE was mentioned in this thread so I figured I’d give it a try. It was reasonably simple to get working, but unfortunately had the posting glitch I mentioned above.
-ghp

I, to, ran into the same error that Roy & Barry reported, and I was able to get around it via the mod that they listed.
However, I’ve run into an annoying side effect of turning the plugin on — the size of my writing box has shrunk down to 9/12 lines (depending on whether or not the toolbar is displaying), despite the setting that I made via the Options screen (30 lines, in my case). If I deactivate the plugin, then the “official” setting works properly.
Odd, no?
FWIW, I downloaded the plugin from the WP Wiki within the past hour, and I’m running WP 1.2.1
Btw, thanks for the work on this plugin, Moises — it’s the easiest solution I’ve seen to date for implementing a WYSIWYG editor into WP.
-ghp