LostKobrakai

Admin modules sometimes do run with output formatting of by default (depends on when they are executed), which would explain the behaviour.

Ah shoot, it isn't.

You could hook FieldtypeTextarea::sanitizeValue for that. If it's not a string with [ or { in the beginning, then encode it.

Just remove the minified version and it will fallback to the unminified one. Also enabling debug mode would work, which does automatically ignore the minified versions for the time being.

I'm rather thought about /site/InputfieldDatetime/InputfieldDatetime.js. Not trying to overwrite any settings, but set them, when a timepicker is initialized (otherwise you cannot be sure you're setting the defaults early enough.

Also if you intend to use the datepicker with formbuilder you should edit the inputfield's js file and not use AdminCustomFiles.

If you can install processwire correctly it's probably not an permission issue, but no you cannot add missing permissions to the user running apache and php.

I'd suggest using wireCopy(), but you should also make sure, that php does have sufficient access rights to the sourcefile as well as the destination folder. Edit: Sry, thought this would also be for single files, but it seems it's only for copying whole directories.

Maybe this will work. if($user->hasRole("t1")){ $posts = $pages->find("template=form_entries, created_users_id=[template=user, roles=t1], include=hidden"); }

I just noticed, that the field editor does not switch to those buttonized tabs on narrow screens, like the page editor does. Maybe this can be made uniform. Edit: Shoot, just had my window exactly at the small state after the media query but before all tabs had enough space in one line.

The 404 page is declared as system page in the constructor here https://github.com/ryancramerdesign/ProcessWire/blob/master/wire/modules/Process/ProcessPageList/ProcessPageListRenderJSON.php so there's probably no way currently to extend this exact behaviour besides editing the file itself. But you could hook Page::viewable and try to just disable the view access for that pages if the current process is ProcessPageList.

Not with the core implementation of WireMail, which does explicitly send a extra mail per address.

For a pure php implementation this is probably as good as it gets. I would just use >= and <= to also get 1.1. 00:00:00 and 31.12. 23:59:59 dates. If you've more cases, where you need to work with dates I'd suggest taking a look at Carbon.

I'd the same problem with my composer files and ultimately decided to put everything into the site folder, whereas the templates folder should only hold things that really belong there (php files and compiled js / css files). I found this to be most in line with the already present structure of things. site/ does hold all site specific data and package.js and other files are configuration like config.php.

Maybe have a look into the FieldtypeYaml module. It's saving data in a textual representation and has multiple optional ways to access those data. As aside: There's no inherently "real" field when we're talking about UI. It's just a matter of having an inputfield and some save method to make a UI field real. E.g. all the module settings' forms have their values stored as json blobs and the forms still look the same as others. If you only need a readonly display it's just less work (no save method) and different markup.

That's essentially what FormBuilder and the pro fields Multiplier and Textareas are doing. Just the serialization method does vary.

Updated the module with a newer chosen release (security related) and fixed the hardcoded admin location in the warning about wrongly configured fields. @kixe There's already a warning if you're using a multi-page field with the wrong inputfield (because it changed from the first versions of the module). I've added a note about installing it beforehand. But there's also no * in the inputfield select for the field, which should indicate that the inputfield is not meant to be used for a multi page field.

There's now a permission in the core to handle this: https://processwire.com/blog/posts/processwire-2.6.23-2.7-rc2-translation-features-license-discussion/#new-lang-edit-permission-for-file-translators-that-arent-superusers

You cannot add the constant to the Notice class without editing the core file, but the message method should be able to receive custom flags even if they are not a constants of the class.

No funk on your side: getValues() was the method to get the array without the keys.

You can, as this bit is the name/path value of the homepage, but why putting the url together manually if processwire can do that job for you.

$values = array_unique($pages->find("template=…")->explode("myField"));

It's might be true that images are slowing down the site, but 2.5 s and more time to first byte is definitely not an image issue.