Soma

Looks expected to me. The template!=rss|home doesn't affect root page, only the children. It's the starting point, thus it can't ignore it.

Ah I was just trying I mixed it up with not showing cache in proache for non logged in users, cause sometimes even logging out leaves the wire_challange cookie alive thus not showing cached page. I never experience your case and using Chrome and PW a lot though not template cache. But what I experienced also from reports that in Chrome sometimes really strange things happens, like showing a completely wrong image on a cached page, somtimes even a icon from Chrome itself!

Sorry that still doesn't do it for me. Still same. If I need more than 5 min to even imagine what you trying to show/say I can't help. Also show some more code like what is $options etc. Just looking at the last "what you get and how it should be" thing, I don't see anything wrong here. But yes not sure I even understand what the question is.

I'm not sure I can follow you in all regards. Trying to decifer what you wrote especially the last sentence. And your post is doubled. Not sure what you mean by ignoring "home" template and what that pages are exactly. And where and how? Anyway just from a glance, a call like $this->pages->get('name='.$this->config->httpHost)) will always return the page no matter what template, status etc. It's like $page->get(id).

@ro-bo Your solution is the only way to go. I'm using same technique on some sites. I don't think it's dirty, this way it's actually pretty flexible, powerful and simple. Edit: But I'm open for suggestions on how such cases could be solved differently.

Well I installed via ModulesManager just today. Looks like I already installed 1.1.2 version. Strange is that it didn't happend on dev install. I just happend on a live install. Kinda not ideal to install a module on a high frequented live site but anyway. I also see that there's actually two error entries of the same. One by me and one by guest at the same second...

Installed this module on dev and no error. When installing on production I got this error: Error: Exception: SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'templates_id' (in /---/wire/core/WireDatabasePDO.php line 191) The module seems to work though. I'm not sure what it is, but I think others reported this too some time ago.

Delete cache and cookies.

No he just needs to upgrade and it should work.

Same as your last thread here https://processwire.com/talk/topic/9637-unable-to-install-language-support/?fromsearch=1 You seem to miss that it was fixed (hopefully) on dev version.

@owzim It's in there by default "parent". See first option https://github.com/somatonic/MarkupSimpleNavigation#same-with-comments

Fieldnames don't allow "-" dash. Cause PHP variable also doesn't.

Just to crosslinking a thread about this already exists, see my response there too. https://processwire.com/talk/topic/8805-slow-admin-localhost/ which I found with search "slow localhost".

Just wanted to mention that this method doesn't allow to use the "Add new" page feature which is based on the family settings of a template.

I remember this a discussion years ago. It's intentional as explained by Ryan for his client project needs - to avoid removing of selected by accident if I remember correctly.

Maybe you should look at source and not inspect with dev tools cause those show generated source by the browser != code sent from server.

Actually both don't work for me. And apart from that an 28MB PDF here?. What's that good for?

It's a very valid question. It's where it can lead to a module mess much like in every module/plugin based system. The kind of: "I have 20 modules that do validation. Which is better, which really is tested and works? Which works for which PW version..." etc.

Thanks for all the praise and feedback. Unfortunately it's a theme that the client wanted and bought. So we are aware of those problems but are not going to change it as the it was never planned and no budget.

I'm not sure. I'm not seeing that here. I wasn't involved on that project so I can't tell if there's something goofy going on with maybe preloading images and critical CSS.

Some time ago we did a redesign and relaunch of http://www.pipistrello.ch/ using ProcessWire. A Circus for children to participate. The design and html theme is wanted and bought by the client, so we don't take credits for that other than ProcessWire work and some small adjustments as was requested.

Same issue as you got here https://processwire.com/talk/topic/5857-using-pages-in-custom-function/?fromsearch=1 and lostkobrakai explained there too ...

@markoj There's plenty of options to handle opening link in new window. But you shouldn't. http://www.smashingmagazine.com/2008/07/01/should-links-open-in-new-windows/ If you still insist. You can for example use jQuery. $("a[href^='http://']").prop("target", "_blank"); Or a hook with MSN to modify item string: https://github.com/somatonic/MarkupSimpleNavigation#hook-for-custom-item-string-new-in-120 $nav = $modules->get("MarkupSimpleNavigation"); function myItemString(HookEvent $event){ $child = $event->arguments('page'); // current rendered child page // any logic with $child possible here if($child->ext_url){ // set the return value of this hook to a custom string $event->return .= "<a href='$child->ext_url' target='_blank'>$child->title</a>"; } } // setup the hook after on "___getItemString($class, $page)" method $nav->addHookAfter('getItemString', null, 'myItemString'); echo $nav->render();

With MSN you just create a dummy page for the external link and add a text or url field to your template like 'ext_url' and then use {ext_url|url} in your item_tmpl.

https://github.com/ryancramerdesign/ProcessWire/issues/1011 What version are you running? That even we have to ask. PLZ always post Pw and module versions. Thanks.