Hi, just to know what version of wordpress are you using?In any case, referring to what your host said, they are right that it’s an error in our plugin, but it’s not the has_cap error. You have two things:
<strong>Notice</strong>: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /usr/www/virtual/xxxxx/www.xxxxxxxxxx.com/wp-includes/functions.php on line 3318
and
<strong>Fatal error</strong>: Call to a member function render() on a non-object in /usr/www/virtual/xxxxx/www.xxxxxxxxx.com/wp-content/plugins/all-in-one-event-calendar/vendor/twig/Environment.php on line 300
I doubt that the notice is generated by us, as the notice happens when a plugin calls has_cap passing a number ( pre 2.0 authentication ). I took a look at our code base and we only pass string like we should ( look at the photo https://take.ms/iHogR ).
What is really causing the failure is the Fatal error and not the Notice as in PHP notices do not stop the execution of the script.
If we were the cause of the notice, i would be more than happy to fix it, but i think we are not. We cause the fatal error and i explained above how that could happen, it seems that a method is called on a non object during the rendering of a Twig template. Unfortunately not being able to reproduce this makes it a little more difficult for us to debug. Could you ask your host for the full backtrace of the Fatal Error?