kongondo

RE unexpected string. That has been there since several versions back. I've never been able to resolve it but I know it has something to do with the menu

It should stay there if you are on list view and have a long list. That way you always have the edit panel in view rather than scrolling back up. When you scroll back up it should go back to the normal position. Please see the gif I posted earlier..

@Nukro, Update is same as any other ProcessWire module. However, in this case, we also have to delete the following folders: /site/modules/InputfieldCKEditor/plugins/mmimage/ /site/modules/InputfieldCKEditor/plugins/mmlink/ /site/modules/MediaManager/plugins/ In addition, you need to remove references to the the plugins MMImage and MMLink from any CKEditor field that were using them. Edit the field Go to Input Tab Under CKEditor Settings > CKEditor Toolbar delete references to MMImage and MMLink Scroll down to Plugins and untick mmimage and mmlink Save The update does not write anything; neither to your file system nor to your database. Therefore, it shouldn't affect anything related or unrelated. Better to be safe always, however, so, create a backup of your site first Backup your files and db replace or overwrite the contents of /site/modules/MediaManager/ with the contents of the folder MediaManager-007. If overwriting, remember to delete the plugins folders as stated above since there will be nothing to overwrite them with from the MediaManager-007 folder Hit module refresh Test that everything works fine Acquaint yourself with the latest changes Let your clients know about the changes

@Rudy...request above noted. Will look into it

Media Manager version 007 (released (23/11/2016)) Happy to announce the latest release of Media Manager. Download via your purchase link. Changelog Multi-tagging: Added to the list of actions to apply to selected media. Tick the checkbox to replace rather than append to existing tags. 'Un-tagging' also available in the list of actions. Uploading now possible when in CKEditor context. Settings moved to own menu item. New settings added: Media title format; Handling duplicate media (all 4 media types); Display current users' media only; Media sorting + sort order Replace/Rename/Skip Duplicate media: When new media loaded and a duplicate is found in the library, this setting tells MM what to do. If using 'Replace' mode, existing tags and descriptions are preserved. There is also a setting to preserve or delete existing image media variations. @note: Might need a couple of refreshes (browser and/or MM before replacement media is shown). Media Sorting: Set via settings (@see #4). Live Media Sorting: In your Media Manager Library, select sort criteria (dropdown select) and sort order (checkbox). These override the sort settings in 'Settings' (@see #3). List and Grid View: Click on respective icons to switch to list versus grid view. In list-view, the current media (displayed on the right pane) remains in view as you scroll the page. @note: currently there is a bug where your media image will remain fixed at the top of the window when you scroll back up in cases where it is taller than your monitor. Please see this post. Insert Link and Insert Image: Streamlined insert link and insert image in CKEditor. MMLink and MMImage plugins are now obsolete! Go ahead and delete them please. Instead, we use and extend ProcessWire's inbuilt PWImage and PWLink. Code refactoring, bug fixes, CSS fixes. @note: As previously announced, this version is still not yet certified as compatible with ProcessWire 2.8 and 3.X. This means the repeater matrix bugs will still be present. Next version of MM will be compatible with these versions of PW.

Just read your post quickly; parent::init(); in your init method would call any .css and .js files named after the module itself (i.e. your process PageBlacklisted.js )

@microcipcip....not sure if you know that a find call, e.g. $pages->find, p->children never returns hidden pages unless you declare include=hidden etc (@see here: http://processwire.com/api/selectors/#access_control

Welcome to the forums @sreeb. Please have a look at this post (including the gists): Use one of those custom functions (or one of your own) and use PHP logic to throw in your data-dropdown-menu in the first <ul>

Rudy, am totally clueless about what you mean . Please clarify. Selected where? In Inputfield/FieldtypeMediaManager?

Oops, that's $sanitizer->text() in action. Will think about what to change it to.

@vanderbreye. Of course . Remember this is ProcessWire..., the ProcessWire. // This will search even in image variations $media = $pages->find("template=media-manager-image, media_manager_image.description%=blue"); #echo count($media); // first() in our case is always the main image/media. foreach ($media as $m) echo $m->title . ': ' . $m->media_manager_image->first()->description . '<br>';

@Nukro I am hoping next week, or the week after at most. Your client can go ahead and upload images. Updating should not affect existing media.

@vanderbreye, it's created on the fly . Have a look at lines #677-718 and the function makeTable() (lines 60-85) in ProcessMediaManager.js

Tried this? https://processwire.com/docs/tutorials/troubleshooting-guide/

@Nukro 1. List view: Yes, that's on my todo list right here 2. I need to dispense with version 7 first. Then I will look into if/how I can integrate custom filters

Moved topic to Dev Talk as it is not, strictly speaking, a ProcessWire question.

@LostKobrakai.....uh, that's the exact link I specified in my post

Hi @spacemonkey95, I am not sure I follow. Tags are specifically what you need to group media. Creating subfolders (aka sub-media pages) would essentially mean a re-write of the module (unless am not thinking this through clearly). I also don't understand what you mean by starting point? Maybe if you could (graphically, if possible) explain your work flow? Thanks. On the other hand, if what you need is the ability for users to be able to only see the media they uploaded, that I can add easily (in fact I have already tested and it works fine). Basically we would use 'created_users_id' to filter out other users' media. I could add this to the upcoming settings.

Yes, there is a way ...there has been for a while actually. It's called OR:groups $search = $pages->find("template=post|project, (categories=one|two|three), (tags=yes|no|maybe), (connectedClient=1065), id!={$page->id}"); That should find results if any of the selectors in the brackets find a match AND the template='blah blah' and id!=1234 are also true .

Welcome to ProcessWire forums @Jee. Count is also available to fields: $out = ''; $items = $pages->find('template=categories, limit=10'); foreach ($items as $i) { $out .= $i->title . '-' . $i->options_multi_field->count() . '<br>'; } echo $out;

@Ivan Gretsky...not yet, sorry. Hopefully I will brighten your life once again soon-ish...

Quick update guys. Frontend module is ready. I have to update the docs first before releasing it though as with anything frontend, there are security implications if the module is not properly set up. Hence, the need to first prep the docs. Will talk more about how it works later but setting up the selects is quite easy. These are defined in a process module in the backend (think Menu Builder) with caching and validation right out of the box. Hope to release next week.

Just a note...a PW 3 compatible Blog is on the (long? ) way (thanks to contributions form @BitPoet, etc...).

Thanks for pinning this down Rudy.

@Michael van Laar...sorry if I sounded a little bit blunt...Just wading through a ton of 'todos' ...so short on time...Let's hear if there are other ideas on how this could be achieved...