ryan Posted June 14, 2019 Share Posted June 14, 2019 ProcessWire 3.0.133 adds a useful new $page->meta() method for a new type of page-specific persistent data storage, adds the ability for users to create their own bookmarks in Lister, and has a handy and time saving update for the asmSelect input type. Read on for all the details, examples and screenshots— https://processwire.com/blog/posts/pw-3.0.133/ 14 2 Link to comment Share on other sites More sharing options...
markus_blue_tomato Posted June 14, 2019 Share Posted June 14, 2019 $page->meta() is great, I will use it in the coming version of https://modules.processwire.com/modules/elasticsearch-feeder/ 3 Link to comment Share on other sites More sharing options...
Tom. Posted June 14, 2019 Share Posted June 14, 2019 Hey @ryan, Just wondering if you saw my update to the WebP functionality? https://github.com/processwire/processwire/pull/145 1 Link to comment Share on other sites More sharing options...
Robin S Posted June 14, 2019 Share Posted June 14, 2019 @ryan, thanks for the new features! In the past I've worked on modules that needed to store data for some pages and I had to create a custom DB table for that - the new page meta feature will avoid this and make module development easier. Regarding the Lister bookmarks feature, it would be nice if bookmarks were able to store filter rows where the value is empty. This is so that a bookmark could include rows that don't affect the results until a user enters a value, but are sitting there ready to use when needed. At the moment any rows without a value are not stored in the bookmark. I know that achieving a setup like this is possible with a Lister Pro instance or with a hook for the core Lister but it would be nice to have the option in Lister bookmarks too. 6 Link to comment Share on other sites More sharing options...
markus_blue_tomato Posted June 15, 2019 Share Posted June 15, 2019 I had some use case, were I have to show some data from my $page->meta() to specific users in the admin panel while they edit the page. I used FieldtypeRuntimeMarkup and created a field which makes only the output of this meta values. It works well. 1 Link to comment Share on other sites More sharing options...
bernhard Posted June 18, 2019 Share Posted June 18, 2019 On 6/14/2019 at 9:37 PM, Tom. said: Just wondering if you saw my update to the WebP functionality? https://github.com/processwire/processwire/pull/145 https://github.com/processwire/processwire/pulls There are still pull requests from 2016... Please @ryan could you take a look at the PR repository just like you did with the issues over the last weeks? There are many simple ones that really just need to be merged (like https://github.com/processwire/processwire/pull/143/commits/80aa0ac2e6383b32a4d0a932d5bec78a8fb5bf14 ). It's really frustrating if one tries to contribute and this contributions just seem to be ignored ? 4 Link to comment Share on other sites More sharing options...
wbmnfktr Posted June 4 Share Posted June 4 I'm just in the middle of rebuilding a website and started to move around some fields and made use of more modern solutions like Combo fields. Doing so I created a field called meta. A few moments later it felt wrong and I remembered that we have $page->meta() now. Shouldn't there have been an error while creating that field? Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now