Leaderboard

This week we have some major improvements to our core date/time Inputfield, as well as a new ability to specify your own custom classes for Page objects. Read on for all the details and examples— https://processwire.com/blog/posts/pw-3.0.152/

Love the custom Page classes!

Done! I got issue #1111, neat ?

You can allow UTF8 characters in page names, or extend the default to allow for uppercase letters through the configuration. You need to update two config settings to tell ProcessWire to allow UTF8 page names and whitelist the characters you want to use, as well as update your .htaccess file to route those URLs to ProcessWire. This blog post has a detailed tutorial. I haven't tested this, but if you only want to allow uppercase letters (and no UTF8 characters), it should be enough to add the uppercase letters to $config->pageNameWhitelist. The default .htaccess routing rule already includes A-Z characters, and uppercase letters are ASCII anyway ...

That happens in ProcessPageListRender::___getPageLabel where strip_tags is invoked. So yes, it's a core issue. I'm not convinced strip_tags is necessary here at all since htmlspecialchars is called anyway.

Just had to look something up in the Tracy Docs and found their donation button ? So if anybody wants to thank the guys behind Tracy, here's the link: https://nette.org/en/make-donation?to=tracy Can't thank you enough (Adrian and the guys from Nette) for this awesome tool!

Wow. Thank you Ryan. Great update.

@thomasaull Array merging may help $headers = array(); $header_variables = array_merge($_SERVER, getallheaders()); foreach($header_variables as $key => $value) { $headers[strtolower($key)] = $value; } Since you require in your module PHP>=7.2.0, ProcessWire>=3.0.98 The getallheaders() function is definitely present.

thanks @MoritzLost @adrian I know uppercase chars are bad but unfortunately the client wants few urls in that way as per documentation that I cannot change or discuss... can't do anything about it...

Can I suggest that a better tactic would be to convince the client the uppercase characters are a bad idea ? It may or may not be an SEO issue: https://www.searchenginejournal.com/url-capitalization-seo/343369/ There is of course the issue that Linux vs Windows work differently in this regard with windows servers treating uppercase and lowercase as the same URL while linux treat them as different. Not that I expect the site will move to a Windows server in the future, but something to be aware of. But mostly I think it just looks ugly ?

@Andy I'd be awesome if you could create a Pull Request for these changes ?: https://github.com/thomasaull/RestApi/pulls

YES! ?

This is already possible with two lines of code, so I don't think a dedicated method is needed. $s = $modules->get('InputfieldSubmit'); $s->attr('disabled', true); $s->addClass('ui-state-disabled');

Just for the record, in AOS you can easily add a WP-like page edit layout by adding enabling Add aos_column_break field to create admin columns tweak under Misc (and adding the aos_column_break field to your templates). The gutter between the columns is draggable.