Soma

Enable advanced mode config. Select fieldgroup underneath the fields from the original template instead of adding them again. It then references the fieldgroup. Or have a hook into the page list action to remove or don't allow 'new' from those pages that have certain level.

Just use $input->whitelist(key,value) to store get vars and pager will auto include it.

Or just use $array = wireDecodeJSON($json);

I looked at some things and pushed some changed to 1.3.1, I think you'll be able to do what you need Changes in 1.3.1 Minor refactoring and optimizations Added support for having placeholder in inner_tpl's opening tag. So you can now also add dynamic values to the opening tag like, much like in the item_tpl 'inner_tpl' => "<ul id='{name}' class='drop-down'>||</ul>", That will result in {name} being replaced by the name of the page (containing the inner childs) To hook into the parsing of the the list opening template you can use the "MarkupSimpleNavigation::getInnerStringOpen" and do you're own conditional replacements.

I don't know Bootstrap well and what extraordinary unnecessary complicated data's and id's and classes it needs. Also I don't want to add features just for Bootstrap. I'm not sure I can follow. What Id is needed where and don't now if it's all possible.

no comment

Use $config->ajax see cheatsheet.

How does it come that some files that are translatable are not shown in the select, and since I can't enter one manually after this module is installed I have to deinstall it. For example wire/modules/Fieldtype/FieldtypeComments/CommentForm.php isn't in select. EDIT: Stupid me didn't see that CommentForm.php was already added, so it doesn't show...

You're right. "process" is a field on the "admin" template, to select the module that defines the process for the admin page. So it's simply saying "make the process of this page this module". And yes the execute() is used as the default method to return the content for the admin page, basicly what you see when you open an admin page, for example /processwire/myadminpage/. Further urls segments can be used by adding other executeName() methods, where Name is the urls segment appended to the admin page url. Like /processwire/myadminpage/save/ would map to a executeSave() method in the process module. If it does exists, it will use it instead of execute() /processwire/myadminpage/mymethod/ would map to a executeMyMethod(). I think it's case insensitive.

On an inputfield on front end form you use $f->maxFiles = n

pageStack

http://processwire.com/talk/topic/3551-small-tip-for-pages-that-will-be-used-with-render/

That would be Ryan's task

Sorry, Teflon is currently not compatible for 2.3+/2.4 I think the module page on modules.processwire.com was updated for all in one step and it's module developers task to check our modules. Just haven't come around to make it, I think it would be a good time now Sorry for the inconvenience this may caused. I will update the info. Also ModulesManager need to somehow account for that (installing admin themes in 2.4). Just give me some time to think how and when. Since there now multiple changes going on old and new theme is a big step

$array = json_decode($jsonstring)

A 404 exception will interrupt the render process and render the 404 page instead of the requested one along with a 404 header and url stays the same. So the render of the 404 page in the background calls the _init.php again. When using the prepend file _init.php you always have to keep in mind that it's called on every $page->render() (you might also do manually in a template to render another page). Depending what you do in the _init.php it may cause trouble cause it's called multiple times for a request.

OK ,its was $config->debug = false and it's not enabled. Still I don't consider this feature that useful. I would prefer a HelperFieldLinks type integrated in core.

This install is in a subdirectory. But don't see why it shouldn't work then.

Updated again core and tried different browsers, no luck.

Just a plain install, nothing special, no multilang...

I have latest dev and not working. Chrome here. No errors.

Just tested with a ModulesManager 1.1.1 installed and updated (using ModulesManager) ModulesManager to 2.1.2, no problems. Still wondering what is different, or when this errors occurs and if it has to do with your server, https nginx or whatever. There's hasn't really changed anything of the core stuff just minor tweaks and JqueryDataTables added.

I don't understand. Does this happen when updating, after updating... I don't see any problems and working/worked fine here. I did some changes on 2.1.2 but don't think that's doing anything you see here. I have problem understanding where and what happened, let alone understanding that error as I don't know exactly when it did happen.

I don't see what could be the problem. Did you install JqueryDataTables module too?

Anyone have also problem with that? When hovering over the ">" on a field (right side) it should show the field name beside the field label. Ryan implemented this couple month ago and sometimes it's working and sometimes not. Sometimes it does work for some fields and not others, sometimes not at all. Apart from that, regarding this feature: This is sort of Ryan implementation of what I did with HelperFieldLinks module (one of my first modules). But I'm not really happy about what Ryan did here... It's not helpful at all and showing only the name on hover doesn't help me anything that much, when then I have to go to search the field anyway. It is also hidden feature, so that you don't really get it without knowing it. What I would like is some better solution to see name and a link to go edit the field directly. This should be in core and visible to superusers. Current implementation doesn't really help me, and I still need to install my HelperFieldLinks module, which I'm not really keen about supporting and updating it all the time cause it's broke already a few times. What you guys think about it? Edit: Since Template label can also be different than the template name, I would welcome it to also show the template name along with the template label. So I don't have to search for it.