Soma

This module can't be installed with ModulesManager as it says it's already installed due to the class name being the one in the core "ProcessLanguageTranslator".

$new_page->getInputfields(); will get the inputfields in context of a page already and thinks there's images or tries to access them, but there isn't. This has come up a a few times but can't find it. FormTemplateProcessor module by Ryan does the same and suffers from the same problem when using file fields (it's not meant to work with it anyway) https://github.com/ryancramerdesign/FormTemplateProcessor/blob/master/FormTemplateProcessor.module One way around this would be to create the form not using $page->getInputfields() but $page->template->fields and use it to get the inputfield foreach($page->template->fields as $field) { $inputfield = $fields->get($field->name)->getInputfield(null); }

This is on a 13" MacBook Pro on Chrome FF Safari The problem seems * box-sizing: border-box and the 100% width height of image. When I turn off the box-sizing the image stretches itself back to normal size. I don't think it's a good idea to use * for stuff.

Delete them with $pages->delete($c, true) Look on cheat sheet...

I don't think there will be one very soon, it requires also to update the inputfield, link and image plugin to work with new TinyMCE API. I haven't looked into in closer but would be quite a long task including inline editing etc. Ryan and others including me are very busy ATM so don't expect to happen very soon, unless someone else takes a stab at it.

Nothing works even setting the span to have the padding and make the full area of the button, so it's like a bug of the button and span text inside. When clicking with the pointer right at the top of the button text it still doesn't work. It's only like 1px range, but I so often hit that spot that it drives me crazy when working and clicking those buttons a lot building a big site.

It's the jquery ui buttons, it's usually generated by js.

I've just put to static and still same. I remember I stumbled over this 1-2 years back and gave up on it after trying to fix it. I think only thing would be to make the buttons different markup and use link or input but not sure what would be best. Edit: The only thing I think works would be to put padding on the span of the button and not on the <button>

Nothing of that works for me here in Chrome. Position relative or not. I tried everything possible. Clicking at the top of the span inside the button doesn't trigger the button, but visually click it down.

I found that at a very specific point on the button the click doesn't work/submit the form. I can click as much as I want and the button gets active state but nothing happens. Very annoying. The span text element inside the button maybe I have no idea. But I'm sure it can be solved.

.ui-slider { position: relative; text-align: left; background: #838688; border: none; -webkit-box-shadow: 0 1px 3px rgba(0, 0, 0, 0.6) inset; -moz-box-shadow: 0 1px 3px rgba(0, 0, 0, 0.6) inset; box-shadow: 0 1px 3px rgba(0, 0, 0, 0.6)inset; display: inline-block; } yep, removing the "display: inline-block" in a inspect makes it work again. The div doesn't have a width that's why it doesn't work. Or adding width: 100%; also seems to do the trick.

ANother thing I wanted to mention is that the buttons sometimes doesn't register the click completly. It's very annoying and it happens quite a lot I have to click again to register. I'm not sure what the cause is, but I remember having this issue with UI buttons a lot (not only here). I'm maybe to fast when clicking and moving away, but it's definately something that breaks the UX.

There's the annoying jump of the content when using the dropdowns fields/templates that is higher than the window, so the scrollbar is enabled and the content jumps to the left. This can be avoided by enabling the scrollbar to show always in the body/html. Something like the body {overflow-y:scroll;}

I just recognized that in the new admin theme, images preview that open in lightbox when clicking thumb are screwed in their size/height. Like the image is display to small in height and streched/screwed. This doesn't happen on other old themes. Also was wondering why the grid view Icon is displayed when there's only 1 image but doesn't do anything but collapse the field. Seems weird to me.

Thanks for trying!

I don't really get what you trying to di anymore. Do you want to not show the page in nav that have checkbox checked or only its children? There is no thing like !children.subfield=value in PW, it's not a valid selector.

selector_field is to define what field or property (runtime) you want to use to specify the selector. Default is "nav_selector" so this would translate to: $page->nav_selector = "yourselector" a) This can be a field on a page, create a text field named "nav_selector" and add it to you template. Now you can enter a selector on pages using this template and the module will take that if it's defined. b) Or you set it on the fly before you render the navigation. Then you don't need to have a text field "nav_selector" added to your templates at all. You just set the property with code. This could be simply a little code you run to set the selector to those pages, in your case those that have the checkbox: foreach($pages->find("dont_show=1") as $p) $p->nav_selector = "yourselector"; In your case I'm not sure what would be the best way to not render children of that page. Maybe something like this: foreach($pages->find("dont_show=1") as $p) $p->nav_selector = "parent!=$p->id"; c) Alternatively this could also work using the options "selector". "selector" => "parent.dont_show=0"; but not sure really this is possible at all

The simplest way would be to modify config of InputfieldTinyMCE using a hook. For example in the admin templates admin.php at the top: wire()->addHookBefore('InputfieldTinyMCE::render', null, 'hookTinyMCE'); function hookTinyMCE(HookEvent $event) { $field = $event->object; if(wire("user")->isSuperuser()) { $field->set("theme_advanced_buttons1", $field->theme_advanced_buttons1 . ",|,code"); } } Or alike in a autoload module. I think it would be time to recive some flattrs from you

So the other editor would see your table and still be able to edit or delete it. To me this makes no sense.

Let me guess you have language support? Im not sure anymore what the problem was but exactly but it bypassed the render function and renders 404 instead so you can't switch language in those cases.

Just wanted to chime in and mention what I've done. I've been working on a new version of this module to support language page names. (mainly speaking only if LanguageSupportPageNames is installed) - support Multilanguage - support for correct view Actions from admin - correct urls within admin - modified locaUrl() to work correctly, coming from LanguageSupportNames module I hope you guys don't mind. I forked the project and comited current version. As you can see there's not much left from the original, but the basic concept is the same. This work was supported and sponsored partly by http://dreikon.de/ with whom I've been doing some PW support work lately. Since it's already some time ago since I made it (meanwhile tons of other work in my head) I just tested again locally with and without LanguageSupportPageNames installed and corrected a little issue. I'd very appreciate if you guys help test this version. And any help or suggestions are welcome. It may not the best code ever written, especially since it's kinda complex I'd be very happy if more eyes take a look. Ideally it would replace the current multisite module and be backward compatible. Thanks You can grab the module here: https://github.com/somatonic/Multisite

This module doesn't work like this. You can't specify "root" pages to build the menu using a find. It works from a "parent" its way down the tree. There's only a selector option to specify what pages would be included/excluded. For simple lists you're better off creating your own code which is very simple in PW.