module Page Reference Context Data

[kixe]

Field that stores one or more references to ProcessWire pages with additional data in field context.
Values are editable via page edit modal of the referenced page provided from the field if module AdminPageFieldEditLinks is installed and "Enable link to create new pages?" is checked in field settings.

Requirements: AdminPageFieldEditLinks >= 3.1.4

https://github.com/kixe/FieldtypePageContextData

https://processwire.com/modules/fieldtype-page-context-data/

Use case example:
The planning of the Tonmeistertagung in the CCD (Congress Center Düsseldorf) from November 3rd, 2021 to November 6th, 2021 is in the finalization phase.
The conference consists of a conference part and an exhibition. The planning is done via a separate frontendless PW instance. There, all companies (pages) that are active at various events are kept in a pool. Changes (address, logo) can always be done there. For the exhibition of the current conference in November, the exhibitor-companies (pages) are selected via a page reference field. A stand number must now be assigned to each selected company (page). We had originally solved this using the Profield FieldtypeTable. However, this had the disadvantage that each entry again made all companies available for selection and did not recognize which were already selected in a previous table row. The new field type now allows the value (company's stand number) to be assigned to a Company (page) in context to a specific Pagefield living in a specific page.

https://tonmeistertagung.com/en/exhibitors/exhibition/

 

[MrSnoozles]

This is amazing! I have missed this functionality in ProcessWire for a while already.

 

Installation

• Install AdminPageFieldEditLinks: https://processwire.com/modules/admin-page-field-edit-links/
• Install FieldtypePageContextData (this module)
• Create a new field of type "Page Reference Context Data"
• When setting up the field:
  • in tab "Details" enter configuration in "Additional page fields in Pagefield context". You can see many examples here https://github.com/kixe/FieldtypePageContextData
  • in tab "Input" select "Enable view/edit linnks on selected pages?". If you don't see this field the module AdminPageFieldEditLinks is not activated
  • in tab "Input" when changing the label field: you can also use the additional context fields as label in the page reference. Symply change your label to a custom label and define it like so: {title}, {_customfield1}, {_customfield2}
• assign the field to your template

Screenshots

When installed and configured correctly you see the page reference like normal. But now you can click it and edit the page in a modal. This modal also contains a new tab "Pagefield Context Data" (the name of the tab can be changed in field settings).

 

Bugs found so far

• On Windows: separating option values for select by \n is not working correctly. Maybe use | instead? (as that's how ProcessWire separates fields)
• for the user template the tab "Pagefield Context Data" is not being displayed

 

Very well done. This is SO useful! ♥

[kixe]

3 hours ago, MrSnoozles said:

• On Windows: separating option values for select by \n is not working correctly. Maybe use | instead? (as that's how ProcessWire separates fields)
• for the user template the tab "Pagefield Context Data" is not being displayed

 

• I've pushed a fix. The separator must be translated into a real line break (expected by the Inputfield). I changed the translation to "\r\n" instead of "\n" only, which should work cross platform. Continue to use the string '\n' in the field settings. Please update to version 1.0.1. Could you please give feedback if it works?
  
  The pipe '|' you mentioned is already reserved to separate an option 'value' from the option 'title' (@see SelectableOptionManager). I prefer to handle the setup according (very close) to the expectations of the inputfield.
   
• ProcessUser and possibly some other processes for editing system pages are not supported. In the special case of ProcessUser, the GET-Parameters forfield and forpage are removed from the url of the modal window for whatever reason. Any idea?

The module is still in an alpha stadium. Thanks for testing and feedback.

[MrSnoozles]

Thanks for the reply. Will try in the evening and report back. I'll also try to have a look into why ProcessUser is removing the GET parameters.

EDIT 1 (FieldTypeSelect):
I did test the new version. When I configure "option1\noption2" the select shows:

• option1
• option2
• option1\noption2

This is because in line 387

$inputfield->option = trim('option1\noption2'); 

is being called, adding the full settingValue as another option. If you continue;  in the block where you're checking if the inputfield is a select, it should be working.
Also instead of using "\n" or "\r\n" you could probably use the constant PHP_EOL which contains the line separator for the operating system PHP is running on.

 

EDIT 2 (Editing pages of template user):
So far I've found out that the redirect is because of the method ___setEditor() in wire/core/User.php. It leads to a redirect that strips the two parameters &forpage und &forfield. If they are appended, everything works correctly. One way to solve it would be to not use ProcessUser and use ProcessPageEdit instead by adding this code to your init method:

// do not redirect to a page using ProcessUser when editing a page relation
$this->addHookBefore('User::setEditor', function (HookEvent $event) {
    if(!$this->input->get('forpage') || !$this->input->get('forfield')) {
        return;
    }
    
    $event->cancelHooks = true;
});

 

This is not yet optimal though, because in the edit screen the "name" is shown in all languages. But imo it's good enough for now. A better way would be if the method editUrl() in the User class would keep the url parameters. But that would be a core issue.

[kixe]

@MrSnoozles
Edit 1: Thanks for feedback. I fixed it in the recommended way.
Edit 2: It's good that you found a solution to your needs.

[MrSnoozles]

If you need any more support for this module please let me know. It's just so useful. Going to try a few more use cases in the coming days.

[kixe]

 

8 minutes ago, MrSnoozles said:

If you need any more support for this module please let me know.

https://github.com/kixe/FieldtypePageContextData/issues