Recently Browsing 0 members
- No registered users viewing this page.
By Chris Bennett
Inspired by @bernhard's excellent work on the new customisable LESS CSS getting rolled into the core soon, I thought I would offer up the module for beta testing, if it is of interest to anyone.
It takes a different approach to admin styling, basically using the Cascade part of CSS to over-ride default UiKit values.
Values are stored in ModuleConfig Module creates a separate AdminThemeTweaker Folder at root, so it can link to AdminThemeTweaker.php as CSS AdminThemeTweaker.php reads the module values, constructs the CSS variables then includes the CSS framework Can be switched on and off with a click. Uninstall removes everything, thanks to bernhard's wonderful remove dir & contents function.
It won't touch your core. It won't care if stuff is upgraded. You won't need to compile anything and you don't need to touch CSS unless you want to.
It won't do much at all apart from read some values from your module config, work out the right CSS variables to use (auto contrast based on selected backgrounds) and throw it on your screen.
You can configure a lot of stuff, leave it as it comes (dark and curvy), change two main colors (background and content background) or delve deep to configure custom margins, height of mastheads, and all manner of silly stuff I never use.
Have been developing it for somewhere around 2 years now. It has been (and will continue to be) constantly tweaked over that time, as I click on something and find something else to do.
That said, it is pretty solid and has been in constant use as my sole Admin styling option for all of those 2 years.
If nothing else, it would be great if it can provide any assistance to @bernhard or other contributor's who may be looking to solve some of the quirkier UiKit behavior.
Has (in my opinion) more robust and predictable handling of hidden Inputfields, data-colwidths and showIf wrappers.
I am very keen to help out with that stuff in any way I can, though LESS (and any css frameworks/tools basically) are not my go.
I love CSS variables and banging-rocks-together, no-dependency CSS you can write with notepad.
By Richard Jedlička
Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.
See example or see usage in a real project.
How to use?
1. Install it:
composer global require uiii/tense 2. Create tense.yml config:
tense init 3. Run it:
For detailed instructions see Github page: https://github.com/uiii/tense
This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
Here's a small new module that adds a "Manage tags" button to the template list, just like the field list already has.
Easily add, remove and change tags for your templates.
Although the PW backend is really intuitive, ever so often my clients need some assistance. Be it they are not so tech savvy or they are not working in the backend often.
For those cases it is nice to make some help videos available to editors. This is what this module does.
A Process module to display help videos for the ProcessWire CMS. It can be used to make help videos (screencasts) available to content editors.
This module adds a 'Help Videos" section to the ProcessWire backend. The help videos are accessible through an automatically created page in the Admin page tree. You can add your help videos as pages in the page tree. The module adds a hidden page to the page tree that acts as parent page for the help video pages. All necessary fields and templates will be installed automatically. If there are already a CKEditor field and/or a file field for mp4 files installed in the system, the module will use those. Otherwise it will create the necessary fields. Also the necessary templates for the parent help videos page and it's children are created on module install. The module installs a permission process-helpvideos. Every user role that should have access to the help video section, needs this permission. I use the help video approach on quite a few production sites. It is stable so far and well received by site owners/editors. Up until now I installed required fields, templates and pages manually and then added the module. Now I added all this logic to the install method of the module and it should be ready to share.
The module and further description on how to use it is available on github: https://github.com/gebeer/ProcessHelpVideos
If you like to give it a try, I am happy to receive your comments/suggestions here.
By Peter Knight
I have a few web forms which require testing on a weekly basis and I don't want the recipients (administrators) to receive these test emails.
What would be a good way to test approx 15 forms from the front end and have the test delivered a list of secondary administrator recipients?
I'm thinking that I could have some kind of config file which watches for a trigger word or email and then understands that it's a test and to bypass the normal admins?
All of the forms ask for an email address so I could setup an email such as 'email@example.com' etc which my config file (hook?) would watch for.
Or is there a better way to do this?
Additionally, I have a few extra requirements...
Forms should goto an alternative success page. This is because I don't want my test to skew my Google Analytics conversion tracking Forms would need to be tested from the front-end and not the PW admin area Any advice appreciated.
BTW I realise this should be posted in the proper FormBuilder support forum. I am in the process of renewing my license for access to that support forum.