!! DEVELOPERS ONLY - DO NOT USE IT IN A PRODUCTION ENVIRONMENT !!
This is just a showcase trying to
@Pariter
What exactly is your problem with following the View Repository link?
@Maurice
When can this be used in production ?
Wanted to do some investigatory work on this item, I don't see it posted for Download. I have a need for something such as this, and would like to see the work you have demonstrated as I learn more about developing components. Thanks!
@MAURICE TAYLOR Hi Maurice, i think OSSN is very modular and is good, with that make the OSSN itself very stable, imagine that the other components are the arms or legs of Ossn, if you want a shoe for the foot, it will improve, but you need to verify the size first to wear that.
This is why components needs first testing and then it will usable in a normal production environment.
I'm not a coder, but i'm infraestructure specialist, my knowledge are referenced to servers, active directory and those things.
But i can understand some language codes, i'm having a lot of interest for php, its seems very enjoyable to learn and experimenting, i tried Ruby and Python in the past, but php its like interesting candy.
I suggest you to try first with Hello World component, try to modify a bit and add things, try to learn from other components and found interesting ways to add functions to your site, from a simple link or menu to a widget or something.
Also .css is very easy if you use the browser inspector with the navigator, you can modify colors and things in real time.
This is fascinating to read and learn, although I'm a newbie and now very little, I have an appreciation for the knowledge you all have. What I think I'm noticing is that coding as to do with having components which is a group of functions that take some action based on the needs of the component. Is that right?
Hi Michael, i added those pulls to my test vm and all working fine, i noticed that now the groups component is responsive and agile.
Also i changed the line ossn_group_load_event
All working normal.
Hello Hugo,
I did some more changes on the Group's class,
see my latest pulls on https://github.com/opensource-socialnetwork/opensource-socialnetwork/pulls
Addtionally you may change that line in ossn_group_load_event
to
if ($group->owner_guid == ossn_loggedin_user()->guid || ossn_isAdminLoggedin() || $group->isModerator(ossn_loggedin_user()->guid)) {
This would give a static "Requests" tab on one hand, but avoids counting of requests twice
@Michael
I tested with the two files updated, no more slowdowns, 2-3s of loading in the group or the member list. Admin, moderator or random user.
Very nice!
Hi Hugo,
I have just made 2 pull requests which should speed up things a bit ... hopefully :)
https://github.com/opensource-socialnetwork/opensource-socialnetwork/pull/2067/commits/7abf77e3c2e46e7975b015d7fa5e93b6047d3c58
https://github.com/opensource-socialnetwork/opensource-socialnetwork/pull/2068/commits/8430b1c5f1268df27c4efa73dedbb9928b6e597c
Please give them a try.
Hi Michael,
I made a new test from scratch. I didnt installed the component (Profile and group notifier)
I have this slowdown when browsing with the member list too. Also i opened a new tab with the backend administrator, if the first tab is loading (front end), the second tab too (backend), its seems cpu or database busy.
I installed group moderators component and picked a random member (User27823) now is moderator.
user27823 (moderator) :
Time wait to view the group: 48s
Time wait to view member list: 24s
Time wait to change page (/group/1/members?offset=5000 or random page number) : 24
user16741 (non-moderator) :
Time wait to view the group: 24s
Time wait to view member list: 24s
Time wait to change page (/group/1/members?offset=5000 or random page number) : 24.
Also, lets say if i want to make "John Doe" a moderator, but i dont know in what number page of the member list he is.
I think Groups component needs a improvement, but how.
Removing the member list will be fix that? but the admin or moderator can't access to the list after that.
Here is a idea: a search bar to find members and only showing the last 10 members in the list. If you want to see more members, the page loads (like when scrolling through /home).
So the concept will help to minimize the group component loading or fetching the cpu or sql database when entering to see the group or member list, probably?
If i'm not mistaken, i'm thinking canModerate or something is making the cpu/sql fetch heavy.