[Plugin: The Events Calendar] Month/Year Drop-down Menu leads to “Page Not Found” error

I am having the same problem with my calendar as well: https://mycitysf.com/calendar/category/events/?eventDisplay=month

Otherwise a great plugin!

Same here!
https://downescreditongc.co.uk/index/category/events/?eventDisplay=month

None of the dropdown options work but you can go next/previous without any issue.

Pretty URLs don’t work either but that’s not as important.

James

Was any solution discovered for this?

Really important I fix this!

@makspot
I followed your link and your site seems to not have this problem anymore. Did you learn how to fix it?

@frognip and @jamblo
I’ve confirmed yours are busted. I’m a broken record on the updating issue, but nonetheless, make sure you’re either using 1.6.3 with WP 3.0 or 1.5.6 with WP 2.9.2. Also, both of your sites seems to be on default Permalink settings. Is this true?

Thanks for replying.

I am using version WP 3.0 and version 1.6.3 of the plugin.
I’ve had to turn pretty links off as that always results in a 404.

The permalink setting I am using is /%postname%/

Is there anything I can do to fix this issue?

Please try change below two lines on \views\datepicker.php

———- 1 ————————–
$link .= ‘&eventDisplay=month&eventDate=’;

change to >>>>

$link .= ‘?eventDate=’;

———- 2 ————————–
location.href = ‘<?php echo $link; ?>’ + jQuery(‘#<?php echo $prefix; ?>events-year’).val() + ‘-‘ + jQuery(‘#<?php echo $prefix; ?>events-month’).val();

change to >>>>

location.href = ‘<?php echo $link; ?>’ + jQuery(‘#<?php echo $prefix; ?>events-year’).val() + ‘-‘ + jQuery(‘#<?php echo $prefix; ?>events-month’).val() + ‘&eventDisplay=month’;

@jeffvfren

Brilliant, worked a treat!

Thanks very much!

Thanks jeffvfren! Works perfectly now!

Thank you jeffvfren, that worked perfectly.

Awesome! Thanks jeffvfren!

Excellent, this fix worked for me too. Jeffvfren is a legend.

Fantastic! This did the trick. Works great now. Thank you!

This broke with the most recent update of WordPress or it may be version 1.6.5. I had to find an older version I had backed up at 1.6.4 for this to work again. The plugin developer should really find a fix for this.