lexhair

gentle bump.

I’m sticking with 2.2.1.1. Admin delete from the post comment gave me a blank redirect with 2.2.2.4.

That’ll work! For some reason, event-calendar isn’t listed on the TRAC as a ‘component’ which is a field you need for ticket submission. I don’t know who manages the TRAC or if there’s a command line setting to add it as a component but that really should be done.

T,
Actually I couldn’t submit a ticket here at the wordpress svn. Your adaptation of the patch is fine but I’m not sure if it will work on a pre-WP 2.3 installation. I don’t have a 2.2 testing platform but I have a small concern the tag query might error out. I can commit a change to do a version check I had in the sourceforge patch, if you’d like.

Rick…for some reason I can’t submit a ticket with the patch. The Trac does not recognize EventCalendar as a ‘component.’ I’d rather not commit a change if the group doesn’t want this functionality.

Rick…it’s at the svn at sourceforge. I’ll go dig it out.

WordPress 2.6.x disables remote blogging by default. Go to options->writing and make sure XML-RPC blogging is checked.

eventcalendar3.php

I’m staying with 2.2.1.1. Icons appeared fine with 2.2.2.0 but when I clicked on the edit, the modal dialog box appeared but did not fill in the fields with the comment data.

Now that I think of it, the modification should still work.

EC3 doesn’t recognize tag pages out of the box. It’s a simple modification to make it tag aware if your theme has a template named tag.php.

AEC 2.2.1.1 solved my JS problems. Thanks!

AEC 2.2.1.1 seemed to fix my JS issues. Links/buttons on the comments section are now working properly with JS overriding default browser redirect behavior on AJAX calls. User editing works again and the timer is back!

Same issue for me when I delete a comment from the comments section (not admin page). Redirects to a blank page. AEC 2.2.1.0.

This solution only works when WordPress is in the root directory.