Soma

.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.

Just wanted to note that this module kinda falls apart with recent changes in PW (2.3.5 dev) dates formatting doesn't work anymore/or never had all labels are separated by "," suddenly after updating it would be nice to either integrate something more advanced into core that allows for more control over labels. Ryan? I spent too much time tweaking and debugging with this modules and my own. Images labels, page fields, dates etc.

I just ran into this myself. I can set the language page names when creating a page or in a Pages:added hook, but when using a Pages::saveReady hook it doesn't work. Simplifyed example: in a Pages::added hook it works setting the page names. ... foreach($this->languages as $lang){ $lname = $lang->isDefault() ? '' : $lang->id; $default = $this->languages->get("default"); $time = time(); if($page->title->getLanguageValue($lang)){ $page->set("name$lname", $time . "_" . $page->title->getLanguageValue($lang)); } else { $page->set("name$lname", $time . "_" . $page->title->getLanguageValue($default)); } } $page->save(); After page is created and in a Pages:saveReady hook the following only sets the default page name, the alternatives stay untouched. ... $page->of(false); foreach($this->languages as $lang){ $lname = $lang->isDefault() ? '' : $lang->id; $default = $this->languages->get("default"); if($page->title->getLanguageValue($lang)){ $pageName = $prefix . "_" . $page->title->getLanguageValue($lang); $pageName = $this->getUniquePageName($page, $pageName); $page->set("name$lname", $pageName); } else { $pageName = $prefix . "_" . $page->title->getLanguageValue($default); $pageName = $this->getUniquePageName($page, $pageName); $page->set("name$lname", $pageName); } } $page->skip = true; $page->save(); The values for the $pageName are all correct but nothing seems to work. Edit: just changed the hook to Pages::save, and it works now... no idea why

A bit more information would be good. What does the error logs say? NO that cache is just to store the json feed locally instead of loading it everytime. But has nothing to do with the rest of PW.

This also seems interesting as maybe also seen: http://madebymany.github.io/sir-trevor-js/

I'm trying to find pages by name. I can't get a page by using it's alternative page name. Assume it's the same page: $p = $pages->find("name=namefor_default"); // this works as normal $p = $pages->find("name=namefor_german"); // this doesn't Doesn't matter what language the user is viewing. Also trying to do something like "name$langID=blabla" just throws error that name1013 isn't a field. I tried all different things but no chance. This makes it kinda hard to build multilanguage page structures that would require to find pages using the path or name i.e. using urlSegments etc. Edit: Only chance seems to use "path=/de/full/path/to/namefor_german/".

Thanks adrian, it's that color picker swatches below the colorpicker stopped working. When clicking nothing happens. THis is with the new theme and after changing back to teflon or old default it works, and there's no obvious reason. I haven't tested in the latest as I simply have no time.

I just pulled the latest version and I must say it seems falls apart for me in various parts. :/ It seems there's a lot of changes that make custom modules not work anymore or have side-effects in some way. I have noticed that now the page tree labels are separated by "/" or "," and using custom page list markup module I now get "," all over. Before latest update: After latest update: Also as mentioned earlier my color picker field stopped working partially with new version and given up on it trying to find the issue (nothing obvious and have no bandwidth) Also after changing to the new admin theme on a complex site I'm working on with multilanguage I changed back after 5 min to my teflon as it's so loud and "messy" I can't work with it. The old default theme still seems a lot better. I'm sorry to say this and appreciate all the work Ryan put into this. But it really all worries me a little not only the admin theme, but also that there's changes done now that seems to break some 3rdparty modules and I'm a little worried. I'm sure only some are affected but still there's now troubles ahead maintaining all those that do break. After all I know there's some transition happening now and it's the price to pay for using latest dev, but I have no choice as to some bug fixes are only available there especially for multilang features.

Make sure you have a trailing slash at the end of the url.

$lalias = "the-name-of-the-page-in-english"; $english = wire("languages")->get("english"); $lalias_name = wire("sanitizer")->pageName($lalias); $page->set("status$english",1); $page->set("name$english",$lalias_name); $page->save();

Actually you need both of these, urlSegments to render those pages on a different level, and the hook is just to conveniently modify the path (esier than manually createing them). I don't see where duplicated content is a problem. EIther use canonical urls, or take care of it with a redirect or some hooks. But if you never have links to those (real locations) you won't have them visible anyway.