Closed (fixed)
Project:
Config Pages
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
2 Nov 2020 at 11:08 UTC
Updated:
11 Dec 2020 at 15:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
shumer commentedHey, probably you would need to do something like that
Comment #3
marknatividad commentedThanks @shumer, I think that allows the reference to be made to the config page type configuration. Is there a way to reference the actual content of a config page?
Comment #4
marknatividad commentedLooking at the module code, a decision was made to remove config pages from the dropdown select.. I wonder what the reason was?
Comment #5
shumer commentedThe ConfigPage is not a usual entity from a Drupal perspective. There is a specific property caleed "Context" exists, so if you'll reference to a entity itself you won't be able to load a proper data when context is changed (for exapmle language or domain). Hence, this type of reference is unavailbale.
If I were you I probably still make a reference to a Type itself as of my first comment. But also you can create a field formatter which will load a proper ConfigPage for required type. This probably can be added to a module, so if you want to introduce a patch feel free to do it.
Comment #6
vitaliiishchenko commentedI added a field formatter which loads a proper ConfigPage for required node type.
Comment #8
miritas commentedI've checked the patch on clean Drupal installation. Works ok for me.
However, I've replaced the use of a static method call with a non-static. The changes have been pushed to Gitlab.
Comment #9
miritas commentedComment #11
shumer commented