Fotis Kokkoras

I had the same problems and ended up rolling back to 3.2.1. It happened on a WP istallation running on Win2003 server (IIS with latest php) as well as on a dev installation running on Win7Pro (with the latest php, as well).

The win2003 server installation had also problems giving me a working upload button – I had to use the alternative provided although at the end it also failed to upload the file.

To make thinks worst, another WP installation running on win7/IIS/latest php works fine with 3.3.

All PCs have WP on IIS/php, all have the upload folder on the same settings, all worked fine with WP 3.2.1.

The only difference worth mentioned in these 3 WP installations is that for some uknown reason the working WP 3.3 is also capable on doing automatic updates. I am manually updating the other two.

I did my homeqork and here are the results:

When the “ALO EasyMail Newsletter” plug in is activated, CMS Tree Page View doesn’t work. Otherwise it works fine.

Any ideas on how to have both work? It looks like a javascript issue.

The warning disapears when I assign a theme location for my single custom menu.

Same problem here. It seems that the plugin assumes a different database schema than the one used in WP 2.9.1. The code tries to read post categories from the wp_categories table. There is so such table in my WP. Catergories are stored in wp_term_taxonomy table.

More details….

The plug in works ok with WP 2.9.1 There is only one issue:

Say that I am setting a post to expire at 17, using the Expirator panel in the Edit Post page. Then I go to the Posts page where it says that the post expires at 15. The same (15) is displayed in all over the WP. Only the Expirator Panel in the Edit Post page dispays the time set.

The good thing is that the plug-in do works. The post expires at 17, not 15.

It looks like WP do not dispay the expiration time properly but I am not sure if this is a WP issue. I still believe that it is related to the daylight saving time – that’s why the 2 hour difference.