Forum Replies Created
-
Posts
-
Making the list of states filterable is a good idea, however currently it is hardcoded to US states and in many places where it is used it cannot be filtered, unfortunately (you could certainly propose a change though).
Would an additional field, populated with UK regions, be of use instead?
Yeah it’s from the Previous Posts link right? I’m not sure without checking to see how the theme determines the need to display that link – which I’m afraid is outwith the support we can offer (since, as you say, it isn’t related to The Events Calendar).
Are the databases of your dev and production sites in synch – is it possible there is a difference in settings (or active plugins) that might explain why you see it on one and not the other?
Hi Alain,
get_posts() is a native WordPress function so parameters like start_date will not be supported – can you try using tribe_get_events() instead?
Hi Steve.
One approach could be to visit Events > Settings > Defaults and specify a custom list of countries. This might simply be the United Kingdom, or if you were feeling creative you could try making this a list of actual counties (rather than actual countries) then change the labeling of those fields where they are exposed to the public.
OK, thanks – I’m not quite clear about the actual problem, though. Can you describe what you want to happen and what actually is happening (if you could share an example from your own site that would be awesome 🙂 )?
Thanks, but the code in the snippet only checks for the existence of a previous event, so on the last event, it displays:
PREVIOUS |Right, it’s just a starting point 🙂
You could extend it and check if the next event is empty, too, then roll that into the logic for displaying or not displaying the pipe symbol or whatever separator you want to use.
On a related note, the prev/next navigation seems to choke on recurring events: if there’s another event between the first and second occurence of a recurring event, it jumps back to the first occurence, instead of the second. Is this a known issue?
It’s not an issue I know of but it’s quite possible – to avoid confusion can you create a new thread and provide instructions to help us see the problem on your site?
Thanks!
Yes that does look like it is coming from Yoast’s plugin:
<!-- This site is optimized with the Yoast WordPress SEO plugin v1.4.7 - http://yoast.com/wordpress/seo/ -->
<meta name="robots" content="noodp,noydir"/>
<link rel="canonical" href="http://www.margaretriverguide.com.au/event/category/live-events/page/8/" />
<!-- / Yoast WordPress SEO plugin. -->(And thanks for bearing with me while we zeroed in on that.)
If you want to target past events only you could possibly use something like:
if (tribe_is_past()) { /* ... your WPSEO tweak */ }You might also combine WordPress and The Events Calendar conditionals:
if (is_archive() and tribe_is_event()) { /* ... your WPSEO tweak */ }If that sort of approach doesn’t work you could try a ‘dirtier’ approach of inspecting the request string and checking for the presence of elements such as the /events/ segment in the URL.
So events are posts, they are just a custom type of post to which extra fields and capabilities – such as dates and the ability to associate venues – have been added.
The first result in the above search of the WordPress plugin directory, for example, looks like it works with custom post types as well as ordinary WordPress posts:
There are quite a few others you could also try if it does not. Does that clarify things?
The forum doesn’t deal with code too well so I think I’m missing some of what you posted (re the problem with the subtitle) … can you share your code via a service like Pastebin or Gist?
Thanks!
I would agree 🙂
Some members of the community have found that changing the product type (via the WooCommerce product editor) from shipped to virtual and downloadable mitigates this problem – though I believe it depends to some extent on the type of payment gateway in use – so that could be a possible workaround in the interim.
(Sidenote – in the next release of WooTickets all ticket products will be virtual by default.)
It’s probably possible to customize things so WooCommerce moves the order status directly to complete however – but it may be better to touch base with their support peeps for advice on how to do that.
Hi bbswebmaster,
Based on your description I think this is simply because the catalog visiblity of tickets is by default set to hidden. If you edit your tickets (in the WooCommerce product editor) you can change this so they are visible.
Does that help?
Hi Boyd!
I believe been a number of improvements relating to query performance – more so in 3.0 which will be released shortly.
That said, there are a large number of variables that have to be considered including the number and type of event posts, whether customizations are in place, the level of resources available to the web and database servers, the amount of visitor traffic, levels and types of caching in use and so on – so it’s not possible for me to say that 3.0 will be a silver bullet but it may at least mitigate some of the issues.
You could potentially measure the difference between your current version and 2.0.11 (and, shortly, you can do the same with 3.0) by installing them in a replica of your production site – that will give you some decent data to help shape your decisions going forward.
Yes, the position is represented by a number and a member of the dev team tells me in our case that is 6 … what’s probably happening here is that our plugin is registering the menu item first then the theme is overriding that.
Our position is defined in the-events-calendar/lib/the-events-calendar.class.php on line 50 (or thereabouts – look for the term menu_position to zero in on this).
We don’t really recommend editing core plugin code – any changes will be wiped when next you update – but so long as you are aware of that you should be good (or you could modify the theme code).
