LostKobrakai

Hi there, I'm currently starting out with some already quite big projects in cooperation with a partner agency in Munich. There are different scopes of work from rather simple-in-structure content websites to a quite complex SaaS webapp in the pipeline. Therefore I'm looking for possible partnerships with at least one freelancer to assist in these projects, possibly as long-term collaboration. Some proximity to our office in munich would be preferable, but is not required, as is knowledge of the german language. Please drop me a line on the forum if you're interested, so we can get into the details. Greetings, Benjamin

About the off topic issue. I'd just message Ryan. I'm sure he'll add multiple users under a single license as well if needed.

That's not true. $page->render() is not new at all, just rendering a single field was added.

There isn't currently. But as soon as ProDrafts is a thing this should really change.

An easy way could also be using pjax, which does simply replace some container element of the dom instead of the whole page.

It might even be, that parts of the docs are created at a time, where the render() method didn't even have any (useful) options.

I'm wasn't talking about it as replacement of php, but using it with nginx cache or varnish (which rather uses ESI).

Does someone have experience with server side includes? I've not used them by now, but would be glad if anyone could provide experiences especially in combination with processwire.

Yeah. Saving a few keystrokes is almost never a worthy trade to code clarity

$pa1 = $pages->find("something"); $a2 = array(); foreach(){…} $pa2 = (new PageArray())->import($a2); foreach($pa1->import($pa2)->unique() as $p){ if($pa2->has($p)) … else … }

The property sort is nothing magic. It's just a simple integer storing the order of pages in the page tree. But as one can imagine this does only work for sibling pages, because each branches sort values are started from 0 again. You could even use 'sort=sort' to force returned pages to be in the sort order of the admin.

You want to sort by '-parent.sort, -created', but I'm not sure if this is even supported currently.

It's usable (e.g. processwire.com is using it already) but it's still in heavy development, so there aren't any guarantees. You'd make up you own mind if you want to use it. You could always give it a try locally.

So the name isn't actually the trigger of the issue. Are there any hooks attached to this page, which aren't on the others?

Could you temporarily rename this very page and see if it does save?

Exactly. You would even get $settings in template context.

Thanks for implementing my feature suggestions just a week after I posted about it. This will certainly make working with the page tree much more friendly especially to beginners/editors.

You could also add a custom api variable like that. $this->wire('variableName', $obj); In your case it's both config, but if you're adding something different this might even be more appropriate.

Export a site profile of it and post it here or at github. Ryan can then concentrate on fixing it instead of searching for the issue.

Probably was the space after the url. Does work now.

Could you please take a look at this one: https://processwire.com/docs/tutorials/troubleshooting-guide/

The config module does store it's values in a json file somewhere in assets/cache iirc.

I just wanted to add my approach of using a static method on my extended multisite module together with a cached list of domain names: https://github.com/LostKobrakai/MultisiteExtended/blob/master/MultisiteExtended.module#L341-L364