[George]

Hey Camile,

Awesome, glad my reply helped. As for licensing, it’s not a problem at all to have a version on your staging subdomain and a version on the “live” site itself as well.

Cheers!
George

[George]

Hey Peter,

Thanks for the update. I’m glad to hear the theme developer is equally frustrated in having you go back and forth between us, and on that note, I just wanted to mention that your patience has been extremely appreciated! 🙂

Unfortunately, I’ve been unable to reproduce this error or discover what the cause of it could be specifically by reading through your theme’s source code. I think the end comments I left in my above reply still apply best here:

Maybe they can test chunks of the everything.js file against these issues and see if that’s at fault, or try removing some of the third-party scripts included in the theme, just as a troubleshooting methodology to try and narrow down the specific culprit here.

Sorry to disappoint or leave you frustrated Peter, this is an odd issue – there are some common things that cause TypeErrors, but I cannot produce theme here and I haven’t been able to identify the source of the problem.

If you’re able to test the theme code manually like this yourself, or you can hear from your theme developer if they are able to test things this thoroughly, please let us know what you find. I will post an update here if I learn anything more, as well.

Sorry for the frustration this is all undoubtedly causing Peter! Thanks for being patient and understanding thus far.

Sincerely,
George

[George]

Hey Gordon,

All I did was name the example function with gpeery_ in function name to personalize it a bit! 🙂 It’s fine to use and shouldn’t conflict with anything or cause problems at all.

Does that address your concern?

Let us know if you get to try out the code as described here!

Cheers,
George

[George]

Progress? I thought tooltips wew the biggest issue here! 🙂 I’m really happy to hear those are working for you now, thanks for the update Catherine.

One thing to point out is that the venues showing up in the tooltips is not quite a problem, but rather a feature/customization request that’s a bit outside the scope of the support forums here. The thing is though, now that we’ve resolved the CSS issue with tooltips and they’re showing up now, I’d recommend trying out Gustavo’s original solution again – see what you find, and keep us posted.

As for the padding, this is another customization request, but the following CSS – although only slightly different than the CSS I posted above, should work if you place it at the bottom of your theme’s style.css file.

For further CSS tweaks on your site, check out the tools I mentioned above: Firebug if you use FireFox, or the Developer Tools for either Safari or Chrome. They’re all free and come with an Inspector tool that’s quite handy in making these customizations yourself as you see fit.

Let us know what you find!

Thanks,
George

[George]

Hi Adam,

Thanks for all three translations here. We’ve downloaded them and now the next step is to test each one. Stay tuned for our testing results!

Thanks Adam! 🙂
George

[George]

Hey Colin,

Unfortunately, there may be very little we can do if the problems of another plugin’s design are ruining the functionality of other things on your site. Your findings here are greatly appreciated though, and it’s possible we might be able to find out what’s going on with issue #2 as you’ve described it here.

To get started on this, when you mention that you “ran the debug”, what exactly do you mean? If you mean the debug bar plugin or a var_dump() of the query results, as it seems to be the case here, that’s quite helpful. One extra step you should take if you haven’t already is to see if any errors pop up on your site if you head to your site’s wp-config.php file and change this line of code:

define('WP_DEBUG', false);

to this:

define('WP_DEBUG', true);

That will display PHP errors on your site if any exist, which can help.

After making this change, to any PHP errors pop up if you try navigating to the Community Events submission page? Or anywhere else on your site? If so, can you copy and paste the entire output of these errors into Gists at http://gist.github.com, then share the link to those Gists here on the forums? (This keeps things a bit easier to read and manage than posting code directly in the forums here).

Let us know what you find!

Thanks,
George

[George]

Hey Stathis,

Thanks for reaching out to us here!

Date names, like month and day names, should indeed be translatable – in the Events Calendar and all of our official add-ons, we use the date_i18n() function to render dates, which is a default WordPress function that handles translating date names like this.

Are you finding this to not be the case? If so, what is the Language you’ve set for your WordPress installation? If you set your WordPress language settings to a language that has these date values translated, then the dates should automatically be translated into that language.

Let us know if this helps! If not, can you explain what you need help with in more detail? We’ll try our best to give a better response from there 🙂

Cheers,
George

[George]

Hey Spencer,

Thanks for the update – however, I unfortunately am still not quite sure what you mean. If you need to use something on the same meta level as _EventStartDate, then the only other default Events-related meta keys are in the knowledgebase article you linked to above → https://theeventscalendar.com/knowledgebase/wordpress-post-meta-data/

To retrieve the tags attached to an event, this is not something that is revealed within the post meta. It’s a separate kind of relationship altogether, within WordPress. There is post meta, which has the meta keys and meta values relationship tied to a specific post, and then are post taxonomies, which are entirely separate from this. To get the tags of a post/event, you’d need to use a function like the one I linked to in my reply above.

Does the information here help? If not, please describe why in detail and we’ll try our best to give a better response! 🙂

Thanks,
George

[George]

Hey Camile,

Thanks for reaching out to us here. I’ll address your questions in order to keep things organized – one thing to point out, however, is that getting the look or functionality of the calendar to match your exact desires may still require customizations, including custom CSS for styling and custom PHP snippets to alter the display or functionality of parts of the plugin. We don’t support such customizations, so I just wanted to point this out to not get your hopes up about what to expect from support here! 🙂 Now, on to your main questions:

1- We have specific needs for our front-page, other event plugins/services do not permit us to achieve these needs. Here’s the wireframe for our proposed site: https://dl.dropboxusercontent.com/u/15710764/gktrpls-site_layout.png

What’s important here, is that we can display the events in a netflix-esque tiling, but also to do the same with Venues and Organizers.

This is an example of customizations to the plugin you’d have to build yourself. Yes, the layout and Netflix-esque slider here are definitely technically possible, but they’re not a default view of the plugin or any premium add-on. Your best bet would be to create a custom page template for your theme, in my opinion, and style things as needed.

2- Events, we have a whole pile of other data that we add for each of our events, venues and organizers. like a detailed list of all their social media links, and some very specific classification choices. Can we add these extra pieces of data to our listings? Can we also do so in a way where we don’t have to add them manually each time, but from groups of checkboxes?

Extra details can indeed be added for all of the content types you mention here. For events, this is quite easy if you have the Events Calendar PRO add-on – there’s a whole section in the Events settings page called “Additional Fields”, which allows you to create additional meta fields for the Events type. Read more about this here → https://theeventscalendar.com/knowledgebase/pro-additional-fields/

As for adding custom data to venues and organizers, this would require a bit more code involvement, but is again indeed technically possible. You can manually code up some meta fields and the form inputs on various admin pages for the features you need, then simply get the meta and display it in events templates by customizing the events templates as described in our official Themer’s Guide, which you should read by clicking here

3- A way to add “neighbourhoods” to the top calendar sort and the filter bar. Our hierarchal breakdown looks like this: Neighbourhood > Venue > Event. But if we plan for the future (we’re talking about a long-term relationship with you guys here) it will end up looking like: City > Neighbourhood > Venue > Event

Not to sound like a broken record here, but yes, this is indeed technically possible, though not something we can offer much support or specific code/advice for here on the forums. If you have neighbourhoods easily accessible based on Venue meta that you add as described in the question above, you can indeed create a custom view and run some basic event/venue filtering based on this meta. For an example of how to build a custom view, I’d recommend checking out our example “Agenda View” plugin here → https://github.com/moderntribe/tribe-events-agenda-view. Some of the code is admittedly a bit outdated, but in general it might offer some inspiration and be a great place to start the learning process here. Another awesome resource would be to simply through the source code of the The Events Calendar itself and see how the default views are created, and how their filtering is processed.

4- My developer keeps chanting “shortcodes”, do you have them? And can I see them so I can send them to him?

At this time there are no shortcodes built into The Events Calendar core, PRO, or any other official add-ons. However, one of our developers Barry has made a plugin called Event Rocket, which is not officially supported, but is very well-made and includes several custom events-related shortcodes – and it’s free! 🙂 https://wordpress.org/plugins/event-rocket/

5- Do you have any intentions on having Facebook and Twitter posting features within the app? This would save us some effort.

At this time, no, these things are not planned features. There’s a myriad amount of other plugins for WordPress, free and premium and good and bad and simple and complex and everything in between, that enable this sort of functionality, so hopefully you can find a simple solution that works well for you.

6- How customizable is the Photo View? We would love to have more control of it, but we’re not sure if that is possible,

The Photo View, and in fact all views, are extremely customizable. For a better sense of exactly how flexible these views are, definitely give our Themer’s Guide a good solid read → https://theeventscalendar.com/knowledgebase/themers-guide/

7- Bonus points: we were hoping that any click on the calendars (we’re most attracted to the Photo View), open a modal/lightbox that auto plays our YouTube video and then gives the option to go to the individual event/venue/organizer page right bellow… is there anything in your plugin that would stop us from doing that?

No, there is nothing within the plugin itself that would prevent this sort of functionality from working, but that of course depends on your exact implementation of things. For example, say you hire a developer to build this for you and they do a bad job of writing the code to enable this sort of functionality, integrate things with a poor lightbox library, or something else undesirable – then regardless of our plugin, things would be quite ugly here and probably not work correctly. So yes, our plugin is well made and the markup is valid on Photo Views, which you can customize extensively anyways, but from there the success of a lightbox integration is all up to how exactly you write the code to do it.

I hope I addressed everything here, let us know if you have any other questions or concerns and let us know what you think about the replies given here. I’m happy to clarify anything if I left it too obtuse here in my original reply.

Cheers!
George

[George]

Hey Spencer,

Getting ticket information for a given event isn’t necessarily as easy as just calling the post’s meta, but you can indeed access the tickets with a few functions.

As a demonstration of this, I wrote a little bit of code for you in this Gist here:

https://gist.github.com/ggwicz/a9589073df0d5f05978b

Try adding that code to your theme’s functions.php file, then navigate to single event that has tickets for sale (even if you just add some “sample” tickets for development/testing purposes).

That code should output the structure of the tickets information so you can learn what to reference if you want to use that information in some custom code, and you can use the code in this Gist itself as a starting point for making those customizations.

Let us know if this helps!

Cheers,
George

• This reply was modified 10 years, 7 months ago by George.

[George]

Hey Spencer,

I’m not quite sure what you mean by the meta key for tags – one thing to point out is that taxonomy relationships are not built within the post meta for a given item.

Can you clarify exactly what you mean here? If you’re just trying to get the given number of tags for an event, I’d recommend looking into using any of the default WordPress functions that let you get tags of a specific item – for example, wp_get_post_tags(): https://codex.wordpress.org/Function_Reference/wp_get_post_tags

You can use a function like this because the “Tags” for events are just normal post_tags within WordPress.

Let us know if this helps!
George

[George]

Hey Joel,

This is an interesting question, and I see why you’d want to enable this.

There’s good news and bad news here – the good news is that this is definitely technically possible to pull off. The bad-ish news is that it would require a decent amount of custom coding, which is outside the scope of the support we can provide here.

Despite that, we’re happy to help with some ideas and basic starter examples before handing the reins fully over to you.

For example, one of the easiest ways to do this would be to overwrite the existing Google Maps link completely using our tribe_get_map_link_html() filter. I wrote a filter and function for you demonstrating this in a Gist here → https://gist.github.com/momnt/fa1fff0c0622e947808c

That should help you get started immensely on this – for further customization here, or filtering of the map links, or to only do this on specific devices, or to simply add this to the existing Google links instead of wholly replacing them, you’ll need to take the reins, but I hope this gives you a great head start!

Let us know if it helps!

Cheers,
George

[George]

Hey Peter,

I’ve been investigating this for quite some time this morning, and am failing to recreate this problem no matter what I try. While your theme developer is correct that the error is coming from our own JavaScript, it seems quite clearly to be directly caused by something from within the theme – if doing nothing else but activating Twenty Fifteen resolves these issues, that is very strong evidence of this.

I’m not quite sure what the problem is. I noticed your theme is extending the Array prototype, and indeed the TypeError being thrown in Firebug is being thrown on the [empty] tg.markers Array. I’ve tried investigating possible issues with this and recreating them, but like I mentioned, I’ve failed.

I know you’ve already contacted your theme developer, and am sorry if you feel like you’re caught in the middle of people who won’t help – we certainly don’t want you to feel that way, but I cannot recreate this error for the life of me (at least, up until this point), and the evidence is showing that something within your theme’s JavaScript is causing this failure.

I’d recommend reaching out again to the theme developer, and share this information. Maybe they can test chunks of the everything.js file against these issues and see if that’s at fault, or try removing some of the third-party scripts included in the theme, just as a troubleshooting methodology to try and narrow down the specific culprit here.

Sorry to disappoint or leave you frustrated Peter, this is an odd issue – there are some common things that cause TypeErrors, but I cannot produce theme here and I haven’t been able to identify the source of the problem.

— George

[George]

Hey Sharad,

Thanks for the update and for going through all these steps – on your submission here, it says that your version of WordPress is currently 3.6 – can you please update this to the latest version? 3.6 is quite outdated, and may be the source of many of your problems here.

Let us know what you find!

Thanks,
George

[George]

Hey Jim,

This shouldn’t be an issue for you at all, as that column data just shows the “Ticket Name” – so, for your 8pm show, just make the ticket name be “8pm” or “8pm Show”, then “10pm” for your 10pm show, and so on.

Here’s a screenshot of where to add this → https://cloudup.com/cUqgwqu9iVg

And here’s how it looks in the attendees list for that event once I went ahead and bought one of each ticket → https://cloudup.com/cQ7f8dOYzKd

I hope this helps! 🙂

Cheers,
George

[Author]

Posts