- Issue created by @JSchref
- πΊπΈUnited States druliner
cd core/modules/contrib/views_url_alias
wget #2
patch -p1 < views_url_alias-add-pri...8676-2.patch
drush updb
All better! Thanks jschref! - π©πͺGermany sachbearbeiter
Hi, can you please make a new release including this patch? Thanks!
- πΊπ¦Ukraine ruslan piskarov Kyiv, Ukraine
ruslan piskarov β made their first commit to this issueβs fork.
- πΊπ¦Ukraine ruslan piskarov Kyiv, Ukraine
The patch 32 can be applied to Version 3.1.0, but in DEV it was fixed in another way.
You can have a look Database Indexes was never created because incorrect key in hook_schema π Database Indexes was never created because incorrect key in hook_schema Fixed .
Leaving this task for reference. Decided do not close this task for now. - πΊπΈUnited States NicholasS
I also got an error related to the primary keys issue, sovled by clearing cache. When adding a content type I got
Drupal\Core\Database\IntegrityConstraintViolationException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '' for key 'views_url_alias.PRIMARY': INSERT INTO "views_url_alias"
Which I think is fixed by having good primary keys
- πΊπΈUnited States NicholasS
So I tried out the dev version but get an error with the Databaseupdate @ruslan_piskarov
Module Update ID Type Description
----------------- ----------- --------------- ------------------------------------------------------------------------------------------
views_url_alias 10301 hook_update_n 10301 - Implements hook_update_N(). Install indexes, add new column, add primary key.
views_url_alias 10302 hook_update_n 10302 - Implements hook_update_N(). Reinstall the schema, rebuild views_url_alias table.
----------------- ----------- --------------- ------------------------------------------------------------------------------------------// Do you wish to run the specified pending updates?: yes.
> [notice] Update started: views_url_alias_update_10301
> [error] views_url_alias_get_path_entity_type(): Return value must be of type ?Drupal\Core\Entity\ContentEntityInterface, Drupal\webform\Entity\Webform returned
> [error] Update failed: views_url_alias_update_10301
[error] Update aborted by: views_url_alias_update_10301
[error] Finished performing updates.Failed to run drush updb -y: exit status 1
- Merge request !31fix error caused by the views_url_alias_get_path_entity_type() function trying... β (Open) created by NicholasS
- πΊπΈUnited States NicholasS
merge request !31 - Allowed me to run the Dev branch database update successfully.
----------------- ----------- --------------- ------------------------------------------------------------------------------------------
Module Update ID Type Description
----------------- ----------- --------------- ------------------------------------------------------------------------------------------
views_url_alias 10301 hook_update_n 10301 - Implements hook_update_N(). Install indexes, add new column, add primary key.
views_url_alias 10302 hook_update_n 10302 - Implements hook_update_N(). Reinstall the schema, rebuild views_url_alias table.
----------------- ----------- --------------- ------------------------------------------------------------------------------------------// Do you wish to run the specified pending updates?: yes.
> [notice] Update started: views_url_alias_update_10301
> [notice] Update completed: views_url_alias_update_10301
> [notice] Update started: views_url_alias_update_10302
> [notice] Update completed: views_url_alias_update_10302
[success] Finished performing updates. - π¬π§United Kingdom rachel_norfolk UK
just adding [duplicate] to title so I donβt keep looking in here for things to do...
- πΊπΈUnited States NicholasS
@rachel_norfolk Is this a duplicate of 3433027? Because that one says fixed, but when I tested the 3.x-dev I still got an error during the database updates and the primary keys on the tables could not be fixed due to that error. That's why I created MR31
- π¬π§United Kingdom rachel_norfolk UK
@nicholass - I was going on the message in comment #6. Thereβs certainly a belief that the issue is fixed in @dev, but in a different way.