lpint

I have reinstalled version 3.5. While I’m waiting for a fix for this, how do I disable auto-updates?

Thank you for your always GREAT support!

Okay … I disabled PublishPress Future. I then moved the 8 events (10 Minute Play festival – May 30, 31, June 1, 2, 6, 7, 8 & 9) to trash. I recreated the events using “custom dates”. The 8 events (all starting at 7:30) were created, but only the first event (May 30) was published. The other 7 events were still in “draft” status. I quick edited the Thursday, Friday and Saturday events to “published” status. I also edited the two Sunday events to change the start time to 2:00 and published them. Everything seems to be appearing in the calendar now.

Next with Future still deactivated, I created a new event for May 30 and told it to repeat until June 9th and clicked “publish”. All events were created (but, again, only the first event was actually published, the others were created in “draft” status). I used quick edit on all the draft events to publish them. They all showed up in the calendar. I then went and moved the three events on Monday, Tuesday and Wednesday, (June 3,4 & 5) to trash. All the remaining events still showed in the calendar. I deleted all my test events.

Next I re-activated Future and ran the same test again. Now, with Future activated, I set the future action to “delete’ on June 9 at 9:00 pm. On clicking “publish”, the expected events were all created. (Again, only the first one in “published” status, the rest in “draft” status.) After changing each event to published, all appear in the calendar. After moving June 3, 4 & 5 to trash, the remaining events all still appear in the calendar.

One of the things I did not do in my testing is that normally I create the events with a start time of the night-time performances and then edit the start time of the Sunday matinees. I did not manually change the start time for any event while testing.

I am dumbfounded (even more than normal) as to why the original events were not all displaying on the calendar.

As an aside … one advantage of all repeat events, other than the original event, coming up in draft status is that I can publish them in event date order, which causes them to be displayed in the admin screen in event date order rather that the “random’ order they were originally created in. But it’s still a lot of extra work.

I think this has been an issue since I started using Eventprime almost a year ago. All other add new functions work fine (venues, performers, events, event types, etc).

I suspect it is something with my setup, since no one else has reported the issue. I suspect it may be an interaction with PublishPress Future Free that I am also using. I will try deactivating PublishPress Future and do some additional testing.

I found a log file named “error_log_mn-act_net”. (mn-act.net is my domain name) The only errors in there seem to be cron errors (“The cron event list could not be saved.”), mostly from the newsletter plugin. I see nothing that mentions eventprime.

I hate to show my ignorance, but … where do I go to see the error log that you want a screenshot of?

Sorry bout that! Try this one instead

Here’s the screenshot of the repeat settings. I use several different methods to do repeated events. Mostly it’s custom dates. In this case I used repeat until a date and then deleted the individual events for dates that were not needed.

This is fixed in 3.4.6. Thank you.

I just updated to version 3.4.5 and the issue still exists. Month calendar view still shows “February, 2024 – March, 2024”.

This issue is still not resolved as of release 3.4.4.

I have deactivated the PublishPress Future plugin and done additional testing.

I created a new event for 6/4/24 and set it to custom dates repeat 6/6/24, 6/11/24, 6/13/24, 6/18/24 and 6/20/24. I then clicked on “publish”. Going back to the all events list, all 6 events were created, but only the original one (6/4/24) was published. The 5 repeat events were all in draft status.

Next I chose to edit the original event for the series (6/4/24). I changed something (in this case the start time) and clicked “update”. I chose “for all occurrences” and clicked “submit”. The all events list now only included the original (6/4/24) event. The repeat events were deleted and not recreated. (I have not tested all repeat types, but I did test ‘days” repeat type for 4 additional occurrences and that seemed to work, so it may just be the custom dates type that has this problem.)

I then chose to edit the original (now single) single event. On checking the repeat tab, custom dates is still selected but there are no custom dates listed. I next add the repeat dates, as above, back in. After clicking “update” the all events list shows all 6 events and all are published.

Hope this helps.

• This reply was modified 10 months, 2 weeks ago by lpint. Reason: update from additional testing

Thanks for the reply. I should have tried your suggestion before contacting you. Even with the PublishPress Future plugin deactivated, the same problems exist. So it obviously has nothing to do with Future. Sorry for not testing further before contacting you. Thank you for your help and for a great plugin.

As of the 3.3.9 version this is still not working as expected.

FYI: I am now using PublishPress Future to handle this for me. It, for the most part, is working. There do seem to be some interaction problems between PublishPress Future and EventPrime. I think the combination of the two is causing a couple of the problems I am having.

The first is the issue of repeated events (using custom dates, at least) being created in draft status. I’m pretty sure that’s some bad interaction between the two plugins.

The second issue is that when I try to edit an event series, two improper things happen. First is that, even though the repeat events custom dates are shown in the repeat tab, The original event is the only one that get recreated. The repeat events are deleted (as normal) bu then not recreated. If I go back into the original event again, there are now no repeat custom dates. It I add the dates back in and update, all events are created as expected.