Wrong 'edit' link in Event Categories list

This doesn’t happen on WP 4.3.1.

I have been monitoring this thread for a couple days, and since no one had replied I just wanted to say that I have this exact same issue. I was hoping version 4.0.2 would clear this up, but it did not.

Click to view screenshot

I am able to successfully edit a category when using this method, as described above:

If I click on the “view” link instead, and then on “Edit Event Category” in the upper black bar, it works fine, and the url is like:

https://localhost/diva/wp-admin/edit-tags.php?action=edit&taxonomy=tribe_events_cat&tag_ID=4&post_type=tribe_events

I wanted to make sure that the plugin developers saw this thread, as one of their stated goals of this forum is to find bugs.

Update: I see that the plugin authors are aware of this issue, based off of their comments over on their support forum:

Link to forum thread

Thanks for your question.

Please make sure you’re using the latest version of our plugin (v4.0.2) and WordPress (4.4) and follow our testing for conflicts guide:

https://theeventscalendar.com/knowledgebase/testing-for-conflicts/

and see if that helps narrow down the cause of this.

Let us know what you find out.

Thanks.

I am using WordPress 4.4 and had the problem before upgrading to the latest version of The Event Calendar (4.0.2). I followed your testing conflicts steps and the problem persists even with only TwentyThirteen theme and only v4.0.2 of The Events Calendar plug-in.

That’s right, I opened this thread stating that I had just upgraded the plugin to the latest version, but I had also upgraded WordPress.

Prior to WP 4.4 there was no ‘wp_http_referer’ variable in the edit url of categories and taxonomies, now they added it, and this, for some reason, broke the edit url of The Event Calendar’s custom taxonomy.

Thank Eric for linking the forum thread on theeventscalendar.com, I don’t know why I didn’t look there before posting, sorry.

Anyway, the problem is that the ‘&’ character before the ‘taxonomy’ variable is erroneously encoded, thus causing the variable name to become part of the ‘wp_http_referer’ value.
Why this happens is really puzzling me…

This issue appears to have been fixed in 4.0.3. Thanks!

Hey Folks,

Sorry for the inconvenience this might have caused to you all. As Eric points out this was fixed in release 4.0.3, so please update and let us know if there are still issues with it.

Thanks for the patience!
Best,
Nico