Chris Brown

More on the UUID vs `long` thing: In https://github.com/laravel/framework/discussions/48933#discussioncomment-7495617 it is pointed out that the posted model code does not contain `protected $keyType = 'string';` for (part of) implementing Laravel's...

We could go various directions with this. But before considering that, I'll point out that the whole reason for `mb4` is to support multibyte characters (like emojis) so that end-user...

As for the `520` vs `general` variant, I've read mixed reviews online about whether to use 520. The challenge is in determining which one to align with, as not all...

> IMO, zc_install should: > > 1. Use the database's default collation for any newly-added tables. > 2. Report to the updating admin if the DB_CHARSET setting doesn't match the...

While I agree that the correct solution is for the end-user to update to the updated plugin. That said, I think the plugin should define its own independent (ideally non-conflicting/non-competing)...

I gather that the intent of this load-order change is specific to "booting up" the (installed) plugins on page-load. The Admin UI for Plugin Manager would require a different change...

> That was also what I was looking for (too many buried classes). Without that change, the Plugin Manager displays the "plugins in the order in which they were installed":...

Open to discussion before merge ...

Hmmm. There's a ripple-effect problem with this as proposed: Editing the product (ie: to "fix" the description) will blank out even more data.

Updated to: - requires the search to include missing-lang products, in order to "find" such products - requires all the fallback-lookups used when editing/previewing/updating to allow for missing data, in...