Look at get_members_of_access_collection()

thanks :)

@Jaqueline  Actually the developer of the plugin does not require his authorisation for changes to his plugins. Sources are there in Github and open source. Anyone can take and change them.

It is just that, when you modify one of his plugins, developer expects you to make the modifications available free of charge back to public domain, just like the original one was. This is quite a reasonable request.

Actually most open source licenses require the same thing. We owe this to Apple/Steve Jobs. Because they took the open source Unix from public domain, modified it, renamed it as "Mac OS" and started selling it for profit without giving back anything to public domain. To prevent further such thefts, license terms were modified some years ago.

As for the posting widget, the available tools from Elgg  are not anywhere near what social media users (of LinkedIn, twitter etc) are used to. Elgg way of posting often looks like mimicking menu options. E.g. when you choose photo upload, actually you are seeing a file upload form or photo upload form etc. This is not what users are used to.

Users are used to LinkedIn or Twitter, where they write a text, enter a URL and it is rendered automatically or they upload a photo and it displays nicely with the text. I know that these companies have deep pockets but user does not care.

A relatively recent yet-another-social-network-software HumHub does it nicely (BTW, this is the only good thing it does. Elgg beats HumHub in every other aspect):

https://imgur.com/wbn0lLb

So far, the posting widget I liked most, was of an Argentinian company called Keetup. As far as I know, they left Elgg dev. And it was only marginally better and nowhere near what HumHub etc does.

All of these discussions make me feel like a villain. I will waste more energy trying to explain to people that my time costs money than just let you have it free. In this light, I have opened up most plugins for free downloads. You are welcome to become a Patron and support the development by subscribing, otherwise just download the plugins and stop making all the noise. Cheers.

Might be that mod_rewrite is not enabled on the server or that AllowOverride is not set to All in Apache's config. I don't know what else might be causing the problem.

I've been working on upgrading my site from elgg2.3.7 to 3.0.3 as well and this is what I learned so far. 

elgg_register_library is removed from elgg3.*. What I did with my plugins was using the word 'require' or 'require_once' inside init function in the start.php file of my plugin. Below is the example:

require elgg_get_plugins_path( ) . 'plugin_name/lib/library_name.php'; 

Read more here http://learn.elgg.org/en/stable/appendix/upgrade-notes/2.x-to-3.0.html?highlight=elgg_register_library

+1

Or move your code from library to start.php or classes

Let's say you have a library at mod/my_plugin/lib/my_lib.php. Then you can load it with the line

require_once(dirname(__FILE__) . '/lib/my_lib.php');

when adding this line at the top of start.php (not inside the init function). This is the easiest way if you don't want to use elgg_register/load_lib anymore (works not only on Elgg 3 but also on Elgg 2). The other way would be to rewrite the code to create a class from the library. But this requires more effort for sure.

Change your site URL: Administration -> Settings -> Advanced settings.

Maybe, you need to change something in your server's configs (e.g. htaccess if you're use Apache: 1, 2).

Read this also.

Mixed Content Blocked is due to loading of http content on a https site. You http can be an external js file, external css file, external image file etc.

What you can do is, study the source code of the page in which you are getting the error.

Press Ctrl + U (this shortcut is for chrome) on the page to view the html source code and look for the string " http:// " (without quotes). Those are the files that might be causing the error.

Now there might be a scenario where the url will look like this -> src="//someurl.com". These type of external url also cause mixed content blocked error.