szabesz

As @BitPoet said, there is AdminCustomFiles module (I've never used it), and AdminOnSteroids module can do it too. Also in config.php something like this: $config->scripts->add($config->urls->templates . "admin/admin_global.js"); $config->styles->append($config->urls->templates . "admin/admin_global.css"); A related good read: http://soma.urlich.ch/posts/custom-js-in-processwire-admin/

I've been trying to do it too, for years not too much success so far, even though I know how useful it is because it always makes me very happy when I find that I did not forget to document something...

I did not add it I just use the Input config of the TextArea inputfield: Format Tags Semicolon-separated list of selectable tags shown in the "format" dropdown.

I've been thinking of hacking it too but as a last resort. The trouble with such workarounds is obvious, when they change the names of the classes, we need to make changes too and I already use some of these admin overwrites. Thanks for the tip though, at least I know where to look at This is just the definition, I cannot see how this can "help". Others were trying to solve this too, eg: https://ckeditor.com/old/forums/CKEditor/Disable-preview-in-format-dropdown https://www.drupal.org/project/ckeditor/issues/2534462

As far as I understand, this module is only about database related migrations and as such not really about setting up ProcessWire. Also, @LostKobrakai doesn't seem to be maintaining it anymore as he seems to be switching to Elixir.

+1 as it sound like a great approach.

Just a quick fix: "...the most powerful tool on this planet..."

Hi, I've been searching for the answer but could only find some hacky "solutions" from the distant past. What drives me crazy is the "preview" feature of the dropdown menus: Is it possible to force the dropdowns not to apply the styles of the editor but use the styles of the button of the editor, or at least use the default styles? I need readable menu items, not those cut-off an useless styled ones. Also, only a few menu items fit in the tiny dropdown area. This is bad UX

More on this here by @Robin S: https://processwire.com/talk/topic/16350-processwire-and-phpstorm/?do=findComment&comment=145018 You can also clone "your default site" easily with: https://modules.processwire.com/modules/duplicator/ by @flydev Keep in mind that using Duplicator you will get the same $config->userAuthSalt which is a minor security issue but you can apply the workaround suggested by @horst: https://processwire.com/talk/topic/15265-generate-new-userauthsalt-for-copied-site/?tab=comments#comment-136537

Yes it does. Thanx

Yes please! I might need such a thing soon, too.

I do not use loginForm so I cannot really test it but after updating I had no issues at all.

This does look really useful if it gets "perfect for all selectors", since it is a great way to get a different point of view of the selectors we write. For example I am very slow at writing SQL since I rarely have to do it (thanks to ProcessWire ) but I can read it so this means I can more easily identify errors in complex selectors just by taking a look at the the actual queries. Also, spotting query related performance issues gets easier. I'm thinking of seeing lots of JOINs and being able to reduce them should they only be a result of a not well written selector. At least this is my understanding right now. Correct me if I'm mistaken...

Hi A VPS (running cPanel perhaps?) might list what is eating up resources. Have you checked that info? Also, it is not free and if you really have not changed anything then it might not be of good use in this case, but it might help: https://processwire.com/api/modules/profiler-pro/

"Sounds" useful Thanks for sharing and caring!

I would vote for this. Users tend not to notice such subtle things like cut-off text in an input box. Looking ugly is better than users having trouble, I think. So I vote for pixels.

One more thing, layout of the input boxes. Is there anything I can do to turn it into a one-liner? Something like:

Works! Thank you very much!

I added a Phone field (called user_mobile) to the user template. I have ListerPro so afterwards I added this field to the Lister of users as an additional column. In this column only the unformatted phone numbers show up and area codes are missing. If I enable country code it is also missing. (I do not need country code right now, I did it for testing purposes only.) Otherwise in Tracy's console echo $page->user_mobile; and echo $page->user_mobile->hungarianV1; etc... work as expected.

https://processwire.com/blog/posts/pw-3.0.86/

Better yet, something like this: I have three different browsers in use: one for regular browsing with plugins installed (Vivaldi with "adblocker", Dark Reader, downloader, etc...), one for development/PW (clean Chrome) and one for logging into 3rd party online accounts only (clean Firefox). Nice and tidy setup

While I generally agree to all the other points raised, I would be cautious with Slack. To tell the truth, I'm barely familiar with Slack but what I've seen so far (and that was about two years ago, so things might have changed) communication in Slack is very fragmented and hard to follow. On the contrary, our current forum has a lot of power in it and is very easy to follow. Maybe Slack can do the same but it is a question whether it is preferable or not.

Very good point! I was in the same boat with SilverStripe. They pushed the system in the direction so that one can practically use their workflow only, major version numbered system updates were not possible because of incompatible modules, etc... Part time developers like me just could not keep up the pace with the changes introduced. In contrast, ProcessWire "just" gets new features, upgrade issues can be sorted out, and breaking API changes are virtually non-existent. You learn it once, use it "forever" For example, I hate that when I need to re-learn M$ Windows/Word just because they completely redesigned the GUI. I'm on Mac$, anyway

Thank you! I have not yet realized it. Good to know

I am about to use this module too (for the first time). The discussed improvements do sound good. Thanks in advance, Adrien!