tpr

https://whatcms.org/c/145_ProcessWire The third site (innobloom) is developed by us. The client spotted this and he is very happy now. So do I.

No, filesort is not implemented. Autosize never worked on ckeditor, use the autogrow plugin for that, cke is a different beast Double click on description icon to freeze the tooltip, then you can copy text or click on a link. I believe the button hover issue was always there, even before AOS. I tried to solve it but haven't succeed.

If they are on the same server, you can try the P switch, eg. like this: RewriteEngine On RewriteBase / RewriteCond %{HTTP_HOST} ^(www.)?oldsite.com$ RewriteRule ^(.*)$ http://newsite.com/$1 [P] Not sure if this will work, you would better consult a system administrator.

Perhaps it's new Processwire\Page();

I'm not fond of the hover solution, because you would need to hover all items when you are searching for an image. Anyone steroids?

@horst How about this? $skipMinify = $config->debug || $user->isSuperuser();

Do they? Aren't you overriding $page somewhere in your code?

Without visible control it would be less beneficial. What I can imagine is a 3-state control (or more) which changes the bg globally. It could be a small circle which loops through the bg colors on click.

$event->object->filename should work I guess.

Thanks, v034 should fix this. The default admin theme is a bit of a stepbrother because I don't use it so such bugs may come up more frequently there. I also got rid of a z-index renumbering issue coming from sass but this doesn't mean there will be no more z-index issues There are some other CSS fixes regarding the layout for the default theme, hopefully I haven't broke anyting. The loader animation should be vertically centered too.

Ok, thanks. It's not the first time I got into this trap, these two modules are easy to mix It seems that EMO also has an issue in what I try to achieve. It adds an inline script at the bottom that tries to call a function which is unavailable if I load the module's JS manually. It seems that there are two PMs to make :)

A minor feature request: make the loading of the JavaScript optional. This could be achieved emptying the script_location field, but the module uses the default value when doing this. I load the JS dynamically using JS, that's why I have a need for this.

Do you have "return $out;" at the end of the function? If not, is there any generated markup? Or is any js or 404 error in the debug console (browser Inspector)?

Nette Forms: I have a very beta module of it. It doesn't have a UI to build forms and I don't plan to add such so it may not suit for everyone. I can send a copy to check, though as I wrote it's not quite ready for production.

Try this: foreach($albums as $album){ // if there's no thumbnail no need to do anything if(!$album->thumbnail) continue; // save srcset tag to a variable $srcset = $album->thumbnail->srcset('thumbnail', 'lazyload my-class inline-block', array('quality' => 80)); $out .="<a href='{$album->url}' class='item {$album->thumbnail->tags} {$album->thumbnail->orientation}'>"; if($album->images){ $out .="<img $srcset alt='{$album->thumbnail->Alt}'>"; } $out .="<div class='item-info'><h3>{$album->title}</h3><h4>{$album->thumbnail->tags}</h4></div>"; $out .="</a>"; } It's written in browser so double check the syntax.

Plus you check for $album->images and then use $album->thumbnail, so one if them may be invalid. You may also check for $album->images->count() if there can be more than one image in the field (and the field name may be "thumbnail").

No, your $album->thumbnail seems NOT to be an image object. Is thumbnail a valid field? if so, if it's set to hold multiple images, try $album->thumbnail->first()->srcset...

What variables are you missing? The function seems OK to me. Do you have a return $out at the end? Or do you have an error when running this?

@adrian I sent you a PM with some additional details about these new panels.

Ok, made some progress: MailPanel.inc: foreach'es in formatEmailAddress and formatAttachments methods suppose that arguments passed are array but that's not always the case so the Mail panel shows an error. Converting them always to arrays solves this: if(!is_array($addresses)) { $addresses = array($addresses); } Intercepting Pages::save work in non-ajax mode, however, there's a blank screen after submission, is that normal? Edit: removing Pages::save makes the Mail panel disfunctional. I guess the info is lost in redirect then because when intercepting the redirect doesn't happen.

Thanks. I think there should be something extra to be added to the Ajax request to be catched by Tracy. What if someone tries to intercept WieMail::send? Wouldn't it replace the Mail panel's functionality?

Looks nice, thanks! I have a problem here, no emails are catched. I use WireMail and while there is no emails sent, the panel is not showing anything. I have an unusual setup for forms, using my own module and Nette Forms, plus using vanilla JavaScript instead jQuery. However, I can switch on/off ajax submit, but in neither modes show anything in the panel. I don't even get the second ajax bar below the default. Detecting ajax was an issue before ($config->ajax didn't work), but setting 'X-Requested-With' in JS solved this. In no-ajax mode there is a redirect going on, maybe that's why there's no catch? When I disable the Mail panel emails are sent right. I also removed all other panels just to make sure. I guess I'll need to let you my PW install to check things, let me know if you need this. As for the Interceptor do I need to trigger Pages::save manually just to make it work? In my module I don't have such hook by default.

Just what the doctor ordered! I'm sure I'll have some cosmetic requests but at first seems very nice.

Have you encountered any JS errors with AOS?

I haven't had the chance to know PW 2.1 so bear with me Well I don't care if something should belong to the core or not. If I need a feature that I can solve relatively easily with CSS/JS to simplify my admin life, I'll do it. If it makes itself into the core I'll happily remove from the module. But it's unlikely that these feature will be part of PW within months or even years, and I need them now. Even the admin themes don't change too rapidly so I have time to fix the errors. Apart from these it's fun to play with this @grimezy download the latest from GitHub, the button and matrix repeater issues should be fixed. The latter was present in simple repeaters too and that was already covered.