nice thought machi

So this is basically an updated version of this: http://community.elgg.org/plugins/385010/1.8f/messages-with-privacy-option-more ? Or is it totally different?

@krischan yeah.... Its updated version of  http://community.elgg.org/plugins/385010/1.8f/messages-with-privacy-option-more

It does support message attachments(files)

hi,

i installed the plugin, but it doent change nothing to the original ... I disable / enable, clean cach but nothing new appear :/

It's the same setting panel as Messages plugin. 

I did something wrong ?

@mecha31

if you override default messages plugin,,it will be work

is this really ajaxed?

@moneya

Yes!!!!!!!

@juniorhallak

nope....not override the_river....

Well, my plugins are open source - but a little credit might be nice :-)

:-) it is good to know you are around slyhne! You have top plugins!

One of the projects I manage added this plugin - it instantly goes out of memory on all pages except for admin context.  Something in here is not scalable.

Additionally, it's not a good idea to overwrite core plugins like that.  Now when I have to upgrade Elgg I have to make sure this plugin is not overwritten by the core plugin again, or track changes, or whatever.  Either way it's overhead nobody really needs and will create headaches.  It would be better to create a helper plugin that modifies the existing messages behaviour, or at the very least create the plugin with a different plugin id and declare in the manifest that it's not compatible with the core messages plugin.

I need to sort out this OOM issue so I'll let you know what I find.

Found it, you are using a *very bad* method of counting unread messages.  You are attempting to get them all from the database (using limit => false in the options) with egef_metadata and returning the size of the array.  This means if someone has 600 unread messages you're trying to load all 600 entities into memory in order to get a count.

Nice plugin.

But I found a little problem with my installation which is hosted with using a ssl-proxy.

For the pagination you set the base url by grapping a system-variable. In my installation this leads to doubling some part of the path and doesn't work.

It looks like that setting the base url is not necessary in this case because the pagination-routine figure it out it self.  After comment the base_url setting out all works fine.

$pagination = elgg_view('navigation/pagination',array(
//                        'base_url' => $_SERVER['REQUEST_URI'],
                        'offset' => $vars['offset'],
                        'count' => $vars['count'],
                        'limit' => $vars['limit'],
                        ));

What to put it into github but it is no code there! :-(