[Barry]

Hi!

What role does the admin-ajax.php play?

Despite the presence of “admin” in that name, it is the recommended controller for any and all ajax requests (not just those within the admin environment) that plugins such as our own generate.

I have the options in the wordpress ssl plugin to force domain mappings so prehaps that could be done with that?

Changing your WordPress and Site URL fields (in the General Settings screen) so they use the “https://” protocol is an easy way to ensure HTTPS is used everywhere.

For anything beyond that, such as extra rules relating to CloudFlare or exceptions for admin-ajax.php requests (if those are needed) we’d really need to leave things in your hands: the vendor for the other plugins/services you are using are probably best placed to help with any questions you have about their usage 🙂

I hope that helps!

[Barry]

I’ve linked this forum topic to the report on our internal bug tracker – and we’ll certainly do our best to re-open this and let you know once we’ve progressed this 🙂

Thanks again and apologies once more for the inconvenience.

[Barry]

Hi Erika,

So that looks good to me with two caveats:

• If your venue URL does not include the protocol (ie, “http://” or “https://” at the start) it will not function quite as expected, so please ensure your venue URLs are complete – or else you could make a further adjustment to the template to add the protocol if it is missing
• I completely forgot that the venue email field is not actually a field that exists by default, which is why you see nothing there (and we’ve slated that same part of the default tickets email for removal in the next release)

Does that help at all/clarify things?

[Barry]

Hi Rush,

I’m sorry you’ve experienced these difficulties and hopefully we can help you to exorcise a few demons, here 🙂

That said, may I point out that we do try hard to stick to one issue per forum topic — this helps to avoid confusion and better enables us to provide timely service to all our customers.

With that in mind, let’s focus on the first of the issues you raised here in this topic and if you can create fresh topics for the other problems one of the team will be only too happy to assist with those, too.

First of all, the plugin has just randomly decided to turn all events to dots. After a bit of searching I’ve discovered that it tends to do this when on mobile as it’s trying to simplify what is shown on the screen of mobile devices. Cool, but we didn’t activate it… it just turned on randomly.

You’re exactly right: this is an attempt to simplify the amount of information shown when a visitor is using a smaller screen, such as a handheld device.

When I look at your site I do see it is “mis-firing” within a desktop context and that certainly isn’t the intended behaviour. However, I believe the problem in this particular case is the minification/concatenation tool you are using.

Ordinarily, the particular assets used to set up a mobile friendly view are loaded via a tag which specifies they should only be used in specific conditions — ie, on a small screen. On your site however a plugin seems to be minifying lots of different assets and is serving them all together with no regard for the media directives.

You’re probably better placed than we are to figure out which plugin is doing this (it might even be something that’s baked into your theme) but if you are using a caching plugin I’d suggest starting there, as several caching plugins also provide minification and concatenation facilities.

How you’ll deal with this will depend on the actual plugin, however I can’t really agree that this particular problem is the result of anything we are doing incorrectly – we aren’t using any particular sorcery to add this media directive, we’re using a well established part of the WordPress API.

Does that help at all/at least steer you in the right direction for this particular issue?

[Barry]

Hi Lindsey,

I see what you mean and if you’d like to post a feature request (this has the benefit of letting others comment on and up-vote your idea, which can be a useful metric for us) we’ll be more than happy to review it for possible inclusion in a future release 🙂

As things stand, though, might it not work to assume the order items correlate directly and in the same order to each matching ticket within the same order?

For example, let’s say order #10 contains 3 ticket purchases:

Order Item | Product ID/Name ("Ticket Type")
-----------+--------------------------------
201        | 10 "Standard"
202        | 11 "Concession"
203        | 11 "Concession"

Let’s also say it resulted in three attendee objects being created in the posts table:

Attendee Object
---------------
350
351
352

No formal connection is stored in the attendee or order item meta data, yet it seems logical and not too risky to assume the relationship plays out like this:

Order Item | Product ID/Name | Attendee Object
-----------+-----------------+----------------
201        | 10 "Standard"   | 350
202        | 11 "Concession" | 351
203        | 11 "Concession" | 352

Would it be possible for you to use that as a strategy for determining which order item relates to which attendee object? The calculation only needs to be performed once, in a sense, since at the point where attendee objects are created you could save the matching order item ID in the post meta table and retrieve it thereafter.

Might that offer a means of dealing with this situation?

[Barry]

Would it be possible to see a further screenshot or two of your plugin admin screen, showing me the top of the screen (in case there are any warnings/notices) plus the entries for our plugins themselves?

Based on the information you provided when you opened this topic it also looks like you haven’t yet had a chance to run through our standard troubleshooting steps – could I ask you to give those a try? In some cases, other plugins or even your theme may ship with a component called PUE which can cause problems with our own licensing implementation.

Let me know how you get on 🙂

[Barry]

I can only apologize for the rough experience which is, admittedly, a failing on our part. I’m sorry the snippet didn’t provide any relief but I’ve raised the priority of this bug on our internal issue tracker and we’ll certainly aim to resolve this as quickly as we reasonably can.

[Barry]

Hi Matt,

Your host’s support rep is quite right – it’s not a resource problem as such – so perhaps something like this would help to describe what’s happening:

Events Calendar PRO makes requests to the Google Geolocation API.

This API allows a certain number of requests per day – but when this limit is exceeded Google will refuse to serve further requests. This can be a problem when the same server is home to many websites, since one other heavy user (of the same API) or lots of light users can collectively exceed the request limit.

It’s not a problem with server resources, more the fact that when lots of sites that use this API are all hosted on the same box their requests are counted together.

That should help them to understand the nature of the problem – which, to be clear, is not a failing on your hosts part. It’s just that, in some circumstances, a standard hosting plan can be unsuitable.

I should also highlight that it is possible to obtain an API key from Google (however, you may need to pay for this – but it is best to check with Google themselves). With some customization work you could add this special key to each request made by Events Calendar PRO, which would provide another route to resolving this.

I hope that helps/clarifies things.

[Barry]

Apologies for the confusion, it looks like we forgot to update things over on Shindig but I’ve made a note for us to do so as quickly as possible – thanks for highlighting this 🙂

[Barry]

OK. Are you able to disable this in the case of requests to admin-ajax.php? If that isn’t feasible for some reason then I’d recommend one of two courses of action:

• You would either need to ensure public-facing event pages are also served over HTTPS, or,
• Perhaps make use of CORS to eliminate this problem

[Barry]

So when you say that the error you quoted occurs on the main page, do you mean the main events page? Or the main page of your blog?

I’m guessing in either case it’s not directly related to the problem you experience on event category pages. It is a bit puzzling that you don’t see any errors in that particular scenario; I wonder even if that suggests we aren’t looking so much at a plugin conflict as something like the available memory being exhausted – and perhaps that just happens to occur when our plugins and Yoast’s are enabled.

Could you share your system information (which can be found in the Events → Help screen)? Can you also confirm if the problem occurs when you have a default theme enabled and no plugins but our own and WordPress SEO?

[Barry]

Would it be possible for you to copy the contents of your custom tickets/email.php template to a service like Pastebin or Gist and share the link here so I can take a look at your changes?

[Barry]

Hi there Matt,

There does seem to be a problem with filters running in autocomplete mode. Would it be possible for you to temporarily switch any filters such as category filter from autocomplete to dropdown or checkbox mode — and does that clear the problem up (at least as a temporary measure)?

[Barry]

Awesome!

[Barry]

I’m sorry it hasn’t been going smoothly – but thanks for providing your URL and the other details about what you are trying to achieve.

So the primary hurdle seems to be letting people find events in or near their location: there are a few ways you could go about this, including some clever use of categories and tags (and you already seem to be using categories within Filter Bar for this purpose).

For true geographic searching, however (ie, where a visitor can specify “New York” or some other placename and find events taking place in that vicinity), you would really need Events Calendar PRO which ships with some pretty neat geolocation functionality for just that purpose.

Otherwise, a customization or smart use of categories as you are already doing is probably the best way to go 🙂

Does that help/clarify things at all?

[Author]

Posts