Javascript Errors

We were running v 2.3.8 but our Google Calendar feed stopped updating. Going to the Events > Import Feeds page and clicking on Refresh for a particular feed resulted in the following JavaScript error:

POST /wp-admin/[object%20Object] HTTP/1.1
Host: mydomain.com
Connection: keep-alive
Content-Length: 32
Accept: application/json, text/javascript, */*; q=0.01
Origin: http://mydomain.com
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Referer: http://mydomain.com/wp-admin/edit.php?post_type=ai1ec_event&page=all-in-one-event-calendar-feeds
Accept-Encoding: gzip, deflate
Accept-Language: en-US,en;q=0.8

HTTP/1.1 404 Not Found
Server: nginx
Date: Wed, 31 Aug 2016 21:00:25 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Keep-Alive: timeout=20
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Link: <http://mydomain.com/wp-json/&gt;; rel=”https://api.w.org/&#8221;
Content-Encoding: gzip

We also wanted to add new event categories, but the Events > Organize page produces similar error messages.

Thinking that the [object%20Object] might be a result of the current plugin not working with our version of WordPress (we’re on 4.5.3), we decided to see if there was an update available for the Time.ly plugin.

The plugin said that update 2.3.12 was available, but WordPress was unable to update because the file was not found. So we logged in to time.ly and saw that the latest version was really 2.5.10. (Not sure why WordPress wasn’t aware of this version.) We now have 2.5.10 installed. Time.ly now requires that we login via the Settings page, so we created a time.ly account and are now waiting for feeds to be activated (at this time, they seem to now be pulling in correctly).

However, we are still unable to create new event categories. The same 404 error occurs because the javascript is still requesting a Url with [objet%20Object] in the path.