In Elgg 3 the normalization of the metadata/metastring table was removed. This will help in speeding up those kind of queries. Time to update ;) view reply

if you draw a 'widget' layout (like done in https://github.com/Elgg/Elgg/blob/a836dda6e17954f8825c728d69b6113e38a01332/mod/dashboard/views/default/resources/dashboard.php#L5-L11) the function 'elgg_can_edit_widget_layout()' is called... view reply

Elgg 3.x isn't compatible with PHP 8. You'll have to wait until Elgg 4 is released, that has support for PHP 8 view reply

I think the best bet is that a subfolder of the data path isn't writable. Have you tried Nikolai's with `chown -R` suggestion? Permissions of 750 should be enough. Maybe have a look at... view reply

there is a function `has_access_to_entity()` https://github.com/Elgg/Elgg/blob/70c2f4535af7b67b690617ebeba74fc59a2b55d2/engine/lib/access.php#L93-L114 view reply

I think your issue has more to do with the migration from 2.3 to 3.3 than with the switch of the DB. The 2.3 site was working? Maybe just to be sure you could regen the site secret on 2.3 before trying the upgrade again? PS: MariaDB isn't... view reply

from within core there are 2 events bound to each action first is the 'action:validate' '<actionname>' (eg. blog/save) hook which is triggered before the action is handled second is the 'response'... view reply

depending on the design of the plugin and privacy issue maybe you could look into making the objects owned/contained by the Site. The site is never removed. Sometimes this can be a solution. The prevent deletion hook is an option. Keep in mind... view reply