Forum Replies Created
-
Posts
-
Going to close this one since it’s been a while with no response from Splurgin. Let us know -in a new thread – if your issue persists!
Hey jadonulrich. I just tested this out on iCal with my Macbook, and I’m actually unable to recreate the problem you noted. When I import the calendar it looks like so: http://d.pr/i/MQ2X.
What steps are you taking to get there? I simply went:
1. File –> Import from within iCal.
2. Selected the iCal file, as downloaded from your site and currently located on my desktop.
3. Imported and reviewed the calendar to find what you see in that screenshot.Hope that helps and sorry I couldn’t offer more. Let me know if you’ve taken other steps than I have here, or if you have any other clues I could take to recreate. Have users of the site reported this as well? Do you find the same problem occurs when you use the ical feed from http://wpshindig.com/events/ical/ ?
Thanks for confirming you got this sorted yourself, gkv, and apologies on my end for the failure to get back to you in a timely fashion (leading you to go it alone). If you still have enough faith in us when it comes time for renewal, hit me up (pro /a/ tri.be) referencing this thread….since I want to give you a discount for your troubles.
Awesome to hear your solution worked, though. I’m marking it as the answer and closing the thread. Thanks again for your patience + support; please do let us know if we can do anything else in the future.
Thanks for the follow-up and for confirming as much, Steve. This is getting a bit outside my area of expertise (I’m not sure what could be causing the problem you’re noting barring something underlying in the theme) but I’ve asked another member of the team to take a look here tomorrow. We’re sorry for the inconvenience and appreciate your patience so far.
Hey there cavesolvent. Thanks for confirming as much; glad to hear that got you sorted. This is admittedly about as deep a solution as we can offer in terms of a workaround. But that said: I don’t think this is an unreasonable request at all, and I’ve logged a ticket for us to evaluate either bumping up the widget count or simply making it a text field where people can enter any number they desire (the latter seems most flexible).
While we’re focused on bugs exclusively for the August release we’re working on now, once we get that out we’ll shift back to feature-related requests. As I don’t see this being a hard one to implement I suspect we’ll see it sooner rather than later. Apologies that I couldn’t offer you anything more substantive in the interim, though.
Let me know if we can do anything else and thanks again for your support/patience.
Excellent to hear that got you sorted, carletto0282! Thanks for confirming. That gives me hope for Splurgin.
Splurgin, can you confirm as much?
Ah, that makes an excellent point. I’ll get a dev to confirm but we probably need to update the Tribe Bar to pull reflect that. I’ll also see if we can provide you a snippet-based solution in the interim. Stay tuned on both fronts.
Ah gotcha! Thanks for the follow-up. This one has stretched admittedly outside my area of expertise; but I’m going to see if Barry from the team can point you in the right direction here. We also realize our docs on tribe_get_events are sorely lacking and should be beefing up the docs.tri.be entry for it to reflect that as part of our current release. Thanks for your patience on both fronts.
Hey, JustJuicy. Thanks for the follow-up and for confirming as much. Jonah has unfortunately left the team, and so I can’t get him to take a look here – but I should be able to have Barry check it out and try to point you in the right direction. The 3.0 codebase has changed enough that it’d make sense to verify this before attempting anything. Stay tuned and I’ll get him to throw you a reply sometime tomorrow.
Gotcha! Thanks, WiredImpact. It’s looking like the first issue – when viewed in action on your site there – might be the same as the second: an AJAX issue in IE8. Since AJAX doesn’t actually run in IE8, users on that browser are going to find themselves sadly unable to access from the datepicker/event bar unless the live AJAX filtering is disabled for your site (which will bring back a “Submit” button they can hit and which will work).
Does that answer your question? Let me know if not.
Hey wmglennosborne + Steve! Thanks for the follow-ups. This is indeed not a setting, but rather something within the plugin files themselves. As this is getting a bit outside my area of expertise I’m going to ask our developer Kyle to follow-up to try and point you both in the right direction tomorrow.
Yo Simon! Basically the way I was thinking you’d do it would be to just change your menus under Appearance -> Menus to target /events/2013-10 instead of just /events. But that wouldn’t eliminate access to other months; it would just start users who clicked there on the month you specified (rather than starting them on the main calendar for the current month and allowing them to navigate around as they saw fit).
Removing access to the other months entirely is a substantially broader effort, unfortunately. It’d require some hacking at the code and customization that is admittedly outside the scope of what we can help on (and because it’d require modifying core plugin files, your changes would be lost whenever you update the plugin).
Knowing this: does the month targeting solution work as a stopgap?
Hey Daniella: thanks for confirming as much. And yes, I agree that the redirect problem is a pain. We’ll be addressing that when we upgrade the forums in a few weeks here 🙂 Appreciate your patience on it in the interim.
Milcms: have you confirmed that this is a theme-specific issue?
Hey Tara! Thanks for the follow-up here, and for uploading the files to Google Docs there. I just had Jessica from our development team take a look at those and create a DIFF file, so you can see the differences added to the plugin code.
It looks like those files are just for the PRO add-on, though, and as a result it doesn’t look like much has changed: seems like just events-calendar-pro/views/single-venue.php was modified.
Can you possibly upload the core The Events Calendar in the same fashion, so we can review that and check the bulk of the substantive tweaks for you?
Hey again smallmammothdesign. This is a solid point; we’re actually based on a couple of unrelated bug reports refactoring some of how the CSS files load (and as that’s partially being done with the feedback of our resident JS expert, I’m expecting it’ll be done with these situations in mind).
If you find this becomes an immediate issue for you again, please let us know and we’ll see what further help we can offer up. Likewise if we see additional reports of this and an increased demand for it in the community, we’ll prioritize accordingly to get users what they need.
Thanks for your patience and sorry I didn’t have anything to share in the short-term. If you need anything else in the future please don’t hesitate to let us know.
