Forum Replies Created
-
Posts
-
Hey pandology! Thanks for confirming as much.
Changing the view names is always going to have to be done using the snippet; there won’t be (or at least aren’t currently plans for) any admin-side tool for relabeling these. But the issue with the day view/view all is fixed in our codebase and will be released in an impending maintenance build 🙂
Thanks for your patience on that end and please let me know if you have any other questions. If you find that the bug is for some reason NOT fixed upon updating, don’t hesitate to open a new thread and we’ll get you sorted in as timely a fashion as possible. Cheers!
Thanks Rick. Just wanted to confirm that we are definitely still looking into this and hope to have a patch deployed in as quick an impending dot release as possible.
Excellent to hear that got you sorted, Jonathan! Thanks for confirming as much.
Fenoco: we can totally help you out here. But would you mind creating a new thread, so Tim (or whichever dev hits it first) can get you a reply in as timely a fashion as possible? Thanks in advance!
Hey wiredimpact! Thanks for the follow-up; I’m not sure if Kyle saw your reply so I just made him aware of it. Expect a reply very shortly and thanks for your patience so far.
Hey agape/Stacy: just wanted to follow-up on this, both because I haven’t seen any action here in a few days and because Jonah is no longer on the team (his last day was Friday, so I’ll be taking over this thread).
Please let me know what else you need!
Hi there supernaut. Just wanted to follow-up on this now that I’ve had a chance for our lead developer, Jessica, to review it. She was able to confirm that this is indeed a bug in the code and we’re working to fix it now for an impending release.
In the interim, you should be able to add the code from this gist to your functions.php file as a workaround: https://gist.github.com/jazbek/6107914. Please let us know if that doesn’t provide a temporary resolution for you.
Otherwise, thanks for the heads up here and know we’re working on a patch now. It’ll be deployed ASAP. If we can do anything else you in the interim please don’t hesitate to let us know.
Hi there pandology. Friday was actually Jonah’s last day, but I’m happy to take this thread over for him. That code would be pasted into your functions.php file.
The day view issue is logged in our central system, and is being worked on for the next release. However until that deploys (probably in the next 2-3 weeks) the error will unfortunately persist. My apologies for the inconvenience in the interim on that end.
Hope that helps, and let me know if you’re still stuck using that gist. Cheers!
Awesome to hear that got you sorted, wiredimpact! I’m not sure Tim saw your follow-up question (we’ve been a bit shorthanded this week due to a bunch of the crew being at WCSF), but I’ve asked him to take another look just now. Expect a reply shortly and thanks for your patience so far.
Miguel, did Jonah’s follow-up point you in the right direction? Have you tried dropping this into functions.php ? Let us know and we’ll get you what you need if there are still unanswered questions. Cheers.
Folks: while I realize it’s going to make some people unhappy, for which I apologize in advance, I’ve deleted all the replies to this thread. It was indeed originally intended to be posted as CLOSED, so people could not reply and instead were required to create new threads for any issues they saw. Based on past experience, it just creates too much confusion to have multiple issues going in a thread this broad. As a matter of principle, please make sure to remember to log any issue as its own, distinct thread – so we can help get you a resolution in as timely a fashion as possible. Thanks for your understanding on this front.
That said, it does sound like a lot of the follow-ups reported here were related to the same issue. If you check this post (https://theeventscalendar.com/support/forums/topic/errors-on-all-event-pages/#post-56826) it should get you where you need to be as we patch this inconsistency.
If you’re still having problems after reviewing and taking the action noted in that thread, create a new ticket outlining your issue and what steps you’ve tried so far…and we’ll do what we can to help. Thanks to everyone for their patience and support!
Hi there ginamwgallery. Thanks for the note here; Barry pointed your thread my way, and naturally I wanted to follow-up with you directly to try and get this sorted. Let me first apologize for the poor experience you’ve faced so far. I know what it’s like to be struggling with a product and to feel you’re alone in doing so; and it’s even worse when you’ve got a deliverable for a client riding on that. I want to do what we can to get back in your good graces. To that end, as Barry suggested, if there are multiple issues at play, we can definitely get them addressed quicker if each is posted in its own support thread.
There are a lot of good points raised here. In terms of the actual problem in this specific thread: I am seeing the aesthetic issue on your calendar there, and it looks largely like a CSS issue that should be relatively easy to tweak. It does look like this is something specific to your installation, rather than a bug in the code, which is why providing you a solution here isn’t a simple “here’s the answer” type reply. It does require some digging and based on Barry’s replies here, it seems apparent to me that’s what he’s trying to do with his clarification questions and follow-ups. Please let me know if you disagree.
I would definitely be interested in hearing more of your feedback on the documentation. While we don’t expect everyone using the plugin to be a dev, we obviously do expect a basic familiarity with WordPress – and a slightly more advanced one if you’re going to be customizing/tweaking/integrating with custom themes. While it’s a bummer to see a comment like “your documentation sucks” without any real supporting claims as to why, I want to see what you think is missing so we can update it accordingly. We spent quite a few man hours on prepping the docs for release before launch and have indeed continued to modify them post-release as well. One section to the themer’s guide that was just added yesterday, in fact, should help you get that CSS issue sorted: https://theeventscalendar.com/support/documentation/events-calendar-themers-guide/#customizingstyles. If there’s anything else you think is missing please let me know so I can go about getting it added. Bad documentation is a bug in itself – and that’s one I can get patched based on your feedback.
As for the videos: aside from the appearance on the frontend (as we used the Twenty Twelve theme in our vids), everything else should be current – and the backend should more or less match what you’re seeing. Those tutorials were all recorded in the past month and WordPress hasn’t changed so dramatically in that time that it would look dramatically different. Are the issues you’re experiencing purely frontend, or are you seeing a different backend from what our vids cover as well?
I will say that I’m disappointed with your criticism on the timing and take specific issue with the line calling Barry’s support “a joke”. While we’ve been faced with an uptick of support issues since launching 3.0, we are still committed to getting every one of those issues addressed as quickly as possible – and the archive of threads from Barry and his colleagues here on the forum should be evidence of that. While I can absolutely understand your frustration about getting the plugin properly integrated on your site, please know that we are doing our best to get you sorted…and that while we are committed to helping everyone, we do ultimately need to prioritize legitimate bugs in the plugin with specific users’ integration issues. We will get you where you need to be here. But if at the end of the day you’re looking for a deeper level of support than what we can provide for a plugin in this price range, or want to work with a company that can provide more timely follow-ups, I’d be happy to refund you the funds you’ve put out in full so that you can find a competing calendar with a support system that better meets your needs.
All that said, I’m sorry if we let you down. Please let me know your thoughts on the point above…if we’re going to proceed with this relationship I want to get it started on the right path, so that everyone’s expectations are on the same page and that you’re stoked about using the product. Thanks!
Hey hc2ca. Thanks for the follow-up here. You make a great point; while we tried to stress in both those links that they were third-party integrations we wanted to offer up as a friendly resource to the community (not something we were actively supporting), it seems we failed in accurately conveying that. I also think there might be some confusion because those were also from the days before we had community events as an option – once there’s an officially supported tool in these situations we generally expect users wanting that functionality will make the jump, or find ways to make the workarounds/custom hacks integrate themselves.
All that said, yes – I don’t mean to argue semantics. We obviously failed you here and I appreciate your heads up pointing out the issue. We need to do a better job going forward of clearly defining what we’ll support and what we won’t, and your feedback here has helped get the ball rolling on such a discussion. If I could interest you in a complementary Community license for your troubles (since we unfortunately won’t be able to do much on the GF integration per my points above) please do let me know so I can get you sorted.
Hi there hca2ca. I saw your last comment here and I wanted to jump in to let you know that we appreciate the feedback. Let me first apologize on behalf of the whole team for your poor experience.
I’m admittedly a bit confused about your point on Gravity Forms, though, since we haven’t ever had an officially supported Gravity Forms integration before now. It’s certainly possible that a pre-3.0 release of TEC/PRO inadvertently worked with GF but that was unintentional and not something by design or that was officially supported.
Please know that by no means are we attempting to force the purchase of an upgrade just to get back that pre-existing functionality. Since we first launched this plugin, the only officially supported (and 100% functional) frontend submission piece was that Community Events add-on…and that remains true to this day. If we’re misunderstood as to your last comment or if we’ve done something to strip away features you had previously, please let me know…since I want to do right by you there.
Thanks for your support and patience so far.
Glad to hear this got you where you needed to be, Terri – thanks for your patience as we worked through it 🙂 I’m going to close out this thread since it looks like you’re set, but if we can do anything else in the future, please just open a new one and we’ll do what we can to get you sorted. Cheers!
