Recurring events on first monday of the month

Join the club! There are several of us with the same problem. Despite being very active on the forum the past two days and a post two weeks ago saying he couldn’t replicate it – zilch! Getting to be a real problem for me as all my recurring events will expire before very long and need to be extended / recreated which will mean none of them will be correct. Most of my events are like this. Very frustrating.

Honestly, I can’t imagine how frustrating it is to provide a complex, FREE plugin …and receive complaints in return.

You’re right Of course. Apologies.

Hi Bart,

I tested it on my system (Dutch) which is working fine.
It gives me the following dates
6 august
3 september
1 october
5 november
3 december
So it appears to me that the problem is not within event manager
It must have something to do either with WordPress version (mine 4.9.7)
Or with some setting in event manager
use timezone = Yes
timezone =Amsterdam
Default country = Holland

Wordpress general
Timezone = Amsterdam
Date notation = 21 juli 2018
time notation = 23.00 e.g. 24 hour clock
Week starts at Monday <– perhaps you have to check this one !!

I have tried your suggestions to no avail. As someone else suggested I looked in the database and find that the fields aren’t being filled – recurrence, incidence, days, frequency etc all blank whereas the older entries are and the date is set to the first of the month.

I’ve turned timezones on / off. Changed the zone from London / GMT / UTC+1 etc and no difference at all. Date & time notations too and start day although it’s a church so Sunday as the first day is pretty non-negotiable!

Hi Patsky,

Although it is still not working, you give the developer information that should help find the root of the problem. If fields are not populated then he can look for the reason why they are not populated. If that happens between releases, it could be that the definition of the fields have been changed, and the database driver cannot update the fields. Another possibillity could be that the variables used during entering, are no longer present or handed over to the database handler. Maybe putting wordpress in debug mode reveales the reason.

One remark to the input mask for reoccurring events. There is a field every “xx” month on the first monday of each month. What is the use of the “xx” field ??. I left it empty and i got no warning. The record was stored properly.

Thanks for you continued input. As far as I know the recurring field is the interval between recurrences e.g. 1 for every month, 2 for every second month etc.

To give more detailed information on the difference in fields from earlier records and newly created I created a new recurring event to match an existing one that occurs every month on the 4th Sunday of the month 0 being Sunday as per General WordPress Settings

PRE-EXISTING RECORDS

Recurring event record:
Recurrence: 1
Recurrence interval: 1
recurrence frequency: monthly
recurrence byday: 0
recurrence by week no: 4
recurrences days: 0

Each recurring instance record:
As above with the exception:
Recurrence: 0

NEWLY CREATED RECORDS

Recurring event record:
Same as above

Each recurring instance record:
Recurrence: 0 (same as existing records)
Remaining fields are all blank

All dates ignore the recurring event entries and are always for the first of the month. Event slug for each appends the first of the month.

Other observations:
Weekly recurring events are correctly listed but also have the same blank fields so turns out this is not significant. Dates are correct and the event slug appends correctly scheduled dates.

So at a complete loss as to where to go next with this.

@Peter_Smits,
I tried your settings and i still get only first of the month in stead of first monday of the month. Very frustrating ??

• This reply was modified 6 years, 4 months ago by bartvandermark.
• This reply was modified 6 years, 4 months ago by bartvandermark.
• This reply was modified 6 years, 4 months ago by bartvandermark.

Hi patsky

Thanks for the information
I think now the developer knows where to look.
Because it appears to me that for some reason the system does not calculate the date properly.
Do you know on which os your system is running?
E.g. windows or Linux.
And which version of PHP the system is using ?
Maybe your site template is destroying information.
I use VANTAGE as template, and that is working fine.
I cannot show you that it is working as I am testing the plugin on a offline site.

Hi Bart,

I can imagine that also because on my Dutch system it is working.
I proposed to patsky to try it with a different template.
Maybe that is something you could try also.
And also check your environment, because we can compare that to see if there is a difference.

Bart /patsky

which version of event manager are you using ??

I use 5.9.5

I am also on latest wordpress

• This reply was modified 6 years, 4 months ago by bartvandermark.

I have it on 2 sites. Both latest WordPress. One is version 5.9.3, the other is 5.9.5. Both have the same problem.

hi patsky/Bart

I am using 5.9.5 and with me it is working properly
In general settings you have an option “performance improvement”
Within this setting you have an option “limit loading js”
I have set this to “No”, so the event manager uses js where it feels necessary

patsky do you know which version worked properly before ?
Obviously is was already wrong with 5.9.3, so from wich version the problems started?
In that way you can narrow down the problem, even maybe go back to the proper working release.

I have the same problem. All recurring events (for example first wednesday of the month) instead show on 1st day of each month.

This error shows in debug log if I add a recurring event with debug on:

[02-Aug-2018 14:48:29 UTC] PHP Notice: Undefined index: start_days in /home/——/public_html/wp-content/plugins/events-manager/templates/forms/event/bookings-ticket-form.php on line 47

Events Manager has been working fine on this site for years. Problem started some time in the past year. Hard to know when as we only discovered it more recently when adding new recurrences. The older recurring events are working correctly so it seems to be related to saving new events as the originator of this thread observed.