Can't remove event or unpublish
By craigmc911 on Friday, 21 September 2018
Posted in JEvents (Free Access)
Replies 7
Likes 0
Views 1.8K
Votes 0
In JEvents Manage Events if I try to delete an event I get the following error "870 -It was not possible to delete this event" I also get "403 You are not authorised to view this resource/perform this task. 1" if I try to publish/unpublish an event. I am logged in as super user.
Permissions
*Admin User - Admin
*Enable User Authorization - yes
*Publish own -Yes

Version : 3.4.48 Stable Joomla 3.8.12
Hello,

You have set 'Enable User Authorisation - Yes' so you would need to add yourself to JEvents -> Authorised Users. We tend to advise disabling this and using the Joomla! ACL.

Many thanks
Tony
tonyp
·
Friday, 21 September 2018 23:57
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you for your quick reply Tony! I did change to the ACL. The issue seems now to only be with some unpublished events from 2017. Still get "870 -It was not possible to delete this event". The 2018 events are all okay.
craigmc911
·
Saturday, 22 September 2018 14:15
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

Great. So 870 usually means a calendar error, if you edit the event set it to a new calendar and then delete does it work?

Many thanks
Tony
tonyp
·
Monday, 24 September 2018 08:26
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks!
This is what I get if I try and change the event calendar:
An error has occurred.
403 You are not authorised to view this resource/perform this task.
I get this message if I try any changes to the event.
craigmc911
·
Monday, 24 September 2018 13:56
·
0 Likes
·
0 Votes
·
0 Comments
·
Ok, so for now disable the JEvents Authorised User Mode in: JEvents -> Configration -> Permissions and try again.

Many thanks
Tony
tonyp
·
Thursday, 27 September 2018 00:12
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for you replies. Still doesn't work. I will maybe just delete the items from the database
craigmc911
·
Thursday, 27 September 2018 15:09
·
0 Likes
·
0 Votes
·
0 Comments
·
It sounds like they could be partially corrupt. A quick fix would be to delete them from the database.

Many thanks
Tony
tonyp
·
Sunday, 30 September 2018 09:25
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post