[Rob]

Thanks for the follow-up, Jason. Just a heads up that given our limited support bandwidth it can take us up to 48 hours to get a response here on the forum – so I’d say hold off on posting follow-ups until at least that long has passed 🙂

If you’re using the auto-import feature in Facebook Events, that will automatically pull in new events at the interval you select (hourly, daily, etc). This should eliminate the need to continually import individual events as they’re published.

Hope that helps. If you’ve got other questions, just let us know. Thanks again for your interest.

[Rob]

Hi there Paul. Thanks for reaching out, and for your interest in the PRO release. At this point the Events Calendar PRO plugin uses its own category taxonomy (rather than tapping into WordPress’ broader one) and doesn’t include tags. However, a user submitted and we published a tut on how to tap into WordPress’ own category/tag structure as you see fit (https://theeventscalendar.com/integrating-wordpress-categories-tags-with-your-events/).

In 2.1, which should be out at the end of the summer, we’ll also be integrating officially-supported tags into the codebase. So relief should be in sight on that end.

Hope this helps. If you’ve got other questions, just let me know. Thanks again for your interest.

[Rob]

Hey Nick. Thanks for reaching out and for your interest in the PRO release. Happy to answer any questions you may have best I can.

If the registration component in Eventbrite Tickets didn’t meet your needs (which allows for you to host “free” events and have people register for tickets to those, effectively adding a registration aspect) and you didn’t want to customize Community Events to make it work (which could be doable with the right finesse), it might be worth trying to hack something together with Gravity Forms.

While we don’t have any officially supported GF integration, I know a handful of users are hacking it to make it work along the lines of what you’ve requested here. Other solutions might be possible with third-party plugins as well.

We may have an official, simple RSVP component coming at some point down the road too…we’ve had a number of requests for that since launching 2.0 and I suspect it’d be worthwhile. However if we added that it’d still be a ways out and probably wouldn’t see the light of day until early 2013 at the soonest.

Additionally, other users here on the forum may have ideas. I’ll leave the thread open so folks can chime in as they see fit. Hope this helps and sorry I couldn’t offer up more. Let me know if you have any other questions.

[Rob]

Thanks for the follow-up, Julien, and for bringing this up again. We do still have this on the radar – as I noted in the other thread, this is slated for inclusion in 2.1. That build is still in the works so while this code has been added in our development environment, 2.1 is not yet ready for prime time so we haven’t released it to the public.

We’re focusing mostly on bug fixes and heavily-needed features for the dot releases (ie 2.0.8), and doing features on a more broad sense in 2.1. Don’t worry, though…this one hasn’t slipped through the cracks. 2.1 should be out sometime later in the summer and will have this fix you’ve requested in it. We appreciate your patience so far.

[Rob]

Hi there Lauren. Thanks for the note here and for explaining the issue; I am definitely seeing what’s going on there and it does look like a bug in the plugin. I’m re-testing on my local machine with another FB page today to be sure but since your site shows the evidence it has been logged for the devs. This as far as I’m concerned is the biggest bug in the plugin right now, and while the fix won’t make it into 1.0.1 (since that’s already completed and launching tomorrow) we’ll have it in the maintenance release coming the first week of August.

I’m also seeing another issue of past events remaining on the list of importable events, which was fixed before launch but must have gotten reverted somehow. I’ve logged that as well.

Thanks for the heads up and for your patience so far. In the interim, it might be good to make any events you don’t want “draft” or “pending review” instead of deleting them outright. I apologize for that inconvenience. Let me know if you need anything else here.

[Rob]

Hey Susan. Thanks for confirming here; that’s weird because I am in the Bay Area myself and have found that events entered in local (Pacific) time on FB enter the same on my WordPress site, assuming it’s configured the same.

Are you saying it was the same time zone but still got mangled? If so, do you have a link to the 7/22 event (or the username for the FB page) so I can give this a shot on my end? Let me know if I’ve misunderstood the issue here.

[Rob]

Thanks for the words, Lauren. I see – speaking of bugs – that you’ve posted another issue in a separate thread, which I’ll be hitting momentarily as well.

[Rob]

Angela: my apologies for taking until now to get you a response here. I assume you’re still having an issue (let me know if not). This does seem like something that Paul will need to chime in on and I’ve asked him to take another look accordingly.

David: I’m wondering if your issue may be related to something else…when I go to your Facebook page as a logged out user (https://www.facebook.com/RiversideCigars) it redirects me to the Facebook home page. But if I go to any other public Facebook page – take https://www.facebook.com/OffTheGridSF, for example – it brings me to a landing page. Are you sure that Facebook page is entirely public? Let me know and I’ll try to troubleshoot from there. Thanks!

[Rob]

Hey Bart. Just wanted to answer and close this out, as I see you got a response in the other thread. Thanks for your patience and apologies again for the inconvenience so far. Let us know if we can do anything else.

[Rob]

Hi Kyle. This is an interesting idea, and you’re not the first to propose it. The answer is: sort of. You can likely hack it together to work – we had a number of users, before Community launched, using Gravity Forms to accept frontend submissions. Tim Bowen at Creative Slice even wrote a tutorial on how to do it (http://creativeslice.com/tutorials/gravity-forms-events-calendar-submissions/), which we helped update once 2.0 launched (https://theeventscalendar.com/event-submissions-using-gravity-forms-in-2-0/) and which sparked a lengthy discussion here on the forums (https://theeventscalendar.com/support/forums/topic/integration-with-gravity-forms/).

While we stopped supporting that GF hack once the officially-supported Community Events add-on came about, I know there are still a few users working with it. My best bet would be to either review those links I provided above, or browse the forums here and on the GF site and see whether any users have posted their experiences. I see there have been a number of discussions here related to it, as per https://theeventscalendar.com/?s=gravity+forms.

Hope that helps and sorry I couldn’t offer up more. Let me know what else I can do or if you have other questions.

[Rob]

Hey folks. Just wanted to give everyone an update as to this (since we were operating at half-capacity last week due to the holiday and didn’t get an update posted here in the thread)…it’s looking like this problem is fixed for about 1/2 of the users we’ve heard from up until now, and our developers are still looking at what exactly the cause is. It is indeed a definite issue related to the 3.4 WordPress upgrade…so if you haven’t yet made the jump you may not want to until we can confirm this is fixed for everyone. We do have the entire dev team taking a look at what’s up here and are doing our best to fix it for 1.0.2 before that ships later this week. Thanks to everyone who is still having problems for their patience so far. If folks who stumble upon this thread can confirm whether it’s working for them or not (so we can keep a general count of how many 1.0.1.1 fixed for versus how many it did not), that’d be fantastic. Otherwise please know that this is still on our radar and, as far as Community Events is concerned, our top priority.

Kathleen, on your note: aside from the email I responded to back on 6/28, I haven’t seen anything come through our support box before or since our original exchange back in May. Let me know if you’re still awaiting a response on something as I don’t have any other unaddressed messages from you.

[Rob]

Dang, sorry to hear about that conflict Tony – glad you were able to identify it though. If you have been in touch with that plugin’s dev and they need anything from us to help make the plugins integrate smoother…just let me know. Happy to send them a copy of the plugin or have our devs answer any questions they might be faced with.

[Rob]

Thanks for the note here, Tom. Sorry to hear this is still an issue for you. While I’m thinking the 1.0.2 upgrade that’s coming tomorrow may fix this, in the interim would you be willing to share a link to the site so we can check this issue out directly?

[Rob]

Hey Tony: even if the plugin is deactivated, you should still be able to add this code (then have it take effect when you activate the plugin). Alternatively you could always do it on a testing / staging site so there was no chance of a negative impact in your live environment.

Have I misunderstood the question here? Let em know if so, and I’ll get you what you need to succeed.

[Rob]

Are you still stuck here, Craig? Let me know if we can do anything to help.

[Author]

Posts