Recently Browsing 0 members
No registered users viewing this page.
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.
Hello Everyone, I was trying to update SEO meta title, description and meta keywords for my website in Process Wire CMS but it saving in the backend but it is not reflecting on my website, Please help me regarding this error. Please find below attached screen shot for your ref. TIA.
Confession bear meme on tests: I'm a virgin.
Never implemented any of them, mostly because I work alone for many years now. But found this cool project today, called Cypress.
This is the easiest way to test a website or app I've found. Check their intro video out: https://docs.cypress.io/guides/getting-started/writing-your-first-test.html
Note: I recommend this Chrome extension to speed up videos: https://github.com/igrigorik/videospeed as the narration of this video is kinda slow. 🙂
I have been asked by a client whether we can setup load balancing for their existing Processwire site.
From my investigations on Google and within these forums, it definitely seems possible but as a newbie with a basic understanding of the subject im a bit lost.
Does anyone know of any existing tutorials for settings up load balancing with PW?
What items would need to be changed on their current stand alone install, is there a list of best practices worth consulting etc?
As I understand it we would need to have some sort of copying mechanism (rsync script most likely) in order to make sure any uploaded assets are shared between the main server and the fallback ones, other than that im not sure what else would need to be ammended.
Any thoughts/help would be greatly appreciated.