Leaderboard

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.

I've been calling it a framework instead of a CMS. I find that's a great starting point to explain how much different it is from a CMS such as WordPress, how it makes zero assumptions and allows you to build whatever you want without having to hack the S#!7 out of it or depend on a bunch of plugins. And so far so good. Clients have been trusting my arguments and accepting PW. Agencies... not so much. They're like christians, and accept only the holy word of WordPress (or whatever they use). They also laugh at me when I say I don't use Bootstrap or CSS preprocessors. Apparently it's a flaw to know CSS enough to not need a crutch to make a responsive column based layout. I'm drifting. Sorry.

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'm thinking about to implement a "show historical label texts" module config checkbox. Antti, would this help to get over this a bit faster? (Some customers really liked that. "Oh, thats so positive! Fine.")

What have you done Adrian!?!? TBH I was surprised that those lived so long. They always made me smile

Done.

Ok, I have tested further and can't find any problems, so I have committed those changes. You should now be able to use debug statements before page ready which should help significantly with module development. Please let me know how this works for everyone and also if you notice any problems elsewhere in Tracy as a result of these changes.

This looks great @horst - just one initial request - can we lose the "Wow that looks great" button label and make it simply "Continue" or "Accept" or something similar. And maybe the "Not happy, crop again" link should be a button with "Redo Crop" ? PS I know these labels are a legacy of the original thumbnails module, but they do sound a little weird to me.

How the new editor window looks like.

Croppable Image 3 for PW 3.0.20+ Module Version 1.2.0 Sponsored by http://dreikon.de/, many thanks Timo & Niko! You can get it in the modules directory! Please refer to the readme on github for instructions. - + - + - + - + - + - + - + - + - + - NEWS - 2020/03/19 - + - + - + - + - + - + - + - + - + - There is a new Version in the pipe, that supports WebP too: - + - + - + - + - + - + - + - + - + - NEWS - 2020/03/19 - + - + - + - + - + - + - + - + - + - ------------------------------------------------------------------------- Updating from prior versions: Updating from Croppable Image 3 with versions prior to 1.1.7, please do this as a one time step: In the PW Admin, go to side -> modules -> new, use "install via ClassName" and use CroppableImage3 for the Module Class Name. This will update your existing CroppableImage3 module sub directory, even if it is called a new install. After that, the module will be recogniced by the PW updater module, what makes it a lot easier on further updates. ------------------------------------------------------------------------- For updating from the legacy Thumbnail / CropImage to CroppableImage3 read on here. -------------------------------------------------------------------------

OMG Reno that looks exactly like what I was asking for. Admit it man, you just slapped that together, just cause you can. Now the question is, how many beers will we have to buy you to get that code?

In most cases you can simply do: if($page->template == "admin") { but this needs to be in ready(). If you need it to work within init(), then I use: if(strpos($_SERVER['REQUEST_URI'], wire('config')->urls->admin) === 0) {

Thanks for your reply. You are right the icon variable only allows a single value. The post from nghi helped me to get it working with custom icons for each marker. Here is the code I used in the MarkupGoogleMap.module: /** Custom Fields */ foreach($pageArray as $page) { $marker = $page->get($fieldName); if(!$marker instanceof MapMarker) continue; if(!$marker->lat) continue; $url = $options['markerLinkField'] ? $page->get($options['markerLinkField']) : ''; $title = $options['markerTitleField'] ? $page->get($options['markerTitleField']) : ''; $icon = $page->marker_icon->url ? $page->marker_icon->url : ''; $map_location_name = $page->map_location_name ? $page->map_location_name : ''; $out .= "$id.addMarker($marker->lat, $marker->lng, '$url', '$title', '$icon', '$map_location_name'); "; } Maybe this will help someone.

@tpr - the latest commit fixes the "Uncaught Error: Class 'Tracy\Debugger' not found" error in modals. I have also changed the behavior slightly. Tracy is now loaded in normal modals, but not inline ones. I think this is a good balance, but let me know if anyone has any strong thoughts on this. FYI - an example of an inline modal is the "Usage" section of a template settings page.

Thank you so much, everybody. I discovered the culprit which is me... I studied the module and the first this it checks is the presence of the <html> tag... and it was missing! Go figure! After all these years making websites!!!! I am ashamed... ;-) Thank you again!

Great - thanks - and please leave the bd() or TD::barDump call in the spot where you are trying to use it. I have also just reminded Ryan about a request I made some time ago for making it possible to specify load order priority for autoload modules, which might also be relevant to what you are seeing.

I'm going to relate this to PW, promise. I'm looking for a cool, simple, free helpdesk system. Nothing too fancy, just letting users in, post a ticket, get replies, talk back, close ticket, reopen ticket, close again. See a list of what was requested, what's open, what's done. Anyone got suggestions? I can only find paid or crap solutions. No middle ground. Now the link to PW: As a way to promote PW, would it be a good idea if we had projects, like a ticket system, free and based on PW? You'll all probably agree it would be relatively easy to pull off a ticket system in PW. I'm imagining something styled by the theme system (I love Reno), using an installation profile to setup, the roles system that's already there, and sold as "the free, processwire powered helpdesk system". Devs need ticket systems and like me want to avoid spending a dime. They find this and try it out. It's cool. Let's have a look at PW since we're here. Whoa this is awesome! And my clients will see the same beautiful, tidy interface on their CMS? Screw you WP, I'm going PW from now on! Does this sound like a good idea or am I just trippin?

This is a great idea (better than mine) if nothing in the module needs to work on the frontend, but one thing to note - if you change the autoload from true to template=admin you will need to do a Modules > Refresh to have the change take effect - I remember pulling some hairs in my early days of module development wondering why it wasn't working

I'm always amazed by the interfaces you implement in the pw admin @renobird. It's crazy.

Looks really great @renobird - I know you say it it is specific to your environment and not meant to be released, but are you rethinking that? The one thing that we discussed in the Tracy thread about this was the ability for the tickets to be initiated from a link on every page so the user doesn't need to specify the page, and also so that the devs can view tickets relevant to the page they are viewing. I'd hate to see us all reinventing the wheel here - how can we move forward?

related to the helpdesk topic i want to suggest that you offer the possibility to support this awesome project (module seems like an offense in that case) with donations and mention the donors somewhere in return. what do you think of that? I'm really thankful for what you built here as i learned a lot and i don't know where i would be today without all the help of tracy opening my eyes. maybe it's just me because tracy came in right in time and i've never used xdebug or the like - but i have the feeling i'm not the only one thinking a bit about it i'm asking myself if that wouldn't be a good feature for the modules directory? offering a donation button connected to the devs paypal account and showing the donors automatically ranked by amount? if that is getting too offtopic don't mind creating a new topic for it... my first intention was related to tracy though, so i'll leave my comment here

Yeah, now I'm thinking about to setup a radio or select with something like: "I am serious" "I like it funny" "I'm brave, surprise me" @apeisa: Yes, that was exactly what one customer said to me a month ago: "Oh, thats nice and not so serious. I like it. It is the same way like Mailchimp do."

Welcome to the forums @tiefenb! more about urlSegments: https://processwire.com/docs/tutorials/how-to-use-url-segments/ https://processwire.com/api/ref/input/url-segment/ Have fun with ProcessWire

Wow - now I feel so boring and serious Seriously (ha ha) though, I think there is a great place for fun elements in software, but I think it's important who it's aimed at and whether they'll see it as fun or just confusing - "you gotta keep it smart people" (dorky TV quote there)! Getting OT, but why do all phone companies around the world seem to use cute animals in their advertising? I don't see the fun because I can't see the connection - the fun has to be relevant.

Aren't your module sponsors withdraw seeing this?

No offense, but oh so many tears. I will get over this. Someday.

As the module config is stored as json string anyways you could use any array structure to model those config data, but there's no ready made inputfield to support that structure by now. All multi instance/multi value fields do depend on actual pages be present (or at least a fieldtype db table for fieldtypetable).

TracyDebugger also has validator support

Not meaning to hijack for promoting TracyDebugger, but if you grab the very latest version from today, it will let you do bd($this->renderAssets()); or: bd($out); to dump as @Robin S suggested. Prior to the latest version of Tracy, bd() calls in PW files often didn't work because of the order of when Tracy was loaded. Hope that helps a little!

Suppose you have a module where you want users to be able to fill out some fields for a configuration, but then the user should be able to add several of these configurations. This is something I've come up against a few times when working on modules. Any suggestions of strategies for this? I'm thinking of something similar to a Repeater - is this possible in a module configuration? I know my module could add a page to the tree and literally use a Repeater field within it but I'm not keen on that because (a) the Repeater module isn't installed by default and it seems a bit mad to require it just for a module configuration, and (b) I'd prefer to have the module configuration done in the module settings rather than on a separate page The only alternative I can think of is to use a textarea field in the module config and require users to carefully format/separate the values for multiple settings on a single line, and with each subsequent line being a different configuration. This seems a bit primitive and error-prone, although it is what I have been using thus far. Is there some middle ground between these two options? Do you think some sort of repeatable block for module config would be a good feature to add to PW? Not something that actually adds pages like a Repeater, but rather something that still allows the whole module config to be stored as a string in the DB.

Alternatively you can have your module autoload only in the PW admin. Then the hooks you add in init() won't apply to API code you use in a template file. public static function getModuleInfo() { return array( 'title' => 'My Module', 'version' => '1', 'summary' => "Module summary.", 'autoload' => "template=admin", ); }

@LostKobrakai @adrian – thanks for the quick replies! I had a brief look at the Repeater Matrix field. It looks pretty good and might be just what I was looking for.

ok throwing in some more ideas here as i think it would really be great to have something like this. i think the priority should be to help US at our work with our clients and not to develop something that spreads the word about processwire... imho the most important parts would be feedbackform directly on the page where the issue occurs (i always have to teach my clients that they send me the URL with every request they are sending). like in my post in tracy (see below) copy&paste screenshots would be awesome: https://github.com/vladmalik/pasteimage simple overview system both for clients and for devs simple notification system i'm really short on time but would help as much as i can if something like this would arise. i'm also willing to sponsor some euros for such a project

creating something cool is the one thing, keeping it up to date is the other... that's the more challenging part. you would have to make sure that all installations of your system can get updated if the user decides to. that's a pain with site profiles. so i agree it would be cool to have simple project/task/ticket management in pw but i think the only possible way would be to develop a module. installable, updateable, maintainable... gitlab has recently announced their new issue board. that looks really nice from what i saw on the video: https://about.gitlab.com/2016/08/22/announcing-the-gitlab-issue-board/

Hi Mike, thanks for carrying this over for me. Using 5.7.13 as far as I can see.

Carry-over from here: @POWERFULHORSE - Sorry to see that error came up, as we have had problems with timestamp fields in the past. What version of MySQL are you running? There is quite a difference between 5.6 and 5.7, but understood that this problem was fixed. Also note that (as you'll see in the posts above), Jumplinks 2 is in development, and it uses Laravel's Eloquent for database interactions. Makes it somewhat more manageable in terms of table schemas (and a whole bunch of other goodies).

I floated the idea of a "Notes" panel for Tracy which I think would cover your needs. Have a read through many of the posts below - @bernhard and @szabesz in particular come up with some good ideas of how this might work. As @tpr suggests, Tracy may not be the place for it, but I am still considering the where and how, but I am definitely keen on building this. The key thing I want is to be able to provide and view the feedback on each page in the front-end, as well as having an admin interface to review and manage them all.

Take a look at Jumplinks: http://rockett.pw/jumplinks/

I actually like when software is not so serious. And I think most people do. Or at least it is not stop for success, take a look at MailChimp and Slack for example. @horst the legacy labels setting would make my day!

Here is a sneak preview of the custom nav items feature I'm working on. They load page lists if applicable, or other pages based on the page type, eg. the Profile page. The main goal is to select pages to add to the main for easy reach. There's also an edit link to the right of the items if you want to edit the page instead list their children. I haven't found a way to inject these pages with PHP to their destination so the last step involves a bit of JavaScript. If anyone knows how to do this, please share.

urlSegments are what you're looking for.

Of the autoload modules in my testing installation, bd() worked in 5 and failed in 7 when called from init(). Probably the random load order issue you mentioned.

Thanks Adrian - all is working now. I'm just wondering if you shouldn't indicate PW 2.8 compatability in the mods directory?

@Mike Rockett - I decided to do some testing here and I think I have a working version for you. There was a lot of code reordering to make this work (needed to put lots into init(), so I need to test some more to make sure I haven't broken anything in the process, so won't push live just yet, but I'll PM you a copy of the version I am testing - would be great to know if it works for you too.

I am fine with that, I just heard 307 mentioned in the context of Google and the new "Strict Transport Security" feature (without understanding every detail of it). That's ok with the loop detection. There are other tools to dig further. It would be just convenience, a redirect problem had driven me nuts recently.

Can you give a bit more information please: 1. What version of PW is installed? 2. Which option did you use to enable front-end editing: Option A, B, C or D? 3. If using B,C or D please provide the template code you have used to try and enable front-end editing. 4. Any javascript errors in the browser console?

A donation button somewhere won't hurt, at least

Bumped to current master to 1.5.4, fixing a potential security issue.

hi @thetuningspoon just wanted to say thank you! i looked to your code and it was really easy to implement my own fieldlink (needed some special selections) like this: php hook: /* pagefield for league selection */ $this->addHookAfter('InputfieldPage::render', function($event) { $field = $event->object; $pages = $this->wire->pages; if($field->name != 'league') return; // load script $this->config->scripts->add($this->config->urls->Webifex . 'pagefieldReload.js'); $admin = $pages->get(2)->url.'page/'; $leagues = $pages->get(1017) // settings ->season // current season ->child('name=ligen'); ob_start(); ?> <div><a class="pw-modal" href="<?= $admin.'?open='.$leagues->id ?>"> <i class="fa fa-edit"></i> Ligen verwalten </a></div> <?php $html = ob_get_clean(); $event->return = preg_replace('/<\/div>$/', $html, $event->return); }); and this simple javascript: $(document).on('pw-modal-closed', 'a', function() { $(this).closest('.Inputfield').trigger('reload'); }); awesome

I think that the basic profile that is included with ProcessWire is probably the best example. Install that, and then copy a few of your other HTML files into the same root directory you've installed ProcessWire in. Those HTML files will still be accessible when accessed in the URL. So if you are putting part of your site in PW and the other part not, then it's just a matter of linking the two (by way of <a href=...>, etc.)