Forum Replies Created
-
Posts
-
Thanks Jessica!
Flavia: we do appreciate your patience so far. Any chance the solution provided here gets you where you need to be? Please let me know if not, or if you have any further questions.
Hey there Flavia! Barry is out today, but I wanted to follow-up here. We’ve spent a good chunk of time looking into this and are pretty stumped as to what could be the cause. Would you mind letting me know what you’re using to translate the frontend of the site there? Is it a distinct plugin, or something else? If you could let us know so we can keep checking this out it’d be greatly appreciated.
Hey folks. Neill is out for the earlier part of today and I wanted to jump in here to make sure I got everyone an adequate reply.
Terri: thanks for the follow-up. Reid pointed out the solution you should need here! Let us know if that doesn’t do the trick, though, and we’ll get you more help as we can.
Sunil: I’m sorry for the inconvenience you’ve faced thus far here. I’ll say right off the bat that if you want to downgrade temporarily until you’ve had a chance to figure out the integration quirks, you can email us (pro /a/ tri.be) referencing this thread and we’ll get you a downgrade script + the last round of code. That said, we are committed to helping folks get their issues sorted…so if you were willing to create a new thread (so as not to create confusion with Terri’s issue) and include a link to the site, we can definitely do our best to get you sorted. Thanks for your patience in the interim.
Hey Ben! Rob from Modern Tribe here. Know that we are committed to looking into this further and our developer has set aside some time for it tomorrow. I see that the login you’d privately sent us is since deactivated; would you mind emailing a fresh one to pro /a/ tri.be so we can test accordingly?
Thanks to everyone for their patience on this end so far.
Gavin, I just wanted to follow-up with you here to apologize for the delay in getting you a reply. We’ve been flooded with questions, requests, customizations, integration problems and the like since launching 3.0 and are having trouble keeping up with the demand.
By way of an update: I’ve prioritized this with our developer Jessica, who will be taking a look first thing tomorrow morning. We’ll be in touch to advise best we can from there. Thanks for your patience and support so far.
Hey Siamack. Thanks for the follow-up here, and for your confirmation of your location of that snippet. While that is pretty basic CSS that it looks like someone did intentionally drop into that file, I can understand – if you’re not familiar with it – that you’d not want to make the change yourself. Do you have either an in-house dev who can make the change with confidence, or – even better – a staging environment where you can make the change to test it before deploying to live.
That said: if this isn’t something you’re in a position to do or are up for, we can issue you a refund so you’re on way to finding something that better meets your needs. Please email pro /a/ tri.be with a copy of your receipt if that’s the case and we’ll get the ball rolling there. Though, honestly, from the looks of things it seems we’re quite close here…and I’m happy to continue advising you if that suggested change doesn’t fix the issues.
Thanks for your patience so far. Please let me know how you’d like to proceed.
Hi there siamack:
Thanks so much for your follow-up here. I am glad to hear the import side of things is already resolved. As for the broader issue: when a calendar that the public relies on is inaccessible and leads to extra work for you, that’s a bad situation and we apologize for the fact that’s where you found yourself with this update. I am 100% committed to getting your update smoothed out.
I talked this over with our dev team, and it looks like the solution here is actually pretty straightforward. It looks like there’s an issue with the site’s CSS that is keeping the calendar from displaying.
Specifically, in your style.css file:
h1, h2, h3, h4, h5, h6 { padding-bottom: 5px; color: #fff; line-height: 1em; font-weight: normal; letter-spacing: -1px; }
That looks to be the reason the calendar is not working in list and in grid view; if you remove or modify that, it should get you where you need to be…but please let me know if not.I hope this helps get the calendar back to where you want it to be, and where it’s usable for your end customers. If the problem persists I’m happy to keep troubleshooting; but if you were interested in another calendar solution, we know Pippin Williamson and his calendar (http://wordpress.org/plugins/sugar-calendar-lite/) is a solid product with dedicated support. If that didn’t meet your needs there are also the major players like Timely or Event Espresso.
Thanks again for your patience so far.
Hey folks. Thanks to mprattmd for getting a patch up here. Curious though: was it formatted the broken way for you when you updated, by default? I just did a fresh install of the tagged release and it showed the proper formatting, which makes me wonder if the error is only triggered on updating. Let me know whether this occurred after you re-added the widget or if you didn’t have to take that step.
cleanlakesalliance: assuming yours was the same problem as discussed above, does the solution presented there help? Let me know if not and I’ll see what we can do.
I just wanted to follow-up to confirm that we DO have a fix in the works for this, and it’s done/awaiting deployment in 3.0.2. Whether that’ll go out this afternoon or first thing Monday morning depends on how quickly we can get through the final QA/packaging, but know it’s coming. Thanks to everyone for their patience so far.
Hey again folks. To follow-up on Barry’s comment, does anyone have further issues we can help with here? If so – please don’t hesitate to let us know and we’ll get you a reply in as timely a fashion as possible.
Hi there Siamack. Thanks for the note here, and please know that we understand your frustration and apologize for the inconvenience here. I want to help make this right for you.
Right off the bat, for your specific problem here: by creating the new event, did it fix it? It’s worth noting that the event which already existed would need to be deleted entirely (and removed from the trash) before you attempted to re-import. Let me know if it is still an issue…I’ll dig deeper if so to see what could be impacting your install on this end and whether we can offer any solutions.
On the broader issue of the 3.0 upgrade: while we tried to stress heavily in all the pre-release updates and upgrade notices that this was a major upgrade (which would particularly cause problems on sites that had customizations), it seems we failed to do so adequately in your case and I apologize there. I know what its like to be in your position and if you’d like a refund and a referral to a competitor whose calendar might work out better, please know the offer is there. I am also able to give you the 2.0.11 code and a downgrade script to help you return to the old calendar until a better implementation of the 3.0 can be scheduled. Email me (rob /a/ tri.be) if you wish to pursue either route.
If you open new threads for the separate issues you alluded to in the 3.0 codebase we are most definitely committed to helping get those resolved. Since 3.0 is the start of a new lifecycle for the plugin, one where we pretty much rebuilt it from scratch, the product was not going to be 100% bug-free. (I’ve never seen a product launch in such a state). I can assure you that literally hundreds of QA hours were spent on this product and that we were confident at the time of launch – and remain now – that the codebase was stable enough for release. We’ve already released one maintenance build and have another coming shortly to increase integration with the themes/customizations we’re seeing reported as conflicts.
I hope this helps. I’m admittedly a bit disappointed to see terms like “support is weak,” when – if you look through the forum archives here and see all the threads our small team has handled – it’s apparent they’re doing their best to assist everyone evenly and fairly. I want to do what I can to turn your experience around here so please let us know what that’ll take. Thanks again for your patience and support.
Hey folks. I see Jonah hasn’t had a chance to reply here yet, and I wanted to jump to do what I can to help / confirm a few points. Big thanks to Andy for his assistance earlier on in the discussion.
*Bryan:* Are you sorted here? I haven’t seen a follow-up from you but wanted to check if you need anything else or have other questions.
*Cynthia:* First off, you make a great point about the code Jonah suggested and its value in the themer’s guide. That is definitely intended to be a living document we modify as we go, and based on your feedback I’ve just gone ahead and added it in now. It sounds like your sidebar issue persists – which is odd, as we did the vast majority of our testing in Twenty Eleven and Twenty Twelve – but 3.0.2 has a specific bit of code that should fix this. It’s coming as soon as we can finish QA – hopefully today – and I’d be interested in hearing if the issue persists for you from there. If it does, I’m going to ask someone (either Barry or Jonah, depending on who is available sooner) to see if they can troubleshoot why.
*SparkUpdates:* Glad to hear you’ve got a workaround in place. Same goes for you: we’ve got a variation of that same bit of code in the impending release, so it should keep you from having to use your own patch. Let me know if not though.
*TabitaGreen:* It sounds like you’re all set. (Thanks, SparkUpdates). Let me know if I’m misreading that.
*BisDigital & Ellaearth:* Would definitely be interested in hearing what the other issues you’re seeing are, if you haven’t logged them yet. Particularly the validation errors but also whether the problems you’re facing are upgrade-related or based on a new install. If you’d like us to help with those just open them as fresh threads and we’ll get to them with haste.
Thanks for your patience, folks.
Hi folks! Thanks for the notes here. Indeed, we have a lot of users running on the Canvas theme and heard pretty much immediately upon releasing 3.0 that this issue existed. Good news though: the fix is something we can make totally on our end without having to involve Woo’s dev team, so we’ve got a patch coming in an impending dot-release (not 3.0.2, which ships over the next 24 hours, but it should be in 3.0.3 which we’ve got targeted for early next week).
In the interim, we’ve put together a gist for your functions.php file that should get things squared. It can be downloaded here: https://gist.github.com/jazbek/5959855.
If the issue persists from there, please let us know. But if you could do so in the existing thread for this issue (https://theeventscalendar.com/support/forums/topic/calendar-listing-all-my-posts-and-ignoring-my-events/) it’d be fantastic. I’m going to close this one for now to avoid having concurrent, isolated discussions. Thanks to you both for your patience and support so far.
Hey Terry. I really appreciate your follow-up here, and while I saw it when you first replied, I hadn’t had a chance to craft a response of my own until now. I can totally understand your experience and that it’d create some tension – no worries at all about the tone or the note itself. I’ve been in your position before and felt very much the same way 🙂 It sucks to be using a product you’ve come to rely on and find it rendered useless; even moreso when you’ve paid for that product.
You raise a good point on the “soft release” front. We haven’t heard this perspective yet but after hearing it, it’s obvious we definitely need to approach with more caution in the future. Let me apologize here for misleading you on that end…and for delivering what you saw as an unstable product. Though the initial release was going to be the same codebase (and same level of stability) for everyone regardless of whether it was a soft launch or a fanfare-driven one, the intention was definitely not to have people testing the plugin for us. It was and remains – in our eyes and many we’ve talked to – a stable release that was ready to hit the public. It certainly wasn’t 100% bug free, as no first release in a plugin’s fresh lifecycle ever is, but it was ready enough that we wanted to get it out there so we could start patching what bugs we’d missed. We’re hoping in the days and weeks ahead, as you update to the newer builds, the stability of the code will speak for itself on this end.
All that to say: I realize it’s been a few days here, and I want to check in as to how things are going. Can we do anything to help get your site squared away? In the early weeks of the 3.0 lifecycle, we do have a bit more support bandwidth to help resolve problems for customers such as yourself doing the 2.x ->3.0 jump. I want to make sure we get you sorted as best we can.
