Leaderboard

This week the focus has been on fixing various issues in the queue at our GitHub processwire-issues repository. So while there aren't any new/exciting features to write a blog post about, there are a lot of commits in ProcessWire 3.0.110 that fix various minor issues. If you are running on the dev branch, the upgrade is definitely worthwhile. You can review this week's commits in our commit log in the date range from August 6 to August 10. Also a big thanks to @netcarver who is now helping to administer the processwire-issues repository.

thx @netcarver for your hints and your kind words ? btw thank you for taking care of the pw issues repository ?

Why not? Does version_compare() not work for you? Or extracting major and minor parts separately? Or if you only need to have consistency for modules under your control, why not define major/minor versions explicitly?

Thx @Mackski I've done a slightly different approach: You now have the option between three methods: save() show() download() The save() method will return the resulting file urls and paths on success: @flydev thx I've added it to the modules directory ?

Hi Bernhard, I hit a similar issue with the ReleaseNotes module. If you have a look from line 203 on for about 20 lines, you can see how my module handles it. I hope that gives you something to work with. (Ignore line 214 - it's now unused and I'll remove it from the next release.) Best wishes, Steve PS> Thank-you for all the amazing modules you've produced!

You should add this module to the modules directory , it rocks ?

Pushed a little Update for basic support of options fields (using the same sql queries as file fields). But I want to share something I needed today to keep my requests simple and my code clean: You can quite easily join two finders where manipulating the SQL would maybe quite complex: $this->rg->assets->add($this->config->paths->siteModules . 'FieldtypeRockGrid/lib/moment.min.js'); $this->rg->assets->add($this->config->paths->siteModules . 'FieldtypeRockGrid/lib/currency.min.js'); $efforts = new RockFinder('template=effort', [ 'title', // fields ]); $projects = new RockFinder('template=project', [ 'title', // fields ]); $sql = 'SELECT efforts.*, projects.id AS projectid, projects.title AS projectname, projects.project_status AS projectstatus FROM (' . $efforts->getSQL() . ') AS efforts LEFT JOIN field_project_efforts AS ef ON ef.data = efforts.id LEFT JOIN (' . $projects->getSQL() . ') AS projects ON projects.id = ef.pages_id /* projectid */ '; $this->setData($sql); Result (with RockGrid and some JavaScript, of course):

Attention: This is the thread for the archived open source version of RockPdf. This module is neither developed any further nor maintained nor will it get any fixes. Modules Directory: https://modules.processwire.com/modules/rock-pdf/ Download & Docs: https://github.com/BernhardBaumrock/RockPDF Please see the new version here:

--- Please use RockFinder3 ---

- Not that I'm aware, pretty standard stuff, nothing custom. - From the Page tree, hover over the artist, select 'New' and I create the child page. The issue starts from the moment the page is created. - The latest (dev) but this started months ago when I was on the latest production release. Thanks, this issue really has been the devil for me to.

@PCuser, I can reproduce it - very weird. My results were slightly different to yours. I've opened a GitHub issue for this: https://github.com/processwire/processwire-issues/issues/666

With ProcessWire 3.0.98 I can't confirm your bug. How do you create your pages? - in browser or via API Which versions do you use? Process wire and modules What modules do you use? Do you have hooks in place?

totally missed that ? thanks!

Thanks @Robin S

A couple of things Ryan has said: https://processwire.com/talk/topic/26-what-is-the-autojoin-feature-in-the-fields-editor-and-how-do-i-use-it/ https://processwire.com/talk/topic/613-underlying-workings-of-autojoin/?do=findComment&comment=4948

20+ year of web dev and we still on this bs. Best thing that happened is: box-sizing: border-box; Jees, we fly to the mars...

I find it ironic that a product called "webpack" is now touting the advantages "code-splitting"? It's like we're adding layer on top of layer of complexity just to get back to where we started.

I've read that one a few weeks ago and while I like the gist of it I find it horrible that the javascript community just seems to replace complexity with even more complexity. Also such blog posts always seem to be about the technical side of keeping js in check, while I feel the biggest gains can be archived by actually doing less in javascript. I'd like to see some practical advice on how to not blow through kb's of npm packages and still having a reasonable interactive website. Yesterday I tried out shopifys draggable library and even that one alone is like a third of the max. size of bundle mentioned in the article – just for drag and drop

@modifiedcontent Maybe this is similar to and this issue https://github.com/processwire/processwire-issues/issues/650 which was recently fixed at https://github.com/processwire/processwire/commit/a1676b0adb3bb7877d0602e1ab1929fd5aff73d4 You might need to download and update Processwire to the latest dev commit? Hope that helps

I've converted the js here (the original was renamed to CookieManagementBanner.jquery.js): https://github.com/rolandtoth/CookieManagementBanner I found some js parts was not used at all, eg. cookieMonster.cfg.block seems redundant (renamed to blockClass in my version), and the whole updateUi method also because there is no "theme" that uses the ".pwcmb--top_push" class (but correct me if I'm wrong). I removed the latter entirely. I have also made some minor CSS updates, eg. pointer cursor on labels and buttons. Hopefully I haven't break anything but a proper checking is needed (I don't use the module anywhere atm to test).

I've had the go-ahead from @ESRCH and have now pushed this to the module repository. Repository Link