Coming soon.

Elgg HybridAuth already supports Mastodon authorization

From docs:

"If deleting recursively, this bypasses ownership of items contained by the entity.  
That means that if the container_guid = $this->guid, the item will be deleted regardless of who owns it."

Look at this.

An example of how to do this in your class.

If you want to look at the code

https://github.com/Elgg/Elgg/blob/b7b6827e6aa3374670414bb9838d4d39e9a9fd4a/engine/classes/Elgg/Database/EntityTable.php#L561-L563

and

https://github.com/Elgg/Elgg/blob/b7b6827e6aa3374670414bb9838d4d39e9a9fd4a/engine/classes/Elgg/Database/EntityTable.php#L584

Developer is here.

custom_index isn't compatible with Elgg Landing Theme.

You can find a warning about this in the plugin description.

Discussed already.

Please ask your questions on the plugin page in the future.

This error occurs when the host in your /elgg-config/settings.php is different from the host in PHP.

This is done to help prevent malicious link generation.

https://github.com/Elgg/Elgg/blob/b7b6827e6aa3374670414bb9838d4d39e9a9fd4a/engine/classes/Elgg/Http/Request.php#L466-L478

@Jerome Bakker, thanks for the detailed insight.

I found the solution to it by properly defining the SSL/https rewrite request in .htaccess as bellow:

#First redirect all Http request to https
#Ensure that we exclude any sub-domains

RewriteCond %{HTTP_HOST} ^(www\.)?myhotfb.com$ [NC]
RewriteCond %{HTTPS} off
RewriteRule ^ https://www.myhotfb.com%{REQUEST_URI} [NC,L,R]

#Secondly redirect all non-www to www

RewriteCond %{HTTPS} on
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [NC,L,R]