apeisa

I have new version coming that introduces ability to create new pages. I would be extremely happy to get some feedback about the methods and arguments I am planning. Currently it works like this: $fredi->newPage("templatename", "title|summary|body"); or $fredi->newPage("templatename", "title|summary|body", $parentPage); That would open new modal with title, summary and body fields. By default it creates new pages under the current page, but you can define alternative parent page there also. I have also created ability to set fieldWidths, just add =XX to fieldname and it gives the width. Those can be used both in edit and new page modals. Like this: $fredi->render("title|author=50|summary=50") I want to take this further: defining required fields and also for new pages prevalues and possible hidden fields. This means that simple string based fields definition doesn't fly that far, or it needs some super nice syntax. Ideas?

This gives all you need: http://mqtest.io/ (also build be real superhero - Viljami)

I see there are pretty big changes on that part coming on dev, and it is actually broken on normal page edit too. This addition fixes it on both (Fredi and PW admin): https://github.com/ryancramerdesign/ProcessWire/commit/fbe7c27e0b5f622ebe72b0f7dd05568a7685615c#L17R154

Ah, I finally found it. This is why custom selector stuff fails on FrediProcess: https://github.com/ryancramerdesign/ProcessWire/blob/master/wire/modules/Inputfield/InputfieldPage/InputfieldPage.module#L141 I think cleanest option would be if getSelectablePages() method would be hookable. Any hopes to get three underscores there Ryan?

Nope. There isn't any setting like that. PW doesn't "know" where it is run or not. It can even run at both domains at the same time (granted they are on same server like horst mentioned).

I found pretty rare bug from Fredi and I couldn't think of clear fix for it: https://github.com/apeisa/Fredi/issues/4 To be honest I don't have a clue why $page works when using normal ProcessPageEdit but not when using FrediProcess. Any help?

There is also handy Process modules, that admin uses. See this as a starting point when building your own: https://github.com/ryancramerdesign/ProcessHello

Congratulations Ryan and family!

I think first one is cleaner, but both of those will fail, if you change your page's parent. You could try this also: $pages->get(1234)->url where 1234 is page id.

Works nicely on android. Thanks for sharing arjen.

Somewhere here on these forums is my processuserextended module, which adds role filters and simple search. On mobile now, will post latest version to github at some point.

That is strange

I was asking about the actual songs in the album. There must be something interesting there if other albums work great.

What is the tracklist of that album?

Try processhello module by Ryan and see how simple the custom admin pages are.

Uncomment the line 20: https://github.com/apeisa/CustomPageRoles/blob/master/CustomPageRoles.module#L20 There were some side-effects to that, so test well and good luck

Thanks for the feedback madmax. I am not planning to take this into that direction. I think it would be better to have separate module for that.

I'm getting exactly same error on one site. For me it already knows the page (/http404/). I don't see the stack trace on error emails though: is there other way to enable those than setting debug mode on?

I like it! There is no better way to propose ideas than this Teppo. First: Yes, simple wrapper is definitely needed. I think it should take same params than mail() does - and just like your proposal works. What I am not sure is that if replace hook is way to go here though? Maybe having general config module (or just config.php) where one could select which mailer is used? Also - not sure about this one - but sometimes one might want to set mailer on code level, something like this: $postmark = $modules->get("MailerPostmark"); $mailer->provider = $postmark; $mailer->send(...); That would allow to having multiple provider modules installed and still having control which one get's used (and possibility to use them in different parts of the application). Having this supported in core there wouldn't be any reason not to build newsletter system in PW...

Just add ProcessFredi.css to your module folder and add any custom css you need.

You can add some checking whether to load script & css yourself. I don't want to add that check there since that method is just a shortcut anyway. There is some discussion about column widths earlier in this topic. In short: yes, they are intentionally left out just because ideally just few fields are used and original widths probably don't work in that case. Oh, and thanks trying Fredi and thanks for your feedback! Highly appreciated.

Images and processwire? I think Horst is your man.

If it is shared hosting, then it might be your neighbor who is getting all the visitors, but blocking the road for your house too...

Maybe in beginning of your prepend template (ie. _head.inc) something like this: if ($page->is("template=rss|specialtemplate")) return;

$fredi should work from both, but it might be you need to load $fredi again ($fredi = $modules->get("Fredi")) in your child template. <?php $fredi = $modules->get("Fredi"); foreach($page->children as $child) { echo $fredi->render("body", $child); echo $child->render(); } Code snippet above doesn't show edit links even for superuser? How about changing it to $fredi->body($child)?