LostKobrakai

Just keep in mind something like this would break it, as keys are not recalculated. $pagearray->remove($somepage);

Nope, but it's kinda easy. // module context $table = $this->modules->get("MarkupAdminDataTable"); $table->headerRow( ["Title", "ID", "Created"] ); foreach($this->pages->find("some=pages") as $page){ $data = array( // Values with a sting key are converter to a link: title => link $page->title => $this->config->urls->admin."page/edit/?id=".$page->id, $page->id, $page->created ); $table->row($data); } // $table->footerRow( $someArray ); echo $table->render();

Ryan stated in the ListerPro Forum, that Lister is not intended to be used in "no-filters" mode, as it's overkill to load the thing for a "static" list. But you can use MarkupAdminDataTable.module, which is quite easy to use and generates the table you see in lister. You only need to fill it with data you'd define. These tables can be made sortable. For filters you would need to have custom javascript or some kind of form, to limit the displayed sites.

I think the hook is the right one, just addHookBefore does force template rendering to wait for your hooked function to finish, while addHook doesn't seem to do this.

Did you do something to prevent timeouts from such big image calculations? The 4k size is not the smallest image for php to parse.

My templates _init.php, but even as I removed that part the rendering of mustache in a appended TemplateFile was earlier than Jumplinks.

This should get you started: https://processwire-recipes.com/recipes/extending-page-save-process/

I've just installed the module, but it seems the redirect is to late and I get a "Cannot modify header information - headers already sent by" error. Edit: Changing the hook from addHook() to addHookBefore() solved the issue.

That's wrong. This are snippets from it's javascript file. I just wanted to know if the textarea it's there, even if it's not visible. function isAddAllowed() { return $('#_' + $ol.attr('data-name') + '_add_items').size() > 0; } … var $addItems = $('#_' + name + '_add_items'); if($addItems.size() > 0) $addItems.val(addValue); But the conclusion is the same, something is blocking the rendering of this textarea. So check if you can add and publish the pages you want to add.

The javascript of the module says that this error icon should symbolize that you can't add pages, because it can't find the textarea I mentioned above. The textarea should have the id "#_{fieldname}_add_items". So you should take a look, why jQuery can't find it, this will at least give you some insight, why it doesn't work or if it's even in the DOM. It actually does add pages in same way my module does. Just copy the name over to the textarea. Only small difference is, that my module does it only once on the form submit.

Maybe check the console for javascript errors as the module does rely on AJAX and copying the new pages in an extra textarea field.

First you'd need to enable this, especially the notes: Secondly, if you'd like to have inline adding instead of this extra textarea, you could use this: Didn't know AutoComplete had this as well. https://processwire.com/talk/topic/8955-inputfieldchosenselect/

Are you talking about me? If so: It would certainly be a intersting thing, but I've a degree in design not computer engineering. While I'm indeed enjoying coding I'm more the one to imagine things and rant on bad ui or ux decisions and less the one to build complex backend systems.

I've seen her tweets about this. It looks great as a small enhancement, but most of the time when I need autocomplete I also need multiselect. So no star for me.

Yeah, just checked it's only safari which does this. I'll send you a small clip, maybe it helps. For the other browsers just a really minor thing. I feel like the animation, which grows the header again to it's bigger size, could be a tiny bit faster. If one is swipping back to top (mostly touchpad, didn't notice it with mousewheel) it feels, like it would slow down the scrolling itself, while you're already on top of the page.

I don't know if you can fix this, but currently it's hard to get the cropping box to the edges of the image, as the borders sometimes doesn't notice the drag end if you're releasing the mouse outside of the image. Top / right seem to work fine, but bottom and left edge don't get it for me. One can always drag the whole box down to the edge, but it would still be nice to have this working in all variations. Edit: @Ryan I can see that you don't want to duplicate stuff. But it would really be nice to have a single interface for editing image variations. This could even include variations generated by the api to be editable instead of just predefined sizes from CroppableModule and/or RTE images. Also now there are two seperate cropping UI's, which could each borrow a thought or two from each other, aside from the fact that just one interface would be easier for the user. Secondly editing api variations would even enable advanced stuff like using the picture element with automatic cropping for different imagesizes, while having the ability to author the crop for e. g. the mobile view afterwards, like showing a tighter crop. With CroppableImage this would only work for fixed aspect ratios.

I don't know about a core api, but there's this http://modules.processwire.com/modules/service-pages/.

I don't know much about the profile. Is RSS included? Did facebook find the feed, as everything else should not matter to facebook. You could also browse the fb apps section for 3rd party tools doing imports. I think there should be a few, too.

You should take a look at mac osx's overscrolling bouncy thing. If this overscrolling is happening while the animation of the header is not finished (e.g. scroll in one stroke to top) the scroll animation gets a shiver.

If you're on a Mac have a look at Tree.

I think this is on purpose. The first row does always provide the link, which does show/hide the edit / view links. I think it was different some time ago, but it didn't feel nice, to be honest, to click the image and have the extra links appearing besides it, maybe even barely fitting in the rows. I really don't remember images in the first row being a good idea.

I've just checked, the module does work out of the box with FieldtypeOptions, so nothing to do for me Edit: At least for the "Interface". Seems like Ryan did not include an option for adding new options from the inputfield by now, like it's for FieldtypePage. The thing I don't like about including it myself is, that I can't really guess a value for the field, while this would give the ability to change the wording afterwards, even if it's only a typo. Maybe we should first ask Ryan if he could implement a standartised way for auto values, then it would be easy to include a "add option" field like for pages. I'll open a feature request over on github.

$page->fields->countries instanceof Field // true That shouldn't be the problem, but there's this in the module: protected function _getField($field) { if(!$field instanceof Field) { $_field = $field; $field = $this->wire('fields')->get($field); if(!$field) throw new WireException("Unknown field: $_field"); } if(!$field->type instanceof FieldtypeOptions) { throw new WireException("Field $field->name is not of type FieldtypeOptions"); } } public function getOptions($field) { return $this->manager->getOptions($field = $this->_getField($field)); } _getField() should error if it's not a field, but the error comes from SelectableOptionManager::getOptions() which is after the _getField() call. So the input is right, but _getField() just doesn't return anything to be used later, or do I miss something?

As mr-fan stated the key here is the FieldtypePage. It lets you link those pages. For your performance concerns, I would say build your code well, use "limit" in selectors as much as possible and let ProcessWire handle the database stuff. It does it very well.