Event Location not working

About how many locations do you have? Are you on the latest release of My Calendar?

A lot of locations, like 150. The site is for a radio station.

Yes, it’s up to date.

It looks like you’re getting a 404 for the autocomplete script itself; at first I thought it was an error when running the script, but the script is coming up not found. Can you verify whether the file exists on your server? It would be at /wp-content/my-calendar/js/accessible-autocomplet.min.js

If it’s there, then this might be some kind of file permissions there. If it’s missing, then I’d recommend re-installing; you seem to be missing at least one file, and could be missing others.

Hmm, I don’t see this file in SFTP.

If I replace the plugin will the client’s events all disappear or are they saved in the database?

All events are saved in the database; you won’t lose anything by replacing.

If you uninstall, you’ll want to make sure the options for behavior on uninstall are set the way you want them (Settings > General), but if you simply upload a new copy via SFTP, you definitely won’t lose anything.

The one caveat is that if you’ve customized your style in the style editor, you’ll want to skip uploading the /styles/ directory.

Thanks! I’ll do this for them shortly and report back how it went.

Okay, I uninstalled and reinstalled the plugin, but the Locations dropdown still doesn’t list any locations.

I’ve deactivated all other plugins and switched themes looking for a conflict, nothing found. Anything else we should try before we switch to another calendar plugin?

I also tried (with all other plugins disabled and a default WP theme) uploading the latest version of My Calendar to replace the plugin. No change to the Location field, still nothing happens when typing there and the same error is in the console.

After reinstalling, is the console error the same, or is it a different error?

Exactly the same error.

So, this turned out to be a version control error that caused you to get the wrong set of files. Just released an update that should resolve this.

Yep, now it’s working. Thanks.