Forum Replies Created
-
AuthorPosts
-
September 10, 2014 at 7:04 pm in reply to: Serial events in events meta cannot be hidden – Bug? #736535
Brook
ParticipantI am sorry, I should have been more clear. Can you do them one at a time? IE check the second box, hit save, uncheck, save, then repeat on the first on.
Eitherway, I am not see that box on the frontend of your site. Even though the second check box was hidden, if you pressed save it might have fixed the problem. Are you still seeing it on your end? If so, would you mind taking a screenshot of it and linking to that screenshot here just so I can be 100% sure I understand what the problem is? Thanks!
Please let me know if that works for you, or if there is something else I can do.
– Brook
Brook
ParticipantHowdy juriklaric,
I am right here! And I bring good news. That should be very possible. If you were to do a theme-override on pro/modules/meta/additional-fields.php and run the $value through do_shortcode, it should then treat the values as possible shortcodes. It is worth a shot. There are some things that could get in the way, but odds are this will work great.
I am happy you were able to get those credits working. Thanks for letting us know! Good for future reference.
Did that work?
– Brook
Brook
ParticipantHowdy efromdc,
That is totally possible. We have a pretty good tutorial on working with that function: https://theeventscalendar.com/support/documentation/working-with-tribe_get_events/
You could just copy last example and remove the ‘tag’ line. Does that work?
For future reference, our forum software is a bit strange in that “bumping” topics can have the opposite effect. We basically have two different counters on the backend, one which shows the last time a topic received a respond, and another show when the last staff response was if there is one. By default they are sorted by the last comment, so we actually manually search for topics that have been bumped. It is a bit of a pain, and means that sometimes they get answered second purely by accident.
Hopefully this response was timely enough. We do strive for a 24hour response time, which means topics from Monday morning like yours might get answered Tue morning..
Let me know if that info helped you with tribe_get_events. Cheers!
– Brook
Brook
ParticipantHowdy corklikedotcom,
That seems quite possible. When I am trying to figure out something like that the first thing I would do is disable the plugin that I suspect might be conflicting. You can do this by going to WP Admin > Plugins > Installed Plugins, finding the plugin and clicking “deactivate”. Does that fix the problem? If so…
It might be possible to get the two working together. When you visit the events page and click Add Media, does an error show up in your browser console? If so, what is it? If it has anything to do with “Including the Google Maps API too many times”, or something like that, it is quite possible we can make the two plat nice together. Just let me know, if you do not mind.
Thanks! If you have any more questions or need some clarification I am happy to expound.
– Brook
September 9, 2014 at 8:16 am in reply to: Serial events in events meta cannot be hidden – Bug? #733291Brook
ParticipantHowdy Christian Kramer,
That was weird. I experienced a similar bug. I found that if I checked the following two boxes, hit save, then unchecked them, it started working properly. On the page Events > Settings > General..
- Recurring event instances
- Front-end recurring event instances toggle
Does that fix things? I am sorry for the inconvenience. It seems like something must have cleared this setting in a strange way, possible related to our past update.
– Brook
Brook
ParticipantAwesome! I really appreciate you’re contribution in pointing this out. It makes me ever more eager for our facelift. We’ll see you on the new site if not before. Cheers!
– Brook
Brook
ParticipantHowdy Andrej,
The problem is that venueCity is not defined. There is more info found in our code comments on month/single-event.php:
/**
* How to Use the Javascript Templating System in this View
* ========================================================
*
* Month view (and week in events pro) has implemented javascript templating to power its rich tooltips and mobile views
* as of Events Version 3.3. This is a guide on how to modify, extend and use this functionality.
*
* 1) Overview
*
* As of version 3.3 our tooltips and mobile views use a custom javascript templating solution.
*
* How it works: event data for each event – such as title, start and end time, excerpt etc – is stored on a data
* attribute tagged “data-tribejson” in the markup. This particular json works with simple single level key value pairs.
* The key is used in the javascript template to call our value output.
*
* The javascript templates are stored in two new files in the views folder, mobile.php and tooltip.php. You can modify
* these templates as you wish, and add new data to it for use either in these templates or anywhere on these views. The
* javascript templates themselves are explained further on.
*
* This “data-tribejson” attribute contains a string of valid json that must have its double quotes escaped correctly so
* it can be used both on a data att and for use in jquery’s json methods. Scary? Dont worry, we’ve taken care of this
* encoding for you, find out how in the next section.
*
* 2) The Template Tags
*
* Two new template tags have been introduced to power this system:
*
* tribe_events_template_data()
* tribe_prepare_for_json().
*
* tribe_events_template_data( $post_object, $additional_data )
* ============================================================
*
* This is the main template tag that will output the string of valid json in the template file. It takes the event post
* object and an optional php array with additional data for output in the json string. Right now we use this only in
* month view in events, and week view in events pro. You can add it to other view files if you want handy event data
* for use in your own javascript. The stock template tag supplies this json string (remember, the key on the left is
* what we use in the javascript template file to call the data on the right):
*
* {
* “eventId”: POST ID,
* “title”: “POST TITLE”,
* “permalink”: “POST PERMALINK”,
* “startTime”: “EVENT START TIME”,
* “endTime”: “EVENT END TIME (MAY NOT BE SET)”,
* “imageSrc”: “IMAGE THUMB FOR MOBILE(MAY NOT BE SET)”,
* “imageTooltipSrc”: “IMAGE THUMB FOR TOOLTIP(MAY NOT BE SET)”,
* “excerpt”: “POST EXCERPT”
* }
*
* tribe_prepare_for_json( $string )
* =================================
*
* This template tag is used internally by the previous tag, but has been made public for your use as well. Please do
* note that any additional params you pass into tribe_events_template_data() will automatically be passed through this
* function and so you need not do that step manually.
*
* Lets say we want to add our own dynamic data from custom post meta to the javascript template for mobile. For now
* lets say that the key name we want to use is “hello” in our js template. The following example shows how we would go
* about adding the custom post meta and appending it to our event json string that is output in the markup.
*
* $additional_data = array();
* $string = get_post_meta( get_the_ID(), ‘hello_meta’ ); // this string can be anything
* $additional_data[‘hello’] = $string;
* echo tribe_events_template_data( $post, $additional_data ); ?>
*
* Explanation: we create an empty array to cram our data into. We can add as much as we want, there are no limits on
* data attribute length in the html5 spec. We want to call this data with the word “hello” in the js template, so that
* is the key name we give it in the php array.
*
* After we have our data we supply it along with the post object. Now we’ll cover the javascript template.
*
* 3) The Javascript Templates
*
* As said earlier the templates are stored in tooltip.php and mobile.php in the month view folder. Javascript templates
* are simply standard html markup with keys wrapped in an expression that our parsing function uses to populate the
* values to. Our expression is a [[, THE KEY, followed by a ]]
*
* The template has 3 modes when parsing these.
*
* [[ ]] is for executing javascript you place between the expression. Note below how we test for the presence of an
* end time and image thumbnail using this.
*
* [[= ]] Is for a string with escaped html.
*
* [[=raw ]] Is for a string with html preserved. make sure to test for xss vulnerabilities using this method.
*
* Now lets look at the tooltip template. Compare the keys in it to the json string in section 2 above to map out whats
* going on.
*
*
*
* <script type=”text/html” id=”tribe_tmpl_tooltip”>
* <div id=”tribe-events-tooltip-[[=eventId]]” class=”tribe-events-tooltip”>
* <h4 class=”entry-title summary”>[[=title]]</h4>
* <div class=”tribe-events-event-body”>
* <div class=”duration”>
* <abbr class=”tribe-events-abbr updated published dtstart”>[[=startTime]] </abbr>
* [[ if(endTime.length) { ]]
* -<abbr class=”tribe-events-abbr dtend”> [[=endTime]]</abbr>
* [[ } ]]
* </div>
* [[ if(imageTooltipSrc.length) { ]]
* <div class=”tribe-events-event-thumb”>
*
* </div>
* [[ } ]]
* [[ if(excerpt.length) { ]]
* <p class=”entry-summary description”>[[=raw excerpt]]</p>
* [[ } ]]
* <span class=”tribe-events-arrow”></span>
* </div>
* </div>
* </script>
*
*
* Please note when creating your own data to feed to this that you must supply the key every time, even if the value is
* empty. The templating function will error if one of the keys in the template is missing from the json.Basically you are going to want to add a new bit of data to the JS template like the example “hello” above. Only instead of “hello” it will be “venueCity”, and instead of using the variable $string you want the data to be tribe_get_city().
Does that make sense? Does it answer your question? Thanks!
– Brook
Brook
ParticipantYou are very welcome!
– Brook
September 4, 2014 at 10:05 am in reply to: Event calendar page blank but individual event pages work #722192Brook
ParticipantThanks Julia for testing that out. It is interesting, when I was looking at your site before it was just returning a blank page. Not it is showing a 404 one. Which gives us a good starting point. This tutorial, while rather long winded, is filled with from great advice for just this scenario: https://theeventscalendar.com/support/documentation/troubleshooting-404-errors/
95% of people just need to flush (refresh) their permalinks as outlined in there under the “What if it is only event pages that 404?” heading. But, if that does not work, it is worth giving the next steps a go. Considering you have already tried switching themes and know that “solves” the problem, you can skip any steps that ask you to switch themes. It would be worth disabling plugins though if you make it that far, just to double check that it is not your theme + a plugin.
Please let me know the results! For now, this is the logical next step. No need to pay anyone or anything.
– Brook
Brook
ParticipantHowdy Christoph,
That could be related from the sound of it. First things first, would it be possible for you to test if this is one of the customizations to your site that might be conflicting. This guide will help you test if something is conflicting. If something is, it then walks you through identifying what is conflicting. Once we know that we can work towards a fix.
If you have complete the “Test if there is a conflict” section and still can not bulk delete, would you mind grabbing your system information and pasting it here? Make sure to use the ‘Set as private reply’ checkbox to protect your private information from the public. You can find the system info by going to WP Admin > Events > Settings, clicking on the “Help” tab, and scrolling down to the ‘System Information’ box. (Or by going to [yoursite]/wp-admin/edit.php?post_type=tribe_events&page=tribe-events-calendar&tab=help) That way I can check for any similarities in your setup.
Thanks!
– Brook
Brook
ParticipantExcellent, Donna! Glad to hear I could be of some help. I am glad custom programming was not the only answer. Cheers!
Please feel free to open a new topic should you need anything else in the future. I am going to archive this one since it is resolved. Cheers!
– Brook
Brook
ParticipantHowdy Alex,
For reasons unknown Akismet marked this post as spam. I am very sorry for the huge delay, two weeks is unacceptable.
We are working hard on a new site, and to be honest some of the info on the current site is out of date. It is true that saved events and organizers are now in the free plugin. Custom event attributes, which is called “Additional Fields” in the plugin, is not.
We are approaching a release of our new site, and at the moment my manager deemed this a low priority update since that page will be completely replaced soon anyways. There is actually a bit of a glitch that makes changes to that page surprisingly difficult.
Does that answer your questions? Thanks again for taking the time to point this out. I wish I could simply run over and change it, but the weird complication makes that not possible.
– Brook
September 3, 2014 at 11:53 pm in reply to: Collecting Attendee Names for Multiple Ticket Orders #721088Brook
ParticipantYou are welcome, Adam! I am happy you are understanding about it, even if it is terrible news.
Thank you for clarifying on what that plugin does. I am going to archive this topic since it appears to have run its course. Let us know if there is something else we can help with in the future.
– Brook
Brook
ParticipantHowdy wickedsimple,
You could do this by leveraging the WooCommerce API. Basically you would want to intecept any product in the “Tickets” category upon checkout, and redirect them to your form. Upon successful submission of that form, you could then send them back to the checkout page along with some extra info telling your gatekeeper/interceptor script that they have filled it out succesfully, then you can process the order and return the result. This is going to require a good bit of programming thought.
You might also be able to accomplish what you want with some WooCommerce plugins, perhaps this one: http://www.woothemes.com/products/woocommerce-checkout-add-ons/
Those are the only two opions I can think of. Does that all make sense? Anything I can clarify or perhaps some additional questions I can answer? Please let me know. Cheers!
– Brook
Brook
ParticipantHowdy kirstyburgoine,
Thanks for taking the time to report this. I am noticing the same thing on my test system. I just reported this in our bug/feature tracker. From there the devs can take a look at it, roll a fix into an upcoming release, and then we will report back once that is done.
I really appreciate your helping us with this report. I want to be upfront, it might be a little bit before a fix is released. As you noted this is not necessarily a bug, but it is at they very least a great feature enhancement. We do have to prioritize this relative to any bug reports we might get, hence why there could be a delay. But rest assured a fix is coming and we will let you know once it is ready!
Does that answer everything for you? Can I be of further assistance? Please let me know. Cheers!
– Brook
-
AuthorPosts
