Forum Replies Created
-
Posts
-
Guessing we’re all sorted here so I’ll close this thread. Of course go right ahead and create a new one if you need further help.
Cheers 🙂
Hi Nathan,
I suspect you are trying to obtain the post ID before the loop has run and so before the $post global has populated. You might need to do things in a different order/run the loop twice.
Hi chirocare – I’m afraid I’m not really clear as to the first problem you described.
Would you be able to break this down into a set of steps I can replicate and perhaps even provide screenshots to illustrate what you are saying?
RELATED: The venue address shows the city/state/zip twice.
Hmm, yeah I see that. Is it possible the city, state and zip have been entered twice in two different fields (can you attach a screenshot showing the Venue Information meta box for that venue)?
Thanks!
When you navigate to another month the calendar is reloaded by ajax. In other words, the entire page does not load a second time – only the calendar section is updated.
Whatever code is transforming the date dropdowns (it looks to me like Yii Framework code, but I could be mistaken) runs when the page first loads but I guess it doesn’t reattach when parts of the page are updated via ajax … or at least that would be my guess.
Beyond that I’m afraid I can’t really help much more with this – if you don’t like the selectors as they appear when you first visit the calendar you should probably touch base with the theme author about removing or modifying that code.
You noted that you tried deactivating other plugins and switching to a default theme … did that resolve the problem? I ask because I can see references to those selectors in your theme, for instance.
Just for clarity, our complete troubleshooting steps are:
- Please ensure that your Modern Tribe plugins are up-to-date and in-synch … for instance if you are using The Events Calendar 2.0.11 you must also use Events Calendar PRO 2.0.11
- Deactivate all other plugins and change your theme to a default, unmodified one such as Twenty Eleven or Twenty Twelve
- Now test to see if the problem still exists
- If the problem has been solved by these steps, start reactivating everything one-at-a-time, testing at each point to see if the issue has returned
- If the issue does return, take note of whichever plugin (or theme) you reactivated immediately before it started again – it’s likely there is a conflict with this item
Does that help you to isolate this at all?
Removing the sidebar by CSS probably isn’t the best route – because the sidebar is still being generated and sent to the browser (even though it appears not to be visible).
That said, something like this should do the trick:
.single-tribe_events aside.sidebar.right-sidebar { display: none; }Currently there is no built-in mechanism for this. I did write a “housekeeping” plugin you could try out – though it’s in need of a little TLC and (importantly) it’s not an official Modern Tribe plugin and it will not be supported on these forums.
It could however provide a starting point to develop your own solution.
I can’t really make any specific recommendations on that front; try searching for some WooCommerce developers or take a look at the profiles of some notable WooCommerce extension authors – they could be worth approaching here.
Hi Tony, sorry for the delay in getting back to you. You may already be familiar with this stuff but, just in case, please familiarize yourself with the themer’s guide and our template overrides tutorial first of all.
You would need to change two templates here. One would be tickets.php and the other would be single.php. Can you try using those alternative versions and see if that works for you?
Hi Matt. Can you take a look at this thread and see if the modified code in the second post works for you?
Hi John, great question 🙂
This is however in the realms of custom WooCommerce development. So, while I appreciate you are doing this in the context of selling tickets to events, it’s really something where you would need to dive into the WooCommerce API (and or work with the Woo team or someone who is suitably knowledgeable with regards to that product) to figure it out. A ticket is, ultimately, nothing more than a regular shipped WooCommerce product.
We can leave this open to see if other members of the community have a solution they can share – it isn’t something that we can really help you with though, I’m afraid.
