kongondo

Things in a modal window or being processed via ajax are many times notorious to debug. I haven't looked at your code much but have you tried debugging every step in your modal window's code using the console, to confirm values are actually being set correctly? Something like.... $subfiles = $this->input->get('subfiles') ? true : false; $data['message'] = $subfiles; echo json_encode($data); exit;

You will only see it if you are logged in as a superuser, something similar to below. No bug related to this has been reported before. If you are logged in as a superuser and you can't see it, then something went wrong with your installation and its best that you start afresh.

Delete is permanent (be careful with that) deletion/removal of that record (from the database)....trash is well, send it to the trash...can be retrieved later in case you change your mind (unless of course you empty the trash, then its deleted)..... http://cheatsheet.processwire.com/ Welcome to the forums

...and the module will not be updated: As for you question, I don't have an answer.... Edit: Silly me! See much better responses below! Padloper all the way!

Glad you got it sorted. Thanks for the feedback. I will look into the wording of the instructions. The first initialisation page is not the cleanup utility if by that you mean the first step of the install. Nor is the second step of the install the cleanup utility.. The cleanup feature is accessed via a sub-menu within the Blog itself (the Process Module)...

....Not sure how to answer this ....The answer is right there in front of you....you haven't finished installing the module. It is a two-step process. What you are seing there is step two (with very clear info ). Complete that (there is an install wizard button) and you'll see everything there is to see. Please read the accompanying README in its entirety to get the most of this module. A copy is here in github

Hi, Where exactly are you looking for it? You should see it in ProcessBlog, i.e. click on 'Blog' in the Admin menu and you should see it in the page that is loaded. Thanks for using Blog!

What is $block? What is pg? Is the image field actually called 'images'?

Very old topic I know. If anyone is sill reading this....Something similar here: https://processwire.com/talk/topic/11040-visual-page-selector-commercial-page-picker-module-for-processwire/ Working on other related things as well...

@landitus. Have a look at this https://processwire.com/talk/topic/11040-visual-page-selector-commercial-page-picker-module-for-processwire/

Here you go: https://processwire.com/talk/topic/11040-visual-page-selector-commercial-page-picker-module-for-processwire/ @Michael, the above hopefully answers you query? If not, I'll fill in the gaps. @caribou: I'll be in touch, if not today, tomorrow, thanks.

Visual Page Selector Released 31 March 2016 https://processwireshop.pw/plugins/visual-page-selector/ As of 04 January 2018 ProcessWire versions earlier than 3.x are not supported ******************************************************* ORIGINAL POST ******************************************************* Introducing VPS, a commercial visual page field selector. This is a pre-sale closed-beta version. This post is WIP and will be updated now and then. ############################ Many ProcessWire users use the 'one image per page' principle to manage and reuse images across their sites. This works fine. However, for site editors who mainly work with images, especially for larger sites, it is sometimes difficult to remember the pages where particular images reside. This module helps to solve this challenge. Harnessing the awesomeness that is ProcessWire, VPS provides a rich editing experience, enabling editors to search for, view, select, add, remove and delete page-images easily, in an easy to use and friendly interface. ProcessWire Lister is the workhorse behind the lightning-fast searches. Editors will be able to search for images by their descriptions, names, partial names, page names, templates, etc. Current Features Single-image mode Full search Batch add/Remove/Delete Image/Delete Page in page fields Image Browser Selectable pages as per page field settings + Lister filters Grid and List View Draggable sorting Responsive (almost fully ..iframes!) Planned Features Multi-image mode (there are times you want to group similar images in multi-image field in one page; e.g. the back, front and side of a car photo) Configurable CSS on the fly resizing vs real image resizing (image resizing can quickly hog memory) Other as per feedback from beta testing FAQs When will this be available? Soon. How much will it cost? Reasonably priced. Announcement soon. Where will I be able to buy this from? At all fine stores that stock quality ProcessWire products Do we really need another page field/inputfield select? See links below. What type of licenses will be available? Soon to be announced. Can I beta test this? Thanks for the interest but all available slots have been taken. Video (excuse the video quality please - too many takes....) Screens Previous Discussions https://processwire.com/talk/topic/10927-wishlist-select-pages-by-thumbnail/ https://processwire.com/talk/topic/4330-get-image-from-other-pages-via-images-field/ https://processwire.com/talk/topic/417-extending-image-field/?p=6982 https://processwire.com/talk/topic/7073-profield-table-and-gallery/ https://processwire.com/talk/topic/3200-image-management-concerns-is-processwire-suitable-for-me/ https://processwire.com/talk/topic/425-file-manager/ https://processwire.com/talk/topic/10763-asset-manager-asset-selector/

Or a redirect....it can do lots of wonders .. Welcome to the forums

There's also this by Pierre-Luc: https://processwire.com/talk/topic/10517-frontend-password-reset/

Have you tried sort=sort in your find? $projects = $pages->find("parent=/work/, sort=sort");

Docs: Sorting the results of a selector => http://processwire.com/api/selectors/#sort

OK, thanks, let u know soon...

Glad you got it sorted. The blog templates are all for demo purposes. So you can edit them as you please, or even not use them (only using their code as a reference if you are new to coding/PW...). The CSS and JS folders are intentionally not copied over...(as explained in the read me )..

Benjamin, That's what I said (sort of) in my post . CSS not nearly done (the links, the page title, etc...) . Went with your suggestion though, thanks.

@caribou, I have been working on a commercial module that does exactly that (minus the thumbnails in the selected pages list). It is nearly done. A few things remain, such as the CSS. See screenshot below for a (unfinished-state) preview. I will try post a video demo later today. I'll be looking for beta testers so might PM you if you are interested. Thanks.

Hi roblgs, Welcome to the forums and PW. Apologies for not getting back to you sooner. Sorry for the 'bad' start with the Blog module. The SQL error you see is something that started happening a couple of PW versions ago. It is safe to ignore it; just reload the dashboard and it will go away Blog automatically installs both MarkupBlog and ProcessBlog, although you may uninstall the former just fine 404s usually mean something wrong with your setup (server). URLs not being found where they are expected to be. I really doubt it has anything to do with Blog per se, but we are still going to help you Do other ProcessWire pages work fine? (Home, About, etc?) Is this a sub-domain? Is your install somewhere we can view it? (i.e. not a local install) Long shot, but try installing using the 'blank profile' Let us know how it goes.

You could filter them out in a temporary array...e.g. //example code $interests = $pages->find('template=poi, interests!=""'); //method 1 foreach ($interests as $int) { foreach ($int->interests as $p) {//interests is a multi page field; PW returns them as objects $array1[$p->id] = $p->title;//overwrite duplicate ids in the array key } } //method 2 foreach ($interests as $int) { foreach ($int->interests as $p) { if(in_array($p->id, $array2)) continue;//if we already have that id, skip it $array2[] = $p->id; } } //testing echo '<pre>'; print_r($array1); echo '</pre>'; echo count($array1); echo '<hr>'; echo '<pre>'; print_r($array2); echo '</pre>'; echo count($array2); Above are just examples. You could even store objects in the arrays, or create a temporary WireArray and store them in there. WireArray and PageArray docs: http://processwire.com/api/arrays/ Btw, the above code will not do the counting you want. That's easily doable as well... Edit: Reading your question again, this is probably not what you want...Oh well, code stays though..

Look at my code...that's an in-memory sort (i.e. the sort is happening outside the database, after the items have already been fetched). In other words, and I should have been clearer, sort within the selector is not working for me either, just as you described

Haven't looked into the implementation yet but you are right; it seems not to be working. However, sorting the PageArray itself works for me, i.e. $pages->find('template=basic-page')->sort('-published'); Not exactly what you are after, but just thought to point that out...