[UX] Rephrase "database updates" so that it is clear that they also perform config updates.

[laryn]

It seems that perhaps the process that is currently labeled "Backdrop database update" (/core/update.php) could be named more accurately. This process includes any update hook at all, and may include or be exclusively config updates, for example. Should we consider changing this term/phrase?

[olafgrabienski]

Good idea! As a start, we could list places and term variations which refer to the (former) database update.

[indigoxela]

... may include or be exclusively config updates, for example. Should we consider changing this term/phrase?

I think about that almost every time I run "database updates" - when I know, that it's actually config. Yes, let's be more accurate about that. 👍

[olafgrabienski]

list places and term variations which refer to the (former) database update

Here's a start:

• database update
• database updates
• run updates (e.g. Admin bar)

[bugfolder]

How about "Backdrop site update"?

[bugfolder]

Here's a PR that changes "database update" to "site update" in most places (unless we're actually only changing the database).

[laryn]

I looked over the changes and the code looks good.

[stpaultim]

This change makes sense to me.

[olafgrabienski]

I also like the direction!

@bugfolder Can you also mention configuration files in the first sentence on core/update.php?

Use this utility to update your database whenever you install a new version of Backdrop CMS or one of the site's modules.

[bugfolder]

Can you also mention configuration files in the first sentence on core/update.php?

I changed it from "update your database" to "update your site", similarly to other changes. That block of text also mentions "This update utility will alter your database and config files," so config does get mentioned.

I notice that all of that text is not wrapped in t(), which I assume is for a good reason; I'm just curious as to why.

[klonos]

Coming late to this: Yes please! 👍🏼 💯

The phrase "System updates" is already reserved for the core version updates, as well as contrib and customer project updates under Configuration >> System >> System updates (admin/config/system/updates). So "site updates" seems sensible/appropriate to me too.

The PR needs a rebase and has conflicts that will need to be resolved.

[klonos]

I notice that all of that text is not wrapped in t(), which I assume is for a good reason; I'm just curious as to why.

I am also not 100% sure about that, but when I've asked previously, I think that the answer was that t() might not be loaded during that stage. It could be an oversight though 🤷🏼

[herbdool]

I've reviewed the code and tested (after rebasing). Looks good now.

[quicksketch]

Awesome, that's a lot of agreement for a string change! I merged backdrop/backdrop#4642 into 1.x and 1.28.x. Thanks @bugfolder, @laryn, @herbdool, @olafgrabienski, @klonos, and @indigoxela!