Community Events – Publish Status Defaults to Draft

[brandonlemley]

I have read several of the posts in the forum regarding a known issue with Community Events which is causing new user-submitted posts to get saved as drafts instead of being immediately published. We’re running community events in a production environment and I wanted to check and see if you have any update on a fix? I’ve tried a couple of the temporary fixes and nothing has worked for me thus far.

[Brian]

Hello brandonlemley,

I can help you out with the Community Events and them not saving correctly when submitted.

We are working on a fix for the next release that should be out by the end of September, but I do not have anything to give you for a hotfix beyond the fixes already out there.

You mentioned that you did not get any of the temporary fixes to work. Were these the two you tried:

https://tri.be/support/forums/topic/new-registered-users-events-show-up-as-draft/

https://tri.be/support/forums/topic/submitted-events-ends-up-as-draft/ – Solution is in Casey D’s post.

Also can you let me know what the setting is for “Default status for submitted events” on:

Navigate to Events > Settings > Community Tab

Please let me know about those two questions and we can go from there.

Thanks

[brandonlemley]

Brian,

Thanks for the quick reply. I test both solutions you mentioned again. The code provided here (https://gist.github.com/caseypatrickdriscoll/7dcfe972e1b8870acef6) didn’t seem to work for me. My test post was recorded as a draft. The default status for submitted events is “Published”. We’re running community events in a production environment and my client is getting frustrated. Any more word on a specific timeline? I’ve seen enough posts on the forum that perhaps a blog post is warranted? Thanks for the help!

[Rob]

Hey Brandon! Thanks for the follow-up here; I head up Modern Tribe’s support team, and Brian brought your last reply to my attention. Wanted to jump in here to offer up our apologies for the inconvenience so far and to shed a bit of light on our release process.

This is indeed a bug introduced in the last release cycle. You are also absolutely correct that this issue has been reported a couple of times previously, and it’s definitely on our radar – as Brian mentioned we’ve actually got a fix in the Current Release (the build we’re working on now) that addresses this and has already passed QA, which suggests it’s pretty much ready to ship. But I do want to note that our release process is generally once every 4-8 weeks, and the bug in question here was reported during this release cycle – which means we haven’t actually shipped an updated codebase since the issue was reported. Our process is such that when a bug is reported after a certain version is released, we’ll log that and prioritize it for the subsequent build. Based on what I can tell that’s how this issue played out The fact that you were in the dark as to how often we release and what our release process entails was absolutely a communication failure on our end, and I apologize that we didn’t properly set expectations on that front. If you have any ideas on how we can do better I welcome them.

When it comes to finding a temporary solution: It’s odd to hear that the snippet there isn’t working for you – I just talked to Brian and he confirmed it gets the job done on his end. Mind elaborating a tad on the problem it yields so we can try to troubleshoot that?

Otherwise, as Brian mentioned, we are working towards a release later this month for the next round of plugins. We generally cannot get more specific than what Brian suggested above – largely because it just sets people up for disappointment. In the past we’ve promised “X build is going to ship by Y date!” and for whatever reason (bugs caught towards the end of QA, merge problems or any number of other reasons) have ended up that missing that deadline and disappointing the community. As such we’ve taken a position of not promising any specific release dates beyond our general goal of monthly/every two month maintenance releases. But you have our word that – barring any major hiccups between now and then – the next round of plugin updates will be out before September wraps. When we do such a release, part of our process involves going back to the forum threads and following up with users:

* If the bug they reported WAS fixed in that build, we confirm as much (as will be the case here)
* If the bug they reported WASN’T fixed in that build, we’ll let them know that it’s still on the radar and that we hope to deploy a patch in a subsequent release (I don’t foresee that happening with this issue since as I noted above it is already fixed)

Anyway…all that to say, thanks for your patience and I’m sorry we let you down. I know what it feels like to have a client who is expressing concern about these things and if there’s anything else I can do (shy of releasing the plugin early) to help set their minds and prove that this is a priority for us, please let me know. You can reply here or feel free to reach out directly to rob (@) tri.be. Thanks a ton for your support and patience so far.

[brandonlemley]

Rob,
Thanks for the quick reply. I absolutely understand that as hard as we all try, bugs happen. I really appreciate the reply and detailed information on the situation that both you and Brian provided. As a developer, I can also appreciate your process and attention to detail during the testing phase. I’m not sure why the interim fixes didn’t work for me, but it sounds like you guys have the situation under control and that a fix is in the works. Until then, I created some code that checks the database for draft events and publishes them out. That seems to be working for us in the interim.

[Brian]

brandonlemley, thank you for the reply and your understanding.

Glad you have a fix in the meantime for the bug.

I am going to close this ticket as there is a fix coming in 3.8 to help solve this. If you have troubles with this issue after 3.8 is released or with anything else please create a new ticket.

Thanks

[Leah]

Hi there,

I just wanted to let you know that we were able to work on this issue for our upcoming 3.8 release. Keep an eye out on your site for an update announcement! If you update and are still seeing this problem, please post a new thread so we can check it out. Thank you for your patience while we got this fix in place.

Best,
Leah
and the team at Modern Tribe

[Author]

Posts