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.Exact same behavior as previously reported here for an earlier version. I am using dev install and all modules (such as registration) are already upgraded.
I have attached a list of my upgrade status FYI
| Comment | File | Size | Author |
|---|---|---|---|
| drupal_projects_update_status.txt | 9.37 KB | behoppe333 |
Comments
Comment #1
ezra-g CreditAttribution: ezra-g commentedThat's because these fixes are included in the dev version of the respective Commons modules.
For this fix, you can either update to a dev version of Commons packaged by build-commons-dev.make, or wait for commons 3.3 due out late June or early July.
Comment #2
ezra-g CreditAttribution: ezra-g commentedComment #3
behoppe333 CreditAttribution: behoppe333 commentedOK thanks. I am using drush and build-commons-dev.make. I am desperately trying to figure out what I am doing wrong, so that my bug reports are helpful rather than annoying. I assume this forum is really not the right place for question, "what am I doing wrong with my drush make build-commons-dev.make" but figured I'd mention it here because once I get that figured out I promise to be a good tester-contributor to the current development effort.
Comment #4
ezra-g CreditAttribution: ezra-g commentedHi behoppe333 - I didn't realize you were using build-dev.make, and this issue queue is absolutely the best place to get assistance packaging Commons :).
The Commons team and other Commons-savvy people are also on IRC in #drupal-commons.
I tried but didn't have any issues enabling the Commons documents module and posting a document to a group. Something for you to try:
After enabling the Commons Documents module, is Commons_Groups overridden at admin/structure/features? If so, if you revert it to default, does that resolve the problem?
If not, can you post the specific error message you're getting?
Thanks!
Comment #5
behoppe333 CreditAttribution: behoppe333 commentedHi ezra-g,
thanks for the reply. I repackaged (rebuilt, remade?) my site and now documents are working for me. Can re-declare "fixed" status and sorry for confusion on that.
For what it's worth, my rebuild process was (1) copy over commons-7.x-3.x-dev-core.tar.gz, (2) extract those files on top of my dev site, (3) re-run "drush make profiles/commons/build-commons-dev.make"
I remain sketchy on why the official instructions say "drush make build-commons-dev.make" and my configuration seems to require me to run drush command from root of my drupal commons site and add "profiles/commons/" folder as prefix to the makefile.
Comment #6
ezra-g CreditAttribution: ezra-g commentedGot it. Thanks for the update! Looking forward to working with you in the queue!
Comment #7
cherrysuede CreditAttribution: cherrysuede commentedHey guys - i'm having this exact error - i updated a live site using the latest dev release. If i unpublish all documents the error disappears. - i added a brand new content type and added the group and user ref fields and tried to add that - and also causes an error if added to a group.
unfortunately i do not use drush
Comment #8
cherrysuede CreditAttribution: cherrysuede commentedso if i log in as admin to the site all documents show fine -
but logged in as an auth user if i try to view a document directly or if i try to view the homepage or any group that has a document - i get
Error
The website encountered an unexpected error. Please try again later.
and in the log i get
EntityMalformedException: Missing bundle property on entity of type node. in entity_extract_ids()
i hope im reporting this correctly and in the right thread - fairly new at this.
Thanks!
Comment #9
cherrysuede CreditAttribution: cherrysuede commentedComment #10
lsolesen CreditAttribution: lsolesen commentedClosing old issues. Please try newest Commons and reopen if you still have the problem.