renobird

Just read that PHP 7 will throw a TypeError exception now, instead of a fatal error. That is a little friendlier to work with.

I've always had them created before I get this stage, so I'm no real help here.

Gah, I meant to say "If ProcessWire can't create one..." Sorry. My point was that if PW is can't create it, you should create it yourself and then just put in the connection details.

That page is just asking you for the connection details to an existing database. ProcessWire can't create one, you have to do that ahead of time.

Ivan, Can you give us a simple walk through of what you are after? For instance, describe what a user with restricted access might be able to see when they login.

I'm not entirely sure I follow what you are after. Are you looking to create a sub-set of the admin and restrict particular users to just those pages? If so, I can give you some pointers.

This is pretty much why I built one instead. We did some test runs with a few 3rd party options, and they were either WAY too bloated, or just felt ancient. There was one (the name I can't remember) that was pretty good, but it was SaaS and we couldn't integrate all our other systems.

Thanks all. There's really a lot wrapped into this. It connects to a lot more than I'm showing here. The test server doesn't show the other kinds of help desks we have. This one is the IT version, but there are 2 other variants of this system, one of which is for marketing (which has a bunch of additional fields when you complete a ticket). The original tickets are powered by FormBuilder. That way there can be all these ticket variants without having to create or try and reuse a bunch of fields. Once the ticket is created, it's sent to a PW page. The Formbuilder JSON (and the JSON for the actual Form) are saved to the page. This way, if the form fields ever change, it doesn't effect old tickets. Essentially the state of the form and the entry are snapshot together and attached to the page. The replies/internal notes are an extended version of the comments field so that everything is contained within a single page. It doesn't have to be that way, but I had already created this modified comments field for another project, so it was the easiest way to go with this project. Anyhow, It's not something I intend on releasing at this time, but may revisit it eventually if there's enough interest. I would remove the FormBuilder dependency if I made it public.

I haven't really read all of this thread, but just wanted to chime in with a brief overview of a help desk system I built. I can only show you screen shots from the test server — since the real one has sensitive data — but I think you get the idea. Unfortunately it's all pretty specific to our environment here, and was never intended to be released. Ticket List This is pretty small in the test environment. The lighting bolt icons open a modal that shows some "quick look" information for admins. Last comment, ticket history, etc... It's just a way to quickly peek into a ticket without opening it. Ticket View Many of these test tickets are filled with a ton of content, but here's one that shows some of the features. It's conversation based. You can attach specific equipment (we have several equipment databases managed in other PW modules). You can add files/images to any reply. Typical help desk stuff really. Reply options This is at the bottom of the discussion, a lot like it is here in the discussion forum. Agents can reply or create an internal note.

The guy is fast folks.

The performance improvement for Inputfield forms sounds incredible. Looking froward to testing that out. The largest number I have to test with is about 60. It was never "slow" before, but it was slower than other templates with 5-10. Great work as always Ryan!

Shot in the dark: are there duplicate pages being added by the last selector? (I'm really only just following from afar, I haven't like into how this works).

You can build a lot of very custom stuff without the need to create another CMS on top of the framework. I have about a dozen or so modules that are essentially standalone apps within the PW admin. I know there are lots of others who do the same. Is there something specific you want to build?

There is this ancient discussion about using ProcessWire as a framework for Textpattern. Never got any traction, but it would have certainly been possible.

Dude! Nice one LostKobrakai...

I'm really loving all the new stuff on 3.x (and now 2.x). Have a great weekend Ryan, and thanks again for being a badass.

For reference, you can also make sure this happens when a page is saved in the admin as well. <?php class AdminHelperHooks extends WireData implements Module { public static function getModuleInfo() { return array( 'title' => 'Admin Helper Hooks', 'version' => 1, 'singular' => true, 'autoload' => true ); } public function init() { $this->addHookAfter('Pages::saveReady', $this, 'hookChangeNameToID'); } public function hookChangeNameToID(HookEvent $event){ $page = $event->arguments(0); // get the page being saved if ($page->template == 'lost-property'){ // check the template $page->name = $page->id; } } }

http://modules.processwire.com/ 404 on some CSS here. This is crazy fast, and sets the bar super high. I'm now sad about all my hosting.

Wow! There is a very noticeable difference here. Everything feels extremely snappy.

Ryan, I'm just seeing this now — doooode — super awesome! I've been head down in some major projects the past few months, so I haven't had a chance to do much more than read the weekly blog posts. I can't wait to dive into some of these new features. Thanks for keeping the Reno Amin Theme up-to-date with all this new stuff.

Perfect. I have a few different scenarios right now that need secure files. I think this module will handle at least one of them seamlessly. Much appreciated Wanze!

Hey Wanze, Are the files for individual pages stored in a directory named the same as the page ID — like a core files field? #lazyweb

I ended up making a ton of mods to this for things that were very specific to our needs. Coincidentally, I worked on cleaning it up and getting it back to a more releasable state earlier this week. I'll take a look at it on the devns branch on Monday/

Hi arjen, I'll dig those up again. Not sure why I would have put an expiration on the pastes.

Hi Tom, I think this was corrected in 2.7.3 or so (somewhere on the dev branch). To fix it in 2.7.2, unhide Admin > Pages.