Leaderboard

Just created a PR in case you don't get notifications ? https://github.com/adrianbj/TracyDebugger/pull/77

Hi @jon9china Nothing special to switch domain. Just remember to edit your config.php file and change $config->httpHosts to your new domain. $config->httpHosts = array('yournewdomain.com'); Gideon

Late response I know, the recent message triggered the notification for this thread!... But I don't think you need a hook for this. The new version of this MarkupSEO allows you to set up automatic field inheritance for empty fields. E.g. so meta title is auto populated by page title.

Hi @Lumi There is no ctime field in processwire. Please follow my example or Bernahrd's example and use created instead. Gideon

In recent PW versions it's possible to insert new repeater items at any position, so if your customer wants to insert an item at the top they can click the "Insert new item before this one" button on the first repeater item. See the video at the top of this blog post: https://processwire.com/blog/posts/new-repeater-and-repeater-matrix-features/ Though I'm not sure why new repeater items added this way are not expanded when they are added, so I've opened a GitHub issue about it: https://github.com/processwire/processwire-issues/issues/1596

No. The point about repeaters is to give you the ability to input repeatable content. The sort order in the backend can be but does not have to be the defining factor for the sort order in the frontend. You can either use the sort order of the backend or you can reverse it. Or you can sort by another property (like created timestamp). Or you can filter content etc etc... $page->your_repeater_field->each('title'); // sort order like in the backend $page->your_repeater_field->sort('-sort')->each('title'); // reverse sort order $page->your_repeater_field->sort('-created')->each('title'); // newest first

Almost exactly 6 years ago Ryan released pagination support for ProFields Table and was thinking about implementing this for more Fieldtypes such as Images: https://processwire.com/blog/posts/fieldtype-pagination/ Unfortunately this hasn’t happened yet, so maybe commission a website from Ryan that involves 600 images per page and he'll prioritise the feature ? The first thing I would do to remedy the immediate problem would be to move the images to a separate tab in the page editor. That should keep the loading times down when you just want to change some other stuff. Otherwise, I guess you’ll have to build a custom Inputfield (perhaps without thumbnails) or structure your site differently. Here is a longish thread about turning off the Image field's auto-thumbnails, maybe it has some pointers relevant to your endeavour: https://processwire.com/talk/topic/21112-do-not-create-default-image-variation-on-image-upload/ You could also try using a Files field instead. I imagine the page editor performance will be better and it won’t auto-generate thumbnails. Of course, you’ll have a harder time scaling and using the images in the front-end. Check this thread for more info https://processwire.com/talk/topic/26113-resize-image-manually/

@GradDev, I think it would be useful to have a setting to determine if duplicate items are unset or skipped when adding to a WireArray/PageArray, so I opened a request for Ryan to consider: https://github.com/processwire/processwire-requests/issues/447

Hi @teppo, thank you for the great module! We use it for an internal project where the search function is very important. Actually we have replaced some fields of type FieldtypeTextareas by FieldtypeCombo (both pro fields). Unfortunately FieldtypeCombo is not yet supported by SearchEngine, we have done this temporarily by the follwing lines in Indexer::___getIndexValue() at line 243: } else if ($field->type instanceof \ProcessWire\FieldtypeCombo) { return implode( ' ... ', array_filter( array_values($page->get($field->name)->getArray()), 'strlen' ) ); Could you consider this in your next release of SearchEngine, please? Best regards, Thomas from XPORT.

v0.1.3 released. This version adds options to set a limit to the number of items that may be selected. When the limit is reached the supported core "multiple" inputfields become disabled. It adds an option for the formatted value to be Pagefile/Pageimage object(s) where that would be relevant. And it integrates with the newly released Select Images module to create a kind of "image reference" field. See the updated readme for more detail.

Also worth a look for new projects:

Hey @Wanze What a great module! Thank you very much - I love the flexibility. One update I would like is the ability to use the meta image field as an actual image field, it would be much more understandable for clients rather than trying to find the image URL.