Forum Replies Created
-
Posts
-
Hi Marlies – thanks for getting in touch.
Will this be a problem if I try transferring the website?
The same license cannot be used concurrently on multiple sites (if we are talking about a single, personal license) but you can definitely move it from one domain to another – we’ve got a page here on tri.be to let users manage keys and associated domains.
Is there a way to use some kind of shortcode to display it on other parts as well?
Well, no shortcode is built in but you could certainly display the ticket form in other locations. You would need to do some amount of template customization work to realize this though, so if you’re familiar with PHP, HTML etc (even if only to a limited extent) so much the better 🙂
That’s a good point and we’ll definitely consider that as we build and revise our support resources.
Thanks!
Hi Khaled,
I’m really sorry to hear that you’re in a difficult position here, realistically though we just can’t offer up spot fixes for every bug that is reported – though we do of course strive to do so if it’s possible and if it is a good use of resources.
I can’t actually bring to mind any other reports of this and so suspect for most of our users this either isn’t a problem that they notice or it just doesn’t affect them greatly. So, although we definitely appreciate that this issue might have more significant dimensions for you and your client, I’m sure you’ll appreciate that we have to allocate our development resources wisely in order to achieve the best results for all of our users. On this occasion we feel the cost of investigating and fixing the 2.0.11 code outweighs the benefits of keeping our team focused on 3.0 development – which will ultimately benefit all of our users.
Once again we do sympathize but we feel this is the best course of action here. Our offer of sending you the 3.0 beta code still stands – so if you have second thoughts and want to take a peek at that before the official release then please do feel free to let us know.
The post type is tribe_events and depending on when your code is running you can obtain that by using the following constant:
TribeEvents::POSTTYPEThe taxonomy is tribe_events_cat and again there is a class constant for that:
TribeEvents::TAXONOMYTerm relates to the actual category you want to pull in, it will probably be either an ID or a slug (or both may be acceptable) – but refer to the slidervilla.com documentation for that 🙂
Hi kaylesimon – thanks for updating us with the solution. Do you need any further support on this one or are you content with the theme vendor’s solution?
No not if it isn’t in use – it just crossed my mind that it could interfere with other event loops, depending on how it was written.
Do you have a staging/development site, or are you in a position to create a fresh installation of WordPress for testing purposes? If so (and only initially installing and activating The Events Calendar and Events Calendar PRO – stick to Twenty Twelve initially, too) can you set up a few recurring events and see if this occurs under those conditions?
Possibly, but only one way (importing recurring events) – unless of course there are other undocumented features like that.
The problem is, given they aren’t documented, I’m not sure we could rely on their continued presence or rely on them continuing to work in the same fashion.
Puzzling. Can you share your custom query code and also confirm that it wasn’t running/in-place when you ran through those troubleshooting steps?
Soon 🙂
We can’t provide a firm date because we want to give it a good beta run in order to iron out the last few wrinkles – but it should be worth the wait.
It certainly is. You can edit the products generated by WooTickets and change the catalog visibility setting appropriately if you wish them to be visible within your WooCommerce storefront.
Hi there: so it seems you are using a relatively old version of jQuery (1.6.2) whereas The Events Calendar expects at least the same version as ships with WordPress by default (1.8.3 at this time).
That can often cause problems like the one you’re describing so at least in the first instance it’s probably worth investigating which plugin/theme is causing the old version of jQuery to be used and then checking to see if it can safely be changed to the current version.
For a little more context on this, please see this thread:
Looks like you’re using Karma by TrueThemes.
One of its distinguishing features is that it filters all of the output in a page or post – in this context that includes the output of The Events Calendar – and applies various formatting effects, such as adding paragraph and break tags (using a filter function called my_formatter()).
This can sometimes be undesirable … to counteract it you would need to wrap any output from The Events Calendar (and actually any other plugins where this is a problem) in some special “shortcodes”:
[raw] ... output from The Events Calendar ... [/raw]The role of those [raw] [/raw] “shortcodes” within Karma is to mark areas where this extra formatting should not be applied (so for instance anything between [raw] and [/raw] should not result in the injection of <p> and <br> tags).
I hope that makes sense, but if you need any clarification on this it would probably be better to reach out to your theme vendor and seek their advice, since my_formatter() and the [raw] [/raw] shortcodes are unique to their themes (so far as I know).
Hi imaginaryjane,
Sorry to hear you are experiencing difficulties. I tried visiting the URL you provided but it would seem either to be a holding page or maintenance mode page … can you provide details so I can see the actual site in question?
(Feel free to check the Set as private reply box if you prefer.)
At the bottom of the details page, the formatting seems to be off with the previous/next links
So for this one you might need to customize one of your templates – single.php – a little, by making a template override just as you did with events.css (again, see our Themer’s Guide and Template Overrides Tutorial for the full lowdown on this).
Basically we’d be converting two divs into span elements in order to avoid a collision with your theme which has set up an !important CSS rule relating to the appearance of div elements within posts (which means it is important for the sake of the theme’s formatting that is is observed).
I’ve outlined the change you need to make here – just follow the direction in the comments.
