Soma

If your image site_logo is set to multiple files, your code will output the url to the assets folder of the page "/site/assets/files/1/" If your image site_logo ist set to allow only 1 file, your code will output "/site/assets/files/1/logo.svg" If the outputformatting for the page is off, both cases will output "/site/assets/files/1/" So my guess is that on your homepage, somehow output formatting is turned off?

Thanks bernhard for the hint. But this is only in modules and when multi-instance is used. The example here is in a bootstrap where there's no $this. What do you mean by "they are working also in earlier versions" ? As those multi-instance examples like $page = $this->wire(new Page()); isn't possible in 2.7 for example. Or am I wrong?

I wonder why nobody/Ryan answers here.... No it's not possible. I also ran into it. InputfieldCKEditor.module does configure purifier hardcoded with the allowing the target _blank. Nothing else. But the thing is we can configure the Link Editor to use different targets. But when adding a new one like "_parent", it won't allow it as it's hardcoded. In my opinion the InputfieldCKEditor.module should recognize the target config of Link Editor and add those to the allowed targets.

Alternatevely if($page->parent->numChildren(true) > 1){ // true = only visible ones } This doesn't load the children/siblings pages just count.

An File field configured as single (max 1), will by default be a single object on front-end (where outputformatting is on), BUT in the backend where no outputformatting is on the field will be an WireArray, regardless of if single or multiple.

Thanks Adrian for this great module. I had some problem getting it to work. Installed on 3.0.18 and no Debug Panel on front end shown. There were some div but empty, and css js I've seen. The module is using Master(dev) (master is dev?) automaticly and I have PHP 5.6.10. Once I switched to Stable it started showing the Panel on front end. Also wanted to add that some of the panel are cut off on the left side by the screen. Also a funny effect is that the modal of the debug panel are moving a bit towards top/left everytime I click on one to show/hide it.

The modules limit is set to 350 currently. But there seems to be more than that already. If I set the config to 400 Tracy shows up. There's a hard limit on the webservice in modules.processwire.com for how many modules can be listed in one go, but can't remember how high Ryan set. ModulesManager would need some recoding regarding the limit, but haven't got time and a good idea how to handle it using pagination. However it's always possible to use the built in module installer.

There's a data integrity check available under "Action" tab when editing a field.

PW aborts the page in a case the page isn't viewable or not found and renders the 404 instead. A 404 is never a redirect to the 404 page. A 404 always stays at the requested URL and sends a 404 header instead. The rendering of the 404 page does a $page->render(), thus calling the init.php again. That's why you should include() a functions php with required_once() or alike to avoid redeclarations.

Your solution does output an UL for each subchildren page...

What do you mean by disable? Some of them seem to need links to work. There's many approaches to archive something like outputting different markup for items. For example the xtemplates 'xtemplates' => '', // specify one or more templates separated with a pipe | to use the xitem_tpl and xitem_current_tpl markup 'xitem_tpl' => '<a href="{url}">{title}</a>', // same as 'item_tpl' but for xtemplates pages, can be used to define placholders 'xitem_current_tpl' => '<span>{title}</span>', // same as 'item_current_tpl' but for xtemplates pages Or a hook might do it.

That's the jQueryDataTable plugin loaded in PW for easy use, so not every module that needs jQueryDataTable would have to include it. What you wanted was this earlier ajax implementation in PW I did before that: http://modules.processwire.com/modules/data-table/

What about leaving the outer_tpl => "||". Then add the first ul and the first li yourself? Do you mean the "parent" class that gets added by default to all active parents?

Even if required it's still possible to empty a field and save it.

As with most code in this forum this is not real and best practice code as macrura also points out. Once there's no image it will fail. Also body I asume is a RTE field and will have a <p> already.

I'm planning to support ProCache and AIOM. But not sure I want to mess at all with image variations. I also don't see that as a cache and think the developer should take care of that depending on the project.

Nice error log with all the info's..m

Thanks for the hint, it's fixed. I thought I tested the link! Considering this module and future development of PW. Yeah, I was playing around with that yesterday, but couldn't see a solution. Unfortunately I knew this would one day lead to complications. :/ After little experimenting I think we need to rethink $page->url rewrites Multisite does in the admin and consequently in the front-end. I always feared it was maybe dangerous/adventurous and would lead to problems sooner or later. There's so many things to consider it's crazy. So, after long thinking and testing, I'm heading towards letting the $page->url alone, to not get in the way as much as possible. Then we just have to make sure 2 things: 1. when an url is viewed containing a "domain" in its path that is recognized, to redirect the correct domain/url. So a view link will just work. 2. to have correct url on the front-end output, we can parse the $page->render() output and replace/fix those urls output from templates and RTE's. This way such new features like the "View" options work out of the box. Also cross Domain linking in RTE would work also. I got a test version working so far but not sure about what to further consider with this new approach.

Bea, thanks so much for your work here, very appreciated! I pulled the R. https://github.com/somatonic/Multisite/tree/dev I'll have a go and add a note on the first post. Sorry for the confusion.

Just to make sure, this doesn't have anything to do with roles, you can't save anything else too? Well I don't know, since the message shows up, the problem lays right there. Maybe somehow your host resolved is different than what you enter.

I'm not sure but I think protocol isn't needed here (http/s).