[Barry]

This reply is private.

[Barry]

This reply is private.

[Barry]

That’s great to hear, I really appreciate you confirming this 🙂

If we can help with anything else, please do create a fresh topic and one of the team will assist as quickly as they can.

Thanks!

[Barry]

This reply is private.

[Barry]

This reply is private.

[Barry]

This reply is private.

[Barry]

Hi there Robin,

I do apologize for the long delay – this clearly dropped through the cracks and is my fault entirely – but let me run through your questions and try to answer them.

Embeddable short code onto a password protected page

Events Calendar PRO does indeed allow you to embed our calendar views on any page you like via a shortcode.

Private events (not accessible by URL if not logged in as the right level of user)

Absolutely – you can mark events as private just as you might a regular WordPress page or post.

– Month view short code
– Events created in wordpress

Both these things! See my reply above re shortcodes and yes, the creation of events is indeed done from within the WordPress environment in a familiar post editor-like experience.

Change calendar title of the shortcode month view

With some customization work this is certainly possible, though there is no built-in user interface with which to control this.

Edit colors of the shortcode month view

We integrate with the Theme Customizer to let you control various facets of the calendar’s appearance – and this also covers month view when embedded via a shortcode.

Change when the week starts on the short code month view

It will respect the “week starts on” setting for WordPress itself, it’s not possible to diverge from that without some customization work.

I hope that answers your questions and do remember that you can try our core plugin, The Events Calendar, for free – it will give you a much better sense of what is possible 🙂

Thanks!

[Barry]

Hi Extreme Networks!

When a valid placename is specified a search is made for events taking place at venues within a certain radius of that place (and you can control the radius – making it larger or smaller as needed – via the event settings screens).

If you or a visitor provides the name of a large region or territory, then the geolocation API returns the coordinates for the centre-point of that area: the problem of course is that even with a large search radius, that will not necessarily cover the entire state of Queensland (or if it is a large enough radius, it may well pull in events in venues outside of Queensland, in adjacent states and territories).

This is an existing limitation of the system and not something for which there are any easy solutions, I’m afraid. Based on my description, though, do you think that is indeed the problem you are hitting?

[Barry]

Hi Cathy,

I’m sorry to hear you have had a rough experience.

Just to clarify things, we are a company who produce event and ticket management software used on lots of websites all over the world … however he don’t actually sell tickets ourselves.

If you paid for tickets via eventbrite.com, perhaps you could reach out to their team for assistance? Or, if you followed a link to eventbrite.com from a specific website, perhaps you could reach out to the operators of that website?

Again, sorry to hear you are missing your tickets but I’m afraid this is not something we can help with as your transaction was not with us but with eventbrite.com/whichever business sold you the tickets.

[Barry]

Also, we are getting feedback from our customers that they are experiencing problems when trying to fill in contact information on mobile phones.

I’m less sure about this problem … which form are you referring to here — is it generated by one of our plugins and can you link me to an example?

[Barry]

Hi Vladan,

I’m guessing orders have been placed for one or more tickets for the event you’re having trouble with. Can you confirm what the status of those orders is?

It looks like you’ve configured your site to only create the tickets/attendees once the order status reaches “pending” or “completed”, so if for example they are currently set to “processing” or “on hold” and have not passed through one of those other statuses, that might explain this.

Let me know!

[Barry]

…By way of further update, that part of the bug that I can see has been logged and we’ll address in an upcoming release (and we’ll do our best to post an update in this topic once that happens) 🙂

[Barry]

Hi Miles,

I definitely see a bug but it’s not exactly what you described, so I wanted to quickly review in case I need to do something differently to see the same thing.

I started with two different ticket types in two different events, each had existing and unique SKUs. I moved an attendee from one to the other and did indeed hit the “Woops! We could not complete the requested operation due to an unforeseen problem” error — however the move was actually successful.

It did not seem to result in a new ticket type being created with a different SKU, however. Is there anything about the process I followed that doesn’t match how you were doing things? What does the new ticket product and SKU look like (does it have “-1” appended to the name, or is it prefixed with “Copy of” or anything like that)?

[Barry]

For sure – let’s leave this open for the time being and let me know if you have any other thoughts or feedback later on.

Please note threads automatically close after 3 weeks without any update, however if that happens simply create a new thread and link back to this one if needed 🙂

Thanks again!

[Barry]

Hi Craig,

What you are describing is the expected behaviour.

A regular category archive contains events in a single, specific category and that’s really easy to map to a nice and clean ‘pretty permalink’ structure, such as events/category/foo.

However, when using Filter Bar, a visitor may choose to filter down to events in one of many different categories, not just one, and the approach we’re using is more amenable to that sort of scenario — nor should it prevent pages from being indexed.

Furthermore, crawlers should ultimately continue to index the individual events that are returned and from there can discover the various category archive URLs which have the sort of URL structure you prefer.

Does that help to explain things at all? If you have further feedback or suggestions for improvement we’re definitely open to hearing them.

[Author]

Posts