ProcessWire 3.0.148 – New master!

[ryan]

Today we have a new master version released, version 3.0.148! The last master version was 3.0.123, so there are 25 new versions worth of upgrades, fixes and optimizations in this new master version, relative to the previous. In this post we’ll take a closer look at what’s new, how to upgrade, and more—

https://processwire.com/blog/posts/pw-3.0.148-master/

[teppo]

Hey Ryan. Great summary, thanks (and congrats!)

Just noticed that the Packagist version is lagging behind – it's still showing 3.0.123 as the latest master. Would be great if you could give it a little nudge ?

Seems that the connection between the GitHub repository and Packagist isn't working quite as expected, and clearly it's not just limited to the dev branch. Perhaps it needs to be re-approved or something ?

Quote

This package is not auto-updated.

Last update: 2019-12-31 14:06:49 UTC

 

[Andy]

Find in version 3.0.148.

AdminThemeUikit has changed.

in _head.php was

    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <link rel="icon" href="/wire/Favicon.ico" type="image/x-icon" />

    <title><?php echo $adminTheme->getBrowserTitle(); ?></title>

now

    <meta name="viewport" content="width=device-width, initial-scale=1.0">

    <title><?php echo $adminTheme->getBrowserTitle(); ?></title>

Now we can't use different favicon for the main site and for the editing mode.
Prior to this case, it was convenient to distinguish between operating modes.

 

[teppo]

1 hour ago, Andy said:

in _head.php was

    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <link rel="icon" href="/wire/Favicon.ico" type="image/x-icon" />

As far as I can tell, this favicon line has never been a part of the AdminThemeUikit that is shipped with ProcessWire. Are you sure this wasn't actually a local modification made by you or another developer?

In either way it's never a very good idea to modify the contents of the /wire/ directory yourself, so even if there was such a line, adding your own favicon there would be a problem — partly because it will very likely get lost when you update ProcessWire.

[Andy]

I absolutely agree with you. Do not touch the /wire/ directory if you are not a developer of this.
However, the customer really wanted the differences between the front-end and back-end icons. This is really convenient when you can see in a browser in which mode you opened them.

And adding the icon to the /wire/ was the fastest but the wrong way.

Adding such functionality to the admin template will be very useful.