since 2.4 upgrade, frontend users cannot publish

We upgraded from 1.9.1 to 2.4 and now the users who used to be able to create and publish an event now see this when they try to publish "You don't have permission to publish the event". These are registered users by the way with special privileges to create events. I only want them to be able to publish their own events - not publish and unpublish all events.

I have it set in Config to defualt publish events created.

How can I fix this? Thanks

Hi

There were some permission checking changes in the recent releases. At the moment, only users belong to groups have Edit State permission in Events Booking set to Allowed can publish their events

For your need, you can try to get this file, unzip it, upload it to components/com_eventbooking/helper folder of your site. It should work as expected

I changed the method canChangeEventStatus in that file to get it works as you want

Regards,

Tuan

I like this modification

yes, this should be default. I'd also like to ask that notification emails go to the event owner and not the default website email. And lastly, the reply-to email on the user emails go to the event owner as well.

Not sure if this is a default behavior. What if you want to allow users to submit events, but want to approve it before the event being published on your site? In that case, users should not be allowed to change status (publish / unpublish) event

Tuan

Maybe best solution would be to have another config option "Can change state of own events"? Like it's with editing now ?
Currently when I gave right to publish event for one users group they are able to publish/unpublish all events and not only theirs.

@thepiston If I remember correctly notification and replay to emails are sent to event owner since 2.3.0. Personally I do not use this feature so I've ask team to customize code for me to send notification only to admin.

Regards,
Wirex

I have had to pay extra for custom code to allow for these notification emails ever since about v1.6 so my site would work how my client wants it. For that reason I tried not to update very often since I would lose those hacks. My admin doesn't want to get notifications about the events of 11 other people. And, when registrants replied to their confirmation emails (to ask questions about event for example) my admin would get all of those instead of the event owner - so I had them set the reply-to email in confirmation emails to event owner's email.