Jump to content
ryan

ProcessWire 3.0.148 – New master!

Recommended Posts

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/

  • Like 18
  • Thanks 5

Share this post


Link to post
Share on other sites

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

 

  • Like 2

Share this post


Link to post
Share on other sites

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.

 

Share this post


Link to post
Share on other sites
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.

  • Like 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...