PW 3.0.130 – Core updates

[ryan]

Work continued in closing out issue reports this week. We’re down to about 60 of them now, though if we subtract issues that aren’t reproducible, are already marked as resolved (close pending), may be moved to the request repo, or are a discussion (rather than something to fix), then we’re closer to half that number. Over these last few weeks we’ve been working on issue reports, but I’ve also been enhancing the core in small ways as well. This post will cover a few of the useful enhancements that have been made in recent weeks—

https://processwire.com/blog/posts/pw-3.0.130/

[Jonathan Lahijani]

Nice update, although I don't think the version bump was committed.

[David Karich]

Hey @ryan, great update! I wonder if the new CacheRender function can also be used for repeaters or repeater matrix items? Like this:

foreach($page->repeater_field as $item) {
  echo $cache->renderFile($item->render(), WireCache::expireSave);
}

It would be great, especially with a lot of repeater items and outsourced render files the rendering can take a few seconds.

[Macrura]

The caching though won't work if you are using wireRenderFile and reusing the same file with different variables that influence the markup when outputting.
There would need to be another option where you could set some type of ID for the cache; Right now, if i have files being used with different options for output based on supplied variables, like a page builder, it will just render the 1st one over and over if i render the same file in succession.

[Jonathan Lahijani]

2 hours ago, Macrura said:

The caching though won't work if you are using wireRenderFile and reusing the same file with different variables that influence the markup when outputting.
There would need to be another option where you could set some type of ID for the cache; Right now, if i have files being used with different options for output based on supplied variables, like a page builder, it will just render the 1st one over and over if i render the same file in succession.

Actually this is possible with the update:

https://github.com/processwire/processwire/commit/12aede03fe297421b538ea6ef16c0f42424077a4#diff-fc95d41f7bed91883ef3f4f16d8c92cdR1104

[horst]

@ryan, I want to test the new blacklist support with WireMail and WireMailSmtp, but on both configurations I get error of missing method isBlacklistEmail()

Error: Exception: Method WireMail::isBlacklistEmail does not exist or is not callable in this context (in G:\VHOSTS\_PW-REPOSITORY\wire-3.0.latest\core\Wire.php line 519)

(I took the latest DEV branch 3.0.130 this morning)

My code is like in the blog example:

    $mail = wireMail();
    $to = ['info@nogajski.de'];
    $result = $mail->isBlacklistEmail($to, [ 'why' => true ]);
    if($result === false) {
        echo "<p>Email address is not blacklisted</p>";
    } else {
        echo "<p>Email is blacklisted by rule: $result</p>";
    }

Also if I use the to() method of the WireMail base class with WireMailSmtp, I need to adapt the cc() and bcc() methods of it to support it too.