Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Drupal Apigee contributed module Upgrade. #127

Closed
ac46471 opened this issue May 19, 2021 · 4 comments · Fixed by #130
Closed

Issue with Drupal Apigee contributed module Upgrade. #127

ac46471 opened this issue May 19, 2021 · 4 comments · Fixed by #130
Assignees
Labels
bug Something isn't working

Comments

@ac46471
Copy link

ac46471 commented May 19, 2021

I have been trying to update apigee contributed modules. I am having some issue while updating the modules. I have put more details below.

Drupal version: 8.9.15

Updated Modules :
apigee/apigee_devportal_kickstart 1.16.0 —> 1.22
drupal/apigee_api_catalog 1.2.0 —> 2.5.0
drupal/apigee_edge 1.20.0 -> 1.21.0

Steps Followed:

  1. composer self-update >> Tried with composer version 1.10 and 2.0.13
    
  2. composer update --with-dependencies --optimize-autoloader >> with this some modules are not updated. So, went ahead and changed version in composer.json file. Then ran same script again.
  3. drush updb

Error on running drush updb:

[notice] Update started: apigee_api_catalog_update_8803

[error] Attempt to create a field storage with an name longer than 32 characters: field_web_hooks_push_notificatio_apidoc

[error] Update failed: apigee_api_catalog_update_8803

and I also tried deleting all the additional fields added to api doc. Then tried to upgrade.I was still getting error

[error] Update failed: call to member function getValue() on null.

@ac46471 ac46471 added the bug Something isn't working label May 19, 2021
@phdhiren
Copy link
Collaborator

@ac46471
Can you share MariaDB / MySQL version as well? It may be related to core issue https://www.drupal.org/node/2565931

@edpahang
Copy link

edpahang commented Jun 2, 2021

@phdhiren
I work with @ac46471. The MySQL version our team is using is Database Version 8.0.19
Let us know if you need more information.

@phdhiren
Copy link
Collaborator

phdhiren commented Jun 3, 2021

@ac46471 @edpahang
I'm able to replicate the issue. It seems due to the longer custom field name. Will check this further for resolution.

@edpahang
Copy link

edpahang commented Jun 3, 2021

@phdhiren
Thanks for the update. We appreciate you looking into this issue.

phdhiren added a commit that referenced this issue Jul 29, 2021
Closes #127 Machine names have a maximum length of 32 characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants