mophilly

Here is a new observation:
If I enable “compatibility mode” in IE 9, the audio plays. Once, and only once, I saw the video for “Company”.

Chrome on Windows does not play the videos either. FireFox on Windows does.

WP started to complain about IE being out of date. That lead to an update of OS and SilverLight. After that, WP was still complaining about IE. However, the IE installer from MS says the installed version of IE is newer than the installer’s version. Hm… Well, onward.

With all that done, the video on my test site began to play in IE9 and Chrome. FireFox continues to work as desired.

On your site, the audio plays but not the video.

I just visited the site.

On Windows 7 using IE9, I can play “Astonishing” but no video. Perhaps that is intentional. None of the other clips load.

Using FireFox 14 on OS X 10.7, all the videos play as well as the “Astonishing” audio.

I am having similar troubles today, so please update this thread if you have any news.

Ms. Quinn has a great voice by the way.

NOTE: I posted a replay to this thread by mistake. This is the “deleted” post.

Just for the record, I have a learned a couple of things that might help someone else. In essence, my original questions are misguided.

First, PEAR is completely separate from WordPress. It can be installed anywhere, such as in a web directory for a “local” install, or elsewhere on a system for use by several web site or applications built with PHP. You can use PEAR packages in WordPress if you are creating a plugin, for example, or possibly in page templates.

Second, HTML_QuickForm has been replaced by HTML_QuickForm2. Unfortunately, the differences are significant, so be aware of that the “upgrade path” requires a lot of changes to forms built on the first HTML_QuickForm. To the credit of the authors, the first version is maintained for bugs and security fixes.

Lastly, there are quite a few packages out there that are bound to out of date revisions of PEAR and its base of packages. If you find a need to update PEAR, do your homework and make certain other apps on the system will not be disturbed, and that subsequent updates of other apps don’t “downgrade” a package.

I hope this helps someone.

I just installed the plugin in WordPress 3.3.1, activated the plugin and visited a page to mark as private. I clicked on the checkbox in the sidebar and the same error was raised.

A dialog is presented saying an error occurred but no explanation text is presented.

Looks like a good plugin. I hope this fixed quickly.

Well, after a bit research, a refresher on mod_rewrite, and some thinking on the cool side of the pillow, I found the answer.

The unwanted 404 began when I enabled pretty URLs in WordPress. This added a block in the htaccess file in the document root of the web site. In the .htaccess document, within the wordpress block, and after the RewriteEngine and RewriteBase directives, I added one rewrite rule:

RewriteRule ^wsA(/|$) - [L,NC]

How the rewrite rule works is explained here: How do I ignore a directory in mod-rewrite

I hope this helps someone.

You need to learn how to use regular expressions, “regex”, or hire someone who knows how to use it.

Regex is a “math” for pattern matching and it works great in rewrite rules. There are lots of web pages that discuss it, show you how to use it, and so on. Nonetheless, the syntax is arcane and can intimidate even the most determined reader.

The work to learn it is time well spent. Once mastered you will be able to set up a few rules that handle many, many cases.

Good luck.

I am using WP 3.1 and version 2.2.3 successfully for simple 301 redirects.

Most are specific page redirects, but a few are out of date directories.

In the Target URL I use page ids.

/?page_id=1288

The HTTP code is 301.

Perhaps you need to restart the http daemon (web server) so the .htaccess file is loaded.