renobird

Hi all, This theme is now part of the core. You can install it instead of the default. Ryan and I are still working on a few minor issues, but overall it should be really solid. Looking forward to hearing what you all think.

Doh! Nevermind. I missed the uninstall this module. On mobile.

Nico, What a great idea! How do you see it working long term? It would be a little weird to leave there for more experienced users, but great to have readily available whenever needed. When you close it, does it disappear for good, or just collapse into a "getting started" header that you can click to reopen?

I love this! Well done bald, you weren't kidding when you said you were saving your post for something special. So good!

BTW, I really like some of the more advanced features in your theme, I hope you continue development. Either as-is or based on a version of Reno.

Hi. AdminThemeReno will be an alternate admin theme available as part of the ProcessWire 2.5 core. (Keep an eye out, Ryan mentioned in another thread we has hoping to soft launch it today). The theme itself will likely stay very minimal (similar to the default theme). You can always fork it and modify it to suit your needs and/or add features.

Thanks Peter. It's been a massive undertaking for sure. It should soft launch soon, and after I've had a chance to actually get it to where I want it, I'll do a case study. All of the really cool things aren't visible to the public. Most of those have been working for a while now.

I think there is just a fundamental difference between what you are looking for in a CMS, and what ProcessWire is. That's not a bad thing. Some people think cucumbers taste better pickled. I currently work with ProcessWire in a University environment (300-500 active users, depending on the number of faculty during a semester). ProcessWire has not only been up to the task, but has far exceeded everyone's expectations. Both from a design/development standpoint, as well as UX for the site editors. One install powers a fairly complex public site (launching in the next few weeks), a faculty/staff intranet, a travel authorization and payment system, a news and events management system that handles around 500 events a semester with dozens of editors, an automated user management system that queries LDAP to determine user access and roles (runs via cron 3 times a day), Faculty syllabus manager (800+ documents a semester, maintained by hundreds of different users). Integration with MailChimp, some basic integration with BaseCamp, user generated forms (powered by FormBuilder), custom user dashboards, etc…, etc… Do you need to know how to code to use ProcessWire at this level? Absolutely. At least a little. In my opinion, that's a good thing. It means you can respond quickly to development needs. It means you can build solutions to suit, and not rely on pre-packed solutions that may not meet all project requirements. It means that you aren't constantly dealing with security patches, upgrade, etc… From a frontend development standpoint it means you aren't trying to work with markup that is bad/dated or has 17 classes on each element. I've been able to accomplish things fairly easily with ProcessWire that I bashed my head against for ages with other CMSs. Are all the typical "enterprise" checkmarks present in ProcessWire? No, but that isn't what ProcessWire is — and I hope it's not something it ever tries to become. At least not in the traditional sense. Depending on your needs and skillset; other CMSs may be better suited. ProcessWire might be a pickle—when what you really want is a cucumber.

Super quick (and completely untested) idea. Maybe you could just add a markup field that shows the related pages? This would happen after the form is built, so no need to have additional fields assigned to the template. Again, haven't tested this, and wrote it mostly in the browser. <?php class relatedPages extends WireData implements Module { public static function getModuleInfo() { return array( 'title' => 'Related Pages', 'version' => 1, 'summary' => 'untested module to show related pages', 'href' => '', 'singular' => true, 'autoload' => true, ); } public function init() { $this->addHookAfter("ProcessPageEdit::buildForm", $this, "showRelatedPages"); } public function showRelatedPages($event){ // page being edited (viewed) $page = $event->object->getPage(); // check if it's a template we want to do anything with. if($page->template == "client" || $page->template == "properties"){ // form $form = $event->return; // build selector to find related pages. // you may want to find the related pages another way, this is just a quick and dirty example. if ($page->template == "client") $selector = "your selector here"; if ($page->template == "properties") $selector = "some other selector"; // find pages based on the selector above $related_pages = wire("pages")->find($selector); // our find returned some related pages if ($related_pages->count() > 0){ // get the markup module $field = $this->modules->InputfieldMarkup; $field->label = "Related Pages"; // label $field->markupText = $related_pages->implode(", ", "title"); // where do you want to insert this in the admin (after what field?) $form->insertAfter($field, $form->get("field_name_to_insert_after")); } } } }

What Andre said. However, If it is possible to populate one autocomplete field with the pages from another—I feel like it shouldn't allow those pages as values, especially since it looks like your autocompletes are populated based on template—it would seem an odd behavior. What happens if you then remove that page that was set from the other field? Would you expect it to get removed from the original autocomplete? Starts to get complicated quickly. Perhaps I'm reading too much into what you are after.

onjegolders, This seems a bit weird from a UX perspective — If I follow correctly: User authenticates with default PW login page. After successful login, user is redirected back to frontend of the site. Why not just create a simple frontend login script? If that isn't an option, then part of what I stripped out of the redirects module I posted in the other thread is a different default page for certain roles. I'll reduce it down to something a bit more generic and post it here in a bit.

Adrian, You are fast. Damn fast.

What do you mean link them? Do you want to have the value selected in one show in the other and vice versa? That isn't possible.

Nice, Glad you got it working. Might be an ever so slight performance improvement by checking the page template before doing anything else. public function redirect($page){ $page = $event->arguments(0); if ($page->template == "blog_post" || $page->template == "gallery_post")){ $errors = false; // check notices for errors before redirecting foreach(wire('notices') as $notice){ if($notice instanceof NoticeError) $errors = true; } // if errors or if no created date is set it means just generated so don't redirect if ($errors || $page->created == 0) { return; } wire("session")->redirect(wire("pages")->get("template=journal")->url); } }

They do save correctly, the hook is after save.

Here is a module I use (I reduced it down to the more relevant bits). Perhaps this will help. <?php class AdminPageRedirects extends WireData implements Module { public static function getModuleInfo() { return array( 'title' => 'Admin Page Redirects', 'version' => 1, 'summary' => 'Redirect to after save for certain template types.', 'singular' => true, 'autoload' => true ); } protected $redirects = array( "news" => "/processwire/news/", "events" => "/processwire/events/", "venues" => "/processwire/venues/", ); public function init() { $this->pages->addHookAfter('save', $this, 'redirect'); $this->pages->addHookAfter('trashed', $this, 'redirect'); $this->pages->addHookAfter('trash', $this, 'redirect'); } public function redirect($event){ $page = $event->arguments(0); $errors = false; // check notices for errors before redirecting foreach(wire('notices') as $notice){ if($notice instanceof NoticeError) $errors = true; } if (array_key_exists("{$page->template}", $this->redirects) && !$errors){ $this->session->redirect($this->config->url->admin . $this->redirects["{$page->template}"]); } } } EDIT: Just wanted to mention that I didn't read your post all that closely, so my apologies if you are looking for something more detailed — short on time.

I guess it just depends on what you need. Hanna codes are great, but nearly as robust a solution as pageTable(Extended). I'm sure someone else will chime in with more details, but good luck whatever route you take.

Hmm. If "check for new modules" didn't clear it up, you can try deleting the module cache files in /site/assets/cache/. Someone else might have a better explanation as to why that's happening. I feel like I've run into it before, but can't remember exactly what I did to resolve it.

unrelated: Jan I love your profile photo - every time I see it I smile.

Try "check for new modules" to clear things out. The update should show then.

Hi Ryan, Any chance you might might convert inline styles to class names in the near future? I'm using formBuilder on a site that has some large forms, and I'm stubbing my toe a little trying to make the forms responsive. I can override the inline styles at a specific breakpoint and make all the widths 100%, but that's a little heavy handed for some situations.

Hey bipster, Entering a title isn't required. Have a look at this thread. https://processwire.com/talk/topic/7477-strategy-for-flexible-content-types-in-a-template/#entry72309

Adrian, I have about 8,000 pageTable pages under a single parent (invasive plant species database). I just consider it a closet that I'm never going to look in. So far I haven't had any issues.

For posterity, and in case anyone missed it: https://processwire.com/talk/topic/7459-module-pagetableextended/?p=72035

Ha! that *wink* should be bigger. BTW, this is so awesome!