Here's the problem...
1. Add new node and assign to content section and save.
2. Click "Moderate" tab.
3. Change moderation status to "published".
4. Click "view" link to view published node.
5. Node appears in browser just fine with URL alias based on content section like...
[node:workbench-access-sections]/[node:title]
...but if I do a slightly different workflow, I get a page-not-found...
1. Add new node and assign to content section and save.
2. Without clicking the "Moderate" tab, instead stay on the "View Draft" tab and change the moderate status to "published" and click the "apply' button.
3. Forwarded to unassigned/page-title instead of content-section/page-title, and so of course there is a page-not-found error.
4. But the page has been saved/published with the correct URL alias, and likewise if I find the page in My Workbench, I can view it with the correct URL alias.
...So basically the URL alias is not being applied using the content section name upon the first save when the first draft is created. The URL alias is not properly set based on the name of the content section until a subsequent draft is saved, or if the node is published.
Is there any way to avoid the behavior described above? I would like the URL alias to be set up properly when the first draft is saved. Please advise.
Comments
Comment #1
agentrickardNice report. I think the problem here is actually in Workbench Moderation -- and possibly PathAuto. We'll need to dig in and see what is being saved and when. it may be a form submit error with the shortcut form element.
Comment #2
MrSasquatch commentedDo you need more information from me? ...or should I report this in Workbench Moderation?
Comment #3
agentrickardNope. I just moved the issue. We're all set. Will likely test tomorrow.
Comment #4
MrSasquatch commentedSweet! Thanks!
Comment #5
agentrickardI cannot replicate this error using 7.x-1.x-dev. I suspect it has been fixed in another issue. Looking.
Comment #6
agentrickardThis is a duplicate issue. #1379088: Changing a title on a draft of an already published article generates a 404 when publishing