MSP01

It's strange if the JS date picker doesn't work, but I'm glad you found a work around.

It works fine for me. If you don't have access to the Pro Fields forum, maybe try sending a message to @ryan

Just a hunch, but are you using the HTML or JS based date picker? If it's the HTML, then the browser you're using could potentially have a bug. A while ago there was a bug in Safari that didn't let you pick dates in December if I recall correctly. If it's the JS base date picker, I've no idea. Unless you've set the minimum date higher than what you tried to pick.

I see, no that's not it.

What do you mean with the "Header label contains a textarea"?

@ryan What version of matrix do the colored background require? I'm using 5 at the moment and only the last label color applied has any effect and it affects all the labels, not just the one it was written on. I'm assuming it's a bug due to version incompatibility or something of the sort?

The Admin Actions module lets you do this (assuming the fields are not used by a template). It has some pretty helpful features including cleaning up unused fields and templates.

That's a good question. Well I managed to solve it by using combination of different selectors for different cases. It just had me stumped for a while because I wasn't sure what was going on.

Yeah, the selector value is sanitized. I actually made a small mistake in my first post. The actual problem is the trailing zero. These don't work CASE 1 title*=test_7.50 CASE 2 title*=test_7.00 This works CASE 3 title*=test_7.5 So basically if you search with *= and the value ends with zero, you run into problems. Using ~= works fine, but this example is simplified and I'm actually searching for a phrase.

So I'm trying two different selector values, both values exist on page titles that are being searched. CASE 1 title*=test_7.50 CASE 2 title*=test_7.00 CASE 1 will return all pages with test_7.50 in the title. However CASE 2 will return zero pages, even though there are plenty with that exact value in the title. Aside from 5 being replaced by 0, the titles and the search phrases are identical. If I change the dot to comma, both values return pages. I was wrong on this, comma doesn't actually work any better. Why does CASE 2 not work? I tried to do some googling, but found nothing on this. I'm assuming the search being a "phrase" and not a "word" search is part of the issue.

We are in need to have general file management. I am trying to integrate good old Responsive Filemanager (https://www.responsivefilemanager.com) to CKEditor but getting frustrated how to include it to CKEditor's config. Like how to set CKEDITOR.replace and etc. CKEDITOR.replace( 'ckeditor' ,{ filebrowserBrowseUrl : 'filemanager/dialog.php?type=2&editor=ckeditor&fldr=', filebrowserUploadUrl : 'filemanager/dialog.php?type=2&editor=ckeditor&fldr=', filebrowserImageBrowseUrl : 'plugins/filemanager/dialog.php?type=1&editor=ckeditor&fldr=' // or '../../filemanager...? }); Nothing seem to bring it to live into general link. Any hints how to achive this, what I am doing wrong or missing? I bet many other may benefit this too, since general file management is one of the biggest things missing in PW.

Is there any smart way to get image variants (and create them if necessary) when using findRaw? We were thinking of using it to get array of several thousand products instead of using page array for performance reasons, but of course getting images becomes a problem. Is using a regular page array a better idea after all? We will need to turn it into an JSON format after so the page array isn't needed except to get the information out.

Thanks @elabx, The FieldtypeDynamicOptions looks exactly like what I need.

I tried to find a way to reference selected files on a page. It doesn't seem there's any easy way to do this. Is coding a new module/field the only way? Basically what Ryan has made in CK editor would kind of work. Ability to first select a page, and then select multiple files that have been saved under that page.

Images disappeared when they were first reordered and then the page was saved. Actual images are in the page folder but db save did fail with attached error so media field is blank. ProcessWire v.3.0.174. Page uses standard ProcessWire media upload but the field is inside a repeater. No custom hooks in saving process. The images in that page are quite big since the page is basically used as image storage. Any ideas why this happened?

It's a little thing, but would it be possible to create images without the .-pim2- part? Currently: original.jpg becomes: original.-pim2-prefix.jpg I'd prefer if it became: originalprefix.jpg

I've attached two files. First one shows the page reference field working as intented (ASM mode) and the other shows what happens when I remove the page reference field from the page template. If I use autocomplete instead of ASM it's broken even more badly. I also tried the image field in the page template instead of matrix, and there it works as intended. So this problem is related to the matrix somehow.

@ryan Page reference fields added in image custom fields do not function properly in the backend, unless the field is also added in the page where the image is located in. In my site I was using a matrix field before the image, so it's possible it's part of the problem. Simple diagram because I'm bad at explaining things: - regular page --- matrix field ---- image field (with its own template to enable custom fields) ----- page reference field (inside image template) <- does not work properly in backend, unless it's also inlcuded in the regular page template Without adding the page reference field inside the page template, it seems javascript or something like that doesn't load properly and it doesn't function when you click the image open to edit its fields. This is especially true when using autocomplete / ASM select options. It's possible adding any page reference field on the page would fix it, but I only tested it using the same field in both templates. Tested using the latest PW dev / matrix versions.

Hi, I added some custom fields into image using the process descriped here: https://processwire.com/blog/posts/pw-3.0.142/ Now I need to search for pages that have images with certain fields/content in them. But I'm running into a problem. Is it possible to use those fields in a selector? It seems you cannot just go with $pages->find('images.somefield=something') because it throws an error. While I was using the included tag function in image fields using ('images.tags!=') worked but after replacing it with page reference field for better tagging, I cannot get it to function - nor any other field it seems.

Same folder with originals with a prefix/affix or possibly a subfolder. It doesn't really matter to us. The image paths in frontend could be hardcoded to fetch the thumbnails, so PW's image-size()->url wouldn't be needed for that. All we're trying to avoid is making one giant job of creating all different image sizes in one go.

Hi, We have a webstore made with PW, where product images are saved in a custom folder directly from ERP. The image url's would be saved in simple text fields. Is it possible to use PW's image resizing functionality when someone visits the page, without actually saving the images into the images field?

Little feedback on the module pages. 1) Search does not seem to include the header in the results (e.g. searching "Admin Action" does not find ProcessAdminActions module). Is this because there's just one giant textarea field that includes all the text in the main content area? 2) It's not immediately clear what the modules classname is. In the old version it was clearly marked, on the new page you have to know it's the heading on the blue. It might be a good idea to add this in a clear way on the right hand bar or somewhere else where people new to PW will easily find it when they're looking to install modules. 3) Googling for modules will lead you to pages that don't work anymore (https://modules.processwire.com/modules/process-admin-actions/)

@WillyC Thanks WillyC. Does this meaning that PW caches queries (like field is loaded once although it is called multiple times within same page process) even if there is no ProCache or similar in use? Or is this a PDO layer feature? It would be nice if developer docs could cover a bit deeper the performance aspects and best practices relating to queries, PW basic caching out of the box, sql&PDO etc. since it is so easy to use lots of fields that drawn the performance in some point. @ryan

I did some tests (for example made 50 extra calls with variations in a loop) with Tracy debugger on question 2) but had no effect on PDO or Select queries in Tracy, which made me wonder. I don't have much knowledge about PDO layer but I guess its caching queries somehow.

This question relates to optimizing Page object, fields amount and SQL calls, and Auto Join option. In short I need to understand how ProcessWire handles next events: 1. I have a template, which calls for example $page->something->title and this is used for example 2 times in code like if simply ($page->something->title) echo $page->something->title; etc. The field "title" has not the Auto Join option enabled. Is this information loaded in $page object initially or will this fire 2 separate but similar SQL calls to load title, even in same that page and template process? 2. Let's have another example. We have $page loaded and the template has helper functions to get for example some settings value. Now we use this helper function to retrieve value like $pages->get('template=settings')->somesetting. This will fire SQL call I understand? How Auto Join would help with this? 3. Will enabling Auto Join on fields cause some performance issues outside certain Page object (field that relates to certain template that is used by Page) overall, like when site is loaded first time? Thank You @ryan Please can I also have your core developer opinion also here since this has significant impact on how the project code should be structured and this could help many thanks!