LostKobrakai

I've a minor suggestion. It would be nice to make the link not wrap between the icon and the text.

Also some people noticed that local installations seem to run slower than server enviroments even with the better hardware/connection. An OS only running a webserver can probably be more optimised than anything local.

Actually Dashboard is the root page (execute()). The default theme does take it easy by just skipping a current page indication.

I'm aware of that, but please double check that. Also this is still a development version, which is not always stable, so please report this as bug at GitHub if you don't find a reason for this behavior.

The issue leading to this is most likely the same as here: https://processwire.com/talk/topic/10302-error-save-pagelistselectmultiple-in-wire-266-dev/#entry97804 Please check all the access / visibility settings for that field as the string of id's is normally visible if you're not allowed to edit a multi select page field.

Vertical rhythm is nice to have, but I doubt that module developers will set their line-heights to fit that rhythm as long as the default admin theme is also around.

Noticed another issue. I've a module with a static navigation via the module .info.json file. Not it's always showing me the first nav item as current, no matter where I click. "nav": [ { "label": "Dashboard", "url": "", "icon": "tachometer" }, { "label": "Projekte", "url": "project/", "icon": "list" }, { "label": "Kritisch", "url": "critical/", "icon": "exclamation-triangle" }, { "label": "Import", "url": "import/", "icon": "exchange" } ]

I don't know if this has changed in the new version, but I noticed, that the line-height is set as absolute value (1.6em) on the body, which should really be relative.

I've not used the Pages2PDF module by now, but you can use the WirePDF module, which is part of the installation, to render any html content you pass to it.

Like all the mentioned modules you named above FormBuilder doesn't submit things via ajax out of the box. In ProcessWire modules try to stay out of the way of their users as much as possible. This means you're free to build the ajax implementation of submitting any form by yourself and just like you need it. The reason you didn't find much about ajax submission in the forum is most likely because processwire isn't enforcing any special way of handling ajax. You could simply try out any basic ajax tutorial you can find on the internet and there will be a way to make it work with this cms. If you handle the ajax part, then you can easily use any of the mentioned modules to do the rest.

@root Please do not post the same questions on multiple threads. Either stay in one thread or open a new thread if you're seeking help for a new problem, but do not post things all over the place.

You can create multiple user templates, since 2.5.14 (https://processwire.com/blog/posts/processwire-core-updates-2.5.14/). I'd use them.

You can hardly use this method, without caching the number of movies by director somewhere in the database. There's no internal counter for pagefield usage, so the only option besides runtime calculation is using a field, that'll hold the number of posts and updates on changes. You should probably use an hook on Pages::saveReady, which does update a "number_of_posts" field in the directors template when you save any post or when you save any director. For initial population of those fields you would need to heavily use uncache to prevent memory overflow, but, together with a not to short execution time, you can once loop over all directors to get initial counts set.

I'm sure pagetable does hook into pages::delete for the exact same reason, therefore I'm quite certain the standart pagefields do so, too.

I'm also using a small module to hook the ace extended module into the "Custom PHP Code" option of page-fields and it just falls back to doing nothing if ace is not installed.

Just noticed your answer by accident, don't know why I didn't see it earlier. I like your idea, but I don't know if this wouldn't be confusing. You're not actually selecting posts, but rather tags, which are used in posts. $pages->find("template=posts, tags=:selected"); That's why I thought a new function could be more appropriate for this, but maybe there can be descriptive enough syntax found to be used by Pages::find. Edit: Looking at it a bit a tad longer it doesn't look as strange anymore. But thinking about the usage, would it be possible to also filter the results of such a query, like getting only tags which are categorized as "tech"? I imagine it somewhat like the sub-selectors.

Here you go: https://github.com/ryancramerdesign/ProcessWire/blob/master/wire/core/Fields.php#L30.

FieldtypeMatrix, FieldtypeJSON or the table pro-field seem to be a good fit.

https://processwire-recipes.com/recipes/activate-all-languages/

You could for example have an user selection, where already chosen users in other pages are excluded. But do this only if the page is the right template as otherwise it'll break the lister selection of the field. So it can get quite complex in this field.

To make this clear a superuser cannot edit the own roles, if that's the case here. It's a security measurement, so that one cannot lock his/her own user out of the system.

Use required_if to make the field required only under the same circumstances as the show_if.

Add "has_parent=/faq/" to the selector.

It should make a difference, as files and images fields are always multi value fields only the output formatting does provide the necessary shortcuts when accessing single image/file fields. As of() is false when saving things you need to handle the field as multi value field.

Or call it like this: $input->post("first-name");