Forum Replies Created
-
Posts
-
Hi Kevin,
After implementing the snippet, the original URL gets 301′d to the URL for the first event in the series, then it looks like it gets 301′d to that wrong URL a second time.
When you say it gets redirected to the wrong URL a second time, can you be more specific? Is it essentially redirecting to the same URL but with a trailing slash, for instance, something like:
* base-event
* base-event/2013-11-01
* base-event/2013-11-01/Or do you mean it is actually redirecting to a URL that returns a 404 or something of that order? It would be great to have a little more detail on this one.
I use Yoast SEO to output opengraph tags, but if you track how that plugin works, it is ultimately using the get_permalink function from WP.
The magic here is that all recurring events in a series share a post ID in common. Given a post ID, then, get_permalink() itself will not be able to distinguish between events in a series (and if get_post_permalink() is used – which would probably be preferable here – the event meta data will anyway not yet have been loaded and so no date is appended).
So this is something for us to look at, for sure, and I’ll make a note to do just that.
Thanks Mastafu: I can see what you mean now and yes, that is one of the issues we were aware of with map view/geo search. Happily it seems to be resolved in our development code (much of which will be available soon in the form of our upcoming maintenance release) and so this unusual behaviour where map limits aren’t respected should disappear at that point.
Great that you resolved it! Remember a great tip to avoid browser caching during testing can be to switch to an incognito or private tab in your browser – that should help you to determine if what you are seeing is what other visitors will see, too.
On a side note I’ve noticed that the calendar doesn’t quite fit on a iPhone screen due to the day labels. It stops at roughly Frid, so Saturday and Sunday are omitted. But this may have already been mentioned before.
I don’t know if there’s a general issue there – a lot depends on your theme – but if for instance it is unworkable when viewed with a default theme in an iPhone (to the best of my knowledge that is not the case) we’d definitely be interested in looking a little deeper.
Since the original issue seems to be resolved though I’ll go ahead and close this thread – thanks!
Hi Larissa,
Nothing jumps out as being incorrect (with where you added the code) so I am unsure why that isn’t taking effect, yet it sounds like you are facing the very same problem that snippet is intended to resolve. One possibility is that we are each using different versions of WooCommerce Subscriptions (1.4.3 in our case) and the script handle is different, or perhaps the situation is being compounded by another plugin/your theme. It’s difficult to say.
With all that said, since not only have you identified WooCommerce Subscriptions as the “culprit” but we are able to confirm this problem happens because they are setting up stylesheets on admin pages that they should not be interfering with, it may be best to go to the source and seek further support from WooThemes/the addon author in this case.
On our end we’ll definitely drop them a line to make them aware of this, too, but I’m afraid there isn’t too much more assistance we can offer at this point.
Hi Ryan,
I can understand your anxiety here: it’s certainly not a low priority, but we have finite resources and it can take time to develop a solution we feel will work well going forward, test and release it – bearing in mind we also have to fit in numerous other bug fixes and feature requests and develop and test those, too.
How much of an impact this might have isn’t something we can advise you on and it goes without saying we’d be disappointed if you chose an alternative calendar plugin. We are close to releasing the next maintenance release, though, so perhaps it would ultimately save you effort to wait for and assess that?
Hi larissa23,
We just obtained a fresh copy of WooCommerce Subscriptions and best I can tell the problem is as per the thread and solution John linked to (by one of our developers, Kyle), unless something else is at play in your installation.
Can you confirm exactly which file you added the snippet to and perhaps even share the complete functions.php file with the fix added (using a service like Pastebin or Gist) so we can check and see if it was added in the wrong place or anything of that order?
Thanks!
Kevin: this does seem to be an issue with object caching and here is a snippet you can try (you could add it to your theme’s functions.php file, for instance) – we’ll also be including a substantive solution in our upcoming maintenance release.
Thanks for your patience while we looked into this 🙂
Sorry for the confusion – my colleague Kelly just informed me you already re-posted and that thread was answered, so I shall go ahead and close this one.
Hi Chris: apologies for missing this however it may have been incorrectly picked out by our spam filter. It’s been a while now so can I just check and see if you still need help?
Great, glad you found a solution (and thanks for sharing 🙂 ) – I’ll go ahead and close this thread now.
Cheers!
Presentationally the same views are used as are for non-category requests. In terms of the logic used to build the query, much of this is handled by WordPress itself (as we are leveraging both custom post types and custom taxonomies) however you might be interested in the code in TribeEventsQuery here (which lives in the-events-calendar/lib/tribe-event-query.class.php).
Hope that helps!
I’m afraid it’s quite hard to help you out here as your site is inaccessible. I do note that when you opened this thread you stated you had tried deactivating all other plugins: can you confirm that at the same time you reverted to a default, unmodified theme and did that help at all?
It’s not uncommon for Javascript issues to be caused, particularly if a theme is bundled with a slider that requires an old copy of jQuery (just as an example, the actual cause could be quite different in your case).
OK, great.
There are some areas we’re aware of that could do with some more attention to improve performance (and work in that regard is underway), but even so there is naturally a limit to what can be done and a pinch point can occur if sufficient server resources are not available while dealing with a large amount of event data.
If we can help any further just let us know!
Hi Daniella: because this is a customization we’re going to have to let you figure it out. There are a lot of resources here on the Modern Tribe site you can learn from (check out the list of items in the Useful Resources widget over on the right) and I think in this case you might also make use of general WP and PHP development tips and tricks from the wider web.
Good luck!
