Leaderboard
Popular Content
Showing content with the highest reputation on 08/30/2016 in all areas
-
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.5 points
-
not sure if this is right, and I'm on mobile. Have you tried to add them to the field? After all pages are created, something like $page->pagetablefield->add($childpage);4 points
-
Personally I don't think the tracking and ranking of donors is necessary or desirable. I support the idea of a donate button in the modules directory (if a module developer chooses to enable that for their module) but when donations become public information then it's inevitable that people start comparing the donations between modules and it creates a "winners and losers" effect that can do harm to the non-commercial motivations that led to a developer releasing an open-source module in the first place. Better to have donations be a private thing that can be a pleasant surprise for a module developer rather than a focus of attention. In the short term please bring on a donate button in the Tracy config screen.4 points
-
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.3 points
-
On my shared hosting the use of Hanna Code tends to trigger a false positive in mod_security (which throws 403s and does other odd things that are a PITA to debug). Therefore I now routinely disable mod_security in my accounts.3 points
-
v054 is up. There were many updates under the hood so make sure to clear browser and module cache. module settings are exported to settings.php on uninstall and restored on install load admin.js and admin.css from /site/templates/ directory if exist new tweak "NavItems" (experimental): add pages to main nav or sidebar (depending on theme) HTML classes added by AOS are added by PHP instead JavaScript: faster and eliminates initial page jump so the loader is no longer needed loader removed added "cog" icon to footer to jump to AOS settings fix: keep sidebar menu colors for non-inline mode (Reno theme) module CSS classnames were abbreviated2 points
-
Something like this could help: $(document).on('keydown', function (e) { e = e || window.event; var closeBtn = $('.ui-dialog-titlebar-close'); if (e.keyCode === 27 && closeBtn.length) { // ESC closeBtn.trigger('click'); } }); You just need to figure out the selector of the close button - I'm not sure they are all the same, but perhaps I'm wrong. In the next version of AdminOnSteroids (uploaded soon) there will be a feature to add custom JavaScript so you just need to place it there.2 points
-
Here are a couple of example modules that do this already: http://modules.processwire.com/modules/process-email-to-page/ http://modules.processwire.com/modules/process-custom-upload-names/ The approach is the same in both, although I don't honestly think you should steal code directly as it's not particularly pretty (a big understatement) - I'd like to redo the approach for both at some point), but it will hopefully give you a starting point.2 points
-
+1 What happens when we click on it, anyway? It does not take us to processwire.com but... The proposed footer logo / current text version should be linked though.2 points
-
Firstly, thanks to everyone who has suggested a Donate button - I am still thinking about this - not sure what my thoughts are yet. Just a quick update on the ProcesswireUpgradeCheck module and the Modules Disabler panel. Ryan has fixed the problem in the latest PW core commits today, although he is still warning (https://github.com/ryancramerdesign/ProcessWire/issues/1990#issuecomment-243401979) about disabling modules. See my next comment about @tpr's approach of storing module settings when uninstalling - as I mention, I am not sure this is without problems as well. I'd like to see a bullet-proof solution, although I am not sure there is one. At least for now, this panel should be a little safer than it was, but I am definitely keen to improve the approach used if anyone has any great ideas!2 points
-
I'd love to see this - I don't think it is taking away from PW branding - in fact I'd be happy to see the PW logo in the footer instead. I think as well as making the client feel like it's a system customized for them, I think the actual key benefit is providing another key visual trigger to let you know what site's admin you are currently looking at.2 points
-
Well if I release 054 you could add js/css tweaks on your own, because AOS will automatically add admin.js and admin.css from "/site/templates" dir. I concluded that this is the best place to have them but please tell if you have other opinion. Changing colors is not that easy, unfortunately. It could be great if someone could take the time and separate color-related stuff in a scss file. This way colors could be edited as variables. I've experimented with css3 features like hue-rotation, saturation and such, and results were great, apart from the fact that if I turned off "NoAnims" in AOS, admin became very sluggish. Even with no animations I suspect many computers would have tough times rendering the admin, unfortunately. I've also added a feature to add extra items to the navigation besides the CustomNavItems I showcased earlier. This allows adding any part of the admin, eg. direct link to the translator or module edit screens: Translator: setup/language-translator/edit/?language_id=1066&textdomain=site--templates--_strings-php HelloWorld module: module/edit?name=Helloworld //disabled item !AdminOnSteroids: module/edit?name=AdminOnSteroids2 points
-
I would also like to join the feature request club This topic reminded me of what I currently do in WordPress development: Besides being able to identify a site, it is also a good thing to tell apart the various instances of the sites we have (development, staging, live version, etc...). In the case of WordPress I use wp-cli to automatically update the site admin's color (the so called "Admin Color Scheme" setting), so that live sites are always in red, dev sites are in blue and staging sites are in purple. In the past, it happened to me that I worked in the wrong admin.... but with this skin changing trick, I'm far less likely to make this mistake again. Now back to ProcessWire My idea is that we could set a value in in config.php, such as $config->adminHeaderColor = #FF3935; which is used by AOS to change the background color of the header. Thanks to AOS I apply sticky headers, so this color indicator could be a strong one. BTW, here is another related feature idea: it would be cool if we could change the ProcessWire logo easily with AOS, replacing it with the client's logo.2 points
-
Ah, good to know, thanks. Therefore in a case like this where you want to filter pages in a Page field I'd be inclined to do an extra $pages->find() for the sake of better readability. $subjects = $page->custom_menu; $subjects = $pages->find("id=$subjects, status!=hidden");2 points
-
Sorry, didn't mention I was using Reno. Now it works. Thank you very much! I added styling for the image with the help of the Admin Custom Files module (http://modules.processwire.com/modules/admin-custom-files/). Is there another/better/recommended way to go?2 points
-
Ah, didn't look which admin theme you're using. Hooking into AdminThemeRenoHelpers::topNavItems should be the way to go. $wire->addHookAfter('AdminThemeRenoHelpers::topNavItems', function($event) { $out = $event->return; $out .= '<li><img src="path/to/your/logo.png"></li>'; $event->return = $out; });2 points
-
I've just added a feature to automatically save module settings to file on uninstall, and restore on install. This way you can uninstall the module without having to re-add settings later if you decide to install again. Additionally, settings can be moved easily from one project to another. With this I can apply more "safe" default settings and leave the more advanced stuff to those who need them.2 points
-
2 points
-
2 points
-
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.2 points
-
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.2 points
-
This module facilitates quick batch creation (titles only or CSV import for other fields), editing, sorting, deletion, and CSV export of all children under a given page. You can even provide an alternate parent page which allows for editing of an external page tree. http://modules.processwire.com/modules/batch-child-editor/ https://github.com/adrianbj/BatchChildEditor The interface can be added to the Children Tab, or in a new dedicated tab, or placed inline with other fields in the Content tab. Various modes allow you to: Lister - Embeds a customized Lister interface. Installation of ListerPro will allow inline ajax editing of displayed fields. Edit - This allows you to rename existing child pages and add new child pages. It is non-destructive and so could be used on child pages that have their own children or other content fields (not just title). It includes the ability to quickly sort and delete pages and change page templates. Also allows full editing of each page via a modal dialog by clicking on the page name link. This is my preferred default setup - see how it replaces the default Children/Subpages with an easily addable/editable/sortable/renamable/deletable list. Note that the edit links open each child page in a modal for quick editing of all fields. Add - adds newly entered page titles as child pages to the list of existing siblings. You could create a list of pages in Word or whatever and just paste them in here and viola! This screenshot shows the editor in its own tab (name is configurable) and shows some of the CSV creation options. Update and Replace modes look fairly similar but show existing page titles. Update - Updates the titles (and any other fields if you enter CSV data) for the existing pages and adds any additionally entered pages. Replace - Works similarly to Add, but replaces all the existing children. There are checks that prevent this method working if there are any child pages with their own children or other content fields that are not empty. This check can be disabled in the module config settings, but please be very careful with this. Export to CSV - Generates a CSV file containing the fields for all child pages. Fields to be exported can to fixed or customizable by the user. Also includes an API export method. Populating fields on new pages In Add, Update, and Replace modes you can enter CSV formatted rows to populate all text/numeric fields, making for an extremely quick way of creating new pages and populating their content fields. Predefined Field Pairings Like the field connections setup from Ryan's CSV Importer, but defined ahead of time so the dev controls what columns from the CSV pair with which PW fields. This is especially powerful in Update mode giving editors the ability to periodically import a CSV file to update only certain fields on a entire set of child pages. These pairings also allow for importing fieldtypes with subfields - verified to work for Profields Textareas and MapMarker fields, but I think should work for most others as well - let me know if you find any that don't work. Access permission This module requires a new permission: "batch-child-editor". This permission is created automatically on install and is added to the superuser role, but it is up to the developer to add the permission to other roles as required. Config Settings This module is HIGHLY configurable down to setting up custom descriptions and notes for your editors. You define one config globally for the site and then optionally you can define completely custom configurations for each page tree parent on your site. There are too many settings to bother showing here - you really just need to look through all the options and play around with them!1 point
-
This module provides a solution for keeping various site settings in one place (titles, slogans, api keys, emails, addresses, etc.). Features - Admin can create unlimited number of settings - Settings can be grouped - Admin can set setting label, notes, property name, field width and type - Settings can be of type text, checkbox, radios, select, email, url, integer How to use In module configuration create as many settings as needed. Customize their label, type, width and provide a name you want to use in a template files (property name). After that admin can set those settings on "General Settings" page in "Setup" section. Every time you wish to output eg. site name you can use $settings->site_name or wire('settings')->site_name or $settings->option2 to get value of 'Check it' as seen on the first screenshot. (Checked checkbox returns 1). You can change global name ($settings) to something else in module configuration. To get basic markup with all settings and their values use $settings->render(), usefull to check returning values (esp. select/radios - their values are sanitized as page names). Current limitation: -no way to change order of settings, -new settings can only be added at the bottom. Multilanguage To make fields multilanguage aware create a field with a same property name with '_languageName' appended. Example: Your site has two languages: default and french, create site_title and site_title_french fields. Put in a template $settings->site_title. If a user has set french language, this module output site_title_french, otherwise site_title. Please notice that render() function is not language aware. https://github.com/pmarki/ProcessGeneralSettings1 point
-
You do realise that if you (and Adrian with Tracy) keep developing your modules at this rate, they will become sentient before I do.1 point
-
Fortunately I have a maximum of 1 dev site and 1 live, and I mostly work on the dev and merge changes. But I see your pain This is where your red-colored admin header will be of great help1 point
-
1 point
-
1 point
-
Here is my post mentioning the idea of file-based settings. I think this could be useful for Tracy too. My current implementation in AOS is very basic, that could be improved with eg. saving settings file with domain suffix (settings-mydomain.com.php), etc.1 point
-
In case you haven't come across with this beautiful blog post from... well, myself, here is another approach to easily distinguish different projects: Per Project Chrome Instances This approach has other benefits too: better isolation, saved passwords, bookmarks bar for the current projet only, etc.1 point
-
yeoman generator for processwire env: https://www.npmjs.com/package/generator-processwire1 point
-
Thanks for the idea, however, I used to use a prominent "corner ribbon" (eg https://codepen.io/eode9/pen/twkKm) but it was not enough, I did make the stupid mistake even thought it was big and red. Maybe its just me, I dunno... The header bar is even bigger and more prominent when it is "sticky", so I hope that will do. BTW, I normally have Tracy turned off for the backend, it's only enabled when fiddling with admin hacks , and this sort of feature probably fits AOS better, I suppose.1 point
-
Just wanted to say a special thanks for this comment - I am very glad to hear it's been so useful to you - several of you have also been instrumental in making Tracy as useful as it is, so thanks to you all as well!1 point
-
@horst is right for sure. The other possibility depending on your needs is this:1 point
-
@horst, thank you for your answer! That may be the one we need to do, must investigate it further. We were able to narrow this issue a little bit. It seems that Apache mod_security2 with OWASP rules gave a few false positives. After disabling those rules one need to clear cache of android application, that can be done via settings -> application settings. That solved some of the cases. However it did not fix the problem with Android 4.2.2 legacy browser. It does not get updated any more. A workaround is to install newer Google Chrome or equivalent which get updated from app store.1 point
-
You should be able to hook into AdminTheme::getExtraMarkup and add your image to $extras["masthead"] (untested): $wire->addHookAfter('AdminTheme::getExtraMarkup', function($event) { $extras = $event->return; $extras['masthead'] .= ' <img src="path/to/your/logo.png">'; $event->return = $extras; }); You can look into AdminThemeDefault/default.php to see where the different extras are used.1 point
-
Hi, and welcome to the forums. How do you have linked to the file? (code example) Where is the file hosted? (locally, remote)1 point
-
How do you or the customer can add pages to $page->custom_menu ? What are the settings for that. Are there hidden pages included, selectable?1 point
-
Hey guys, Just yesterday I launched my new website, SuperTINY agency : http://supertiny.agency. It's a small but pretty heavy website with all the webgl going on. Older machines will choke. I'm using PW v3 on this one. Took only a couple of hours to install, setup the fields and templates necessary to run the portfolio, add AIOM and SEO and get it running. Got to love PW for that. The case studies are built using a repeater with fields that show/hide according to what's selected on a "type" selector. Clean, simple, just the way I like it. Enjoy.1 point
-
1 point
-
This looks awesome Tom! Finding a decent helpdesk package these days is qiute tedious. There are some good options, but no free ones for the smaller folks. Really nice to see this kind of thing wrapped up in PW.1 point
-
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 working1 point
-
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", ); }1 point
-
I'm always amazed by the interfaces you implement in the pw admin @renobird. It's crazy.1 point
-
@operat - welcome to the forums! Here's some info on the field that LK mentioned: https://processwire.com/blog/posts/processwire-3.0.4-repeaters-revisited-preview-of-profields-matrix/#new-profields-repeater-matrix-field1 point
-
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?1 point
-
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."1 point
-
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.1 point
-
I don't think it's possible. Check out this SO answer: http://stackoverflow.com/questions/31861822/google-maps-how-to-show-city-or-an-area-outline/31865958#318659581 point
-
New fun little site: http://wineatsandsweets.com. Responsive. Even though this is a little site on the front-end, in the admin, we have done a lot of work to handle and process entries. ProcessWire made making the custom functionality and organizing the admin for a great user experience a breeze. Every time I make a site and do a bit of work in the admin, I am amazed that I am able to produce results that look, feel, and act as if the whole CMS was custom rolled for my clients. PW FTW! Using a few modules, Field type Star Rating Process Page Field Select Lister Pro Pro Fields Field type Range Slider I wanted to add that every-single piece of content on this site was added and produced by my client. That always amazes me. Processwire is so easy to use for my clients that I just give them the keys and they go to town working on their website(s).1 point
-
Buchhandlung Scheuermann Today we have relaunched the site of a local bookstore, Buchhandlung Scheuermann. The site is based upon PW 2.7 and twitters bootstrap 3. It is fully customizable for the customer because we made use of: PageTables ALIF Croppable Images And the admin's sweeties are: Admin Custom Files Pageimage Manipulator 2 Pia - Pageimage Assistant ProCache Spex Wire Mail SMTP1 point