Transaction isolation level warning

Aannnnndddd a patch.

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!

Hi, can you please make a new release including this patch? Thanks!

ruslan piskarov → made their first commit to this issue’s fork.

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.

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

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 !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.

just adding [duplicate] to title so I don’t keep looking in here for things to do...

@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

@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.

Looks like the issue i have is better to post to https://www.drupal.org/project/views_url_alias/issues/3491389 🐛 Some path alias crash the creation of the views_url_alias table Active

nicholass → closed merge request !31

In any case, it's pretty unbelievable that none of the maintainers has bothered to take care of this and release a new version. Such a poor plugin culture only exists in the oh-so-great Drupal community.

Please don’t berate the maintainers on an issue, sachbearbeiter, it simply doesn’t help the situation in any way.

Maintainers are all humans doing an essential role voluntarily and their inclination to do that is only harmed by that type of comment.

May I suggest instead that you contribute to the issues here that still need to reach a reviewed state and help them be ready for a possible release?

However, if you are so disappointed in the contribution culture in Drupal, may I suggest trying another cms, instead?