Forum Replies Created
-
Posts
-
Yeah, I (and with me many others I think) can’t wait for the official compatibility update to be released! ?
Oh man us too. We are currently playing the waiting game on WPML. Then once they’ve released everyone will be waiting on us again. But we’re working on it as fast as we can.
In theory I should be able to make it possible to embed tickets from one event into an another via a shortcode. So you could create a set of tickets in your primary language, which it sounds like is Dutch. Then grab the event ID for that post. In your translated post embed a shortcode like this: [event_tickets_area id=”123″] and that will show the exact same tickets for sale on the English page, including the same stock count. There are two caveats about this that may or may not be deal breakers:
- The ticket area will still not be translated. If your tickets have dutch titles, the dutch titles will persist on the English page. You might could workaround this by including a short tutorial just above the shortcode explaining what each ticket/title does in the English page. Another possibility, might be a bit crazy, would be to give your tickets numeric titles. Like ticket 1, 2, 3… Then it won’t matter that they are not translated. Again a brief tutorial above the tickets area might appropriate expanding on what each ticket # includes. Up to you how you would want to handle this, maybe you have an even better idea better suited for your site?
- The tickets area is not yet embeddable on other pages via a shortcode. I recently wrote this miniature addon that allows you to embed it elsewhere on the same page as a shortcode: tribe-snippet-tickets-shortcode-2016-08-11 When I built it I was thinking it would likely be possible to add the ability to embed the tickets on other pages using the same shortcode with some more time spent developing this.
If you think the above workaround would work for you (for now, while we wait) let me know. I can look into crafting a new version of that shortcode that you could install on your site.
I should note that we have drifted a bit from the original issue now. For the sake of not spamming Daniel’s inbox with a conversation he might not be interested in, would you mind opening a new topic to continue this discussion?
Cheers!
– Brook
Howdy caldia,
I would love to help you with this.
That is something WordPress does when you have set it to show the Excerpt/Summary rather than a posts full text. In this case WordPress can not show the formatting because it is showing the summary instead. You can alter this setting in WP-Admin > Settings > Reading . Or you can manually craft an excerpt for each post and insert it into the excerpt box, which is available on events as well. Since this excerpt is not auto generated WordPress does not need to strip HTML from it, so any HTML in there will show.
Does that all make sense? Did that work for you?
Cheers!
– Brook
Howdy Andres,
I would love to help you with this.
It looks like your theme is set to show excerpts rather than a post’s full text. When you have it set to show excerpts WordPress will strip formatting from the post.
If you go to WP-Admin > Settings > Reading you can alter the setting from “Summary” to “Full Text”. Does this do the trick?
If not, could you try changing templates in WP-Admin > Events > Settings > Display . You will notice a few templates available in the dropdown menu, try each one, hit save. Does one of these behave how you wanted?
If all else fails you might reach out to Divi. Ultimately the theme can override any setting if it wants to. So if your theme is setting things to be summary/excerpts even when you have set it not to, the fine folks behind Divi should be able to help undo this.
Did one of those work?
Cheers!
– Brook
Howdy James,
I would love to assist here. First I want to make sure I understand where you are seeing this. What page is it? Is it in the WP Admin area? Can you share a screenshot or describe a little more where the automcomplete box is not appearing?
Thank you!
-Brook
Howdy Jeremy,
I would love to help you with this.
When were those duplicated created? Were they from the bug in version 4.2.2 of Pro that existed briefly a few weeks back? Or from before that?
Depending on how they were created I might have a solid method for cleaning these up. Do you have access to your MySQL server where you could run a query, perhaps through WP Admin? If so could you run this query?
https://gist.github.com/elimn/a998d7b67f6166dab5e17ec071eb35ee
It will return a list of events IDs and how many recurrences each one has. Ideally we will see a small number of events, maybe even 1-2, that has an insane amount of recurrences. Can you share the output of that query with me so I can consider some possible options for you?
Cheers!
– Brook
Howdy WSi,
I would love to help you with this. You could certainly as much our API as is convenient. You could store everything as venues, then use the Google Maps scripts with our plugin to show them as maps. Or you just use our Google Maps scripts, if storing them as venues does not make sense for some reason.
Geolocation is so trivially simple with Google Maps. You provide an address or lat/lng and they will give you the map. Google will be the one doing most of the work for you here. You just need to store the address or coordinates somewhere. You could do it as a venue, or it might make more sense doing it a custom field on one of the other post types.
The main thing you would probably want to share would be the Google maps script, which you can configure an API key for and everything from our admin. Just enqueue it where you need and then craft your map query.
Does that all make sense? In brief, you can basically use as much of our API as you want if it will make your job easier. How much I’d recommend using will depend on the job.
Cheers!
– Brook
You are welcome! Good news, the new version is out!
As you might note we addded a fix for the iCal times being off. Does it work for you after updating?
Cheers!
– Brook
Alright Nigel thank you so much for your patience. I did determine the cause of this. Your site has a considerably number of post tags. Our plugin makes each of them a selectable option in WP Admin > Appearance > Widgets . But there are thousands of them, and so all of those options on one page can be a bit much, causing the server to give up and stop outputting the page.
To fix this try pasting the following snippet at the top of your theme’s functions.php file. Replace the opening “<?php” with this snippet, as this snippet includes that opening tag.
https://gist.github.com/elimn/d023f0678a5800af74452c98673091dc
I just wrote that snippet for this issue. I believe it will solve the problem. I am also logging a ticket for us to find a more elegant solution in the future.
Does that all make sense? Did that work?
Cheers!
– Brook
You are so very welcome! Just to error on the side of caution I’ll leave this thread open another couple weeks. If you notice more errors I’ll be here to review them.
Cheers!
– Brook
Excellent news!
That sounds like the result of a known bug with version 4.2.4 of the iCal importer. We are working on a fix, and it might very well be ready within 24 hours. Until then the only option is to downgrade to version 4.2.3. You can download the past version here: the-events-calendar-importer-ical.4.2.3
If you are not sure how to downgrade checkout this tutorial: Downgrading a plugin . Or if you prefer to wait for the update that might make sense. Assuming you have your license key input now, once the newer version is out with the fix all you should need to do is click Update in WP Admin, just like you would update any other plugin.
Will one of those options work?
Cheers!
– Brook
Oh no worries. You would do that by using code similar to what I shared. I gave you an exact example of the HTML you would need to use for the H1 (which I copied/pasted from your theme’s source code):
<div class="page-head"> <h1>Heavy Gig Guide</h1> <div class="stripe-line"></div> </div>And this is the exact CSS you will need to insert for the above H1 to look like it does on the other pages:
.tribe-events-before-html h1.page-title { font-size: 46px; margin: 0 10px 0 0; line-height: 1.2; }You will need to do something similar with your H2s. I did not see the H2 used when I thumbed through your site, could you point it out?
It’s worth noting that our support does not typically cover providing exact code like the above. On rare occasions I can sneak some past my manager like that. But as outlined in our Terms Of Service while we provide example code it will often be up to you or your website developer to adapt the code to your site. I just wanted to mention this in case you were not aware.
Cheers!
– Brook
Great questions Dennis. We definitely like to find temporary workarounds when we can, you got some interesting ideas here.
The workaround which Daniel indicated indeed does the trick for me as well. Do you have any experience with it since last week?
Nothing has changed in the last week, except that we’re on week closer to a still unknown release date.
Another suggestion could be to use eventbrite?
Our primary WPML gent said Eventbrite is not very well tested at this time. I doubt it will work better for you. If you want I could give you a zip copy of the latest version so you could test it out further.
The thing that is not clear to me is which issues are impacting you specifically? Obviously Daniel found a work around for the first problem, and you’ve confirmed that works. Is the ticket area just not showing up your secondary pages, or is it showing untranslated? Or is it something else? I can think of some workarounds to those problems, they are not ideal but could help temporarily until WPML and us have released some proper solutions. Just let me know what you are hitting.
- Brook
That makes sense. If you are willing to hire someone for this you might checkout our list of customizers:
https://theeventscalendar.com/knowledgebase/find-a-customizer/
The primary issue that I was seeing is that the field keys are stored as escaped values, but in the various views you have mentioned it searches for unescaped field keys. Since it finds none these are blank. This is of course not an issue for basic latin characters since they can be stored as database keys without needing to be escaped, hence why this issue is primarily only affecting non latin alphabets. If you tell this to the customizer it will help bring them up to speed on the technical specifics. They further might be interested in the fix I crafted earlier that applies to one of the views. That view was patchable via filters, and it shows how to fix things.
Please let me know if you have any more questions. Cheers!
– Brook
