You didn't really answer my question. Why do they need to be represented as a group? What is the reason why they can't be regular elgg users and post content to a regular group that they are members of?

How about creating a single user account called "Group X" that they all can use with the same password? Is there something that prevents this?

I'm just trying to see the bigger picture behind your idea.

Ah ok. Your question had something different in mind. The thing is that our project wants to increase the social experience when staying together (at one place) and using a social platform like elgg. It's kind of innovative work we are doing to seperate from so many other social networks like Facebook where there is no real social perspective as dynamic group which changes every time.

It's not about a static group. You must create these groups/sessions instantly, dynamically and on demand depending on who is being together. Other people shall see that you are with your friends or your family at a certain time. So i'm sorry if i mixed up the term "group" which is used directly in elgg with my original intention.

You asked why they do need to be represented as a group. I hope i could bring you the idea near. One of the project leader said that this is a really interesting thing to work at and he made a requirement for me. At first i should just do some concept work and then try to create a real solution (if possible in a short period of time).

I think your idea with this created user account is not that bad. Thing is that it really needs to be created on demand and only temporary. It's definitely another approach i should consider.

Now I'm starting to understand. An interesting idea indeed.

Well here's one approach that came into my mind:

Each user has their own personal user account.

After signing in the user would select the participating people. This information would be linked to an object. Lets call that object a "session". The session would have a relationship to all the selected users e.g "User A is a participant of Session B, User B is a participant of Session B, etc".

When creating any content there would be a hook that would save a relationship between the content and the session object ("Blog A is a product of Session B"). Then it could be possible to later on fetch all contents that are product of the session. (The actual owner of the content would of course still be the person whose account was used at login.)

The river could have items like "People A, B and C published a blog post 'Our new blog'".

Also it would be possible to find out all the sessions that any particular user has participated. "User A has participated 15 sessions this year."

I don't know how usable this approach would be but at least you have some more food for thought. :)

That's what i thought so far but i could receive the object but not the metadata. I tried to call a elgg_set_ignore_access(true) before i wanted to get the metadata and it worked. Am i wrong now?

greets

How are you saving the metadata?

$entity->metadata_name = $metadata_value

should work just fine, but if you are using an API function in my experience sometimes there is trouble.

@rob2109, this is not an appropriate time to use the elgg_set_ignore_access function. I haven't looked into the details, but if I had to guess, the problem is likely that metadata has an owner_guid too, so when the acl is private, it remains private to the original owner, even though the associated entity has had its owner changed.

Thanks for your help but i tried that and it did not work. My command was like this:

$this->conn = mysql_connect($host, $user, $pass, true);

No difference.

The thrown errors which are always different. The only thing they have in common is that it is a mysql error. I copied the whole error into pastebin.

http://pastebin.com/tWGHQRs6

I'm looking desperately for a solution. I hope anyone can help.

greets

Try to disable the access_plus plugin. It looks like the error is originating there.

Is that not this plugin? I couldn't find the code the error stack trace references in the latest version of that plugin.

Thanks for your help. The problem really seemed to be in relation with that PlugIn. The error was not thrown when i deactivated the PlugIn, but a different appeared. But i solved it by cutting the code out of the init function of my plugin. Now i'm opening the connection within a different file and all works fine until now. I'll tell you here if i got any other errors.

But anyway i should update the plugin to avoid more problems.

greets