**Description of the need**
Since URL Aliases often closely match the title of a piece of content, you could think of a node's URL Alias like its machine name...
**Proposed solution**
That got me thinking; why not make the URL Alias field part of the node's Title field, in the same way that a Machine Name field is part of the entity's Title field?

So, when you create a piece of content for which URL Aliases are enabled, they would appear next to the Title as text that's generated automatically as you enter the Title. And there'd be a button that would enable an editable field for if you wanted to change the URL Alias to something other than the default.

Based on this (and other) screenshots, I believe WordPress does (or did) something very similar:

(Source: https://www.theblogstarter.com/how-to-add-links-to-your-wordpress-blog/)
EDIT: Updated WP screenshot/source.
GitHub Issue #:
3993
Recent comments
Thanks Meaghan. I have solved this error. The issue was that after the upgrade, I re-enabled the civicrm related modules at a time that leads to the error. But after that I tried and re enabled...
Facing an error after upgrading Civicrm version from 5.78.3 to 6.5.0
Ah yes. Thank you very much.
Porting of module Views Raw SQL
Go to admin/structure/views/settings and click on "Show information and statistics about the view during live preview"
Porting of module Views Raw SQL