I've been having problems with posting content. It just failed and i found the errors referred to common_notify. So I disabled the module and I was able to post again, however no email notification when out.

The error message I got was when commons_notify was enabled was:
EntityMetadataWrapperException: Unknown data property field_target_nodes. in EntityStructureWrapper->getPropertyInfo() (line 339 of /var/www/vhosts/commons-dev.communitydoor.org.au/httpdocs/profiles/commons/modules/contrib/entity/includes/entity.wrapper.inc).

I upgraded to the dev version and that actually allowed me to post content with commons_notify enabled.

However, the email that gets sent is blank. It contains a To and and From field and that's about it.

I really need the email notifications to work. Any suggestions?

thanks

Comments

stevehutchison’s picture

stevehutchison commented

I notice on the project page for Commons_notify it says "Experimental code for the notification system in Drupal Commons 7.x-3.x." Does that mean its a big buggy?

jpontani’s picture

jpontani commented

You may need to do a features revert on Commons Notify. Sounds like one of the message types shipped with Commons Notify didn't get the right field instances created.

I would also check out #2030133: hook_commons_activity_streams_message_selection_alter to add a message for custom content, you need to add field_target_nodes and see if the fix mentioned in #2 works for you.

japerry’s picture

japerry
Location KOMK
commented
Status: Active » Fixed

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.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.