PW 3.0.122 – Core updates

[ryan]

Last week's version 3.0.121 was the first release candidate for our next master version. Several issue reports were covered this week for minor things, and they are all included in this week's dev branch version 3.0.122. Please consider this version the RC2 (release candidate 2) for our next master. There's nothing major to report, but if you'd like to see the list of changes relative to last week's version, please see the dev branch commit log at: https://github.com/processwire/processwire/commits/dev

If you have a chance, please upgrade to version 3.0.122 and let us know if you run into any issues. Thus far things are going smoothly and it seems like we are very close to the next master version, perhaps as soon as next week. 

Since I don't have much more to report than the above, we'll skip doing a blog post this week. But after last week's post, a couple of people asked me about ProMailer (as mentioned, which we use for the weekly email distribution), so I'll be sure to write more on that soon. Attached is a screenshot from the message editor screen that reveals several aspects of the message sending part at least. Thanks for reading and I hope that you all have a great weekend! 

 

[Gideon So]

Hi @ryan,

Can you look into this issue again: https://github.com/processwire/processwire-issues/issues/724

The fix is good for single language environment but there is error show in the backend under multi-language settings:

https://github.com/processwire/processwire-issues/issues/724#issuecomment-443126270

 

Gideon

[horst]

ping: @ryan

This one would be really useful: https://github.com/processwire/processwire/pull/117

Also this is not an issue, it would be really helpful to have this enhanced debugInfo integrated into the current dev branch, before it becomes the new stable.
It doesn't affect any other method or param, - only enhances the __debugInfo() method with useful informations.

This would be really helpful for debug and support cases, if someone encounters a problem and ask here in the forums for help, we can get a good insight / overview in his/her current images system by simply asking to show us that info.

[adrian]

I'd also love to see more/better debugInfo for other PW objects as well, as per: https://github.com/processwire/processwire-issues/issues/575

[HerTha]

On a (quite freshly installed) test site with UIkit3 profile and running on PHP7.1.24 I upgraded to latest dev (3.0.116 -> 3.0.122), which brings up an error message:

Fatal Error: Uncaught Error: Call to undefined function ProcessWire\mb_convert_encoding() in /wire/core/Sanitizer.php:1036 

Seems to be related to one of the most recent commits?

May be specific to that particular PHP version?

(sorry for reporting here instead of github)

 

[HerTha]

okay - seems I have to ask my site admin to install an additional PHP extension - "mbstring"

I guess, during a PW install from scratch the presence of this extension is checked by the installer...

[horst]

2 hours ago, HerTha said:

I guess, during a PW install from scratch the presence of this extension is checked by the installer...

Yes. And, if you are not able to do a fresh install, you may install and use the Diagnostic-Modules from @netcarver to do a check on unknown server environments. ?

[HerTha]

@horst thanks for confirming!

And: oughta check the modules directory more frequently. A horn of plenty! ?

[PWaddict]

@ryan You should update the version of InputfieldAsmSelect.module to 122 to enable cache busting on jquery.asmselect.css so everyone can view the new change you did about:

.asmOptionDisabled {
    color: #999 !important;
}