Pre-existing before changes:
1. Media bundle - for images and video.
2. Assets loaded to media bundles.

Set up Patterns:
1. Media images already exist as content.
2. Added Pattern Type Media
3. Media bundle - image and video
4. Label and enabled completed.

Set-up Settings:

1. Entity type media set up.
2. Separator -
3. Character case checked.
4. Update action - Create a new alias. Delete the old alias.
5. Transliterate prior to creating alias - checked.

All caches are flushed

Bulk Generate is executed for media.

RESPONSE --- No new URL aliases to generate.
Despite existing media where the alias is not applied, and should be flagged for bulk regeneration.


davebeach created an issue. See original summary.

LpSolit’s picture

Status: Active » Postponed (maintainer needs more info)

Are media configured to have their URL alias automatically generated? If not, then the current behavior is expected and is the correct one.

cmcnamee’s picture

I am having the same problem, same version.

1) I updated my "blog_post" content type path pattern from [node:title] to article/[node:title]

2) I tried every option under "Bulk Generate". When none them worked, I deleted all path aliases and tried Bulk Generate again.

3) Still, the path of the node remains node/107


After adding this comment, I noticed that I said I made the path pattern article/[node:title], but when I looked again (see screenshots), I apparently had used [current-page:title] of which wouldn't work (whoops).

I updated the pattern to article/[node:title], did a Bulk Generate, a cache clear, and now the paths are working just fine.

So, to the original poster of this issue... try double checking the tokens you used in your path pattern. See if that fixes your problem?