[Barry]

OK – but are you positive you’ve configured WordPress to work in French (assuming that’s your language of choice here)?

If I visit the standard WordPress login screen at wp-login.php everything is still in English which makes me think you may not have configured the language settings.

[Barry]

I’d expect so: your first three upcoming events (at least, as of this morning) all take place at the same venue and I see that same venue is used for some other events further down the list, too: so there will appear to be a single marker for those.

Is there any way to increase the size of the list displayed at one time so that more markers appear on the map at once?

It’s possible (though a fairly advanced customization) to include more markers than there are events/venues on a given page of map view – but that can also result in a confusing user experience and from the sounds of things I’m not too sure that is what you really want here?

[Barry]

Hi James,

I’m sorry to hear that you are disappointed in our level of service.

We want to help to the extent we can – but it isn’t practical for us to offer unbounded assistance for every problem and at this point I would like to draw a clear distinction between support on one hand and customization work on the other.

In delivering support our primary goal is to help you understand how the plugin works and point you in the right direction if something is unclear.

Collecting bug reports and – where it’s reasonable for us to do so – helping you workaround any bugs until they can be resolved in a future release is similarly a high priority task in terms of our support service.

However, when it comes to customizations – changing how the plugin functions and behaves – service is naturally more limited.

We simply cannot afford to act as an on-tap design/development service – that just isn’t our role and if our product page, terms and conditions or anything else led you to believe it was then we’re more than receptive to your feedback so that we can make things clearer for other current and future users.

Even so, we fully recognize that for our users to get the most from our plugins they will frequently need to customize them. To that end we develop and maintain a rich set of learning resources in addition to providing more-specific assistance on a topic-by-topic basis where it makes sense for us to do so.

But because something has changed you now don’t seem to recognise it as a problem and have suggested something that “Typically we wouldn’t recommend that approach” or bat it away for us to find someone else to support your plugin.

Typically we would not recommend it – nor did we recommend it in the other topic you referenced (the proposed solution there came from a customer).

That’s not to say you can’t or shouldn’t apply it – and hopefully with the direction I gave you in my first reply you can use it on a current version of our plugin if you choose to do so: that decision is something for you to make (and if you don’t feel comfortable, don’t do it – hire someone with suitable skills or explore a different strategy such as I outlined).

Lastly, I would take issue with your statement that we are “batting things away”. From Leah pointing you to a possible existing solution on the forums to my helping you apply it to the current release we’ve done our best to get you on track.

To close:

• What do you still need help with to drive this forward? We can’t build the final solution for you, but perhaps we can point you to some further resources if you have additional questions
• I will talk to Leah and highlight your concerns, with a view to possibly re-prioritizing any tutorial work on this subject

I hope that clarifies our position and definitely let me know if you’ve got further thoughts/questions here.

[Barry]

Hi there – just checking in since I got the sense you were anxious to resolve this quickly (plus, I may be out tomorrow and so unavailable to assist again until Thursday).

The team and I had a quick chat about this topic to think about why you may be unable to locate the files in question and one thought was that perhaps you are using the theme/plugin editor built in to WordPress itself (and which has various limitations) – might that be the reason?

If not, please do share some links to screenshots that illustrate what you’re seeing. Thanks!

[Barry]

Going to close this topic as it’s been sitting quietly for quite some time now (apologies if you still required assistance, jeanmaheu, but hopefully you created a fresh topic or you could always do so now).

[Barry]

As this topic is almost a year old at this point we’ll go ahead and close it out. WPML compatibility is still on the radar and we’ll be sure to post updates on our blog as and when it progresses 🙂

[Barry]

Hi Gonzalo,

If you define a standalone function – ie, it doesn’t belong to a class and will never exist within an instantiated object – then you cannot use the keyword $this.

Instead, if you need to refer to members of the main TribeEvents object from your function, please use TribeEvents::instance() in place of $this.

I hope that helps – however because we’re now very much in custom development territory we’ll be unable to help further and so I am now going to close this topic.

Good luck, though, it definitely looks like you are quickly closing in on a nice solution 🙂

[Barry]

So it’s using the coordinates rather than the street address, and those coordinates have been determined as:

8°04'14.8"N
98°19'50.7"E

If that’s incorrect it may be that you need to modify the address slightly and re-save the venue, however – unless you’ve made modifications to the default behaviour of the plugin – those coordinates would have been provided by Google’s geolocation API.

Can you try making some other forms of the street address in the first instance and see if by playing with it you can get any closer?

[Barry]

Hi Gonzalo!

add_action( 'tribe_venue_table_top', array( $events, 'displayEventVenueDropdown_custom' ) );

The above is telling PHP to look in the wrong place – your custom replacement is not a part of the main event class, it’s a standalone function 🙂

Try changing that to just:

add_action( 'tribe_venue_table_top', 'displayEventVenueDropdown_custom' );

Does that help?

[Barry]

Hi Susan,

I’m sorry to hear you’ve hit up against some difficulties.

Can you provide a specific example of the problem you are facing here? Can you also confirm – by private reply if you prefer – if there is a URL where I can see this (I realize you provided a URL when you opened the topic initially, but it appears not to resolve correctly).

Thanks!

[Barry]

Hi Robyn:

I’m sorry you hit up against difficulties – there does indeed seem to be a problem here. If you are comfortable doing so, can you try adding the following code to your theme’s functions.php file?

https://gist.github.com/barryhughes/ed8b4fb340fe73e16449

You may need to do a browser refresh before it takes effect, but it will hopefully stop those links from effectively being blocked on smaller devices.

Does that help?

[Barry]

Hi!

If you create user accounts using the “author” role, or reassign existing users to that role, they should then be able to login, create and publish their own events.

Does that help?

[Barry]

Hi Jeff!

Just as with our other plugins you can easily override and modify our templates – and as almost all text is passed through translation functions it may even be possible to leverage third party plugins like this one to make these changes 🙂

Also, can fields be added/removed in the ticket purchase form?

That is certainly possible, but is a more advanced customization to make and realistically you would need a decent working knowledge of WooCommerce and WordPress development generally to push this through.

Definitely achievable, though 🙂

[Barry]

Hi Thierry,

You mean the Events List widget right?

I believe that string has already been translated in our French translation (to Voir plus) and if you configure your site to use French it ought to be transformed as expected.

WPML may be the complicating factor here, however. Can I ask: if you deactivate WPML and ensure your site is set to operate in French, is it correctly translated then? (I realize that may not be a practical solution – but I want to ensure the problem is as I suspect).

[Barry]

Hi Gonzalo,

Overridding the template (modules/venue.php in this case) is still a good way to go since if you write a replacement function you can drop it in there, replacing the call to tribe_community_events_venue_select_menu().

Alternatively, you could unhook TribeEvents::displayEventVenueDropdown() — currently it runs when the tribe_venue_table_top action fires — and hook up your alternative function.

It is a slightly more advanced customization and if you have any doubts I’d recommend following the first strategy and overriding the modules/venue.php template.

Does that help?

[Author]

Posts