kongondo

Yep, that too ...edited post above, thanks..

Hi @Barido. Welcome to the forums. Glad you find the module useful. That should be fine since MarkupBlog finds the 'main' Blog pages by their IDs (e.g. Blog, Blog Posts, Blog Settings, etc). You will want to backup everything first before attempting that move though, just in case... Cheers, /k

Hey, @microcipcip, welcome to ProcessWire and the forums. I seem to recall that handle

@Nukro 1. Is it possible to save the filter interface configuration (like in ListerPro)? No it's not. But the filter should remember the filters you set up last. The filter interface as it is is generated by a core module InputfieldSelector (even in ListerPro). Saving the configuration bit is something extra ListerPro does and Media Manager doesn't. 2. Filtering tags by words (it should ignore the order) doesn't work as expected. I have experienced some weirdness myself but I probably have an older version of InputfieldSelector. The 'OR' filter has not been working for me, i.e. find image media or document media or video media tagged as 'travel'. It is something am looking into and thanks for raising this. @elabx Is the module compatible with PW 3.x ? Officially, not yet although some people have been using MM in PW 3 without any issues, certainly not files being deleted . I am currently working through a requests queue after which I will deal with compatibility issues @all I was hoping to release the version 7 of MM by next week but there have been delays (external factors, etc) so there will be a bit of a delay am afraid, sorry. Just to remind you what I am working on: Multi-tagging (and bulk removal of tags as well Media replacement (part of a setting on what to do when MM detects a duplicate media is being uploaded ) Sorting media by tags (and sort order) Uploading of media via the CKEditor plugins Bug where CKEditor plugin MMLink is conflicting with PWLink (e.g. takes over double click) List view of media (especially useful when dealing with documents with long file names) A couple of other enhancements (including CSS Fixes) Thanks

@LostKobrakai, I'm not sure @regesh included it. I have seen this problem before, a long time ago, but can't find the relevant info at the moment.. Edit:

Your true is probably being converted to an integer 1. The second parameter of json_encode is $options and it expects an integer representing a Bitmask of JSON constants.

@Gideon So....any reason why this thread is self-titled?

Also...json_encode(array, true) is not valid...That function, does not take such a second parameter http://php.net/manual/en/function.json-encode.php

Is there any reason you are using $_REQUEST['search'] instead of $input->post->search (or $input->get as the case might be)...?

Brilliant!. Exactly what the doctor ordered . I needed something that will run without user intervention (i.e. without the need for web visitors)

Excellent, thanks! Does Pro method mean it will run automatically (i.e. not lazy and does not require, for example, a 'web visitor')?

@DarkwaveSurfer, Please see post: post_small_image only works when the second parameter of renderPosts() is true (like in your case, so it should work...hmmm). Try removing the post_large_image from the options if you are using post_small_image. I haven't looked at the module in a while so I'll need to re-educate myself with some of the options . Have you tried post_small_image => 2? That should display (IIRC) the featured image after the post title.

Welcome to the forums @DarkwaveSurfer, Glad you are finding the module useful. The template would be 'blog-post'. But you already have an image field in that template, so why add another? In addition, Blog already has a featured image feature. Sorry the docs are not up to date. Please have a read from this post forward..You have fine-grained control where to show your featured image, whether it comes from the image field or the RTE.

Welcome to the forums @shango Working on it....no ETA for now though.

@Nukro Changing core files is never recommended. Have you tried to play around with the settings in the module InputfieldPageName as stated in the $sanitizer docs (please see below)? Does that help? That core module is found at /your-pw-admin/module/edit?name=InputfieldPageName $beautify (optional) bool or int Should be true when creating a file's name for the first time. Default is false. You may also specify Sanitizer::translate (or number 2) for the $beautify param, which will make it translate letters based on the InputfieldPageName custom config settings.

Hi @Rudy, Glad that you are liking Media Manager. I have not used that theme before but will look into it. However, it seems @tpr has nailed down the issue to CSS. If that's true, don't know how to get around that since MM plugins don't come with their own CSS files.

@Nukro, what @adrian said. . Thanks Adrian. PW is automatically sanitising the filename in WireUpload.php I wonder though whether this $beautify parameter would do the trick? Never used it so don't know for sure.

And this too http://processwire.com/api/ref/

You could also add the class in its separate .php file and require_once (/path/to/the/external/file/) that file within your module...

Nice one! Seems it's been around since 2.7...so, yeah, newish

Similar to above...this nugget by @diogo has served me well in the past... Also, is there a possibility to do it over the command line?

Thanks @BitPoet...appreciate the work. I have seen the PR...Will get to it when I finally install PW 3.x/2.8 ...hopefully soon.

Thanks. I'll appreciate some backward compatibility though (i.e. I will not be namespacing any of my modules but will let the compiler do its work)...

Your post is misleading (by omission) . For more than 2 years now Blog module has shipped with its own 'clean up utility' hence no need for such manual intervention unless one didn't follow the explicit uninstall instructions.

It will be available...eventually :-)...I have quite a number of modules to maintain so there has to be a pecking order, I am afraid, and my pro modules come first, naturally. I would appreciate it if users could help me by testing and reporting any bugs in the GitHub repo. For instance, I know we have to switch to magnific. Many thanks.