szabesz

Oh, sorry for that Well, switching theme I have AdminThemeDefault, but sticky header does not work for me either. That's "AdminTweaks -> Sticky header", right? Since installing AOS, I do not use the default theme anymore...

I've just updated to 0.5.6, and I do get the AdminThemeReno class and the sticky header.

If we probably do not get too many log entries, then log to file will probably do, however, if we do get too much stuff, logging is normally recommended during testing sessions only.

I often see such features to be (superuser) configurable: no log, log to screen, log to file, log to both.

This discussion might help: https://processwire.com/talk/topic/13977-custom-php-code-selector/?do=findComment&comment=125688

So that is why he did not have time to release his video tutorials? Never mind, at least cmscritic.com is back to normal. Thanks for reporting!

If I were you, I would take a different approach. Instead of nesting repeaters (wich have know performance issues, though this has been inpoved recently in 3.0.4 and 3.0.5). It is normally recommended to create a (e.g.) Galleries as parent ProcessWire Page, and under it you can create as many Gallery pages as you want. A short tutorial on this: This approach is quite common, you can read about it here, for example (same approach as blog/blog-item or tags/tag-item in this example): Tips on how to set thing up in the admin:

@Hector Nguyen I've never heard of it but Magallanes does look "interesting" indeed. So I'm interested in how you will set up your projects. I would be happy to improve my workflow if Magallanes can be the tool to do so. As for your actual question, I could answer it too but let's leave it to more experienced ProcessWire developers. I might miss something...

Since the preparation for 3.x release is already underway, see: https://processwire.com/blog/posts/pw-3.0.32/ And of course, the 3.x line is the future, the 2.x line is "just" there to ease the switch and give enough time for developers to decide how to switch from 2.x to 3.x. One can either upgrade or wait until upgrading becomes feasible, if at all. But Ryan has explained it a lot better than me

The use case is this: I have a local dev instance and I also have the live site and sometimes even another staging instance for testing another "branch". So same project, but different environments running different clones of the site. It does matter whether I make changes to the live site or to my local instance Since the admin area looks identical, it is easy to pick the wrong tab without noticing, especially around midnight

Interesting idea. Thanks for sharing!

Beautiful blog post indeed! However, you used the keywords: "for the current project only". I mean, I mixup the admins of the same project, so that is what I've solved with different admin theme colors. It would be an overkill to launch 4 Chrome instances for a project, 2 or three for another, and trying to tell the instances apart from my macOS dock would be frustrating. I also use other browsers too sometimes (for example here is Blisk I recently learnt about here, in the forums), although Chrome is my favorite for development so far.

For ProcessWire too How about a core module that supports it? Or at least a 3rd party module that is a joined effort and can be used in such cases by module devs?

+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.

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.

I even made a bash script to hack it:

Maybe because of System Integrity Protection eg.: http://www.macworld.com/article/2986118/security/how-to-modify-system-integrity-protection-in-el-capitan.html The mac I use for development is still running Yosemite, so I have not yet tried to apply this change on El Capitan. Note, that I use this change for wp-cli too (so, still on Yosemite).

The cause of the error was this "N98 will be trying to use your Macs native PHP which isn't configured for MAMP's MySQL resulting in the database errors." N98 is a phar file, just like wireshell. This worked for me: Change directory to /usr/bin cd /usr/bin Change the name of the native php to keep a backup (just incase) sudo mv php php.old Create a symlink to your php version sudo ln -s /Applications/MAMP/bin/php/php.[VERSION]/bin/php php You can redo this, so you might want to try it just to see what happens.

@Soma I used to have a similar issue with Magento's cli tool: https://magento.stackexchange.com/questions/26001/how-can-i-get-rid-of-all-the-various-database-related-erros-of-n98-magerun

Wow I will try it out for sure. As for the path, well, I do not think we have other viable options than using this path, so let's go for it, maybe with an additional subfolder to keep things organized, such as: /site/templates/aos or /site/templates/AdminOnSteroids which is longer, but more concise than "aos". About the color issue: I was just thinking about something like this (sorry for the actual colors, it is just an example...): #masthead, #branding, .main-nav-toggle { background-color: red !important; } #ProcessPageSearchQuery { background-color: darkred !important; } I do not want to recolor the admin, the WP part of the comment is just an example I'm familiar with. Changing the head is just enough for the use case I've outlined. But with the new admin.js and admin.css feature one can easily do this.

@bernhard Thanks for the link to the topic! I skimmed through Ryan's replies and the only thing that seems to matter is this: " I do think the software name ProcessWire, version number and copyright should always remain in the footer of the admin at least." I agree, I never wanted to remove these Also, I always educate my clients and teach them the name of the underlying system(s)/pieces of software they use.

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.

Sounds pretty cool! Thanks.

@Speed I have MAMP Pro so I do not know if it works (also, it is an old post) but you might want to give it a try: http://jonathanmh.com/using-virtual-hosts-with-mamp-free/

+1