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

A bugfix release for Elgg 3.3 is now available

There is get_subtype_id() which is similar to elgg_get_metastring_id(), no similar way for elgg_get_metastring_map() PS: please try updating to Elgg 3.3 then you don't have to worry about subtype id's and metastring id's view reply

@John.iwt Unfortunately, I need to use Elgg 2.3 because is the version implemented for my solution, and I am not thinking of migrating to Elgg 3 yet I am afraid. Please check if you can't upgrade to Elgg 3.x soon because hopefully... view reply

if your coming from 1.8.3 you need to take this long way 1.8.20 1.9.7 1.10.6 1.11.6 1.12.17 2.3.16 3.3.15 Also have a look at http://learn.elgg.org/en/stable/admin/upgrading.html view reply

Ah OK, here we go ;) In the action that follows the button click: $user_file = new ElggFile(); $user_file->owner_guid =... view reply

With the default ElggFile this isn't possible, you could make an extension of the ElggFile in your plugin and overrule the function getFilestore();... view reply

@Vangardis please keep in mind http://learn.elgg.org/en/stable/guides/dont-modify-core.html If you modify files directly in Elgg core those modification will be lost when you update. You can make a plugin with the modifications you need that way... view reply