Soma

mydomain.com/login/page/edit/?id=1011 ... is /login/ you PW admin/installation? It's just I'm not sure where template files would be involved in backend editing? This is not possible I think. What fields are they? What data do you enter extactly? The only scenarion that comes to mind is that you enter some data in that last field that is suspicious and maybe some security setting on server does not allow for posting those through a form and you get a 404... But maybe not. Ok seeing the modules list, try deinstalling some of those like Process Page Dele, Modules Manager, HTML Purifier?

What are you missing again? Paths prefixes? you mean like /de/... /en/... ? Those are set on the homepage name.

Yeah that is because it turns on "modal" mode in the system. It's quite tricky/hacky and I don't consider it stable One side effect is the one you mention after install, but if you reload the refresh the admin url or clean out the &modal=1 (not sure anymore) you should see the Pages screen normally as before.

Something like this? https://github.com/somatonic/PageReferenceLink I have started this module long ago but didn't come to finish it and just pushed to github. If someone likes to help out as I'm busy with other projects this could be taken and improved with settings and what not. Or Maybe it is of use for Fredi.

Replace only wire folder and do clap your hands two times. Done.

Ah when saving the page? Of course if you provide more infos so we could reproduce we may be able to know whats going on. And what does the template code have to do with it?

PW fields have nothing to do with 404. Its a page not found error page that always comes from when entering a url that does not exist or is not viewable.

Yeah nothing special here with get and selector that is not explicit calling a page, it behaves like a find with limit=1. The sorting is something I wondered too, sometimes you have to define sort=sort to get the manually sorted (also with find()), but then it's all normal and behaves as it should. Behind the scenes $pages->get(selector) will call $pages->find() at the end. You can also use $pages->findOne(selector) and will return the first matches page and return a Page not PageArray.

$page->find() or $page->get() does nothing... however if you use a selector in get(selector) it behave different and return first found entry and it's not specific, so include=all or include=hidden will have a effect. But I meant $pages->get(id) or $pages->get("/path/") is explicit and will get the page regardless of it's state, it's a explicit API call.

Grüezi Daniele, you will get access to the form builder support forum once Ryan sees this. I'm not sure what you need to archive, but since the entries are stored as json you can't search for entry fields. If you want to use API to find entries you need to store them as pages. You can access the entries in DB through $forms foreach($forms->get("contact-form")->entries->find() as $e){ echo "<p>{$e['e_mail']}</p>"; }

get() will get the page regardless of its status. It's a explicit call. $pages->get(5766) will always get the page with id 5766 whether it's hidden unpublished or red or blue. So include=hidden won't do anything here.

I pushed update to github pages, but it's still not updated... give it some time...

Just updated Captain Hook to 0.2 with latest dev version (+14 new entries) Enjoy

@marty, just read this and I thought you don't use images in RTE? However I think with my ImagesManager it would be easily possible to add a image from thumbnails... {image=1023, thumbnail=small}

... and end up in endless loop land. ;-) Better just save the field only $item->save('sort_title') so the hook doesnt get called again and again and...

Well it works. This module doesnt throw 404 so there must be something wrong with the url the item gets from the page field. Make sure the redirect_page is populated with a page that is viewable.

I use modal frontend editing in PW since the beginning. It's as easy as providing a edit link that open in a iframe modal and add ?modal=1 to the url.. I wrote and showed even code example in this thread. http://processwire.com/talk/topic/2382-processwire-setup-and-front-end-editing-made-easy/ Just seems nobody really bothered about it, but go all crazy with this module.

Bad idea. It's not gonna work, because the module code get's loaded by php even before it's installed, once you click refresh for new modules you'll end up with a error for the whole site if php is not 5.3...

Just wanted to add also that this check doesn't work you added for PHP 5.3 as a module will get parsed before installing! I recommend to add notes to all your modules that require PHP 5.3 in big red letters in the thread and in readme's. Its very annoying, and even people said so, bu you didn't do anything to fix it! /rant over

You should also update the modules.processwire.com module version...

There was a thread by onjegolders (?) or some other guy about this subject... just can't find it. Maybe this thread also belongs to development/pub thread?

$config->minify = new FilenameArray(); $config->minify->add("test.js"); $config->minify->add("test2.js");

You just answered the question by yourself.

Horst tha meta data man!

Add a text field to add an alternative sort title to sort by it instead. No other way if you still want to keep it easy with pager.