markus-th

Hi everyone, For those of you running into compatibility issues with PHP 8 or needing a newer version of the underlying mPDF library, I wanted to let you know that I am working on a modernized successor to this module. To avoid clogging up this thread, I have started a separate discussion about the new project (currently named Wire2Pdf) here: If you are interested in a maintained version with PHP 8 support and new features, please join the conversation over there. Thanks!

Hi everyone, Like many of you, I have relied on the Pages2Pdf module in the past. It was a great tool, but unfortunately, it seems to be no longer actively maintained. With the shift to PHP 8 in most modern environments, the older version of the underlying mPDF library used in the original module has become a bottleneck, causing compatibility issues. Since I needed a working solution for a current project, I have already created a fork and updated the code to work with a newer, PHP 8 compatible version of mPDF. The Idea: Wire2Pdf I am planning to release this updated version as a new module under the name Wire2Pdf. This would distinguish it from the legacy module and allow for new features (like custom font support) without breaking older installations. What I have done in a fork so far: Code refactoring for PHP 8 compatibility. Updated the mPDF library to a recent supported version. -> https://github.com/markusthomas/Pages2Pdf Before I proceed... I wanted to check with you first: Is there still a strong interest in a maintained module based on mPDF, or have you moved to other solutions (like RockPdf)? Are there specific pain points you had with Pages2Pdf that I should address if I move forward with Wire2Pdf? If there is enough interest, I will polish the code, package it as a new module, and release it. Cheers! Markus

Hi everyone, I wanted to share a small utility module I’ve put together to help keep the /site/modules/ directory tidy. What it does: When updating modules ProcessWire renames old module directories by prepending a dot (e.g., .ModuleName). Over time, these "hidden" backup folders can clutter your file system. ProcessModuleCleaner identifies these orphaned directories and allows you to delete them directly from the admin interface. Key Features: Automatic Detection: Scans your site modules folder for any directory starting with a dot. Native UI: Built specifically for the ProcessWire backend using UIkit 3 classes for a seamless look. Interactive Selection: Uses AlpineJS for a fast and responsive "select all" and delete workflow. Safe Deletion: Uses ProcessWire's WireFileTools for reliable recursive directory removal. How to use: Install the module. Navigate to Setup > Module Cleaner. Review the list of found folders. Select the ones you want to remove and click "Delete". Screenshot / UI: The module displays a clean table with the folder name and the last modified date, so you know exactly how old those backups are. GitHub: https://github.com/markusthomas/ProcessModuleCleaner Module Directory: https://processwire.com/modules/process-module-cleaner/ I hope some of you find this helpful for keeping your production or development environments clean! Feedback is always welcome. Cheers!

There is a module in development: https://processwire.com/talk/topic/31052-xforum-proof-of-concept-front-end-forum/ I tested it a while ago, and it worked fine. You only have to customize the styling to your needs.

If you dynamically add parameters to your link, you can use them in a hook: $wire->addHookBefore('Pages2Pdf::download', function($event) { /** @var Pages2Pdf $module */ $module = $event->object; $input = $event->wire('input'); $sanitizer = $event->wire('sanitizer'); // 1. Check if we are in your specific scenario // (Optional: limit this to specific templates if needed) $page = $event->arguments(0); if($page->template != 'your-list-template') return; // 2. Retrieve your filter parameters from the URL // Example URL: ?pages2pdf=1&filter_category=music&date=2023 $category = $input->get('filter_category'); $date = $input->get('date'); // 3. Build a safe filename string // It is crucial to sanitize these inputs to avoid invalid filesystem characters $filenameParts = [$page->name]; if($category) { $filenameParts[] = $sanitizer->pageName($category); } if($date) { $filenameParts[] = $sanitizer->pageName($date); } // Add unique ID or timestamp if you want to avoid caching conflicts completely // $filenameParts[] = time(); $newFilename = implode('-', $filenameParts) . '.pdf'; // 4. Overwrite the module setting for this specific request $module->set('filename', $newFilename); }); Important: The hook must be implemented via init.php. It does not work in ready.php. Actually tested it here to add the amount of portions into the filename: https://www.dothiscookingthing.de/rezepte/lachs-spiesse-mit-garnelen-aus-dem-ofen/

What I meant to say was that the relaunch was perhaps a little rushed. It's not a good user experience if the users doesn't get what is presented to them.

Has anyone else noticed that the screenshots of the “new” backend are incorrect, as it does not exist at all in the current master?

I'm confused. Isn't ProcessWire primarily the tool we want to convince more developers to use in order to gain a larger user base? So this page should primarily be used to convince developers of the advantages with examples (sorry to say that) instead of animations that have nothing to do with ProcessWire. To convince customers of the system, it would be better to provide a good demo that shows how simple ProcessWire is to user. However, this could also be done here, among other places: https://www.softaculous.com/apps/cms/ProcessWire

I see this the same way on Win 11 with Chrome/Firefox/Opera/Edge.

I think everyone here knows that and just wants to help improve the site for new users. On the download page I noticed Softaculous: Here, especially with regard to new users, the text could be updated. However, in my opinion, the demo available there is a problem that is more likely to deter new users than get them excited about ProcessWire: No one new to Processwire can figure out the backend or anything else from this demo.

I found some issues in the modules directory: Long Text on a paid module need a bit of a gap. Also the paid-filter don't work properly, none of @bernhard's modules are shown.

Unfortunately, it still doesn't work. @diogo Not such an easy fix after all?

My quote of the century

You had Padloper v1, the Migration is for Padloper v2. I think it is better to start from the scratch. @kongondo Please update the title, I also thought I could migrate my old Padloper v1 store to PWCommerce.

Everything you need is already in ProcessWire 😉 Look in the details-tab from your image-field -> https://processwire.com/blog/posts/pw-3.0.142/ For CK-Editor: In the image-dialog you can set alt an "title" (figcaption)

I use the RepeaterMatrix in most of my installations to build page content. To make elements visually easier to grasp, I use the option to adjust the colors in the item headers. Unfortunately, this no longer works with the new theme. Original: New Default: New default with @ryan's admin-tweak.css @adrian I agree with that. In my opinion this is not a good user experience. The "old" style was a lot better/faster to scan.

@bernhard this Setting-Options only appears when you Choose "Default" not when you go to "Original". I agree, the options to choose the favorite theme would be a good solution.

There is a lot of talk about “design by committee,” which I also think is wrong. But nobody asked for this, not even @bernhard. I have followed his posts very closely and all I can see is that he had hoped that the community would be consulted before the design phase. And I absolutely agree with him on this point, because if wishes and ideas had been solicited beforehand, I am quite sure that this thread would have been much less emotional. Now to my “problems” I currently manage nearly 50 active ProcessWire projects, and the advance announcements of a more modern admin theme naturally raised expectations that have now turned to disappointment for me, as many of my installations run on UIKit-based custom modules that are sure to cause problems with the CSS overrides. For me, this means that all development systems will soon need to be updated to the DEV version in order to identify and address any problems. I hope to find the time soon to contribute constructively to improving the theme.

At first you should check the errorlog. To find it go with FTP to site/assets/logs/errors.txt Normaly it is easy to update Processwire with simply upload the new wire-folder, index.php & .htaccess to your server (it depends a bit on your previous PW-Version) Here you find the Upgrade-Guide -> https://processwire.com/docs/start/install/upgrade/

I only use the API key in Curl requests and that works perfectly. (PHP-Session) $url = "API-URL"; $curl = curl_init(); curl_setopt($curl, CURLOPT_RETURNTRANSFER, 1); curl_setopt($curl, CURLOPT_URL, $url); curl_setopt($curl, CURLOPT_HTTPHEADER, array('x-api-key: *******************')); $data = curl_exec($curl);

Gemini (Basic 2.0 Flash) - not so bad.

I think URL hooks can be a good solution for this case: https://processwire.com/blog/posts/pw-3.0.173/

Many thanks for the module. I have some small ideas that could make it easier to install the forum on an existing site and integrate it seamlessly into the layout. Are you planning to make the module available on GitHub?

Nice, thanks for sharing. BTW: Works also perfect for the ProModule RepeaterMatrix from @ryan

@Klenkes I currently have the same problem with v 1.0.9, after a downgrade to v 1.0.8 everything works as expected again.