[Barry]

Hi Stephan,

I´ve modified just one thing: The submission form in my community plugin (I added some explanatiosn..)

So long as you followed the approach recommended by our Themer’s Guide (that is, you copied the templates to your theme directory and modified them there) you should be good 🙂

With that said, some of the default Community Events templates have changed in order to introduce improvements, here’s one example:

• In 3.10, it is possible to customize the “Event” keyword (you might prefer to use “Party”/”Parties” instead of “Event”/”Events”, for instance)
• The revised community/edit-event.php template that will ship with 3.10 respects this setting
• If you modified that same template via an override, your customized version probably will not respect that new setting – but of course that doesn’t mean there will be a “breakage”, merely that you won’t benefit from the update in that particular detail

If you do have doubts and concerns, though, the release candidates are available for you to test with so you can adjust your custom templates accordingly.

However – though I can’t offer any guarantees (since I don’t know exactly what changes you made) – it doesn’t sound like there will be much of a problem in this case.

and one more thing: the update sustains/preserves my existing events/locations/venues ?

Absolutely – and we have tested this extensively ourselves.

Even so, making a backup – and knowing how to restore it – is a sensible precaution to take before any update (and, arguably, should be done routinely).

Good to know you guys care for a dull dabbler like me 😉

We definitely care and work hard to make things as easy as we reasonably can 🙂

[Barry]

Hi Stephan,

I’m sorry that our emails alarmed you and hopefully I can allay some of your concerns.

A set of much-needed changes will be shipping with the upcoming release and what we wanted to do with our recent emails was simply to keep users like you informed – and give you the advance notice needed to prepare.

It isn’t a foregone conclusion that you will actually need to make any changes: for many if not most users we expect the update will be seamless. However, the plugin naturally needs to change over time in order to improve and for bugs to be fixed. Consequently, there is an increased possibility that those users who have customized things may need to make some adjustments to their work.

This is one of the reasons that we have decided to provide access to release candidates, which are “preview releases” you can take for a spin before the official update ships.

If you want to access these, please simply visit the Account → Downloads page.

Remember also that, while we naturally recommend you keep things up-to-date, you don’t have to update the very instant our next release becomes available: you are free to make the updates at your own pace.

Is it kind of dangerous to update to 3.10? To me that sounds like that. “Make backups, try it on a test-system, read carefully….” worrying!

No – it should not be dangerous.

Again, we do anticipate that where users have modified specific areas (such as month view tooltips or week view) there may be a need to tune those customizations or revert to the default templates that ship with the plugin until various customizations can be reworked – to learn more, please see this blog post.

Our advice that you backup is really just a reminder of a common best practice: updating WordPress itself, themes or plugins is generally a smooth process – but there’s always potential for unforeseen issues to crop up that are nothing to do with the work we’ve done in this release specifically – and making a backup is nothing more than an easy-to-implement safeguard to protect yourself and provide a means of restoring the site’s previous state.

Similarly, the suggestion to test things out somewhere other than your live site is some helpful advice primarily geared at users who have made customizations and want to see how they fare with the next release before rolling it out on the live site – it’s a sensible precaution we simply wanted to draw attention to.

To sum up, our 3.10 release contains a large number of improvements, fixes and new functionality and we of course want to get those enhancements in the hands of users like yourself with the minimum amount of disruption – but, yes, some work may be required to let specific customizations persist.

If you still have concerns please do let me know – and I’m sorry if we alarmed you unduly.

[Barry]

Hi Northern Pacific Digital,

Great question! You are correct that we don’t have any specific guidance for this one, but it’s certainly possible to make all kinds of changes to this component.

As ever the Themer’s Guide is the best starting point for anyone who is interested in customizing our views generally.

While I don’t know exactly what kind of change you are envisioning, it may be that the section of the guide covering customization of styles will be the most applicable here (if for instance your plan is to change the color of the text to something consistent with your other hyperlinks, or something of that nature).

[Barry]

Hi!

It’s been a while so I’m going to go ahead and close this topic.

• Need help with anything else? Go right ahead and post a new topic, one of the team will be only too happy to help
• Still need help with this issue and need to re-open it? Again, please simply create a new topic and link to this one to provide the team with some context

Thanks!

[Barry]

Hi!

It’s been a while so I’m going to go ahead and close this topic.

• Need help with anything else? Go right ahead and post a new topic, one of the team will be only too happy to help
• Still need help with this issue and need to re-open it? Again, please simply create a new topic and link to this one to provide the team with some context

Thanks!

[Barry]

Hi!

It’s been a while so I’m going to go ahead and close this topic.

• Need help with anything else? Go right ahead and post a new topic, one of the team will be only too happy to help
• Still need help with this issue and need to re-open it? Again, please simply create a new topic and link to this one to provide the team with some context

Thanks!

[Barry]

Hi!

It’s been a while so I’m going to go ahead and close this topic.

• Need help with anything else? Go right ahead and post a new topic, one of the team will be only too happy to help
• Still need help with this issue and need to re-open it? Again, please simply create a new topic and link to this one to provide the team with some context

Thanks!

[Barry]

Hi!

It’s been a while so I’m going to go ahead and close this topic.

• Need help with anything else? Go right ahead and post a new topic, one of the team will be only too happy to help
• Still need help with this issue and need to re-open it? Again, please simply create a new topic and link to this one to provide the team with some context

Thanks!

[Barry]

Hi!

It’s been a while so I’m going to go ahead and close this topic.

• Need help with anything else? Go right ahead and post a new topic, one of the team will be only too happy to help
• Still need help with this issue and need to re-open it? Again, please simply create a new topic and link to this one to provide the team with some context

Thanks!

[Barry]

Hi Jessie,

Thanks for clarifying – I did initially misunderstand.

That said, I seem unable to replicate this: if I create a test event and import it nothing changes in respect of the original event’s status as a public event. If I go on to edit the description, again, the event remains publicly visible (on eventbrite.com).

Are there any other steps I’m missing here?

[Barry]

Hi Jessie,

I do indeed see this if I import, make a change locally (ie, from WordPress) and update the event there.

This certainly seems like a legitimate bug and I’ve recorded it on our bug tracker – we’ll do our best to get a fix in place in an upcoming release and will endeavour to post an update here once it is ready.

Our apologies again for the inconvenience in the meantime.

[Barry]

Hi Jessie,

I’m sorry to hear you are hitting up against difficulties.

This shouldn’t happen and I’m not aware of many other reports along these lines from other users – nor can I replicate the same problem – and so it does tend to suggest that the issue is, for some reason, local to your site.

Our plugin will set the post status to either publish (if the event is “live” on eventbrite.com) or draft (if it is not) – no where does it try to set a post status of private, which makes this a little puzzling.

I definitely appreciate you having gone to the trouble of testing for conflicts and it’s puzzling that those steps didn’t uncover anything.

Is it at all possible there are some customizations that were made directly to core plugin code, or that perhaps were applied to your local copy of the Twenty Fifteen theme – or anything else of that nature that you can think of?

Could you share (by private reply, if you prefer) a URL to one of the events on eventbrite.com?

Thanks!

[Barry]

Hi Allyson,

Community Events is extremely customizable and the best starting point if you’re new to making changes like this is our Themer’s Guide, which explains how to safely override and customize our templates.

In this case, specifically, you could remove the state and province fields by overriding the community/modules/venue.php template. Within that you could remove the country and state/province fields by eliminating this section of code:

https://gist.github.com/anonymous/22932ffd5a0571f5eb9c

Instead, I’d like to add town names… and have it mandatory to select one for every event.

Definitely possible. Look just above the section of code I copied above and you will see the existing city field, which you might change to a pre-determined dropdown.

To learn about enforcing this as a required field, please review the following knowledgebase post:

theeventscalendar.com/knowledgebase/required-fields-for-events-submission-form

I hope that helps 🙂

[Barry]

Hi Francois,

Normally that extra line would not appear and I can only guess that some other component on your site – your theme, another plugin, a customization – is randomly outputting an extra blank line.

Though it’s a pain, the best way to drill down and figure out where the root of this lies is to run through our standard troubleshooting steps. Of course, you may prefer to do this on a test site.

Can you give that a go and let me know how you get on?

Thanks!

[Barry]

Hi Marc,

Can you confirm which route you followed to hide them? Did you set the visibility to private, for instance (if not, could you give that a try instead)?

Thanks!

[Author]

Posts