[dlishdesign]

Hi Barry,

Thanks for the update. Closing off the original ticket makes it feel like you have no way to get an update on the status of the bug fix (especially when no time period is given), I really didn’t want to open a new thread but didn’t see another way. From a client perspective, this really makes it difficult to trust the process by which you are taking to address this issue and bug fix because I’m blind and kept out of the loop.

For a bug like this that breaks an essential part of WordPress core, I would imagine this is a high priority item. Futhermore, its difficult knowing that you’ve purchased a pro license for an awesome plugin that is breaking an essential part of WordPress core functionality that ultimately limits what you can do in publishing your site (unless you deactivate your plugin). I can understand and respect you have monthly (1-2 months) release cycle but what concerns me about what you said is that it “potentially may wait for more than one release cycle.” because it isn’t a high priority (which I beg to differ). So essentially I could be waiting 1-6 months for a bug fix that is effecting multiple of my WordPress sites. That seems pretty crazy and not very reasonable at all, especially for a paid subscription.

I’m a pretty patient and understanding guy, but I’m not too happy about how the process of reporting a bug has gone for me and the communication (and lack thereof) has gone so far.

[dlishdesign]

I’m currently using a custom Genesis Child Theme but this issue happens on any theme. I recreated this bug using a fresh install of WordPress 3.9.1, the packaged Twenty Fourteen Theme and Event Calendar v 3.6.1 and Event Calendar Pro v3.6.1. No other plugins are activated.

Here is a screenshot to help you visualize whats going on: https://www.evernote.com/shard/s54/sh/23d4646d-c1fb-4e79-85a4-d5228f40e0b9/f60e2023391f902ebc5fe28934a2c3e3

Let me know if you have any further questions.

[Author]

Posts