All Activity

Thank you @Juergen for the fixes. Sorry not to reply before but I have few free time. ^^ I found more issues: File upload is limited to 500 MB: $zipUpload->setRule('allowedFileSize', '524288000'); But I can add a file larger, the form is valid and the upload starts, but then the server is not happy: With module FrontendLoginRegister, in Account Settings I add Language field. I have 2 languages, french and english, french is default. The form displays the 2 languages only if user is actually using french, when using english, only english is listed in the Select field. If user selects english and save, it works. If user selects french it is not saved. I try to investigate the code quickly, only to find that in Select::___renderSelect(), when user is using english, $option->render() returns an empty string for french.

I've been going crazy for three days trying to figure out how to modify this .htaccess file so that it's acceptable to the server. I took the one generated with the site-blank installation with softeiaculos and transferred it to a site-regular installation. But even then, the site is still not navigable. On permacultura-cattolica.it, you'll see that only the homepage is navigable, not the other pages. For the love of God, isn't there an explanation and solution for this problem in the manual and on the ProcessWire website?

I haven't tried the template caching quite yet but it's on my 'discovery' to-do list for sure!

Thank you so much, you saved my day.

Yep, I confirm this still works today. However, the website in question is still using an earlier version of ProCache. 😄

I completely agree — keeping CSS variables semantically meaningful and scoped at the right level makes a big difference for long-term maintainability. Using names like --muted-color or --masthead-active-color outside their intended context can lead to confusion down the line, especially as the project grows. Your idea of compiling a starting list of variables with clear usage definitions is an excellent step. It’ll help ensure we separate “color intent” (like --text-muted or --background-accent) from “specific context” (like --masthead-bg). Once that foundation is consistent at the root level, we can easily extend or override in components without breaking semantic meaning. Count me in if you start that list — a collaborative approach could really make the design system more scalable and self-documenting.

@Robin S That's the post...not sure why I couldn't find that. Thanks! @ryan Great idea! And here's what GROK just spit out. Very interesting and looking forward to picking up a copy of ProCache very soon. server { listen 80; # Adjust to 443 ssl if using HTTPS server_name yourdomain.com; # Replace with your domain root /path/to/your/document/root; # Replace with your actual document root location / { # Check if request is not POST if ($request_method != POST) { # Check if query string is empty if ($args = '') { # Check if specific cookies are not present if ($http_cookie !~ "(wire_challenge|wires_challenge)") { # Check if cached file exists and serve it try_files /site/assets/ProCache-xxx/$uri/index.html $uri $uri/ /index.php?url=$uri&$args; } } } # Fallback to PHP if no cached file is found try_files $uri $uri/ /index.php?url=$uri&$args; } # Optional: PHP handling for ProcessWire location ~ \.php$ { include fastcgi_params; fastcgi_pass unix:/var/run/php/php-fpm.sock; # Adjust to your PHP-FPM socket fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; } }

@prestoav, thanks for the compliments 🙂 I forked AIOM primarily to fix issues I was facing, and then it somehow developed into the version with the caching options. I don't use minification of CSS/JS. I think it's enough to use simple preg_replace to remove blanks. It's painful to follow and track issues for all libraries now included in the module (voku html_min, simple_html_dom, symphony css selector, lessmin, cssmin, jsmin, ...). Not worth it for those few percentages. But hey, the module works, even on PHP 8.5. Did you try/test caching options? @David Karich, I didn't change the class name as I wanted to preserve its name and your contribution/authorship of the module. Thanks for the module! I'll PM you.

@Jim Bailie This seems like a good question for ChatGPT, at least to get a starting point. I asked it if it could convert .htaccess to nginx and it said: So I uploaded this v1 ProCache ruleset from one of my site (I replaced product key with "xxx" for this example): # PROCACHE vfd31e36cd7ffdab982312621683b6fee RewriteCond %{REQUEST_METHOD} !=POST RewriteCond %{QUERY_STRING} !.*=.* RewriteCond %{HTTP_COOKIE} !^.*(wire_challenge|wires_challenge).*$ RewriteCond %{DOCUMENT_ROOT}/site/assets/ProCache-xxx/$1/index.html -f RewriteRule ^(.*) %{DOCUMENT_ROOT}/site/assets/ProCache-xxx/$1/index.html [L] # /PROCACHE And it gave me this: # PROCACHE vfd31e36cd7ffdab982312621683b6fee equivalent for Nginx location / { # Skip cache if POST request, query string present, or cookie contains wire_challenge / wires_challenge if ($request_method = POST) { break; } if ($query_string != "") { break; } if ($http_cookie ~* "(wire_challenge|wires_challenge)") { break; } # Serve static cached HTML file if it exists if (-f $document_root/site/assets/ProCache-xxx/$uri/index.html) { rewrite ^(.*)$ /site/assets/ProCache-xxx$uri/index.html break; } # Default: pass to ProcessWire (index.php) try_files $uri $uri/ /index.php?$query_string; } # /PROCACHE I have no idea if it's nginx version works or not, but seems like it might be a potentially good way to convert something like this.

Speaking as a user, this module is incredibly helpful and I'd love to see it back in the main module directory and continuing to me maintained. Thanks to you both.

@matjazp Thank you for your work and for keeping the module alive. We can talk about adding you as an owner in the Git repo so that the module can be further developed. If you're interested, just get in touch with me.

Hi @matjazp Thanks for the information. I've be playing with your fork version this morning it's worked well. Any chance you'll add this to the module directory?

This is great! The filter feature alone is so good! Will save a lot of time. Thank you very much for this fantastic module!

Maybe one of these?

This is an inputfield module I made as a replacement for InputfieldPageListSelect, due to frustration with it not opening the page structure to the currently selected page. Please note the requirement of ProcessWire >= v3.0.248 when using it as an inputfield for a Page Reference field due to this now fixed core issue. The module doesn't make the PW version a strict requirement in case you just want to replace instances of InputfieldPageListSelect via the bundled ReplacePageListSelect module. Page Tree Select An inputfield for selecting a single page from the page tree. This inputfield is similar to the core InputfieldPageListSelect, but it has the following advantages: It automatically expands the tree to the currently selected page. This avoids having to drill down through the tree when you want to change the selection to a sibling or child of the currently selected page. This was the primary motivation for creating the module. It's faster to navigate through because the whole tree is rendered at once rather than branch by branch. It provides a filter feature to locate pages by title anywhere in the tree. When the tree is filtered you can hover a page title to see the breadcrumb path to the page in a tooltip. It provides buttons to clear the current selection, to restore a changed selection, and to scroll to the selected page. Configuration The following config options are available when using the module as an inputfield for a Page Reference field: Exclude admin pages: excludes pages from the tree that have the admin template (only affects superusers who can otherwise see pages with this template). Exclude pages by template: pages having any of the templates you select here will be excluded from the tree. Descendants of any excluded pages are also excluded. Limit for total pages in the tree: this limit is applied to the selector that finds pages for the tree (default is 5000). Limitations and considerations Performance seems to be reasonable when the tree consists of up to 5000 pages. Your mileage may vary and the module may not be suitable for sites with a very large number of pages (unless excluding pages by template in the inputfield configuration). Pages in the tree show their titles rather than any custom setting defined for the template "List of fields to display in the admin Page List". Page titles are only shown in the default language. The module does not reproduce some of the quirks/features of ProcessPageList such as excluding pages that are hidden and non-editable, and forcing the sort position of special pages like Admin and Trash. ProcessWire >= v3.0.248 is needed for the inputfield to appear as an option in Add Field due to this now fixed core issue. Replacing InputfieldPageListSelect in the ProcessWire admin An autoload module named ReplacePageListSelect is bundled with InputfieldPageTreeSelect. Install the module if you would like to replace all instances of InputfieldPageListSelect in the ProcessWire admin with InputfieldPageTreeSelect. For advanced use cases there are two hookable methods: ReplacePageListSelect::allowReplacement($inputfield): set the event return to false to disable replacement on particular instances of InputfieldPageListSelect. ReplacePageListSelect::getPageTreeSelect($inputfield): set excludeAdminPages, excludeTemplates and limitTotalPages properties on the event return InputfieldPageTreeSelect object when replacing particular instances of InputfieldPageListSelect. https://github.com/Toutouwai/InputfieldPageTreeSelect https://processwire.com/modules/inputfield-page-tree-select/

I remember a while back someone posted an nginx config file they got to work with ProCache. I CANNOT find this post and if anyone has a better memory or search skills than me, I would be very greatful for a link. I've got another project coming up where we'll be building our first public facing website with PW so I'd like to get going on this. Thanks in advance!

https://github.com/matjazpotocnik/ProcessWire-AIOM-All-In-One-Minify Note that AIOM+ has a caching component, similar to Procache.

Hi @matjazp, thank you for the information. Could you share a link to your fork of this module? Thanks!

[Update] More flexible access mails (v 1.0.11) Just pushed a small update to the module — a few quality-of-life improvements for access mails. What’s new Custom intro text for access mails – There’s a new field called Access Mail Intro Text (optional) access_mail_addon_txt added to your product templates. Whatever you put in there gets prepended to the access mail’s lead text — great for short intros, personal notes, or product-specific instructions. Hookable mail variables – PLMailService adds the hookable method ___alterAccessMailVars($vars, $mod, $user, $links) You can now easily tweak mail content in your ready.php, for example "first purchase vs. repeat purchase": wire()->addHookAfter('PLMailService::alterAccessMailVars', function(\ProcessWire\HookEvent $event) { $vars = (array) $event->arguments(0); $user = $event->arguments(2); // check if this is the user's first purchase $purchaseCount = ($user->hasField('spl_purchases') && $user->spl_purchases) ? $user->spl_purchases->count() : 0; $isFirstPurchase = ($purchaseCount <= 1); if ($isFirstPurchase) { $vars['preheader'] = 'Welcome! Your new access is ready.'; } else { $vars['preheader'] = 'New access added to your account.'; } // Hand back the modified variables $event->return = $vars; }); As always, feedback, ideas, and real-world use cases are more than welcome — especially if you’ve built custom hooks for your own onboarding or mail flows. Cheers, Mike

@prestoav David doesn't maiantain this module anymore. In my forked version this fix is already integrated.

For anyone trying to use this module in PHP 8, after changing the 2x lines mentioned previously in the main module file I was getting the following error at line 314 of /lib/JSMin-2.1.7.php : ord(): Passing null to parameter #1 ($character) of type string is deprecated The line in the file is: if (ord($c) >= self::ORD_SPACE || $c === "\n" || $c === null) { return $c; } Changing it to his solves the issue: if ($c === null || ord($c) >= self::ORD_SPACE || $c === "\n") {return $c;} @David Karich This is a super module and including the three line changes outlined in this thread would be a really nice thing if possible!

Hi, well, all this sounds quite normal, when starting an install process, if the htaccess file is named .htaccess the web site will try to work as if it were installed which is not the case in the contrary, wuen the install process is running/finished this file needs to be renamed as .htaccess with the starting period else it won't work as the server won't find it as a genuine .htaccess file il you have a look à the install.php file code, you'll see when the mutation takes place 🙂 have a nice day

I converted the htaccess.txt file provided with processwire-master to .htaccess, but when I did so, the installation wizard would not start. Instead, the following page appeared: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at webmaster@permacultura-cattolica.it to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request. So I renamed htaccess and the installation process was completed, but now this error message appears in my browser on every ABOUT page of the blog: Not Found The requested URL was not found on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. I wonder what I need to write in the htaccess file to make the server like it. I should note that the installation was completed without any problems using Sopeiaculos with the current server settings. So the server supports Processwire. I had to uninstall and proceed with manual installation because Sopeiaculos installed a blank site instead of the blog.

v1.0.2 Bugfix: Fix deprecation warnings in PHP 8.2 (contributed by esszett in #2) Note that the module now extends the WireData class instead of Wire. This is recommended for modules now and shouldn't cause problems, and it gets rid of any warnings because of undeclared property access. If this is causing any unintended side effects, let me know.

The CustomPath module works fine for our purposes. Thanks for the hint.