adrian

Glad you sorted out the name problem. The simplest way for you to handle making acs.php url accessible is to instruct users of the module to move the file into the site root. You could try to do this programmatically on install, but the module may not have write permission so not good to rely on this. If the user has to manually move this is obviously more problematic for the user, so the best approach is probably to make a companion helper Process module and attach the process to a hidden page under Home > Admin. There a several example of this approach in the modules directory, but just because I just did this myself recently with Tracy, take a look at this: https://github.com/adrianbj/TracyDebugger/blob/master/ProcessTracyConsole.module You'll see that it adds a page that can be called via a URL and assigns the Process to that page. Also note that the main Tracy module: https://github.com/adrianbj/TracyDebugger/blob/master/TracyDebugger.module#L38 installs this helper module automatically. Hope that helps.

Hey Adam - have you noticed the case used in the names of all other modules? Just match that and you'll be fine.

Depending on your needs, you may prefer to use this module, rather than actually renaming the page: http://modules.processwire.com/modules/process-redirect-ids/ I am not saying it's a better approach - just different

This is the one I have always liked: http://jeffreysambells.com/2012/10/25/human-readable-filesize-php But I would also vote for an option to automatically calculate the number of decimal places / significant figures.

Thanks @monchu and @Robin S - I have checked here and also see the problem based on deleting the default Find Lister. I have posted a Github issue: https://github.com/ryancramerdesign/ProcessWire/issues/1868

Yeah, there a several posts about this if you look back through this thread, as well as a Github Issue (https://github.com/somatonic/HelperFieldLinks/issues/6) - sounds like Soma has had trouble reproducing, so maybe one of us needs to help out and put together a PR that fixes them all - anyone keen?

Ok, the latest version comes with the new Console panel that I introduced a few posts back. Here are the key points/features on this panel: Has full access to all PW variables: $pages, $page, $user, etc Works really nicely with fl() calls, but you can also make use of d(), l(), or even simply echo() All output is generated via ajax, and so is virtually instant No need for editing a template file and reloading the page in browser - simply type your code in the console panel for an instant result Only available to superusers Caches code in the filesystem so it stored between page reloads, navigation to other pages, and even browser restarts Note that for those of you upgrading you will need to install the new Process Tracy Console module that is now included. For new installs, this will be installed automatically with the main module. Remember that this allows you to run any PHP code, so be careful! Please let me know what you think. Here are some example calls and their results:

In addition to the core cropping functionality, there are two third party cropping modules: http://modules.processwire.com/modules/croppable-image/ http://modules.processwire.com/modules/fieldtype-crop-image/ Neither of these work properly in PW3. The one you are using is tagged as compatible up to PW 2.4 only. The other one has a dev branch (https://github.com/horst-n/CroppableImage/tree/PW3) that works for 3.0.17 only. You should have a read of these threads: https://processwire.com/talk/topic/13215-pw-3017-major-upgrades-to-images-field/ https://processwire.com/talk/topic/13279-pw-3018-yet-more-images-field-upgrades/ Not everything is relevant, but there is a lot of discussion about further enhancements to cropping in the core to allow for predefined crop ratios etc. I think if you are wanting PW3, then unfortunately you will need to be satisfied with the core cropping for the time being.

Hi Peter - I am using it here on PW3 and it's working just fine. Are you having any specific problems with it?

Glad to help Zahari! I think your question has no definite answer. I do however think that all the profiles should be namespaced, or none namespaced (https://github.com/ryancramerdesign/ProcessWire/issues/1866). I think it is confusing to have a mix. It is going to be a difficult time with those profiles being namespaced when many modules are still relying on the filecompiler to make them PW3 compatible. Personally I haven't been namespacing template files yet (or my modules for that matter) because I want PW2 compatibility. But moving forward I expect at some point we'll all be namespacing by default and not relying on the filecompiler. So for the moment, maybe just be aware that when calling a module's class like that, you will need to reference it in the global namespace and all will be good. You'll notice in that GH issue I linked to that I pointed Ryan to this thread, so maybe he'll also chime in here with his thoughts now that PW3 is getting close to being the stable branch of PW/

I'm afraid I don't really know what you are trying to change - by the ""Page tree" menu item is marked as active/current", do you mean the breadcrumb trail? Perhaps a screenshot may help us understand your goal a bit better.

Hey @tpr - you have been busy while I have been away I haven't played with it yet, but it looks awesome - do you feel like another feature request? https://processwire.com/talk/topic/13041-pw-3015-new-quick-tree-debug-view-panels-and-more/?p=118514 Not sure how easy this would be to do in your module, but thought I'd throw it out there!

Looks like you have a namespace issue - I am using AIOM on a PW3 site without any problems - the file compiler is properly taking care of things. That error is coming from the uncompiled version of _main.php though - are you using PW3? Do you have the filecompiler on? Are you manually specifying the ProcessWire namespace? I am guessing the latter - you are manually specifying the namespace, but AIOM is not namespaced, hence the problem. What happens if you do: <link rel="stylesheet" type="text/css" href="<?php echo \AIOM::CSS('css/stylesheet.css'); ?>"> Note the backslash to request the class in the global namespace.

Take a look at: http://modules.processwire.com/modules/process-redirect-ids/ It may work as is for your needs, or you can take a look at the approach used as it also hooks into ProcessPageView::pageNotFound

Fantastic writeup and insight into the development process and the speed gains from Latte and Procache! Just one quick comment - the image in the banner is suffering from some JPEG pixilation around the person. Weird thing is that photo is actually of where I am currently hiking/climbing

Hi @RobinS - thanks for the report - I am still away from the office and don't have a chance to test properly right now so not sure if I am on the right track, but would you mind testing the attached version of ProcesswireLogsPanel.inc (attachment removed as it is now available as part of the Github repo) - based on the error message I think it should fix things, but you mention the error is in all panels, however I think the error is likely just propagating through and is really on coming from this file. Let me know if this works - if it doesn't, I sort it out properly when I am back in the 8th of June. Thanks!

Before I go, here's a preview of a php console that will be released when I am back. Enter code which runs in the background via ajax, with the results displayed below. It will also support ACE editor for code highlighting and other cool things. 10/4, over and out!

Just heading out the door - honest , but just wanted to say that I am definitely keen on the functionality being discussed and am keen to build it - I am also not sure if it belongs as part of Tracy, but I do like the idea of having one toolbar that can handle all my needs. As it is, I often also use horst's ALIF for the user switching functionality. I am not sure I would want a third toolbar for viewing TODOs, and posting/reviewing issues/bug tracking. I think that potentially Tracy could morph into something that is all encompassing because I think with the Panel Selector panel you have a very easy way of enabling/disabling tools quickly as needed. I am interested to hear how the discussion has progressed when I am back, that's for sure.

Yeah, I fixed that a while back - Tracy is now at 1.7.7 Btw - thanks very much to both you and @szabesz for all your thoughts on the notes/issue tracker panel. I am packing to leave shortly, so haven't liked/responded yet, but some great ideas/discussion which I'll respond to properly when I am back in two weeks.

Thanks - if you (or anyone else) get the time that would be great, but don't stress about it

I like where you are headed @szabesz - I think issue tracking displayed within the context of the page it refers to could be an excellent tool for giving and receiving feedback to/from clients. I am pretty excited about this because I have a hard time getting clients to interact with trello - maybe having this right on the website will make it more usable for them. I am going on vacation for the next two weeks starting tomorrow, but I would like to look into this when I am back. It would be great to get more thoughts from others before I start coding it, so feel free to continue the conversation while I am gone. Anyone feel like mocking up the UI so we can plan the implementation well? Back to the issue of the core Tracy master branch - that still hasn't been fixed so I have rolled the included code back to the version of the core before the problem showed up. I think that is the best compromise until it's fixed - at least this way you can get most of the improvements of the new version. Be sure to clear your browser cache if you find issues after rolling back - there were some CSS changes that caused the panels to be a bit buggy when I first rolled back. See you all in a couple of weeks.

https://processwire.com/api/selectors/#or-groups

Hey Soma and Charles, Sorry about the issue with the master/dev version of the Tracy core - this is a recent problem that started 3 days ago: https://github.com/nette/tracy/issues/185 - I was hoping I would get a response that would help me get it going again, but still no luck, but hopefully it will be up and running again soon. Soma - I think the panel positioning/moving issues have all been fixed in the master/dev version. I was contemplating backporting to stable, but the master version has been tagged as RC1, so I think it will be released as stable pretty shortly. In summary, depending on your server you will probably need Stable for the moment - I'll update here as soon as master is reliable again because there are some great improvements in the new version.

I think you might need to do that via an API call

Quick FYI - I just committed support for using the Validator behind htaccess protected sites. There are new config settings for entering the username and password to be sent with the request. @tpr has just tested for me and it's working great for him, but because I am using wireHttp->get first, and then falling back to file_get_contents, I am not sure if it will work for everyone as is. Not enough time right now to test thoroughly, so let me know if anyone using htaccess protection has any problems with this new one. To quote @tpr - "I can no more hide behind htpasswd and say that "Everything is valid, trust me" :)"