tpr

InputfieldURLChecker This is a tiny module to add a URL check button to InputfieldURL. It's live, meaning that it opens what you just typed in, and visible only if the field is non-empty. It's as unobtrusive as can Modules directory GitHub It would be the best if something similar would be built-in to PW. There will be probably some tweaks and settings in the future. Suggestions welcome (even for module name).

Have you tried tweaking php settings, eg. max_input_vars? See for example https://processwire.com/talk/topic/8345-deleting-large-number-of-images-silently-fails/

And PW would be spelled as ПроцессШире

Base: There's scss also recently: https://github.com/matthewhartman/base/tree/master/src/scss v2.5 was out just today with a major class name changes (cite: "I also renamed all the grid classes, containers, etc to all be consistent.") Pure: it was a negative surprise to see that there's no grid offset and push-pull features. Fortunately there are unofficial additions to overcome this but it should be part of the framework imo, at least in a modular way.

PW recognizes standard PHP date strings as I know, so this should work: <?php $events = $pages->find('parent=/events/, date>today, sort=date'); ?> https://processwire.com/api/selectors/

Create another template to those pages and edit the template. Then go to the Files tab and specify another file in the "Append file" section. Plus you may need to tick the checkbox to disable automatic appending of _main.php.

Thanks all for your thoughts, I like this topic! There's surely no "the one" CSS framework. In fact each project may require another fw that fits. Larger projects may benefit of large fws with extra stuffs like carousel, lightbox, etc, while a very simple one requires only a grid and some helpers. Here are my findings with some fws: Fluidable It's only a small grid system but sometimes that's all I need. There are many similar out there, I found this one first and it worked fine. UIkit I liked it much but of course I had to manually tweak things here and there. Unlike other large fws I like its feel and design. Foundation I used this only in a few project but always felt it's too much. Usually I don't participate in projects where such a big fw would be beneficial. Bootstrap That's the de-facto CSS framework and if you do frontend you can't avoid it. I won't start a project with it unless I have to, but I manage many sites where it is used. Most of them are using only its grid and the menu component but they are pulling the full fw. Base That's the one I use the most. It's a grid and some nifty helpers. I started with v1 back then until it turned out that it's not mobile-first. This was fixed in v2, now it's a great starting point. It doesn't have any extra (js) components but that's good - I prefer doing such stuffs with 3rd party plugins. Pure I'm trying this out right now. It's really tiny and works fine so far. I'm not sure I will use it in the future instead Base, time will tell. What I would really like to see is some kind of class name standardization. Almost all have different namings (e.g grids), so it takes some time to get in picture when switching projects.

Seems like a module is about to born

This seriously made me think of creating a minimal template to wp-* URLs saying "This page was intentionally made without WordPress."

I guess you could set a common (empty) file as template file using a hook but maybe I'm wrong. Otoh there are so many files in the system you will never use, why bother with these?

Room for improvement?

So true! He's possibly a before hook on topic::render

Actually it does. I've sent you a PM with a live link.

I just made one which works well, the only thing it doesn't do is multi-level items. What's your preferences?

Yes, that could be an optional checkbox, though it won't help me too much but perhaps more useful to others. I thought about duplicating the original file ("filename.jpg.original" or something). This would almost duplicate the storage needed but original images would be kept.

Two WiP images: I planned to add only auto-optimize. But if you don't start using the module when starting the development then many images will remain unoptimized, requiring manual optimization. So there's a bulk optimize feature which works, though it can be really slow. I may take the effort and add a "stop" button but I don't want to overcomplicate this thing. Currently it overwrites original files, which is dangerous, I know. Should it create a backup of the images? Any suggestions on how? I also plan to add an exclude (or include?) list feature, just to make sure. Which one would you recommend (if any)?

I feel your pain! Prepare for the worst

That would be out of this world! Especiall this feature: (just checked the date and no, it's not April 1 )

I would set up the structure similarly, and set the relations on each item individually with two new Page fields ("parent organizations" and "members", for example). Of course this setup needs individuals to be put under parent "ind", and organizations under "org". If you are concerned with how to find members of an organization or vice versa, you can use the Finder.

Why is the first post absolutely unrelated with the topic title?

My best bet is that he is Siri/Cortana or he is collecting info for his dissertation/article/whatever. The only positive outcome of this topic is WillyC's post informing us that google search is also on WP now

Sure! There are some minor issues I'm aware of that needs to be eliminated, plus creating some (very) basic admin settings to it. Mass optimizing could be an issue with many images but that's something I will ignore in the first round.

Great, thanks! Seems to work fine. $thumb = $event->return; It was the turning point, so it catches the output for further process? Hadn't thought about this.

I'm unable to find out how to hook the process of creating image variations. I would like to use resmush api to optimize images. I'm using the service successfully on adding images using $this->addHookBefore('InputfieldFile::fileAdded', $this, 'optimizeImage_InputfieldFile'); and I also added a new optimize() method to image fields that can be used like this: $page->image->size(100,100)->optimize()->url But it would be nice if it could be fully automatic. That is: optimize on upload - DONE optimize on request - DONE optimize automatically if new image size is requested (eg. changing from size(100,100) to size(480,200)) - FAIL ImageSizer::resize seemed the right one but it returns only "true" and I can get only the image file name in the cache dir. What I would need is the final image path and final image url. Any thoughts on this?

Nice blogs!