Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I can create projects and tasks, but when I try to reply to a task and update its status I get the following error:
EntityMetadataWrapperException: Unknown data property field_oa_worktracker_comment_ref. in EntityStructureWrapper->getPropertyInfo() (line 339 of /var/www/atrium/profiles/openatrium/modules/contrib/entity/includes/entity.wrapper.inc).
The website encountered an unexpected error. Please try again later.
I'm using Open Atrium 2 alpha5
Comments
Comment #0.0
Dracolyte CreditAttribution: Dracolyte commentedAdded OA version
Comment #1
wrap2 CreditAttribution: wrap2 commentedI am getting the same error. In two situations.
1. In OA_WorkTracker
When the creator administrator of the task attempts to change a task "assign to" and
"status", clicking "save" throws a "Comment field is required." The record is not changed.
Doing the same, but adding text to the comment field. Clicking 'save' and error message appears:
EntityMetadataWrapperException: Unknown data property field_oa_worktracker_comment_ref. in EntityStructureWrapper->getPropertyInfo() (line 339 of /var/www/profiles/openatrium/modules/contrib/entity/includes/entity.wrapper.inc).
2. In Discussion Page
Additionally, when I add a comment to a discussion page, clicking 'save' there now throws this same error message.
This did not happen prior to DL and EN enabling the OA_Worktracker module.
Comment #2
dsnopekThis looks like the same issue as #2062899: Error when editting a task which includes more information and screenshots. Closing as duplicate.
Comment #3
wrap2 CreditAttribution: wrap2 commentedThis may appear to be duplicated, but the original poster is pointing out a more severe issue.
Elaborating further:
With OA_WorkTracker enabled,
this "EntityStructureWrapper->getPropertyInfo() (line 339 ... " error is thrown not only in
OA_WorkTracker but also in
OA_Discussion (blog) located in another SPACE/Section.
So it is breaking other OA module.
Comment #4
dsnopekHrm. I'll re-open and change the title to reflect that. However, I'll add that I personally haven't be able to recreate this issue (yet).
Comment #5
wrap2 CreditAttribution: wrap2 commentedFirst, thank you and all "committer folks" and what you do for Drupal and OA.
"I personally haven't be able to recreate this issue"
Do you have UUID enabled, disabled, or deleted from your system?
Comment #6
dsnopekI do have UUID enabled.
However, I think this another Features issue - it should have created the field_oa_worktracker_comment_ref field but didn't. Doing
drush features-revert oa_worktracker_comment_ref
should fix it.I've created an issue to work on these Features issues: #2098475: Issues with Features not fully creating everything on install
Comment #7
wrap2 CreditAttribution: wrap2 commentedworked for me, too.
Comment #7.0
wrap2 CreditAttribution: wrap2 commentedClarified what is meant by "updating" a task