[Rob]

Hi again Sandro. I spoke with Daniel about this one today, too, and the issue here is a bit more problematic than that of your other thread. This is a byproduct of our broader need to integrate the plugin with WPML…as it stands we are not 100% compatible. That would be required to make this work; its not a quick fix. Maybe there is a hack that can be done with filters…but it’s sadly outside the realm of what we can support. We are working towards such an integration and hope to have it in place in a release before the end of the year.

Apologies I couldn’t offer anything more specific than that. Let me know if you’ve got other questions and I’ll do what I can to assist. Thanks again for your support.

[Rob]

Hi again Sandro. Wanted to follow-up on this now that I’ve had a chance to talk with Daniel, our resident WPML expert. It sounds like what you’re requesting here is requested by a lot of folks, but WPML doesn’t currently support it in-full. The good news is it seems you resolved this for the most part; the remaining problem seems largely due to a wrong query somewhere. Daniel can take a look, but would you mind posting the complete code from your ecp-single-template file? It looks like what we see above is incomplete…I’d recommend dropping it into pastie.org and sharing the link here.

While the remaining issue doesn’t quite seem specific to our plugin, Daniel will be happy to review your code and see if he can point you in the right direction. Cheers!

[Rob]

Hey there PB. Thanks for the follow-up; glad to know the host has confirmed that they’re all set here. Did updating to the latest builds – 2.0.9 for The Events Calendar/PRO, and 1.0.2 for Facebook – rectify this at all? Is the behavior still the same even with the new code?

[Rob]

Hey guys. Thanks for the notes here, and apologies that I haven’t seen your responses until now…for some reason the email notifications did not deliver as I’d expected them to. Glad to hear that the majority of these fixes helped you out, Daniel, but the issue of the page IDs getting disappeared was definitely unintentional – and I haven’t seen other reports of that yet. Have you started a new thread for this? If you do, we can take a look and work to get any bug that may have been introduced squashed for the next release.

Thomas: that’s the first time I’ve heard of this issue, but it’s definitely possible…as we started with this release allowing for the import of photos from Facebook, which the plugin grabs automatically. Sounds like something is amiss with that functionality but if you post a new thread here we can take a look and try to troubleshoot this with you.

Thanks again for the heads up, guys. Let me know what else we can do on this end.

[Rob]

Glad to be of service, Kelly – and thanks for the follow-up to nudge me on this issue yesterday, too. If you need anything else down the road just holler.

[Rob]

Hi again all. To follow-up on these points:

*Toru:* Thanks for reporting this. Yes, the settings update and the additional fields issue are byproducts of some bad code we introduced during the 2.0.9 dev cycle. This is unfortunately and something we’ve stripped out for the next release, once users brought it to our attention, so it won’t be a problem going forward. While the arrival of bugs is an unfortunate but necessary byproduct of the development cycle, we realize this is an inconvenience and apologize on that end. You will definitely want to ALWAYS back up your site before updating any plugin, regardless of how minor, but know that with the next release you won’t have to worry about settings, etc getting lost.

*Andy:* I’m with you there, man. Past a certain point, folks, please open new threads if you think your issue will warrant any discussion beyond a single response.

*David:* Thanks for the clarification, that does make sense. Looking in our projects system I see we have this as a high priority issue for the next release (it was planned for 2.0.9 but we couldn’t track down the source of the issue by launch date); so know that relief is in store on that end. Thanks for your patience so far there.

Let me know if anyone has any other points, and I’ll follow-up to get you what you need. Thanks again for your support.

[Rob]

Hey Doug – glad to hear you’ve been making some progress on this, and apologies on my end for letting it slip through the cracks…we generally try to hit all threads within 24 hours of being posted and we obviously failed you here. As such I’ve asked a member of the team to take a look first thing tomorrow to see if they can point you in the right direction…if they can’t, we’ll keep escalating it up the dev ladder until we can.

Stay tuned and thanks again for your patience so far.

[Rob]

Hey guys. Thanks for the follow-ups here, and my apologies for letting this one slip through the cracks. Finding the solution here is a tad outside my area of expertise, but I’ve asked Jonah to take a look…and if he can’t figure it out we’ll run it up the flagpole until we can find someone who is able to. Thanks for your patience and understanding so far…we’ll do what we can to get you through this.

[Rob]

Hey guys. Thanks for the notes here, and my apologies for the fact that this thread slipped through the cracks…we’ve been going through some staff turnover on the support side that could account for this, but that’s no excuse and I apologize on behalf of the whole team for the delayed response. Happy to take ownership on this one for you now, though, to ensure we get it squared away in a timely fashion.

A couple things for you to check right off the bat:

* Did this get fixed with the update to 2.0.9, which has come out since you first posted?
* Does changing to a different template under Events -> Settings have any bearing on the problem?

Let me know about those points, and I can do what I can (or bring in a dev as needed) to get this squared away. Cheers.

[Rob]

Hi folks. Thanks for the note here; as you may have seen in the release notes for the core The Events Calendar/PRO, there is a problem with the update prompt in 2.0.9 – where if you update The Events Calendar before any of the add-ons, those update prompts will no longer work. There are a couple of easy workarounds for this: one, you could just delete The Events Calendar and re-download/re-install 2.0.9 from WordPress.org (we released a hotfix a few days after the initial build that actually resolved the issue for anyone who downloaded it going forward).

Alternatively, if you’ve already updated core, just re-download Eventbrite from the tri.be website. If you try to upload it and are facing an error saying that the directory already exists, it’s because the folder names are the same. The easiest workaround here would be to just rename the source folder before attempting to upload it. It’s also worth noting that this update error will be gone in the next build, so you won’t have to worry about manual updates.

Hope this helps. If it doesn’t, please let me know and I can continue to troubleshoot as needed.

[Rob]

Hi there Julie. Thanks for the follow-up on this, and my apologies on behalf of the whole team for our failure to get you a response since 9/12. Just as a heads up…Joyce is unfortunately no longer with us, but I’m happy to take point on this and get it resolved for you.

Can you confirm that you’ve updated to The Events Calendar 2.0.9 and Community Events 1.0.3, and find this issue persists from there? Want to make sure we’re on the same page here before I get a dev to take a look. Thanks in advance.

[Rob]

Hi Vincent. Thanks for the note here, and my apologies that this one slipped through the cracks…not sure how that happened but I apologize on behalf of the whole team.

As for your specific issue, it doesn’t appear we’ve had earlier reports of this…so you may have uncovered a bug. But, I’m unable to recreate it using the latest code. 2.0.9 has been released since you first published this…were you able to update? If so, can you confirm whether or not the issue persists when running the 2.0.9 code base?

Let me know and if it persists and I can get a dev to take a look. Thanks again for your support and patience so far.

[Rob]

Hi Ken. Thanks for the follow-up here, and I apologize for the delay in getting you a response on this one…Joyce is actually no longer with us, unfortunately, but I’ve passed this onto another member of the team who will take point and get you a response no later than tomorrow.

Thanks again for your patience and support so far.

[Rob]

Opening this momentarily to update with some context from Larry, who was participating earlier and emailed with some insights. Larry’s functions.php file was appearing like so: http://pastie.org/4800030. Hee pasted the suggested line — if ( !defined( ‘DOING_AJAX’ ) ) — ahead of the require_once statement, and it seemed to fix their issue.

Yes! Just wanted to get this logged, in case anyone else finds themselves in a similar predicament down the road. Closing the thread once again now 🙂

[Rob]

Hey guys. Thanks for the notes on this; the problem you’ve noted is unfortunately a known issue that was introduced in 2.0.9. We apologize for the inconvenience on that end. The good news is the ability to update still works; it just needs to be done manually. as such the fix is simply to re-download the PRO release from the tri.be website and manually install it.

Sorry if this has an impact on your confidence, Jim. As I noted above we have already identified the source of it so that no problems should persist when the next release is out. As with any plugin, bugs will unfortunately but inevitably arise from time-to-time…luckily thanks to reports from community members like yourself, we’re usually able to fix those so they’re never present more than 1 release cycle. No babysitting of the plugin should be required with this particular issue…just a simple 1-2 minute plugin upload.

Hope this helps. Let me know if you guys have any other questions, and thanks again for your patience so far.

[Author]

Posts