Forum Replies Created
-
Posts
-
That’s an excellent bit of feedback, snorton. We’ve noticed a lot of what you’re mentioning here are indeed prepping some new docs/tutorials that should help people understand the breakdown & specificity of the stylesheets.
Hey littlerchicken. It looks like this one slipped through the cracks, for which I apologize. I’ve got another member of the crew on deck to take a look here and reply as soon as possible. We really appreciate your patience so far.
Hey Greg. Thanks for the post here, and my apologies that it took us some time to get you a reply on this.
What’s the name of the theme you’re using here? Are you running the latest version of it as well as the latest (at this point, 3.0.3 and 3.0.5) versions of our plugins as well? The newest release of the latter should have optimized a few issues that might have helped here.
Let me know and I’ll do my best to get you a reply in as timely a fashion as possible. Thanks for your patience so far.
Hey Gregg. Thanks for the note here, and I apologize that it took this long to get you a reply. You raise an interesting point: the first part of this behavior as you’ve described it is by design, but the second does sound like a bug. However I’m unable to recreate it on both my local or on the site you’ve linked to.
Was this fixed in the 3.0.3 / 3.0.5 upgrade, or did you resolve this yourself? Let me know if I”m misunderstood and I’ll do my best to get this sorted in as timely a fashion as possible.
Dorothy: we totally dropped the ball by letting this thread slip through the cracks. I apologize and want to get this addressed for you. While it’s a bit outside my area of expertise, I’m reviewing with the team and should be able to get you a follow-up in some capacity shortly. Thank you for your patience so far.
Hey granatdesign. I’m sorry that we failed you here, and let this slip through the cracks. It’s back on the radar now and I’m committed to helping you get it resolved. While this is a tad outside of my technical area of expertise, I’ve got a more dev-minded member of the team on deck to take a look here shortly. Thank you for your support and patience so far.
Hi Sam. It looks like this thread slipped through the cracks, for which I apologize. While this is a bit outside my technical area of expertise, know that it’s on the radar now and I’ve got someone on deck to take a look and reply shortly. I’m sorry for the inconvenience in the interim.
Hey, twentwatchers: I apologize that this one slipped through the cracks on our end. While it’s a bit outside my technical area of expertise, know that it’s on the radar now and I’ve got someone on deck to take a look and reply shortly. I’m sorry for the inconvenience in the interim.
Hey there cavesolvent. Thanks for the note here. I just checked out that snippet and it worked fine for me running the latest code (though it’s 3.0.3 and 3.0.5 by now, that shouldn’t make much difference). It’s worth nothing that this doesn’t impact the widget settings; you still will only see 1-10 as options in the dropdown. It will only show count as defined by that code on the frontend of the site.
Did you place it in your functions.php file? If so, can you confirm whether it works on Twenty Twelve as well? That’d allow us to see if this is a theme conflict and we can try to advise from there. Thanks!
Hi fldrs and the rest of the folks in this thread. Thanks for the follow-up – I can understand your frustration here. We are continually working to optimize the plugin to better integrate with a wider range of themes, and we realize Thesis is a widely used one. Know that the ball is rolling on that and I apologize we couldn’t offer you an immediate solution.
In terms of the license key linking, that’s luckily a relatively easy issue to address by following the steps here: https://theeventscalendar.com/finding-your-pro-license-key-re-downloading-the-plugin/#key_disconnect. If you’re still stuck from there feel free to email pro /a/ tri.be and I’ll get it sorted for you.
Hey jaxxnux. Thanks for this, and I’m sorry you’ve faced this problem. Was this only happening with a given recurrence pattern, or have you already sorted it? I just visited the site and checked out a few recurrences and they were looking good.
It sounds like you’ve isolated it to the theme and while we can’t guarantee integration with every theme out there, I want to see if there’s a way we could optimize our code – or just provide you a snippet – to better address this in your case. Have you raised it as an issue with the theme shop too? I’d definitely recommend as much in case they could do the same on their end.
If the issue is indeed persisting and you’d be down to provide steps to recreate with a copy of the theme for local testing purposes, I’d be able to give it a shot and rope in a dev as needed. Let me know and thanks for your patience so far.
Hi again, wwa! Thanks for the follow-up, and no apology needed….that’s my job 🙂 I appreciate the clarification too. Admittedly the note did come across to us as more a lack of trust issue, and it’s relieving to hear that’s not the case.
Regarding the issue here: I just checked our internal ticketing system, and I do see we have a ticket for our developer Jessica here to address this pending an answer to Barry’s questions from 7/31. Now that we’ve gotten those addressed and confirmation on the specifics of your setup, we’re happy to continue helping here as best we can.
I hope you’ll understand that while we’re committed to helping everyone as best we can, there are limitations to our response time. The most we can guarantee at this time is a response to a user’s reply within 24-48 hours during the business week, and by reviewing the thread here it appears as though we’ve met that commitment…but please let me know if I’m misunderstood there. We do want to get this addressed both for you and so other users who find themselves in a similar position down the road have an existing thread to review.
If you can confirm once again that you’ve deactivated all other plugins & reverted to the default Twenty Twelve theme (so you’re just running our plugin on a clean install), and that the issue persists there, it does sound like sending over credentials as Barry suggested is a logical next step for us to investigate. Please confirm in doing so that you’re aware of the risks as outlined in his August 1 note. In terms of creating/sending the account, we encourage users to send them via the private messaging function here on the site. If you’d prefer you can email them to pro /a/ tri.be with a link to this thread.
Hi there wwa. Thanks for the follow-up here. I wanted to jump in here to provide a bit of clarification on our support system. I can absolutely understand your apprehension towards giving a contractor access to your site, but I should specify – to be 100% transparent with you – that every single person on the team (support, QA, development, design) is a contractor. That’s how our entire company is structured and we don’t have any devs who are employees. So while we can rope in a developer to take a look here, I want to make sure you’re aware that – like Barry – they too will be a contractor.
That said, we only have people on this team who we trust, can vouch for and who we know are adequately representing us as the face of Modern Tribe. There has never been an issue where a member of our team violated that trust and if there were you should know that we’d take immediate action to rectify it. While I realize that assurance might not be enough to make you feel fully confident, I stake my name personally (as well as that of the company) on this claim.
That said, since this is generally our standard practice for providing support, there unfortunately isn’t much we can do if there’s a requirement that contractors not be allowed the access they’d need to fully test. I want to do what we can to get you sorted here, and we are committed to helping best we can. But if you think it’d make more sense and would feel more comfortable with a calendar solution backed by a support team of full-time employees, please let me know so I can get you a refund (thus allowing you to take your $ and put it towards something that better met your needs).
Thanks again for your feedback and patience. Don’t hesitate to reach out if I can clarify or elaborate on anything.
Hi, Brad – sorry to hear you found Leah’s response unprofessional. Know that this was certainly not our intent.
I replied to your review this morning and your email just a moment ago. The latter is a more appropriate venue for this conversation than the forums so I’m going to close the thread so we can keep discussion going in just one spot. Thanks!
