pdp8user

I’ve been wondering the same. I expected it to go away after a period of time but it hasn’t.

Thanks to Helga for the heads-up, and for pushing the change through!

Just a note to others seeing this issue. There are many more plug-ins affected than those mentioned above. There’s a list on the WordPress Trac site.

But even that isn’t comprehensive, because some plug-ins are using out-of-date commercial libraries. I ended up doing a text search on .php files in plug-ins directory, looking for “wp_edit_nav_menu_walker” in order to find a rogue plug-in on one of my sites.

5.4.0.1 doesn’t fix it.
I looked more closely at the code of this one and can see the cause.

The issue arises in class-r34ics.php, in the case statement around lines 457-482, in both the 'list' and 'month' cases, where $first_date is given a value when $pastdays is non-empty. The gmmktime() function call computes the first date by counting back from the beginning of the month, not from “today”.

Change gmmktime(0,0,0,date('n'),-$pastdays,date('Y')) to gmmktime(0,0,0,date('n'),date('j')-$pastdays,date('Y')) and it fixes it:-)

Yep. That fixed it! Thanks for the very prompt service!!

It occurs on all three of "list", "month" and "week".

I’d be suspecting that the recent change to r34ics_boolean_check() has something to do with it, but I’m not up do diagnosing the subtleties – PHP is far from being my primary language:-)

Hi Matt,
Great initiative!
If by “Select user meta” you mean the ability to select which columns will be in the resultant CSV file then GREAT!!
Some of the meta fields can be VERY large (one is over 37kB in my data), and make they it hard to deal with the resultant CSV file. If they aren’t need in the export file, it would be a great help to prevent them from being exported in the first place:-)

Regards
Brian Marriott

Update to my previous reply about the Cherry framework:
Their tech support people recommended that I remove the masking of the JQuery version by editing the file “wp-content/themes/CherryFramework/includes/theme-scripts.php” to remove the references to “jquery” and “jquery-migrate”.
Commenting out that block of 5 lines fixed the problem cleanly!
Brian

Thanks, Nick, that helped.

It seems that my purchased theme was masking the WP version of JQuery (1.12.4) with a much older version (1.7.2).

I’ve been able to resolve the issue by replacing the file in the Cherry Framework directory with a copy of the JQuery 1.9.0, which I gather from another post is the minimum version that Simple Calendar can work with.
Unfortunately it is a very dirty fix – I had to rename the 1.9.0 file with the 1.7.2 title before the Cherry Framework would see it. Not nice:-(

The Cherry Framework being supplied with the theme is V3.1.5; the current Cherry is v5.0. I must say I’m not happy that template authors sell out-of-date software without informing prospective purchasers of the fact.

Brian Marriott

I’m having the same problem, too.
WP version is 4.7.3, which includes JQuery 1.12.4 and JQuery UI 1.11.4
Parent Theme is Cherry V3.1.5 with a child theme “theme52270” by TemplateMonster.
None of the code has been modified.

I’ve tried the JQuery updater plugin. Not only does it not resolve the issue but it breaks other aspects of my theme.

The Calendar is a List view using the Default calendar type to display a Google calendar.
No changes were made to the provided template.

The error occurs when you click on either of the forward or backward arrows in the “simcal-calendar-head’ div.

Otherwise, it’s a great plug-in!