Leaderboard

I am using Bookstack too for some docs. But I really do not think it should be used for community maintained docs for an open source project. Those should be open for commits from everyone. I think that VitePress or Docusaurus or Mkdocs or even some php static site generator. The docs are markdown in the repo and contributing is just a PR.

That was quick. Thank you! I added a config checkbox in my Site.module to toggle behavior and added this to the hook function: /** * Switch LiveReload for backend based on module setting * @param HookEvent $event */ public function switchLiveReloadBackend(HookEvent $event) { $page = $event->arguments(0); $enable = $this->wire->config->isDev && (bool) $this->liveReloadBackend; if ($page->template == 'admin') $event->return = $enable; }

Hey @gebeer I have added support for this on the dev branch, please check 🙂 Here are the docs: https://github.com/baumrock/RockDevTools/tree/dev/docs/livereload#disabling-livereload-for-specific-pages

This issue has been raised by @adrian as well in the new admin theme thread and aknowledged by @ryan:

This week I’ve bumped the dev branch version number to 3.0.249. This includes a little under 20 commits with various small updates, also including several to the new AdminThemeUikit default theme. This will likely continue for a couple more minor versions on the dev branch as we continue to optimize and improve it. See dev branch commit log for more details. I’m currently developing a portal application in ProcessWire for a client, and also working to finish up the ProcessWire.com website with the new design. We’re getting very close to having it technically ready, leaving just some writing for the homepage and features sections of the site. So the new site could be online in as soon as the end of the month. Stay tuned! Thanks for reading and have a great weekend!

There is a free online event on ::: June 17, 2025 ::: 13:30–18:30 CET/CEST ::: 07:30–12:30 EST/EDT ::: 11:30–16:30 UTC https://lp.jetbrains.com/phpverse-2025/ @ryan what about taking part as a speaker on such events to make PW more popular?

Doesn’t GitHub have a built-in wiki feature? I don’t come across GitHub wikis much, but apparently you can open them up to anyone with an account, and mix and match text formats: https://docs.github.com/en/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages

Yes! This would be great! I like the idea....but... I've got Node fatigue 😁 and I really don't like writing Markdown... So what now? If only there was a way I could work comfortably in ProcessWire and export to Markdown, or better to GitHub... Yes! This is it. OK, I really don't want to use Laravel blade or Twig. Just give me plain PHP. Wait, https://www.atasasmaz.com/p/atas-php-ssg https://github.com/atas/ssg Yes! Now I can have my cake and eat it too! 😄. I'll have a play and see if I can use this in ProcessWire, maybe as a library or a module. This, I think, offers the best of several words! Living the dream! Everyone can generate their Markdown as they please! 😄 Thanks for the idea. I'll have a play. We'll also need to come up with a templating structure of some sort for the docs, to guide contributors. Thanks!

Hi @bernhard, is it possible to enable livereload only for frontend, like it used to be in RockFrontend? I think there was a switch in the GUI to enable it for backend. Now we only have the $config->rockdevtools = true; setting. Do we need to hook somewhere (maybe Page::render) to set it to false if template == admin, or something like this? Where to place the hook? I see in bot RockDevTools class and LiveReload class the check for the config value is in the constructor. So we would have to hook before the RockDevTools module is loaded, right? Or is there an easy solution, that I overlooked? The docs don't mention anything. Having reload in the backend can sometimes be annoying, e.g. when working on migrations and saving a file with unfinished migration or copying an existing migration file for reuse etc. Some control here would be much appreciated.

Unrelated but how can something not work on shared hosting? Especially something open source in 2025. Is there some over thinking here when something like Google Docs would be just fine?

I believe this is a bug. If UIKit theme is used and we traverse to Modules > Configure > AdminThemeUikit > Forms + input, the setting for “Input types that should be offset with additional top/bottom margin” has no affect. I started with Fieldset, but it didn't work. I thought, maybe it’s just the Fieldset field which isn't working; so I placed the entirety of **all** the available fields in that setting. But no fields are effected within my admin screens. I logged out and cleared my cache but still nothing. What **does** work is going into the individual settings for each field (at the field level) and activating the extra margin setting there. But at the global UIKit setting, it appears something is broke. (Attached is the setting I’m referring to.)

Did this ever get addressed? I know it's been many years but I'm still having the same problem.

I installed it on MAMP Pro and also on its own cPanel account, as it does not support shared hosting. I also tested the Docker option back then and it worked as well, but I am not fluent with Docker so I abandoned that project for a while. But I might get back to it as the idea was to run it it on a QNAP NAS. And it worked but I did not find the time to finish the task to setup automatic backup for it.

Oh dang, that was yesterday. Did you get to participate, @bernhard? The FrankenPHP and Building MCP Servers With PHP sessions looked intriguing, and I always enjoy hearing Jeffrey Way speak.

Padloper is dead! Long live Padloper! It is official! Padloper is now ProcessWire Commerce. ProcessWire Commerce is a free, open-source fully featured e-commerce module (plugin) for building and managing fully function online shops (stores) in ProcessWire. It is flexible, extensible, highly customisable, scalable, robust, multilingual by design and battle tested. Pro Support ProcessWire Commerce is designed to be easy to develop with and to use. For some, you might need extra reassurance that professional help will be available if you need it. Or, you might have a question about how to perform a certain thing or wish to support the project to ensure that any issues are dealt with quickly. Or you might want to sponsor a particular feature. If this is you, Pro Support and custom development can be purchased from my website. Community Support These forums. Donations If you value my work or my work helps support your work or you just want to say thanks, please consider donating. Thanks! Requests Modalities are still being worked out. Please note: I'll add features at my own pace; if and when I can (reasons for this discussed elsewhere in the forums). I'll focus on security, PRs and maintaining the project and major bug fixes. I hope community will contribute. Sponsored (pay for a feature) features: This can be by individuals or community driven. Please contact me for availability. Known Bugs ProcessWire Commerce Admin GUI is broken in the new admin theme, i.e., ProcessWire 3.0.248 (or newer). Save + Exit and similar broken on some pages at some recent ProcessWire version. Manually order creation broken (backend). Please file bug reports in the repo here - https://github.com/kongondo/ProcessWireCommerce/issues. Contributing This is a community project. All contributions are welcome! We are still working out how the 'how'. Documentation Please see this thread. Other Important Stuff Migrating from Padloper. Community help request. Tech Stack ProcessWire (PHP). Vanilla JS htmx Alpine JS Tailwind CSS MySQL Download Here you go!

I'm using a regular UIkit modal... Original theme: With the default theme the modal is vertically centered, which causes a weird glitch when closing it: As the UIkit docs mention there is a standardised way to center the modal: https://getuikit.com/docs/modal#center-modal. And as you can see there it will work properly if used properly. I don't know why the default modal is vertically centered with the new theme, but I know that adding these kind of visual "optimisations" causes problems. Could you please stick to default UIkit markup and concepts as much as possible with your overrides to avoid these kind of issues? Thank you.

Text Readability A module that uses the PHP Text Statistics class to evaluate the readability of English text in textarea fields according to various tests. The available readability tests are: Flesch Kincaid Reading Ease Flesch Kincaid Grade Level Gunning Fog Index SMOG Index Automated Reability Index Spache Readability Score Dale Chall Readability Score Coleman Liau Index The results of the enabled tests are displayed at the bottom of textarea fields – either when the "book" header icon is clicked, or at all times, depending on the option selected in the module configuration. An interpretive tooltip appears when you hover any of the result values. Requires ProcessWire >= 3.0.246 and PHP >= 7.2.0 Why is readability important? Readable.com says: And: The Wikipedia article on readability has useful information too. Module configuration Select which readability tests you want to enable. For each test there is an "about" link to information about the test. Select whether the results of the enabled readability tests should be shown only when the header action icon is clicked (default), or if the results should always be shown. For multi-language sites, select which ProcessWire language represents English (as the tests are only intended for English text). Advanced If you want to disable the readability test results for a particular textarea field you can hook TextReadability::allowReadabilityResults. Example: $wire->addHookAfter('TextReadability::allowReadabilityResults', function(HookEvent $event) { $field = $event->arguments(0); $page = $event->arguments(1); // Disable readability results for the "body" field on the "home" page if($field->name === 'body' && $page->template == 'home') $event->return = false; }); https://github.com/Toutouwai/TextReadability https://processwire.com/modules/text-readability/

Ever needed a color picker on some kind of settings page? Didn't want to install and setup a full-blown colorpicker module? Here's a quick and dirty hook to change a regular text field into an <input type="color"> type of input: Before: After: <?php public function init(): void { wire()->addHookBefore('Inputfield::render', $this, 'changeFieldType'); } public function changeFieldType(HookEvent $event): void { $f = $event->object; $colorFields = [ Site::field_col_primary, Site::field_col_secondary, Site::field_contrast_primary, Site::field_contrast_secondary, ]; if (!in_array($f->name, $colorFields)) return; $f->attr('type', 'color'); } So right before the text input is rendered we change its "type" property to "color" and the browser will render a default color picker 😎 It once more shows how versatile ProcessWire is. And maybe it helps someone... 🙂 PS: Be advised that with that hack you only modify the optics of the field. The field will under the hood still be a regular text field, which means you'll not get any sanitisation or such from it and you might have to take care of that on your own. In my case it's a superuser-only settings page. So it is no issue at all.

@maximus actually there is already ratio inside the pageimage class see here: https://processwire.com/api/ref/pageimage/ And you could also solve this without generating new images. You could set a square container and put the orginal img inside it. Then use CSS to get what you want.

Be careful with your site. ? Please create a backup of your website files and database first before trying anything else. No access is better than no site. Does your /reset.php work or do you see a 404 page not found page or errors at all? If it does work you could try this code to create a new SUPERUSER: <?php // if previously tried with this solution // https://processwire-recipes.com/recipes/resetting-admin-password-via-api/ // you need to include ProcessWire here as well - line below // require "index.php"; $newadmin = new User(); $newadmin->of(false); $newadmin->name = "newCmsAdminUser"; $newadmin->email = "user@domain.tld"; $newadmin->pass = "aSecurePasswordHere"; $newadmin->addRole("superuser"); $newadmin->save(); $newadmin->of(true); ?> I really don't know if this will work with ProcessWire 2.2.3 or if you need further adjustments.

@mke, there is a property and helper method in InputfieldFile that allows a maximum files size to be set but there is no config field for it in admin and you would need to set the max file size in a hook in /site/ready.php: $wire->addHookBefore('InputfieldFile::render', function(HookEvent $event) { /* @var InputfieldFile $inputfield */ $inputfield = $event->object; if($inputfield->hasField == 'YOUR_FIELD_NAME') { $inputfield->setMaxFilesize('2m'); // Set the max file size in bytes or use string like "30m", "2g" "500k" } }); Also, for some reason max file size settings of less than 2MB are not enforced - see here.