[capecodlife]

I went through all the plugins one by one – ending up with 2 plugins active – and once I disabled the Community Events – I can log in and the screen appears. Even with the events calendar running. This is where I believe the problem lies…

[capecodlife]

This was just confirmed by our hosting company as well – The problem is with the Community Events – We all need a fix for this “paid” add-on – can someone post an update on this please ???

[capecodlife]

I am experiencing the same problem – I have pinpointed the problem to be with the Community Events plugin. I can still access the wp-login.php page – but cannot access the /wp-admin page – it redirects to the root URL – Do we have a fix ?? I have tested this in development and production…

[capecodlife]

Howdy,

Thanks again for all the time you guys have spent on this project. In lieu of Community Events, I’ve been working on the Gravity Forms & Event Calendar Pro front-end submission form.

Updates:
– Created boilerplate GF form XML file with all necessary ECP fields
– Added recurrence (both On and After)
– Added all day event
– Added country/state/province (dropdowns for US and Canada)
– Fixed Venue/Organizer duplication on GF submission

See it in action (this is a live form): http://capecodlife.com/events/submit/
I’ve documented my work here: http://anthonydispezio.com/blog/gf-ecp-frontend-submission/

Keep up the great work!

[capecodlife]

Hello all,

Thanks to everyone for sharing their ideas thus far!

I’ve got a workaround going for the venue name. While workarounds are terrible for productions environments, perhaps we can get closer to a proper manipulation.

Tested on:
Gravity Forms 1.6.2
Gravity Forms & Custom Post Types 3
The Events Calendar 2.0.3
Events Calendar Pro 2.0.3

Short answer:

add the following line to the Venue Field declarations in the new format_event_date function

$_POST[‘post_title’] = $_POST[‘input_’. $venueName];

Long answer:

I poked around in the events classes and located a couple methods designed for updating venues and organizations separately from the event (starts at line 1500 in the-events-calendar.class.php).

After following the data down the rabbit hole for a while, it appears as though the new function (for the theme) and the save_venue_data method (the-events-calendar.class.php) cancel each other out as an attempt to sync the venue post_title with the venue[Venue] value.

Commenting out these methods allows for the Venue name to be saved when adding an new event, but breaks the “al-la-carte” saving of a venue or organization.

There is a particular conditional in the save_venue_data method that runs right before the custom field data is parsed (this conditional doesn’t exist for organizers). The conditional checks to see if the value of “post_title” exists (I assume within a Venue post object). To circumvent the conditional entering a new title of “Unnamed Venue,” I passed the post tile as the venue name (see Short answer above). The save_venue_data skips the value change and passes the correct value along to venue[Venue] accordingly.

It does the trick without editing any plugin files, but is in no way a “fix”.

The problem seems to stem from how the Venues and Organizers handle custom fields. The organizers use a custom field for the title, while the Venue interacts with the post title. That would explain the conditional check for a post title when parsing the data.

Is anyone else seeing the post title field for their venues? Or do I have an upgrade bug? Or are they actually stored both as post titles and custom fields?

[Author]

Posts