Didjee

Hi @teppo, are there updates on this that you can share? 😉

I want to exclude pages with certain templates from Insert link > Select Page. Is this possible using a hook?

Hi @BitPoet, I was wondering if it is possible to get this module working in a Textarea Rich Text (TinyMCE) field within a ProFields: Table field? Now I'm getting the error messages below in TracyAdmin. The Table field 'table_directives' has 3 rows with 2 TinyMCE Textarea fields ('medication' and 'remarks') per row. PHP Warning: Attempt to read property "table_directives_0_medication__pages__useAction" on null in .../InlineCompleteTinyMCE/ProcessInlineCompleteTinyMCE.module:267 PHP Warning: Attempt to read property "table_directives_0_remarks__pages__useAction" on null in .../InlineCompleteTinyMCE/ProcessInlineCompleteTinyMCE.module:267 PHP Warning: Attempt to read property "table_directives_1_medication__pages__useAction" on null in .../InlineCompleteTinyMCE/ProcessInlineCompleteTinyMCE.module:267 PHP Warning: Attempt to read property "table_directives_1_remarks__pages__useAction" on null in .../InlineCompleteTinyMCE/ProcessInlineCompleteTinyMCE.module:267 PHP Warning: Attempt to read property "table_directives_2_medication__pages__useAction" on null in .../InlineCompleteTinyMCE/ProcessInlineCompleteTinyMCE.module:267 PHP Warning: Attempt to read property "table_directives_2_remarks__pages__useAction" on null in .../InlineCompleteTinyMCE/ProcessInlineCompleteTinyMCE.module:267 PHP Warning: Attempt to read property "table_directives_3_medication__pages__useAction" on null in .../InlineCompleteTinyMCE/ProcessInlineCompleteTinyMCE.module:267 PHP Warning: Attempt to read property "table_directives_3_remarks__pages__useAction" on null in .../InlineCompleteTinyMCE/ProcessInlineCompleteTinyMCE.module:267

@virtualgadjo putting title and headline before search_index does the trick somehow ?. Now the ordering of the results is the way I want it to be. Technically I can leave title and headline out of de indexed fields in the module settings.

Hi @virtualgadjo, thanks for your quick response! I was using SearchEngine::find() for the results and not a regular ProcessWire selector. Mainly because with SearchEngine::find() you can use "_index_template" for sorting results by template (see SearchEngine module settings). AFAIK, sorting by template is a not build in feature for page selectors. But I found a way to accomplish that: Now I'm using the code below instead of SearchEngine::find() Results are first sorted by the given template order. After that, pages with $query in title or headline will be shown before pages with $query in search_index but NOT in title or headline. $templates = ["news", "blog", "archive", "plain"]; $results = $pages->find("title|headline|search_index~*={$query},template=".implode('|', $templates)); $sortedResults = new PageArray(); foreach ($templates as $t) { $sortedResults->import($results->find("template={$t}")); } $results = $sortedResults;

@teppo First of all, thanks for this great module! I've used it several times already. For a project I'm working on right now, I'd like to sort the search results like this: First based on indexed templates. This is possible with the "_indexed_templates" option, so no problem. After that, pages where the search term appears in the page title should be placed above pages where the search term only appears in the page content and NOT in the page title. Is this possible when using SearchEngine::find()?

Hi @horst, I have a setup where I use a Repeater for page sections. Elements can be added within a section using a RepeaterMatrix. When I use a CroppableImage4 field within RepeaterMatrix, it cannot be used by non-superusers (eg users with the 'editor' role). If the user clicks on the thumbnail to make a crop, they get the following error message: "Not editable. The process returned no content". I have given the user role the "croppable-image-4" permission. If I use CroppableImage4 in a RepeaterMatrix that is not inside a Repeater, it works fine. So I suspect that the problem only applies when CroppableImage4 is used in a 'nested' RepeaterMatrix. See attached screenshots for the error message and to give an idea of my setup.

Hi @teppo, first of all, thank you for this wonderful module! Do you see a possibility that ProFields Table will be supported in the future? I am certainly willing to sponsor (part of) the development costs for this!

@Robin S wow, this is really great! Thanks for spending your weekend hours on this update ?

Hi @Robin S, Thanks a lot for this module! Exactly what I was looking for ? Version 0.0.8. of RepeaterMatrix introduced the 'insert before' and 'insert after' buttons. If I limit the use of matrix types to 1 item per type, it's still possible to add a new item via 'insert before' and 'insert after' (see screenshot below). Is it possible to prevent this?

@skeltern I think this solution of @horst solves your issue.

@horst Your adjustment of the webp() function fixes the issue! Thanks for diving into this!

Hi @horst, thanks for your code example, but unfortunately it still doesn't work as expected. See the attached screenshots below, both of the overview of generated variations in the backend. I made an 'extreme' cropping to show the difference with the original image. 1) The image variations before loading the template with your example code in frontend. I marked the cropped variation with a red border: 2) The image variations after loading the template with your example code in frontend. I marked the frontend-generated 900 pixel width variants with a red border. The JPG version is OK, but the WEBP version is not ? Groeten terug uit Maastricht! ??

@horst I use the code below in my template to generate different sizes of a cropped image: <source type="image/webp" srcset="<?= $page->image->getCrop("default")->width(450)->webp->url; ?> 1x, <?= $page->image->getCrop("default")->width(900)->webp->url; ?> 2x"> <source type="image/jpeg" srcset="<?= $page->image->getCrop("default")->width(450)->url; ?> 1x, <?= $page->image->getCrop("default")->width(900)->url; ?> 2x"> After I re-crop the image in the backend the variations of the jpeg version are regenerated, but the variations of the webp version are not regenerated/showed in the frontend. Is there a way to overwrite the webp variants after the image is re-cropped? Deleting all variations in the backend before re-cropping the image doesn't solve this issue. See also this post (not related to CroppableImage)

Thanks Horst, that works! I need different sizes of the same crop to use in srcset for responsive images. I referred to this in your opening post: