Hey there,

Can you include your FTP's access by editing your first post so that I can have a better check and troubleshoot on your site?

When I was trying to access your EasySocial component from the backend, it gave me this following error:

Error

You are not authorised to view this resource.

Can you update this account that you provided to Super User privilege so that I can have a proper check on your site?

Hello,

I have updated the access in site details. This is an administrator, not a super user.

If not sufficient, please send me the tables / settings to be checked.

Kind regards
Andre

Hey there,

Can you update your FTP's access so that I can troubleshoot it for you?

Hello,

I have updated the access page.
The user is an administrator. If you need access to tables, please send a request and I will extract the data.

By the way, I have another ticket open, which deals with a similar error: New conversation without ACL creates a white page...

Kind regards
Andre

It seems like this 'Fadhli' user account doesn't have Superadmin privileges, so i was unable to access your site backend global configuration setting and Easysocial setting page, you can check at my attached screenshot below.

By the way, if you urgent to fix this issue, you can try switch your event description editor from your site backend > Easyblog > setting > event > layout > Default Editor For Event Descriptions and see how it goes.

It might be one of the editor on your site caused this issue.

Hi Arlex,

This is the solution. The default editor was set to CodeMirror (no clue, why).
The correction is in ES, not EB. :-)
backend > EasySocial > setting > event > layout > Default Editor For Event Descriptions

After change to TinyMCE, the function was available.

Nevertheless, the program should capture this problem and display a warning message instead of a white screen.
I will close this ticket.

Thank you.
Andre

Yes, it should show the error but i think you have set your site error reporting to none, this is why it doesn't show the error on the page. If next time hitting this kind of similar issue, you can set error reporting to maximum, then refresh the page and view page source, i believe it will show some error message.

By the way, thanks for getting back to us your issue resolved.

Just for your information, I have locked and marked this thread as resolved to avoid confusions in the future. Please start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiries.

Thanks for understanding