I want to share a new module with you, which makes the creation and validation of forms easy.  Take a look at the following example of a simple contact form:

// A very simple example of a contactform for demonstration purposes

$form = new Form('contactform');

$gender = new Select('gender');
$gender->setLabel('Gender');
$gender->addOption('Mister', '0');
$gender->addOption('Miss', '1');
$form->add($gender);

$surname = new InputText('surname');
$surname->setLabel('Surname');
$surname->setRule('required');
$form->add($surname);

$name = new InputText('name');
$name->setLabel('Name');
$name->setRule('required');
$form->add($name);

$email = new InputText('email');
$email->setLabel('E-Mail');
$email->setRule('required');
$form->add($email);

$subject = new InputText('subject');
$subject->setLabel('Subject');
$subject->setRule('required');
$form->add($subject);

$message = new Textarea('message');
$message->setLabel('Message');
$message->setRule('required');
$form->add($message);

$privacy = new InputCheckbox('privacy');
$privacy->setLabel('I accept the privacy policy');
$privacy->setRule('required')->setCustomMessage('You have to accept our privacy policy');
$form->add($privacy);

$button = new Button('submit');
$button->setAttribute('value', 'Send');
$form->add($button);

if($form->isValid()){

  print_r($form->getValues());
  // do what you want

}

// render the form
echo $form->render();

This piece of code creates a simple contact form and validates it according to the validation rules set. Inside the isValid() method you can run your code (fe sending an email)

Highlights:

• 30+ validation types
• Support for UiKit 3 and Bootstrap 5 CSS framework
• SPAM protection
• Highly customizable
• Hookable methods for further customization
• Multi-language

You can download and find really extensive information on how to use at https://github.com/juergenweb/FrontendForms.

Please report errors or suggestions directly in GitHub.

Best regards and happy testing ?

If you have downloaded the module in the past I recommend you to uninstall the module completely and install the newest version 2.1.14. There are a lot of changes in the new version, so please test carefully.

The intention for the development of such a module was to provide a ready-to-use solution for user management, which can be installed and put into operation in a few minutes.

It works out of the box, but it provides a lot of configuration settings in the backend:

Highlights

• "One-click" integration of an user login/registration system without the hazzle of creating all pages and forms by hand
• "One-click" switch between login or login and registration option
• Double opt-in with activation link on new registrations
• Option for automatic sending of reminder mails, if account activation is still pending
• Option for automatic deletion of unverified accounts after a certain time to prevent unused accounts
• Option to use TFA-Email if installed for higher security on login
• Mutli-language
• Select if you want to login with username and password or email and password
• Select the desired roles for newly created users
• Select, which fields of the user template should be displayed on the registration and profile form (beside the mandatory fields). Fields and order can be changed via drag and drop functionality
• Offer users the possibility to delete their account in the members area using a deletion link with time expiration
• Customize the texts of the emails which will be send by this module
• Usage of all the benefits of FrontendForms (fe. CAPTCHA, various security settings,...)
• Support for SeoMaestro if installed
• Lock accounts if suspicious login attempts were made
• Support of Ajax form submission

This module runs on top of the FrontendForms module, so please download and install this module first.

UPDATE 03.11.2023: The module is now available inside the Processwire modules directory: Frontendloginregister

This module is early Beta stage, so please do not use it on live sites at the moment.

If you discover any issues, please report them directly on GitHub ?. Thanks!

I’m happy to share NativeAnalytics, a native first-party analytics module for ProcessWire.

The module is now available in the ProcessWire modules directory:
https://processwire.com/modules/native-analytics/

NativeAnalytics provides a useful analytics dashboard directly inside the ProcessWire admin, without relying on external analytics platforms, third-party scripts or external APIs. All analytics data is stored locally in your ProcessWire installation, which makes it a good fit for projects where you want a simpler, more self-contained analytics solution.

The module currently tracks and displays:

• page views
• unique visitors
• sessions
• current visitors
• top pages
• referrers
• devices and browsers
• 404 hits
• engagement events such as form submits, downloads, tel/mail clicks, outbound clicks and custom CTA events

It also includes:

• charts and trend views
• comparison between periods
• custom date range filtering
• page-level analytics inside the page edit screen
• optional monthly email reports
• optional PDF report attachments
• exports to CSV, PDF and DOCX
• helper examples and a small snippet generator for custom event tracking

New in the latest version:

• Goals and conversion tracking
• event-based goals, for example form submits, CTA clicks, downloads or tel/mail clicks
• page/path-based goals, for example thank-you pages or booking confirmation pages
• conversion rate reporting based on sessions and unique visitors
• a dedicated Goals dashboard with goal cards, goal trends and goal overview
• easier goal setup with helper text, quick presets and suggestions from already tracked events and pages
• daily aggregate tables for events and goals
• raw event retention setting
• additional database indexes and cleanup helpers for larger datasets

There are also several privacy and consent-related options:

• optional cookie-less visitor/session mode
• consent-based tracking
• helper functions for custom consent integrations
• optional PrivacyWire localStorage consent helper support
• cleaner behaviour when global tracking is disabled

The reason I built this module was that I wanted something that feels natural inside ProcessWire itself, instead of embedding another analytics service into the admin. For many sites, it can be useful to have core traffic, engagement and conversion data available right where content is managed.

Goal tracking was added because several users asked for a simple way to measure important actions without having to fight with external analytics tools. For example, you can now create a goal for a contact form submit, a CTA button click, a file download or a visit to a thank-you page, and then see conversions and conversion rates directly in the ProcessWire admin.

A small note about very large datasets: NativeAnalytics includes retention settings, daily aggregate tables and cleanup tools, and the latest version improves this further for events and goals. For very high-traffic sites, I still recommend using sensible raw data retention and keeping long-term reporting based on aggregated data. I do not want to overclaim without real long-term benchmarks on extremely large datasets, so feedback from larger installations is very welcome.

! If you tested one of the earlier development versions named PW Native Analytics, I recommend uninstalling that old test version first and installing NativeAnalytics as a fresh module, because the module name and structure changed during development.

Multi-site analytics is not included yet, but it is something I am looking into. It would need proper per-site separation in the stored analytics data, so I want to approach that carefully rather than adding a quick workaround.

Feedback, bug reports and suggestions are very welcome.

Get it here:
https://processwire.com/modules/native-analytics/

Enjoy!

If you find NativeAnalytics useful and would like to support further development, maintenance and testing, a small donation is always appreciated.
The module will remain free, but support helps me spend more time improving it and adding new features.
DONATE

It adds a Settings item to the ProcessWire admin menu and creates one central page for global site values like:

• copyright text
• footer content
• contact info
• social links
• SEO / AI summary text
• images
• repeaters
• Repeater Matrix
• page references
• other regular PW fields
  Ofc. add your own fields of choice to it, or delete the ones you don't need!

It uses a normal template + page approach instead of a fake config form, so it works much more naturally with ProcessWire fields.

It also includes a small helper box on the settings edit screen that shows ready-to-use template snippets for each field. It tries to generate smarter examples depending on the field type, including more complex fields like images, repeaters, matrix items, multi-value fields, etc.

Settings Menu:

Editing Values, adding/deleting custom fields and shortcut to Fields for quick creation of new ones.

Quick helper for showing everything on frontend!

Example usage on templates:

<?= siteSettings('ss_copyright_text'); ?>
<?= siteSettings()->ss_footer_text; ?>
<?= $siteSettings->ss_contact_email; ?>

The admin is in English and the module is translation-ready.

Just install the module, and that's it!

Just sharing it here in case someone finds it useful.

Download Here:
ProcessSiteSettings-v13-fixed.zip

• "What templates does this site have?"
• "Show me the fields on the blog-post template"
• "Search for pages containing 'summer'"
• "Find all images with 'lake' in the filename"

Why I Built It
Cursor can see your template files and code in the local directory, but it can't see what's actually in your ProcessWire database — which templates and fields are registered, what pages exist, or what content they contain.

With ProcessWire MCP, the AI can:

• Query the actual database schema (not just parse template files)
• Look up page content by ID, path, or selector
• Understand field configurations (types, settings, which templates use them)
• Search across all text content and find files/images
• Get RepeaterMatrix content with type labels
• See file metadata (dimensions, descriptions, URLs)

It's the difference between seeing $page->body in code vs. knowing what that page's body actually contains.

Architecture

Cursor Chat → MCP Server (Node.js) → PHP CLI → ProcessWire API

The module consists of:

• PwMcp — A ProcessWire module with a CLI interface
• mcp-server — A Node.js server that speaks the Model Context Protocol

The CLI can also be used standalone for quick queries from terminal.

Available Commands
 

Example: Health Check

php site/modules/PwMcp/bin/pw-mcp.php health --pretty

{
  "status": "ok",
  "pwVersion": "3.0.241",
  "siteName": "www.example.com",
  "moduleLoaded": true,
  "counts": {
    "templates": 45,
    "fields": 72,
    "pages": 960
  }
}

Example: Content Search
Ask Cursor: "Search for pages containing 'summer'"

{
  "query": "summer",
  "count": 5,
  "results": [
    {
      "id": 1764,
      "title": "Lake District walks in summer",
      "path": "/guides/lake-district-summer/",
      "template": "page-guide",
      "matchedField": "Body",
      "snippet": "The Lake District offers some of the best walking trails in summer. From gentle lakeside strolls to challenging fell walks..."
    }
  ]
}

Example: File Search
Ask Cursor: "Find images with 'lake' in the filename"

{
  "query": "lake",
  "count": 5,
  "results": [
    {
      "filename": "lake-windermere-sunset.jpg",
      "url": "/site/assets/files/1070/lake-windermere-sunset.jpg",
      "size": 31207,
      "sizeStr": "30.5 kB",
      "description": "Sunset over Lake Windermere",
      "field": "Images",
      "page": {
        "id": 1070,
        "title": "Lake District walks in summer",
        "path": "/guides/lake-district-summer/"
      },
      "width": 500,
      "height": 626
    }
  ]
}

Example: Get Page with All Fields
Ask Cursor: "Get the page at /about/"

{
  "id": 1050,
  "name": "about",
  "path": "/about/",
  "url": "/about/",
  "template": "basic-page",
  "status": 1,
  "statusName": "published",
  "parent": {
    "id": 1,
    "path": "/",
    "title": "Home"
  },
  "numChildren": 5,
  "created": "2023-05-15T10:30:00+00:00",
  "modified": "2024-11-20T14:22:00+00:00",
  "fields": {
    "title": "About Us",
    "body": "<p>We are a team of dedicated professionals...</p>",
    "Images": {
      "_count": 2,
      "_files": ["team-photo.jpg", "office.jpg"]
    }
  }
}

Example: RepeaterMatrix Support
The module fully supports RepeaterMatrix fields, returning the actual content with type labels:

{
  "matrix": {
    "_count": 3,
    "_items": [
      {
        "_typeId": 1,
        "_typeLabel": "Body",
        "Body": "<h2>Welcome to our guide</h2><p>This guide covers...</p>",
        "Images": null
      },
      {
        "_typeId": 2,
        "_typeLabel": "FAQs",
        "faq_question": "What is the best time to visit?",
        "faq_answer": "The summer months offer the best weather for walking..."
      },
      {
        "_typeId": 3,
        "_typeLabel": "Call to Action",
        "cta_title": "Plan Your Visit",
        "cta_link": "/contact/"
      }
    ]
  }
}

So thats the first part done and working.

My next plan is to be able to 

1. PULL / convert a databse page into a local text file which lists all page properties, fields, template etc
2. edit the file as a local text file
3 PUSH the text file back into PW so that the original content picks up the changes

Just having fun and building something useful. Very likely there are similar solutions or better ways to handle this but this suits my workflow ATM.
Cheers
P

I am currently developing a new module for a client project and wanted to quickly reach out to see if there is broader interest in the community for a solution like this.

The Use Case My client needed an appointment booking system similar to "Calendly". However, they had specific requirements:

1. Zero external dependencies: No third-party SaaS for GDPR/DSGVO compliance and to avoid monthly fees.

2. Full Design Control: It had to fit seamlessly into their custom design.

3. Lightweight: No heavy bloat.

The Solution: WireBooking is a native ProcessWire module that handles appointment slots and bookings using standard ProcessWire pages.

Current Features:

• Frontend Wizard: An interactive, step-by-step booking process built with AlpineJS and Tailwind CSS.

• Native Storage: Bookings are saved as standard ProcessWire pages (booking-entry), allowing you to use the full power of PW selectors and hooks.

• Backend Management: Simple interface using the native ProcessWire Admin Theme (UIkit) to view bookings.

• Notifications: Sends confirmation emails to the customer and admin, including generated .ics calendar files for Outlook/Apple/Google Calendar.

• Availability Management: Manually block specific time slots or entire date ranges via the module settings.

• AJAX Driven: Dynamically loads available slots via JSON to keep the initial page load light.

The "Catch" (Requirements) To keep the module lightweight and modern, it is opinionated regarding the frontend stack. It assumes you are already using (or are willing to include):

• Tailwind CSS (Utility classes) for the styling.

Usage Example: Using it in a template is extremely simple:

<?php echo $modules->get('WireBooking')->renderWizard(); ?>

I need your feedback! The module is currently functional for this specific use case (Consultants/Service Providers). Before I invest time into generalizing it for a public release on the modules directory, I have two questions for you:

1. Is this something you would use? Is there a need for a native "Calendly" alternative?

2. Is the dependency on Tailwind a dealbreaker? Since the markup relies on Tailwind utility classes, it might be hard to style if you use Bootstrap or custom CSS.

Looking forward to your thoughts and suggestions!

Cheers, Markus

GitHub: https://github.com/markusthomas/WireBooking

Download

You can find the latest release on Github.

Documentation

Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.

Custom Panels

The goal was to make it simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.

Roadmap

• Panel types
  • Google Analytics
  • Draft
  • At a glance / Page counter
  • 404s
•  Layout options
  • Render multiple tabs per panel
• Chart panel
  • load chart data from JS file (currently passed as PHP array)

• Last update: June 2024
• Current stable version: 1.5.4
• Dev version: github dev-branch

You can find the module on Github and in the modules directory :

• https://modules.processwire.com/modules/duplicator/
• https://github.com/flydev-fr/Duplicator/archive/master.zip

Quote

To restore a website, just upload the package and the installer, then go to yourwebsite.com/installer.php then follow the instructions.

PLEASE, do not forget - after the end of the process - to delete the installer.php file and your package 

Screenshots / Features

• Dir and files exclusion

• CRON job

• Advanced settings 

• Local and Cloud storage

Protected links leak the email address of the person who copied the link into the page (eg. https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.antarctica.gov.au&data=05|02|EMAILADDRESS%40example.com...)

This is not ideal, and we find more and more protected links turning up now that most of the Microsoft product offerings use protected links (Teams, Office, Copilot etc.)

TextFormatter modules typically only reformat the text on output, leaving the page content containing the protected link. Is it acceptable for a Text Formatter module to save the formatted string back to the page? Maybe as an optional configuration in the module settings? Or, is it better to achieve this using a standard module?

I’m currently working on a module called WireMedia Library and wanted to share the current state of development to get some feedback on the concept.

The main goal is to provide a central interface for managing media across the entire ProcessWire instance while staying 100% compatible with the native storage system.

The Concept: The module acts as a central hub. You can upload files to the library and then select them from any page. When a file is selected, it is copied into the local page’s file/image field. This ensures that the files remain "native" to the page they are used on, keeping your API calls and templates exactly as they are.

Key Features of the current prototype:

• Central Media Overview: A unified view of all media assets in the system.

• Usage Tracking: The module indexes where files are used. Even if a file is used within a Repeater, it identifies the "leading" parent page so you know exactly where your assets live.

• Database Indexing: A custom database table keeps track of file locations for fast performance.

• Rebuild Index: A tool to rescan the system and ensure the database stays in sync with the file system.

• Native Workflow: Since files are copied to local fields, you can still use all native PW features (like cropping or focus points) directly on the target page.

Planned:

• Permission System: Granular access control for different user roles/folders.

I am still undecided about the final licensing or if/how I will release the module, but I wanted to show the UI and the logic behind it to see if this approach resonates with the community.

I’d love to hear your thoughts on the "copy-to-field" approach and the general UI!

This module allows ProcessWire to send transactional emails via Brevo.

Download the latest version: https://github.com/ttttim0709/WireMailBrevo

Installation

• Copy the WireMailBrevo directory into your site/modules/ directory.
• In the ProcessWire admin, go to Modules > Refresh.
• Click "Install" next to the WireMailBrevo module.

Usage

Example usage:

$email = $mail->new();
$email->to = 'recipient@somedomain.com';
$email->subject = 'Test #1';
$email->body = 'An example email';
$email->send();

Use of Versions: Check the Brevo dev section for more information about Message versions

$email->versions([
    [
        'to' => [
            [
                'email' => 'bob@example.com',
                'name' => 'Bob Anderson'
            ],
            [
                'email' => 'anne@example.com',
                'name' => 'Anne Smith'
            ],
        ],
        'subject' => 'This is my version subject line',
    ],
    [
        'to' => [
            [
                'email' => 'jim@example.com',
                'name' => 'Jim Stevens'
            ]
        ],
        'htmlContent' => "<!DOCTYPE html><html><body><h1>Modified header!</h1><p>This is still a paragraph</p></body></html>",
    ],
]);

Configuration

After installing the module, you can configure it by going to the module settings page. You need to provide the following configuration options:

• Brevo API Key: Obtain this key from your Brevo account settings.
• Sender Email Address: The email address to be used as the sender.
• Sender Name: The name associated with the sender's email address.

In "sampletemplate.php"  fields can be accessed by $page->interval->date_from   and   $page->interval->date_to - everything fine!

When using in a selector these fieldnames are invalid. e.g.

$pages->find("template=sampletemplate, interval.date_to > today")  throws an exception, no column with that name...

the schema definition for the fields is

    public function getDatabaseSchema(Field $field) : array  {
        $schema = parent::getDatabaseSchema($field);
        $schema['data'] = 'date default null'; // date_from
        $schema['to']   = 'date default null'; // date_to
        $workspace->url = 'KEY data (`data`, `to`)';
        $schema['keys']['to']   = 'KEY `to` (`to`)';
        return $schema; 
    }

i.e. date_from is mapped on standard column 'data' and date_to is mapped on 'to'.  When i use the real database column name 

$pages->find("template=sampletemplate, interval.to > today")

it works.

How is it possible to "correct" the names so that the name to access the field (e.g. $page->interval->data_from) and the name to be used in a selector is the same?

and: Is there a description of the PW database schema definition to be used in a getDatabaseSchema() ?

i am trying to develop a simple Fieldtype module and followed Tutorial on developing a Fieldtype module.

I installed the module (Fieldtype and Inputfield) created a field of that type, add such a field to a template and edited a page.

After entering values and click save button the method processInput() is invoked but then nothing happens,  sleepValue() and wakeupValue() are never invoked, the resulting editor page ends up showing empty entry fields.

What i'm getting wrong?

<?php

namespace ProcessWire;

class InputfieldTimeframe  extends Inputfield  {

    /** 
     * getModuleInfo is a module required by all modules to tell ProcessWire about them.
     * Information about your module and some settings and definition of module dependcies
     * @return array
     */ 
    public static function getModuleinfo()  {
        return [
            'title'    => __('Inputfield Timeframe',                   __FILE__),
            'summary'  => __('Inputfield for start date and end date', __FILE__),
            'author'   => 'T. Heinlein',
            'version'  => "0.1.2",
            'icon'     => 'calendar',
            'permanent' => false,
            'requires' => [
                'PHP>=8.0.0',
                'ProcessWire>=3.0.244',
                'FieldtypeTimeframe'
            ],
        ];
    }


    public function __construct() {
        parent::__construct();
    }



    public function ___render()  {
        $value = $this->attr('value');
        $field = $this->field;

        $html = "<div class='interval'>"
        . "<input type='date' name='datefrom'>"
        . "<input type='date' name='dateto'>"
        . "</div>";
        return "<div style='border:solid 1px red;'>$html</div>";
    }


    public function renderValue()  {
        $value = $this->attr('value');
        return "$value";   // TODO:  locale format
    }

    public function ___processInput(WireInputData $input) :self {
        $value = $this->attr('value');
        $input->datefrom = trim($input->datefrom);
        $input->dateto   = trim($input->dateto);

        $value['datefrom'] = $input->datefrom;
        $value['dateto']   = $input->dateto;

        bd($value, "processInput");

        return $this;
    }
}

<?php

namespace ProcessWire;


class FieldtypeTimeframe extends Fieldtype  {


	/** 
     * getModuleInfo is a module required by all modules to tell ProcessWire about them.
     * Information about your module and some settings and definition of module dependcies
     * @return array
     */ 
    public static function getModuleinfo()  {
        return [
            'title'    => __('Timeframe',                           __FILE__),
            'summary'  => __('Fieldtype representing a timeframe with start and end date', __FILE__),
            'author'   => 'T. Heinlein',
            'version'  => "0.1.1",
            'icon'     => 'calendar',
            'installs' => 'InputfieldTimeframe',
            'requires' => [
                'PHP>=8.0.0',
                'ProcessWire>=3.0.244'
            ]
        ];
    }


    public function __construct() {
        parent::__construct();
    }


    /**
     * define the table columns needed for that field type AND an additional column 'data' for a primary key.
     * (this is low level input for the database)
     *  *** this method MUST be implemented when writing a custom fieldtype
     */
    public function getDatabaseSchema(Field $field) : array  {
        $schema = parent::getDatabaseSchema($field);
        $schema['data']      = 'varchar(64) NOT NULL';    /* data is required field for system purposes */
        $schema['datefrom']  = 'date';
        $schema['dateto']    = 'date';
        return $schema;
    }

    public function ___sleepValue(Page $page, Field $field, $value)  {
        bd($value, "sleepValue");

        $df = $value['datefrom'];
        $dt = $value['dateto'];

        $res = ['datefrom'=> $df, 'dateto' => $dt];
        return $res;
    }


    public function wakeupValue(Page $page, Field $field, $value)  {
        bd($value, "wakeupValue");
        return $value;
    }

    public function getBlankValue(Page $page, Field $field) {
        return array();
    }


    public function getInputfield(Page $page, Field $field) {
        $inputfield = $this->wire('modules')->get('InputfieldTimeframe');
        $inputfield->class = $this->className(); /* adds the class name as a css class to the wrapper element */

        $pageValue = $page->get($field->name);
        $inputfield->setAttribute('value', $pageValue);

        return $inputfield;
    }
    

        /**
     * @param Page $page
     * @param Field $field
     * @param int|object|WireArray|string $value
     * @return int|null|object|OpeningHours|WireArray|string
     * will be called on before sleepValue and after wakeupValue
     */
    public function sanitizeValue(Page $page, Field $field, $value)  {
        if (! is_array($value) ) {
            $value = $this->getBlankValue($page, $field);
        }
        return $value;
    }
}

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:

1. Is there still a strong interest in a maintained module based on mPDF, or have you moved to other solutions (like RockPdf)?

2. 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

class ProcessPageEditImageSelect_Pickpage extends ProcessPageEditImageSelect implements Module, ConfigurableModule {
    public static function getModuleinfo() {
        return [
            'title' => 'Page Edit Image pickfrompage',
            'summary' => 'Extends core module: Enables specifying a default page to pick images from if the page being edited has no image fields.',
			'autoload' => true,
			'permission' => 'page-edit',
        ];
    }

	public function __construct() {
		parent::__construct();
	}

	public function init() {
		parent::init();
		bd($this->data);
	}

	public function ___execute() {}

	public function getModuleConfigInputfields(array $data) {
		$inputfields = $this->wire(new InputfieldWrapper());
		$modules = $this->wire()->modules;

		/** @var InputfieldPageListSelect $f */
        $f = $modules->get('InputfieldPageListSelect');
		$f->attr('name', 'defaultPage');
		$f->attr('value', @$data['defaultPage']);
		$f->label = $this->_('Default page for images if no image fields');
		$f->value = @$data['defaultPage'];
		$inputfields->add($f);

        /** @var InputfieldPageListSelect $f */
        $f = $modules->get('InputfieldTextarea');
		$f->attr('name', 'templateDefaultPage');
		$f->attr('value', @$data['templateDefaultPage']);
		$f->label = $this->_('Default page by template for images if no image fields');
		$f->notes = "1 pair of selectors `{template}:{page}` per line, e.g.,: `1:/home/`, or `home:1`, or `contact:template=home`";
		$f->value = @$data['templateDefaultPage'];
		$inputfields->add($f);

		return $inputfields;
	}
}

where the execute method is the one here and the init method returns the core module's data but my execute method has no effect. What's wrong with how I'm doing it?

Thank you

On pages where it doesn't apply, there's an error notice from the init method of the core module:  

Modules: Failed to init module: ProcessPageEditImageSelect_Pickpage - No page specified

but nothing shows (Tracy debugging) if not autoloaded, and ___execute has no effect either way.

The wireMail() function replaces all instances of PHP's mail() function in ProcessWire's source. It works in a similar way as PHP's mail() except that supports a few different usages. Standard usage would be this:

// to, from, subject, body
wireMail('user@domain.com', 'ryan@runs.pw', 'Mail Subject', 'Mail Body'); 

Another usage would be to give it no arguments, and it'll return whatever WireMail module is installed for you to use yourself. If no WireMail module is installed, then it returns ProcessWire's WireMail.

$mail = wireMail();
$mail->to('user@hi.com')->from('ryan@runs.pw'); // all calls can be chained
$mail->subject('Mail Subject'); 
$mail->body('Mail Body');
$mail->bodyHTML('<html><body><h1>Mail Body</h1></body></html>'); 
$mail->send(); 

Since all of this stuff is only on the PW 2.4 dev branch at present, I'm posting this primarily for people that are interested in creating WireMail modules. For instance, I know that both Teppo and Horst (and perhaps others?) have put together such modules and ideas, so this is all aimed at coming up with a way for those ideas to be easily integrated into PW by way of modules. To make your own WireMail module, you simply create a module that extends WireMail and provide your own implementation for the send() method. Of course, you can go further than that, but that's all that is technically necessary. I've attached an example module called WireMailTest that demonstrates a WireMail module. When installed, it is used rather than PW's WireMail. This WireMailTest module includes lots of comments for you in the code of it, and you may find it helpful to use it as your starting point. 

WireMailTest.module

For you guys developing modules, please throw any questions my way and I'm happy to help. Likewise, let me know if you think I'm missing anything important in the base interface that the modules are based upon and we can update it. 

I recently released the module Template Twig Replace that enables templating using the Twig engine instead of the default php/html templates.

The module hooks into PageRender::___renderPage, replacing the original method and setting the Twig rendering results to the event's return property. I've taken a good amount of information from this post to achieve the results.

Now I've discovered that pages will not be cached if the module is active.

Some digging into the core (/wire/modules/PageRender.module) showed, that the method, I'm hooking not only renders a page but handles page caching (and some form of access control) as well.

As a quick fix I duplicated the code handling cache files in my module to ensure pages a properly cached as usual. The fix is already commited to github and should be available in the module directory soon.

This is would my module currently looks like:

public function init() {

    // ... some more stuff ..

    // replace default page rendering by hooked method
    $this->addHookBefore('PageRender::renderPage', $this, 'renderPageWithTwig');
}

/**
 * Hook callback for PageRender::renderPage
 *
 * Replaces default page rendering entirely.
 *
 * @param HookEvent $event The hook event
 * @throws WirePermissionException Page is not currently viewable.
 */
public function renderPageWithTwig(HookEvent $event) {

    $parentEvent = $event->arguments(0); // grab event provided to PageRender::renderPage

    // don't mess with admin templates
    $page = $parentEvent->object;
    if ($page->template == 'admin') return;

    // double check page's status
    // taken from PageRender::__render()
    if ($page->status >= Page::statusUnpublished && !$page->viewable()) {
        throw new WirePermissionException('Page \'' . $page->url . '\' is not currently viewable.');
    }

    // forced replacing of default page rendering behaviour
    $event->replace = true;

    // look for cached data
    // taken from PageRender::__render()
    $options = count($parentEvent->arguments) ? $parentEvent->arguments[0] : array();
    $defaultOptions = array(
        'forceBuildCache' => false,
    );
    $options = array_merge($defaultOptions, $options);

    $cacheAllowed = wire('modules')->get('PageRender')->isCacheAllowed($page);
    $cacheFile = null;

    if ($cacheAllowed) {
        $cacheFile = wire('modules')->get('PageRender')->getCacheFile($page);
        if(!$options['forceBuildCache'] && ($data = $cacheFile->get()) !== false) {
            $parentEvent->return = $data;
            return;
        }
    }

    // allow page fields to be accessed directly in Twig
    // e.g. {{ page.myfield }} instead of {{ page.get('myfield') }}
    Page::$issetHas = true;

    // render template
    $twigVars = $this->collectVariables($page->output);
    $output = $this->getTwig()->render($page->template->name . '.' . 
                                       wire('config')->templateExtension, $twigVars);

    // cache output if possible
    // taken from PageRender::__render()
    if (!empty($output) && $cacheAllowed && !is_null($cacheFile)) $cacheFile->save($output);

    // manually set return of original event
    $parentEvent->return = $output;
}

But I think, the best option would be finding a hook the only renders a page's content and replacing this method.

Is there a better hook to use that leaves handling page caching and maybe other pre- or post-processing alone and does template rendering only?

Regards,

Marco

Hi all,
I’ve recently published a module and it still shows as pending. I can’t see it in the "My Modules" directory overview – although I can navigate to the module page directly via URL. 
Two questions:

1. Is it intentional that even the author doesn’t see their own pending module in the overview?

2. What’s the process for a module to move out of pending status? Does it require manual review or certain criteria?

Thanks for any insights!
Cheers, Mike

I’m excited to announce a new module currently in beta: ProcessDataTables – designed as a universal “Swiss Army knife” for backend data visualization. Before the development of the ProcessUserDataTable module we developed a sleek module for a client called ProcessDataTable (singular), which featured the same guided, user-friendly install process with select/multiselect configuration fields but the possibility to handle the column display with small PHP templates. It was also designed for using it with a single table. But we saw the need for a truly flexible solution that can handle an unlimited number of tables in the ProcessWire admin.

ProcessDataTables (plural) is aimed at more experienced ProcessWire developers who need a rapid, highly configurable, and reusable tool for building complex data overviews and admin dashboards. Unlike the original (still unreleased) single-table module, which focuses on ease of setup, this new version prioritizes scalability, customization, and extensibility. We are currently using it in combination with @bernhards incredible module RockCommerce to display E-Commerce related data for backend users.

Why ProcessDataTables?

• Unlimited custom tables: Quickly define as many tables as you need for any data structure or ProcessWire template.

• Advanced configuration: Control each table’s columns, data sources, selectors, and field-level output via PHP stubs.

• Per-field templating: Every column can use its own output template for advanced formatting and presentation.

• Global module config: Set date/currency/number formatting, labels, and output options from a central settings screen.

• Built for developers: Configuration is more open and flexible, allowing you to create advanced dashboards and reporting interfaces for any ProcessWire installation.

Differences to the (yet unreleased) ProcessDataTable Module

The original ProcessDataTable (singular) module was focused on single-table use cases and offered a more beginner-friendly installation process:

• Guided setup: Selection of templates and fields through select/multiselect inputs in the config screen

• Quicker onboarding: Suitable for smaller projects or less technical users when only one data table is needed

Status

• ProcessDataTables is currently in beta – feedback, ideas, and bug reports are highly appreciated!

• Looking for real-world use cases and input from the community to help shape the roadmap.

Screenshots & Example Workflow

In the README of the module you find example screenshots of the module config, adding tables, and customizing table columns)

Get it here: 

https://processwire.com/modules/process-data-tables/

https://github.com/frameless-at/ProcessDataTables

If you have ideas, feature requests, or want to help test or contribute, please reply below or DM me! 
Looking forward to your feedback and suggestions!

Calling the configurable module from the frontend refers to the Process module page for data.

I'd like to make the Admin->Setup->My Module page managed by module-specific permissions when logged-in to admin. All works while I'm logged in as Superuser but crashes with 
Error: Exception: You do not have permission to execute this module - ProcessMyModule

when a frontend guest.

Fairly confident it's in the mymodule.info.php permissions array. Just can't seem to nail it.

Help appreciated.

Solution:
I created a role without any permissions. On the admin page I only allowed superusers or users with the specified role to view certain sections.

Or do I need to write the logic myself?

Thank you very much

for a RockForms nette Form I need a custom Markup for the RadioList Control.

addRadioList outputs the control per default as

<label><Input type=radio /> Text</label>

what I want to achieve:

<Input type=radio /><label>Text</label>

I can add classes and Separator Markup. But how can I inject a custom Markup?

Any ideas?

even with the latest version of PW the image upload module does not working anymore.
When dragging in an image the spinner keeps spinning at 100% (1st sceenshot) and the console throws an ajax error (2nd screenshot).

Not even with PHP 8.0 … latest working version is 7.4.x … how can this be? PHP 8.x is around for quiet a while now.