[Barry]

Hi Luke,

Thanks for posting!

If you haven’t already done so I’d recommend reading through the Themer’s Guide which covers the basic steps for safely overriding our templates.

From there, you’ll probably be interested in the modules/meta.php template — you’d probably want to add your new section after the point where the organizer template is included but before this line:

do_action( 'tribe_events_single_event_meta_primary_section_end' );

I hope that helps!

[Barry]

Happy to help 🙂

I’ll go ahead and close this topic – though it might be worth flagging this up to the authors of the Disqus plugin if you wanted to, as the priority change encapsulated in that snippet would probably be safe to make within their plugin itself.

[Barry]

Definitely feel free to propose this as a new feature over on our UserVoice page – that way, others can comment on and upvote the idea 🙂

Thanks also for marking this as resolved, I will go ahead and close it out – of course, please don’t hesitate to create new forum topics if you have any further questions!

[Barry]

Definitely, I hope to update you again as soon as possible.

I’d hate to falsely set anyone’s expectations, though: right now our next upcoming release is in the final stages of quality control and so it is pretty unlikely we’ll be able to fit in further code changes (which this fix would require) – so it is likely to take just a little longer to deliver on this issue.

Thanks for your patience in the meantime.

[Barry]

Hi Marjet,

To clarify, that setting blocks those roles from the admin environment (ie, the WordPress dashboard) but they should all still be able to create events via the Community Events submission form.

If that is indeed what you are experiencing, it is the expected behaviour 🙂

I can not get the contributor to only add to the community events.

I may have misunderstood.

Did you mean that you only wish contributors to be able to submit events via the Community Events submission form? If that’s the case, I’m afraid it is not directly supported.

However, you could add some custom code that runs before that page loads and either displays an alternative message or redirects the user someplace else (if they are not a contributor).

[Barry]

Thanks Paul.

Might this short snippet, which you could insert into either a custom plugin or your theme’s functions.php file, help?

function support_disqus_events() {
	remove_filter( 'comments_template', 'dsq_comments_template' );
	add_filter( 'comments_template', 'dsq_comments_template', 100 );
}

add_action( 'wp_loaded', 'support_disqus_events' );

[Barry]

Hi Sascha, we’ll certainly keep you posted.

I do not yet understand why the placeholder %s is replaced with “veranstaltung” without the capitalization. IMO the translation states “Veranstaltung” for “event”.

The problem is that in some languages and in some sentences it would be bad form to capitalize that word. For that reason there are places where it is converted to all-lowercase. Of course, that doesn’t work well in languages such as German – which we now realize and will address is quickly as we can.

[Barry]

Hi Paul,

I’m sorry to hear you are experiencing difficulties.

Although the amount of support we can provide for third party plugins is limited (particularly when the problem doesn’t exist if native WordPress facilities are used) I’d be happy to explore it a little with you.

Firstly, do you know when this problem started? For instance, was it a specific release on our side or on the side of the Disqus plugin you are using that triggered it?

Secondly, if you visit Events → Settings → Display which template is currently in use? Can you try changing this to something else and see if that makes a difference to this specific problem

Let me know how you get on!

[Barry]

Hi Marjet,

In simple terms, do you wish to let contributors interact with Community Events (via the frontend of the site) but ban them from any admin environment interactions?

If so, might the block users from dashboard setting found in Events → Settings → Community help?

If not and you are determined to continue with the user role editor approach, might it be the case that you aren’t seeing any changes because you are using an existing user account? What if you create a new user in the contributor-role – do you see the changes then?

[Barry]

Hi Uroš,

That figure (50MB) simply reflects your current PHP configuration, so one approach here could be to adjust that value. Typically this is done by amending the php.ini file – though in some installations it is possible to change it with an amendment to your .htaccess file instead.

If you are unsure how to do this or which approach will work best in your environment I’d recommend chatting with your webhost.

Alternatively, you could leave that be and add an extra validation step which discards images that are too large (or chops them down to size) only when they have been posted through the frontend Community Events submission form – that way you could still upload larger files from within the admin environment.

I hope that gives you some ideas you can work with 🙂

[Barry]

Hi JuveCreative,

Interesting request!

Though working through customizations like this one are a little bit beyond the level of support we typically provide here on the forums, it does sound like this would make for a great enhancement.

In terms of removing past/expired events from the search results, it looks like others have already requested this and I’d encourage you to add your support.

On the other hand, I don’t however see any existing requests to respect the show only the first instance of each recurring event within search queries – but you could certainly create one.

Posting feature requests in this way is a great means of getting ideas in front of us and it allows other users to add their support – giving a great sense of just how much demand there might be 🙂

[Barry]

The thing is that the keywords “event”/”events” are customizable: some people prefer “party”/”parties” or “lecture”/”lectures”, depending on what they use the calendar for. For that reason, we use these %s placeholders.

So those particular keywords are inserted dynamically rather than being drawn from the translation file … but of course different languages have different rules relating to capitalization which leads to problems like this one.

Unless, you come up with yet another hint.

I’m afraid I don’t have much else to suggest right now, besides a quick reminder that you must compile your .po file into a .mo file (otherwise WordPress cannot use it) 🙂

[Barry]

Hi Marcuz,

I hesitate to suggest it but it would be possible to create your own custom translations to workaround this. The reason I hesitate is that it can be a pretty complex process, more on that in a second.

The key however is that the word “event” (or “events”) is generally inserted into translations via a placeholder, something like this:

View all %s

In the above example, %s will be replaced with a term meaning “events”. The official German translation for example looks like:

Alle %s anzeigen

However, it would be possible to create a custom translation that dispenses with the placeholder and uses proper capitalization:

Alle Veranstaltungen anzeigen

(Apologies if that actually is not the correct form, but I’m just trying to illustrate how to solve the problem.) With the placeholder removed you have full control over the way the word “event” is translated and capitalized in each string.

Learning how to create translations is a topic in itself and not something we can guide you through here, suffice to say there is plenty of documentation in the WordPress Codex and manuals. You would also need to learn how to deal with strings that contain multiple placeholders if you wish to avoid errors. Example:

This %s will expire in %s

Leaving one and removing the other will cause problems, you’d need to use numbered syntax like this:

This event will expire in %2$s

As you can see, we have replaced the first placeholder and changed the second so it clearly indicates its position – more detail on this can be found in the PHP manual.

Unfortunately it is beyond the scope of support we offer here in the translation forum to go into more detail on this – but do also know that we have increased the priority of the bug report and are actively considering different ways to deal with this.

[Barry]

Hi Steven,

Might that match the event cost?

It’s a little tricky to judge from a screenshot – can you share a URL where I can view this (by private reply if you prefer)?

Thanks!

[Barry]

Hi Jason,

Thanks for highlighting this (and our apologies for the disruption).

Commenting that out seems like a solid working solution until we can make a change in an upcoming release, but it certainly seems like it is a left-over piece of code we can now dispense with 🙂

[Author]

Posts