Leaderboard

PwQuickFixes This module is intended to serve as a collection of ProcessWire fixes that can easily be enabled via checkboxes in the module's config. It is NOT intended to be a replacement for github issue reports or pull requests! The idea is that we have a place where we can put fixes for issues that are not yet fixed in the core until they get properly fixed there. It is also not my intention to put pressure on Ryan to fix issues quicker. The idea is that we have a place where we can share our fixes across projects and across users and maybe get a better feeling on the "impact" of different issues. The module could also make it easier for Ryan to test issue reports and the solutions provided by the community: Intended Workflow Identify an issue Create the related files in the fixes folder of this module Create a PR so that I can merge the fix and everybody can use/test/improve it Create an issue in the official PW issues repo and link the fix in your description Usage Just add your fixes in the fixes folder and activate them in the config of this module (via checkbox). See the Foo example module how to add JS and CSS. https://github.com/BernhardBaumrock/PwQuickFixes

Oh gosh! It's so relieving to know mine is still in pretty good shape comparing to you guys. It is still new and shining (when looking from some angles). The only thing with it really is that my then 2-year old managed to take off the up arrow key. I do not know how can a little kid make something totally disappear in just a few seconds. He did not eat it (at least nothing came out). I searched everywhere, found quite a lot of useful stuff, but not the key. So I moved F10 as a substitute as it is obviously much less critical one. A few little tips for someone in the very same situation: Use Esc+0 to quit Midnight commander. Use a pencil to save bios configs. Never worry 'bout anything else!

Glad you stopped that infectious thing before it could take CTRL of world domination! ?

Even though I feel pretty confident in using and working with Processwire and building lots and lots of different projects with it... your task/idea would be still a challenge for me - in some kind. There is so much more involved than just a registration form, all those fields, user restrictions, notifications, and whatsoever. To be fair... you will have to code and customize a lot here. Installing a few (more) modules wouldn't do the trick. If this is kind of a long-term or fun project to get more into coding and challenging yourself: just start, try and break things, rebuild your code, do whatever is needed. If this is a paid job or something you really want to share with others: well... maybe look for something that already exists, that is tested and maintained. Like this forum. It's a super solid piece of software. Not that cheap but robust, tested and maintained.

Sorry, I didn't count correctly. There are much less possibilities: 991677934870949689209571401541893801158183648651267795444376054838492222809091499987689476037000748982075094738965754305639874560000000000000000000000 ?

Hey, @Macaco! This very question has been asked a trillion of times on the forums. And here is the way to find the answers already given: go here and search. The forum search does not work well. The closest to what you desire is probably the Duplicator module, but I never used it in production. I suggest you make yourself comfortable with moving you site here and there "with bare hands" anyway. It is not that hard. You just need to: Copy files. Backup database and restore it where you want the site to be moved to (probably some local dev env like xampp or laragon). Adjust site/config.php (or better use config-dev.php - look here at the very botoom). There is a lot to it only the 1st time)

ryan had helped me a few weeks ago via PN. sorry that i didn't write the solution in the forum before. i hope it's no problem that i write the private message here.

@entschleunigung and/or @Vivian Please create an issue on the processwire-issues repository on Github for this, as it needs to be looked at. @entschleunigung If you don't have a github account, just sign up for a free account, then follow the numbered steps on this page to add the issue to the issues repository. Thank you for your co-operation!

RockAwesome ProcessWire Fieldtype to easily choose FontAwesome Icons Usage Install the module. Set paths in the Inputfield's settings page. Add a RockAwesome field to any template (or change an existing TEXT field). Preview https://modules.processwire.com/modules/fieldtype-rock-awesome/ https://github.com/BernhardBaumrock/RockAwesome

This week we’ll take a quick break from core updates and have a look at a new module called UserActivity, just added to the ProcessWire ProDevTools package— https://processwire.com/blog/posts/user-activity-module/

Tis the season to clean out the mechanical keyboard (first time in 7 years)...

Kids are, - hmm, well, - mysterious. Many, many years back, when I bought my first pelican case, you could read something in the warranty description like: :-)

Have you cleared all previous cookies and session files? Just to make sure there aren't any "old habits".

ProcessWire is mature enough. But is not a ready-made solution for this niche, like the names you mentioned. I have made a system quite similar to what you've described here. But it was a lot of work. And it was made with PW to support dealing with objects already in PW. So I would support @wbmnfktr here. If you got time budget and the skills (or want to aquire them), and you know you will use ProcessWire for some things not available out of the box in the ready-made solutions, than go for it using PW. If not and you just need a quick turnover, use one of a plethora of ready made stuff. Just test it out out before making a final decision.

Yeah, the idea is to have a shared place where we can apply those fixes and do not have to wait for core fixes. The benefit compared to placing hooks into /site/ready.php is that we can share our code, it's easier to test in different environments and we can provide better suggestions for a fix to ryan. PS: Happy 1000 @wbmnfktr ?

Oh...kay... that clears up some things. So instead of waiting for the official fix we can now apply our fix to our environment whenever needed. Sounds great for those like you and @adrian who love to dig deeper into the core code. ?

Sorry for the confusion ? There are several issues with the PW core. Some of them get fixed quickly, some don't. All those issues exist on every project and one has to fix them on every project. This module makes it easy to place fixes in a central place and activate them one by one. It was just a quick idea when I read this comment today: https://github.com/processwire/processwire-issues/issues/802 I've just added a fix for the annoying 404 error: https://github.com/BernhardBaumrock/PwCoreFixes/commit/c4fa410654d0d4a4f8a50c53315a350cdf60d347

Yep, I think the most tips above linking to the blog are only valid for greater pw versions. (Dev-Branch)

@bernhard just installed RockAwesome to have a play with it. It's excellent! Straightforward and intuitive... Thank you.

They do it all the time. No matter how many accounts exists... most of the time all people use just one. I always try to convince clients not to share accounts, but in some cases they flatly express that they will indeed use "shared accounts" no matter what. Their excuse usually boils down to laziness: they do not want to deal with managing users at all. In such a case I ask them at least to call such a user as "shared editor" or similar so that at least we know how to treat that account in question. So for the reasons outlined above, some support for this would be welcome, maybe with some additional logging options so that we can track down such activities even days after...

In those times when I was still smoking and rolling myself I had to vacuum my keyboard twice a day! Insane! This way the keyboard lastet 8 to 12 months. No longer. Full ashtray and tobacco crumbs all over the place, and the coffee! THE COFFEE! The diabolical mix of the three elements locked up CTRL and SHIFT first and then the TAB key. Haha... I wish I had photos of that scenery, I would have won this content! For sure!

@charger I have no other ideas how to solve your case. Could you describe the steps to reproduce the error? You can take a starting point of any site profile and outline the steps to reproduce the issue. That would make it much easier for me to help you.

Shouldn't the manufacturer name be FILTHCO?

You have 99029007164861804075467152545817733490901658221144924830052805546998766658416222832141441073883538492653516385977292093222882134415149891584000000000000000000000000 possibilities to put the keys back... ?

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. ProcessHelpVideos Module 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.

REMOVED Free Processwire Template