The drush entup command has been deprecated since the last Drupal release. How to fix this problem in the dashboard ?

Entity/field definitions
Mismatched entity and/or field definitions
The following changes were detected in the entity type and field definitions.
Profile

The Active field needs to be updated.

CommentFileSizeAuthor
#5 profile-fix-status-field-3060368-5.patch1.17 KBjsacksick
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

zenimagine created an issue. See original summary.

bojanz’s picture

bojanz CreditAttribution: bojanz at Centarro commented
Title: Mismatched entity and/or field definitions » Status report still shows "The Active field needs to be updated" after running updates
Category: Support request » Bug report

There should be no need for entup because each module's updates should perform the needed changes.

However, I can confirm that locally I am also seeing that message, even though all updates have been run.
We have a bug.

colinstables’s picture

colinstables CreditAttribution: colinstables commented

I Have the same problerm?

Gil'Barbare’s picture

Gil'Barbare
he/him
Primary language French
Location Rennes
CreditAttribution: Gil'Barbare as a volunteer commented

Drupal 8.6.15
Same Problem :-(
Thanks for help.

jsacksick’s picture

jsacksick CreditAttribution: jsacksick at Centarro commented
Status: Active » Needs review
FileSize
profile-fix-status-field-3060368-5.patch1.17 KB

EntityPublishedTrait defines the status field as "translatable", which wasn't the case with the manual base field definition we had before.
I believe it shouldn't be translatable since none of the other fields are.

After running the update, the warning is gone.

phl3tch’s picture

phl3tch CreditAttribution: phl3tch commented

#5 solved the problem for me.

steveoriol’s picture

steveoriol
Location Grenoble 🇫🇷
CreditAttribution: steveoriol commented

#5 solved the problem for me too.

benjarlett’s picture

benjarlett CreditAttribution: benjarlett commented

sorry, not working for me :(

jsacksick’s picture

jsacksick CreditAttribution: jsacksick at Centarro commented

@benjarlett: did you apply the patch and ran the updates?

aspilicious’s picture

aspilicious CreditAttribution: aspilicious commented
Status: Needs review » Reviewed & tested by the community

I can confirm this works

Londova’s picture

Londova CreditAttribution: Londova commented

#5 solved the problem for me too.

DuneBL’s picture

DuneBL
Primary language French
CreditAttribution: DuneBL commented

#5 rocks

  • bojanz committed 887a555 on 8.x-1.x authored by jsacksick 
    Issue #3060368 by jsacksick: Status report still shows "The Active field...
bojanz’s picture

bojanz CreditAttribution: bojanz at Centarro commented
Status: Reviewed & tested by the community » Fixed

Committed #5, thanks jsacksick!

mlecha’s picture

mlecha CreditAttribution: mlecha commented

I added the patch to my composer.json, did an update with composer which applied the patch, run update.php and the error is gone.

Should I now remove the patch reference from composer.json before the next composer update?

Thanks for you comments!

TomSaw’s picture

TomSaw CreditAttribution: TomSaw commented

#5 worked but had to apply the patch with:

patch -p1 < some_patchfile_.patch

rather than:

git apply patch some_patchfile.patch

usually the git-way worked but in this case, no error, no patching at all :/

thalemn’s picture

thalemn CreditAttribution: thalemn commented

#5 patch resolved the issue

my process:
downloaded patch file into the profile module directory
profile-fix-status-field-3060368-5.patch

terminal into profile module directory
terminal: $ patch -p 1 < profile-fix-status-field-3060368-5.patch

terminal into drupal install directory
drush updb

happy dance

quapou’s picture

quapou CreditAttribution: quapou commented

Hello,

I have the same problem :
"Profile
The Active field needs to be updated."

I have done all the updates but the error message remains.
Should I apply the patch : "profile-fix-status-field-3060368-5.patch" ?
And How ? (I am not using composer an drush).

Thank you.

bbuchert’s picture

bbuchert CreditAttribution: bbuchert as a volunteer commented

@quapou https://www.drupal.org/node/620014

sagesolutions’s picture

sagesolutions CreditAttribution: sagesolutions commented

Confirming that #5 patch works for me.

ohmdesbois’s picture

ohmdesbois CreditAttribution: ohmdesbois commented

I confirm that after applying the patch #5, the update runs normally and there is no more warning message.
To reply to #mlecha, it is then possible to remove the patch and redo a composer update, the database having been updated, there is no more warning.
Thanks

bojanz’s picture

bojanz CreditAttribution: bojanz at Centarro commented

Update to rc6, no need for a patch anymore.

bojanz’s picture

bojanz CreditAttribution: bojanz at Centarro commented

Update to rc6, no need for a patch anymore.

Status: Fixed » Closed (fixed)

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