Leaderboard

https://www.php.net/manual/en/info.configuration.php#ini.max-input-vars As you may already know, it can be changed in your hosting provider account. Possible solution: https://modules.processwire.com/modules/process-admin-actions/ FTP Files to Page Add files/images from a folder to a selected page. Something that could be useful - to put in the admin.php file (source: Adrian): $this->addHookBefore('InputfieldFile::render', function($event) { $inputfield = $event->object; if($field = $inputfield->hasField) { if(!is_object($field)) return; $p = $event->object->hasPage; $inputfield->label .= ' (' . $p->{$field->name}->count() . ')'; } });

Today, I am glad to announce that the module support the native image field ??

Hello, I would like to present you a new module which aim to facilitate the productivity of your editors/publishers when working on ProcessWire. The idea begun when my co-worker told me that when typing in ProcessWire CkEditor field he was feeling "loosing motivation" when writing big wall of text and/or inspiration. So he opened his web-browser and show me a site looking to Wordpress - feel free to put your preferred emoji here - then he opened Gutenberg... typed some text and moving some "blocks". I understood immediately why he got this feeling with CkEditor. If you or your client feel like this guy, then you will love this module ! What is currently supported ? Features Auto-save Medias upload support HannaCode support Blocks Implemented Heading Image Paragraph Embed Quote Code Link Table (beta) Block Delimiter Raw HTML Note (custom block markup) Feature Request Frontend Edition And there you go for the preview - sorry I am to lazy and bad at typing text so I had a copy/pasta moment : Module featured in the ProcessWire Weekly #317 - Thanks @teppo

This module enables you to automatically create pages based on a ProcessWire page template, eg Calender detail page, that has calendar event recurrences. Download from GitHub: https://github.com/clipmagic/ProcessRecurringEvents

I was impressed by their response time actually. I thought I'd have to wait a while but they managed to resolve it via a live chat (took about 30 minutes).

Awesome! ... well, not awesome that the DNS was messed up, but you know, awesome that they got it solved — eventually ?

Most likely a silly question, but are you certain that the DNS records point to the correct address? Linode didn't change anything regarding these when they upgraded the server? If you check the records for this site manually (host -t A www.yourdomain.com, or nslookup -type=A www.yourdomain.com if you're on Windows), are they correct? Also: if you try the domain with a service like https://isitup.org/, does it work there? Just trying to figure out if it's an issue with your environment, or a more widespread thing ?

Quick update. MB version 026 and 027 have now been merged into master. Please see the linked posts and the extra fields section of the docs for the changes. Thanks.

@Ivan Gretsky Thank you for reminding me about this! Not only are there new features, but the dev version already has fixes for the issue you filed recently! I note that I added these features way back in January 2020! For now, I'll just blame the pandemic/isolation for my forgetfulness ?. I'll merge to master asap. Thanks.

What do you mean by form output? Generelly, forms are used for input ? The first step is to determine which interactions you want to track. For example, you could track an event: ... whenever a form is successfully submitted. ... whenever a form is partially filled but then abandoned. ... each time somebody fills out an individual field (will result in many events). ... whenever somebody finishes an individual step of a multi-step form. Beyond that, you first need to determine what your client wants to know, in terms of specific metrics, interactions etc. Most of those you can do with simple event handlers reacting to form changes, inputs and button clicks. // find all formbuilder forms on the page const FormBuilderForms = Array.from(document.querySelectorAll('form.FormBuilder')); // track the submit button FormBuilderForms.forEach(form => form.addEventListener('submit', e => { // this assumes you're using gtag.js with transport mechanism 'beacon' gtag('event', 'form_submitted', {/** add additional information based on the form data */}); }); A bit more tricky is tracking submissions only after they've been validated server-side, since you can't catch that with JavaScript. However, after submitting a form you will usually show a success message or redirect to a dedicated thank you page, so you can just track those: // FormBuilder uses this ID for the submission message const FormBuilderSuccess = document.getElementById('FormBuilderSubmitted'); if (null !== FormBuilderSuccess) { gtag('event', 'form_submission_result', {/** track the name + result of this submission */}); } Does that answer your question? It's just a matter of determining what you want to track, and then adding appropriate event handlers with JavaScript.

Good day, @kongondo! I can see some great features (like extra_fields option) on a dev branch (added in version 0.2.7). Is there a reason for not releasing it yet for everyone to enjoy on a master branch, which is being installed by default?

You can load all the CKEditor assets in a template by loading the module $modules->get('InputfieldCKEditor'); This will load all assets to $config->scripts and $config->styles Now in your main.php (or template file that renders your <head>) you need to include something like foreach ($config->styles as $file) echo "\n\t<link type='text/css' href='$file' rel='stylesheet' />\n"; foreach ($config->scripts as $file) echo "\n\t<script src='$file'></script>\n"; This approach is only working with the delayed output strategy.

Hi all, greetings! OK another solution, adding here so I don't make the original post too long. So it turns out our client needs, except default language as Greek, also true Greek URLs not only "Greeklish" (as Greek in ascii chars was "baptized" before the UTF-8 wide adoption, from Greek+English). The great thing is that @ryan took care of that as shown here https://processwire.com/blog/posts/page-name-charset-utf8/ It requires ProcessWire 3.0.12+ as explained in the article, so if you're stuck with older versions for any reason, you can use the solution on the original post. We implemented already and it seems to work as expected on the testing server, still testing though. The Greek char mapping is absent from the Core still so adding here the steps we followed (retracing steps from above blog post, adding the Greek chars) 1. Add the following to your /site/config.php file. $config->pageNameCharset = 'UTF8'; $config->pageNameWhitelist = '-_.abcdefghijklmnopqrstuvwxyz0123456789æåäßöüđжхцчшщюяàáâèéëêěìíïîõòóôøùúûůñçčćďĺľńňŕřšťýžабвгдеёзийклмнопрстуфыэęąśłżźαάβγδεέζηήθιίϊκλμνξοόπρσςτυύφχψώω'; 2. In your .htaccess Locate directive 16a (near the bottom of the file) and comment it out by placing a # at the beginning of the line. What we are doing here is disabling the .htaccess limit on only allowing ASCII URLs to pass through to ProcessWire. Below the above directive (16a), you'll see directive 16b, which contains the alternative to the one you just commented out. Un-comment that directive by removing the # from the beginning of the line that it is on. This is what it looks like (minus the line wrapping): (ADDING HERE THE GREEK CHARS) RewriteCond %{REQUEST_URI} "^/~?[-_./a-zA-Z0-9æåäßöüđжхцчшщюяàáâèéëêěìíïîõòóôøùúûůñçčćďĺľńňŕřšťýžабвгдеёзийклмнопрстуфыэęąśłżźαάβγδεέζηήθιίϊκλμνξοόπρσςτυύφχψώω]*$" This is what the names and URLs look now: Cheers, Elissavet from Crowdland

Right — seems like it's an issue with formatting, i.e. single quote gets escaped (converted to HTML entity). Try $sanitizer->selectorValue($page->getUnformatted('title')) instead, that should work.

How does everybody feel about creating a separate language pack for official and/or popular modules which would usually be in the site folder? I just noticed the Norwegian language pack making that switch. Especially for the Pro modules (Lister, FormBuilder) it would be nice to have a drop-in solution. And if you don't need them, just install the core language pack and everything stays the same. As far as I can tell, the current de-DE language pack doesn't include module translations, right? I'd be willing to create a repo and get things rolling.

Not yet, when the website used to promote the module will be ready, the release date will posted here. Same here, and what I can say/confirm, is that once you get your hand into the editor, you will want to use it ? Thanks you for your interest. PS: If you think onto something that should be indispensable and that need to be implemented, please do not hesitate to ask/discuss the feature here.

You can use something like this: $template = $pages->find("template=species"); $children = $pages->find("has_parent=$page"); $windows = $template->import($children); edit: added double quotes (browsercoding is bad)