AndZyk

Hello @Flashmaster82, if you think you found an error: Look in the console of your developer tools if there is an error. Try to reproduce the problem on a clean ProcessWire installation. If you can reproduce it, report it on GitHub (https://github.com/processwire/processwire-issues/) with more insights. For me the jQuery date picker is working. So maybe there is an issue on your installation maybe with a conflicting module or caching. Regards, Andreas

❤️ Bonobo

That is what I am doing. I usually add a file field "downloadsForTextareas", which is collapsed if empty by default, to the bottom of the template. That would be nice but works only for images as far as I know, and I have not really used this option yet. I would be nice, if one could set a preferred file field for downloads in the field settings. 👍

I have tested the pull request in the meantime and it works. 👍 I am now using the module with pull request, but it would be nice if the module author could merge it.

That was just my attempt of being funny. I thought the smiley would make it clear, but of course I don't want to blame or disrespect anybody. 😉 If you have reasons to use a PHP version, which had its end of life 4 years and 5 month ago, this is fine. Like you said it is your own decision.

My wording "required" wasn't good. Looking at competitors I think it should be maybe: Minimum PHP 7.2 or PHP 7.4. Recommended PHP 8. If you still use PHP 5 in 2023 I think you should search help. 😊 Thank you for making things clear. I understood your first sentence exactly, that you had experienced those issues with PW, which is not my experience at all. I also think that GitHub branches in general should try to target no warning/errors or blank pages. Regarding PW that is already the case in my opinion.

I think this is an unfair statement. In my experience PW had no warnings or errors with PHP 8.1 since PW 3.0.210. And for compatibility with PHP 8.2 there is a GitHub issue where you can report warnings or errors: https://github.com/processwire/processwire-issues/issues/1664 So if you @cwsoft really have experienced a warning, error or "blank page of death", could you please provide an example or report it to this thread? 😉 Since PHP 8.2 is the latest version and PW has a big core, I think it is fair not to expect it to be compatible with it over night. Requirements In my opinion I think the minimum recommended PHP version should be the last supported PHP version: https://www.php.net/supported-versions.php So at the moment this would be PHP 8.0. Recommending an unsupported PHP version maybe would not make a good first impression. Versioning In my opinion I also would recommend switching the versioning of PW. PW 3.0.xxx started in 2015 and while I understand the explanation for the versioning process, from a marketing and user perspective there is lack of distinction between the different versions. Other CMS celebrate major upgrades with a major version bump (3.1 or 4.0) and some give those versions even silly names just to make it clear in the marketing or for the users, that this version has something special to offer. 😀 But as always, much love for PW. ❤️

Thank you both for your sharing. Maybe @wbmnfktr wants to share his approach too, because I think he uses TailwindCSS as far as I know? 😊

Sorry, if this is off-topic, but I am wondering regarding TailwindCSS: Since TailwindCSS covers the CSS part of components, what do you use for making the components interactive? Like for example a carousel, accordion etc. I saw that there are frameworks for TailwindCSS like daisyUI, Flowbite or Tailwind Elements. But isn't that the same like using a framework like Bootstrap or UIkit? Or do you use a different plugin for every component? One thing I like about frameworks like Bootstrap or UIkit is, that they offer a complete package. I don't want to be too dependent on many third-party plugins.

Hello @zx80, I have no experience with translating modules, but have you tried the instruction of the ProcessHello module? Source: https://processwire.com/modules/process-hello/ It seems that you create those CSV files via the backend and then download them to bundle them with your module. Regards, Andreas

That seems to be the defaultExtractor of the PurgeCSS configuration: https://purgecss.com/configuration.html So sadly no regex for safelisting UIkit classes. 😊

I have tried PurgeCSS today on UIkit with my good-old CodeKit App: https://codekitapp.com/help/purgecss/ It works for a majority of the classes, but it seems that PurgeCSS doesn't recognize rules like for example .uk-child-width-1-4@m > *. For this you have to write regular expressions to safelist these classes: https://purgecss.com/safelisting.html But I never really got the hang of regular expressions, so I might will pass. It seems too much of a hassle just to reduce maybe 100 kb of CSS. 😅 I guess PurgeCSS works best with utility based frameworks like TailwindCSS, where there are not much complex opinionated CSS rules.

You can reduce unused CSS in UIkit if you manually only import the needed component partials from _import.scss. But yeah it would be nice if UIkit would have a automatic way to reduce unused CSS like PostCSS. I hope this will be a feature of UIkit 4. 😀

One more thing if you are building your own form: You can clean every data entered in the form by sanitizing every input. 😉 https://processwire.com/api/ref/sanitizer/ $fullname = $sanitizer->text($input->post->fullname); // Long $fullname = $input->post->text("fullname"); // Short https://processwire.com/blog/posts/processwire-2.6.14-brings-major-enhancements-to-sanitizer-and-input-api-variables/#sanitizer-and-input-are-now-a-couple

That is also a option. 😀 If you just want to exclude search engines, you could make your page hidden and exclude it in your robots.txt But if you wan to protect your page, a .htaccess protection works as well. You could try the free LoginRegister module, if you want a better looking login form integrated with PW: https://github.com/ryancramerdesign/LoginRegister There is also a commercial successor of this module: https://processwire.com/store/login-register-pro/ Regards, Andreas

Hello @zx80, I would go with a module for forms like the commercial FormBuilder or aformentioned FrontendForms. I have build forms in the past, but nowadays I use FormBuilder for every form, because forms can be complex to develop and maintain. Both FormBuilder and FrontendForms have protection well covered: https://processwire.com/store/form-builder/#spam-filtering-features https://github.com/juergenweb/FrontendForms#spam-protection-and-security-features For protection I am always using a honeypot and Google reCAPTCHA field with filtering by specific mail addresses or keywords, when I still get Spam. FormBuilder has an extra module for a Google reCAPTCHA field. Regards, Andreas

Hello @Boost, have you seen this page: https://processwire.com/about/wordpress-vs-processwire/ ? 😉 Regards, Andreas

Hi @franciccio-ITALIANO, it seems, that you always have the same ID "block01" for all your modals, so only one modal will always be opened? You should make the ID dynamic. <?php foreach($page->box_ripetitore as $b => $boxrip):?> <!-- INIZIO BLOCCO RIPETUTO --> <div class="<?php echo $boxrip->box_ripetitore_colore?>"> <div class="uk-tile" id="op31h2"> <a href="#block<?=$b?>" uk-toggle> <h2 style="font-family: Anton; font-size: 3em; color: white;"><?php echo $boxrip->box_ripetitore_tit?></h2> </a> <div style="font-family: Oswald; color: gold; font-size: 1.5rem;"><?php echo $boxrip->box_ripetitore_sottotitolo?></div> <!-- SEZIONI FOGLIA --> <div id="block<?=$b?>" class="uk-modal-container" uk-modal> Regards, Andreas

Future Bass + World Music = Jungle Bass CloZee: Queen of Jungle Bass 🔥😍🤩

Hello @Roope, first of all thank you for your module. I am a long time user of your module and so far it has been working really fine. 😀 With PHP 8.2 I get following warning: Other than that the module is working normal. If you please could fix this warning that would be great. There is already a pull request for this warning, but I have not tested it. Regards, Andreas

Thank you @bernhard for pointing me to this thread. This explains why this behaviour is necessary, although I wish it wouldn't. 😀 Then I will stick to my hook solution, if this is a recommended solution for this case. So far I haven't used custom page classes, but thanks for the hint.

I have figured out which hook suits my case and decided to pre-select the options with the pages added hook: // Hook after page added $this->addHookAfter('Pages::added', function(HookEvent $event) { $page = $event->arguments(0); if ($page->template->name === "job") { // Pre-select job buttons $page->setAndSave("jobButtons", [1, 2]); } }); But I find this solutions still not very satisfying, because I think it should be possible to pre-select options without having the field to be required. Unless there is a reason behind, that I am not able to see.

Hello, a client wanted to have the option to activate/deactivate two buttons on a page. But the default behaviour should be that both buttons are activated. So I have added a select options field with two options, which control if the buttons are visible or not. Now I can set both options to be preselected, but in order to makes this work, the field has to be required. But I don't want this to be a required field, because pages also should have the option to show no buttons. I honestly don't understand what's the reason, why this field has to be required, in order to show preselected options. Now I could add a third option "No buttons" or flip the logic to use this field for hiding butttons or I could use a hook for preselecting the options. But I am not sure which hook to use. But I hope there is a more elegant solution. Had somebody else this case before? I think this should be a common case. Regards, Andreas

If the customer only wants to control the first level, then a page reference field should be enough. If the customer wants to control everything, then maybe a repeater with depth and page reference field should do the trick: https://processwire.com/blog/posts/pw-3.0.44-repeaters/ But I never had this case. Most clients want just rarely changes, which you can update in your code.