ColdForged

Check the FAQ. Two possibilities are an aspell path issue or a failure to create/write to the personal dictionary due to a path or permissions problem. Hope this helps.

Define “stop working”. In the absence of any updates to your WordPress installation the only other thing that might chnage would be underlying PHP or MySQL versions.

Bear in mind, podz, that aspell is an actual executable on the server, not a PHP service of any kind. If you have shell access, just do an “aspell” and see what comes up :).

Awesome podz! You’re the first I’ve heard running it that way.

Note that the lastest version has been released. This version includes the ability to add words to the dictionary. Hope it helps someone!

Nice, man! Hell, I hope 1.3’s looks something like that.

Please note that I’ve released a new version that includes the ability to allow your readers to check their spelling before submitting comments. Hope it helps someone!

Thanks, glad you found it useful.

That’s great news, Greg! Glad I could help.

Also I just looked in my database and while there might not be an interface for adding custom fields to the static pages, they are still created if needed. For the aforementioned static pages that use RunPHP, I have the appropriate custom fields in the database.

I wonder was your static page created with an earlier version, or with 1.3a5?

True catch there, mine were created under 1.3a4.
wptexturize() may indeed be a culprit. I tend to have Textile 2 doing my post massaging, so that may be the difference. Please note that I am not doing the double-equals “turn off Textile processing” around my PHP invocations on those pages, though. It may be from the ordering of my add_filter() calls… Textile 2 is being added as a 6 on the_content whereas RunPHP adds itself as a 5.
Maybe this helps?

I don’t know about the custom fields, but my static pages use RunPHP jsut fine. I use it in my About page to get the post and comment numbers and in my Colophon to get the PHP version.

Hot. Perfect. Thanks!

Wouldn’t text-to-speech use the alt text? In which case, it would work jsut fine.

Here is an example.