Creating a group gives EntityMetadataWrapperException: Unknown data property field_target_nodes error

At what point do you receive this error?

.That error message has shown up in the following issues and I believe was possibly fixed with a fresh update of Commons_Wikis. Check the first issue "Undefined.." comment #4 & #5 for more information.

• Undefined property: stdClass::$updated in commons_wikis_node_update()


• Implement email notifications & UI with Message Subscribe


• Activity stream message for when a wiki node is updated


• EntityMetadataWrapperException When Setting Group Content Visibility

@Topcheese - Thanks for referencing those issues!

@milkmiruku, I'm not able to reproduce, so perhaps you're experiencing a duplicate of one of the above issues.

Please re-open this issue with steps to reproduce if you're still having this problem.

Thanks!

Last Commons have this error. Also during installation,

@lbarsov, I would like to help, but I'm not using Aegir, and I'm not currently having that problem. If your problem is not related to any of the issues I listed in comment #3, then you might want to reopen this issue. You might also want to include some more details on your environment(Aegir?), and to include some of the steps taken.
-Thanks

I received this exact same error when I tried to create a content of type Quiz (which I installed separately, version 7.x-4.0-alpha12). I tried upgrading my site from Beta1 (the stable release) to the latest Dev release (commons-7.x-3.0-beta1+12-dev), but it didn't fix the issue. I ran update.php (there were no db updates to execute) and I reverted all of the enabled features that showed "overridden".

Seems to me that this might be a duplicate of:
http://drupal.org/node/1868776

The errors are very similar.

Also got this error when creating a new Webform (using Webform version 7.x-4.0-alpha6).

Unable to reproduce after doing a fresh install of the Jan 10th dev release when creating Quiz or Webforms.

Run into this problem with beta3.

And I solved it by replacing it with beta2.

http://drupal.org/node/1909238

First and foremost: Thanks for all the hard work, everyone. Commons 3.0 is really great!

Back on topic...

I was seeing this error with only commons_follow and commons_activity_streams enabled.

It was happening every time I tried to save a node.

I was not using the profile build - this is probably the source of the error.

It looks like the commons_activity_streams feature SHOULD be adding these reference fields to the message types, but when I inspect them, the fields are not there:

This is in contrary to when I check on these same message bundles on a true commons build:

In short: perhaps someone knows why these fields are not getting inserted into the new message bundles? I can add entity reference fields to them manually, but it also appears the meta fields are missing.

I was not using the profile build - this is probably the source of the error.

Can you elaborate on how you built Commons? Did the method include all of the patches in the drupal-org.make file?

I am building it as part of a distribution so the modules are downloaded through a drupal-org.make - I've doublechecked all the dependencies for commons_activity_streams and it looks like the dependencies and patches are the same.

One thing I also tried was building a fresh version of commons using build-commons.make, then moving the modules and libraries outside of the profile into sites/all - I then installed standard Drupal and turned on the commons_activity_streams feature. In this instance, the feature showed up overridden, however, the fields were in place.

This also seems to happen when enabling commons_groups on the standard profile. We get a content type called groups but it has no fields.

Anyway, I'll leave this as postponed until I can figure out what the difference-maker is. I'd yet to see a situation where a feature gets enabled but the fields do not get inserted along with the rest of the bundle until today... quite strange.

Perhaps a feature request of 'can commons modules work outside of the commons distro build?' ...would be nice-to-have eventually. :)

Ok - I'll chalk this one up to fatigue. Its working now. I had overlooked #1064472-64: separate fields from field instances

I am a newbie at drupal, and I am having the message error:
EntityMetadataWrapperException: Unknown data property field_target_nodes. in EntityStructureWrapper->getPropertyInfo() when I try to edit a wiki. Is there a solution for this?

This is after installing the Commons Wiki for drupal 7.

Thanks!

Please refer to #2065381: EntityMetadataWrapperException errors due to features not being reverted for reasons why its important to revert all features after enabling a feature in commons. We don't automatically revert all features because we don't want to destroy user customizations.

The easiest way to revert is with 'drush --force -y fra' if you have drush enabled. Warning: this will remove any customizations / overridden features you may have on your install. Proceed with caution!

Re-open if you feel that this message is in error and can be replicated after reverting all features.

We ran into this issue when creating new content that was *not* a Commons content type (additional content type "News").

Traced it back to the Message entity not having the required field field_target_nodes when firing off message commons_activity_streams_node_created. (So yes, Commons ideally would have added the field to this Message entity.)

Messages can have different fields for different Message entities, so you might need to check that the Message you're sending when you see this error has the required field, OR we need to adjust the code (modules/commons/commons_activity_streams/commons_activity_streams.module around line 44) to check whether $wrapper has attached field field_target_nodes before trying to set the property (or whether it's one of the messages that Commons has set up).

The message in question can be identified from $message_type at that point.

Anyway - manually adding existing field field_target_nodes to messages like commons_notify_node_created / commons_activity_streams_node_created got us around this issue without having to revert all the customisations in place. Messages and their associated fields live at admin/structure/messages

(Perhaps you could also disable the message in question.)

I am having this issue too how do i fix it

Thanks