Maybe you'll want to use user-friendly interface for Roles
After activating Rules_ui that must be enabled with Rules (dependency), any user's profile does not open, the page is left blank. Trying to access the profile from the options appears this error below
Unexpected error while performing an AJAX call. Maybe the connection to the server is los
I did this on the test site
Iionly, I was able to upgrade without the above error. I deactivated the old user_support, and renamed it with another name. I put user_support updated and activated, all without leaving the administrator page.
I still took advantage of the old user_support language file, I had to do a few translations
thank you
I deleted this error but still have the one below, would you have a tip?
[Sat Dec 08 15:22:40 2018] [error] [client 2804:d41:4a96:dc00:b9ae:fd0e:a7f5:4e35] PHP WARNING: 2018-12-08 18:22:40 (-02): "gmdate() expects parameter 2 to be integer, array given" in file /home/dddrj/public_html/mod/celebrations/lib/celebrations_lib.php (line 20), referer: http://www.chocolate.com.br/admin
this line is 20:
https://es.wzm.me/products/view/75/t2 on my site works very good.
what is link your site? what is version your site elgg? thank you
Look at our eStore
thank You RvR
buy theme..kkk
Just changing the word friend_request in all plugin files would I be able to activate this second plugin?
Bad idea.
Just copy language file from 'another friend_request plugin' to 'friend_request plugin' instead.
E.g.:
from mod/another_friend_request/languages/pt_br.php
to mod/friend_request/languages/pt_br.php
In this case, you shouldn't install 'another friend_request plugin'.
Or create a new plugin (you can use My plugin also) and repeat above step:
from mod/another_friend_request/languages/pt_br.php
to mod/my_plugin/languages/pt_br.php
In this case, you should install my_plugin and move it at the bottom, after 'friend_request'.
It's not as simple as to just modify the language file if you want to make use of both the original friend_request plugin (more importantly: still keep the "friend" relationship in its original functionality in use) and a second "real_life_friends" plugin.
Even if you would only want to offer the "real_life_friends" functionality replacing the meaning of just a "friends" relationship you would also have to override some language strings of Elgg core that also handle the friends functionality because the friends_request plugin only adds some additional functionality and modifies existing functionality of Elgg core respectively.
If you would want to keep the original "friends" functionality unchanged (and also want to keep the friends_request plugin in use in parallel to your "real_life_friends" plugin) you could start with the friends_request plugin to create a clone. But in addition to changing the language file only you would also have to change for example the function names as they need to be unique. And you would have to introduce your own relationship (relationship name) as using the existing "friend" relationship would not work (and friend would be a "real_life_friend" if the relationship is handled by the same relationship name). As the friend_request plugin only adds some additional functionality (dealing with the creation and deletion of the friend relationship but nothing between), you most likely would have to clone/adjust some friend functionality of Elgg core, too (e.g. real_life_friend page, widgets etc.). It shouldn't be too difficult to get this done. It would just take some time. One point would be difficult though: access control. The friend relationship isn't just some "visual" thing (that would just show which user is friend with another user) but also is used as an access level to restrict access to content (or some functionality) to friends only. It would be much more complicated if "real_life_friends" should also have some specific access restrictions. If this is not intended and it's only meant to have some visual indication of who knows who beyond the scope of the site community it would make this much easier.
Thank you RvR e Iionly. I thought it was easier. It would have an easier plugin to change. As Iionly explained there is muta thing to be excluded from freind_request. This plugin would be cloned from friend_request but would be simpler. The user would only validate another user as real, already known.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.