PW 3.0.145 – Core updates

[ryan]

ProcessWire 3.0.144 and 3.0.145 add improved field template context override settings and include a new Inputfields API, along with numerous other issue fixes, optimizations and improvements to the core. This blog post is a continuation (and more in-depth version) of last week's post on 3.0.144 that was in the forum—

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

[Jonathan Lahijani]

Excellent update.

One minor nitpick about the overrides tab.  When a field has been added to a RepeaterMatrix, can you have it show the Matrix Type Name (such as "gallery") instead of (or in addition to) the Matrix Type ID ("matrix4").  It would be much clearer that way.

[ryan]

@Jonathan Lahijani Showing the namespace (matrix4) is something new to this version of PW, and it can do that because namespaces of fields within a fieldgroup are a core concept. So this is an extra that we didn't have before, but that I think is worthwhile here. However, Repeater Matrix is a module, and not even a core module, so things like RepeaterMatrix type names/labels are not known to the core. Part of ensuring the core remains flexible and maintainable means that it does not get involved in the implementation details of specific Fieldtypes. It just knows the Fieldtype interface, which is common to all Fieldtypes. So there's no reasonable way for us to have this particular core Process module identify labels of matrix types to show here. When it comes to RepeaterMatrix, the preferable way to edit these settings would be when editing the RepeaterMatrix field, rather than when editing a field within it outside of the matrix context. By doing that, the RepeaterMatrix module has control at that point, so implementation details are fully in scope and you wouldn't need to now what "matrix4" means or anything like that. 

[Robin S]

The Inputfields JS API is really cool, thanks @ryan!

What do you think about adding a feature so that some (all??) of these JS functions could be triggered via URL query string parameters? As per my request here it would be neat to be able to create links (e.g. modal) to a form that automatically show/hide/highlight/etc particular fields.

[dotnetic]

Robin's idea also relates to my request "Show form inputfields according to GET parameter".