url stringlengths 50 196 | text stringlengths 3 17.2k | heading stringlengths 2 103 | embeddings list |
|---|---|---|---|
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#extending-search-index | Extending Search Index
The portal engine is powered by Elasticsearch for search, listings and filters. Therefore, it's needed to store the data
from Pimcore elements into Elasticsearch indices.
Take a look at Index Management for an introduction on how
to index the data into Elasticsearch and keep it up to date. There ... | Extending Search Index | [
-0.0988270714879036,
-0.21631741523742676,
-0.28640320897102356,
0.07584258913993835,
-0.03735934942960739,
-0.004970986861735582,
-0.10726174712181091,
0.07634954154491425,
-0.2006872296333313,
0.03137779235839844,
-0.25433453917503357,
0.3370717465877533,
0.20013755559921265,
0.244043022... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#extending-search-index-via-events | Extending Search Index via Events
The regular index update process stores a defined set of standard data types in the Elasticsearch index which makes it
possible to find, filter, sort and list them in the portal engine.
It is possible to extend the index with custom attributes if needed. For this purpose the following ... | Extending Search Index via Events | [
-0.02443595603108406,
0.030649591237306595,
-0.25509944558143616,
-0.0925171747803688,
-0.17582546174526215,
-0.015222374349832535,
-0.2494051307439804,
0.27262821793556213,
0.08964542299509048,
0.04874406009912491,
-0.10991692543029785,
0.24314890801906586,
-0.0988943949341774,
0.18416896... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#updateindexdataevent | UpdateIndexDataEvent
This event can be used to store additional fields in the search index. Depending on if you would like to index additional
data for assets or data objects use one of the following two events.
Pimcore\Bundle\PortalEngineBundle\Event\Asset\UpdateIndexDataEvent
Pimcore\Bundle\PortalEngineBundle\Eve... | UpdateIndexDataEvent | [
-0.2561069428920746,
0.04762671887874603,
-0.2320571392774582,
0.08763761818408966,
-0.18694277107715607,
0.03583893924951553,
-0.022114941850304604,
0.20105130970478058,
-0.07976062595844269,
0.036748796701431274,
-0.1507590264081955,
0.34862154722213745,
0.05446091666817665,
0.1512109637... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#system_fields | system_fields
Base system fields which are the same for all assets or data objects (like id, creationDate, fullPath...). | system_fields | [
-0.2604462206363678,
-0.24531446397304535,
-0.14910638332366943,
0.16652359068393707,
0.30379268527030945,
-0.03800321742892265,
0.3628128170967102,
0.14569447934627533,
0.03265087679028511,
0.06463603675365448,
0.30139830708503723,
0.19689017534255981,
-0.023840146139264107,
0.07480128109... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#standard_fields | standard_fields
All data object or asset metadata types which are supported out of the box depending on your data model. | standard_fields | [
-0.1690821349620819,
-0.5218403339385986,
-0.14664992690086365,
0.12284405529499054,
0.31871727108955383,
-0.013834384270012379,
0.152403324842453,
0.16054785251617432,
0.057169392704963684,
0.07688191533088684,
0.2770545184612274,
0.06682474911212921,
-0.11479891091585159,
0.4494832456111... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#custom_fields | custom_fields
This is the place where you are able to add data via the UpdateIndexDataEvent. As soon as additional fields are added
they are searchable through the full text search (depending on the mapping of the fields). | custom_fields | [
0.09039833396673203,
-0.01576615311205387,
-0.302126944065094,
-0.01602962613105774,
-0.10729099810123444,
0.0482044480741024,
-0.06495040655136108,
0.16000786423683167,
0.11715374886989594,
0.2630900740623474,
-0.04222138226032257,
-0.08148671686649323,
0.0797593966126442,
0.1084794476628... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#extractmappingevent | ExtractMappingEvent
With this event it's possible to define the mapping
of the additional custom fields. Again there are separate events for assets and data objects.
Pimcore\Bundle\PortalEngineBundle\Event\Asset\ExtractMappingEvent
Pimcore\Bundle\PortalEngineBundle\Event\DataObject\ExtractMappingEvent
| ExtractMappingEvent | [
-0.35389283299446106,
-0.025149580091238022,
-0.1330357789993286,
0.3163864314556122,
-0.008936767466366291,
-0.23325075209140778,
0.08086654543876648,
0.09620413929224014,
-0.04345039650797844,
0.20341171324253082,
-0.2791053056716919,
0.620913565158844,
-0.03947607800364494,
0.2503494918... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#filterablefieldsevent | FilterableFieldsEvent
Now as the mapping is defined and the data is indexed, it is possible to create a filter on this data. The
Pimcore\Bundle\PortalEngineBundle\Event\Search\FilterableFieldsEvent can be used to make the new fields appear in the
filter field selection of the data pool config document. | FilterableFieldsEvent | [
-0.4737180769443512,
-0.12312130630016327,
-0.10900276154279709,
-0.1328517645597458,
-0.13517527282238007,
-0.4514161944389343,
-0.06196955218911171,
0.17002081871032715,
0.005457042250782251,
0.07441787421703339,
-0.37002015113830566,
0.45240518450737,
-0.0054780165664851665,
0.292049199... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#sortablefieldsevent | SortableFieldsEvent
The Pimcore\Bundle\PortalEngineBundle\Event\Search\SortableFieldsEvent works quite the same way like the FilterableFieldsEvent
but defines fields which can appear in the list of sortable fields. | SortableFieldsEvent | [
-0.3403061628341675,
-0.13514608144760132,
-0.1737533062696457,
-0.11437994241714478,
0.08515413850545883,
-0.19936057925224304,
-0.28678321838378906,
0.11890064924955368,
-0.1940009444952011,
0.21871748566627502,
-0.1662660837173462,
0.489646315574646,
-0.21480262279510498,
0.179953143000... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#listablefieldsevent | ListableFieldsEvent
The last event is the Pimcore\Bundle\PortalEngineBundle\Event\Search\ListableFieldsEvent. This can be used if you would
like to display the additional fields in the list view of the data pool listings. | ListableFieldsEvent | [
-0.5075427293777466,
-0.2458932101726532,
-0.17092594504356384,
0.023001443594694138,
-0.029805710539221764,
-0.07121117413043976,
-0.21582180261611938,
0.12466535717248917,
-0.009090721607208252,
0.16320423781871796,
-0.2764015793800354,
0.5070726871490479,
-0.05667206645011902,
0.0404922... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#example-1:-assets | Example 1: Assets
The following example creates an EventSubscriber which adds an additional field to make it listable, filterable and
sortable. The logic applies to assets and divides the assets into file size groups:
small: < 300KB
medium: 300KB - 3MB
big: > 3MB
<?php
namespace AppBundle\EventListener;
us... | Example 1: Assets | [
-0.28720229864120483,
0.1887538731098175,
-0.17322112619876862,
0.393722265958786,
0.12005329877138138,
-0.31609129905700684,
0.20601342618465424,
0.23450420796871185,
-0.04390465468168259,
0.344550758600235,
-0.13652047514915466,
0.1617879867553711,
-0.2011290192604065,
-0.125813886523246... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#example-2:-data-objects | Example 2: Data Objects
In this example a "User Owner" field will be provided for car data pool documents. "Owner" is defined as Pimcore user
name of the creator of the car data object.
<?php
namespace AppBundle\EventListener;
use Pimcore\Bundle\PortalEngineBundle\Event\DataObject\ExtractMappin... | Example 2: Data Objects | [
-0.22204160690307617,
0.3455018997192383,
-0.17902220785617828,
0.2953338623046875,
0.04976098611950874,
-0.4707143306732178,
0.3454635739326477,
0.08128244429826736,
-0.32088661193847656,
0.36013686656951904,
-0.06085910275578499,
0.25387096405029297,
-0.008461246266961098,
-0.13485822081... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#update-index-mapping-and-data | Update index mapping and data
Call the following console commands as soon as the event subscriber is set up in the symfony container configuration.
bin/console portal-engine:update:index update-asset-index # update asset index mapping and put all assets into the queue
bin/console portal-engine:update:process-index-queu... | Update index mapping and data | [
-0.34236887097358704,
0.10978429764509201,
-0.12732836604118347,
-0.04843105375766754,
-0.1351417899131775,
0.0262080579996109,
0.046720683574676514,
0.31008172035217285,
0.13062506914138794,
0.25792640447616577,
-0.1173677071928978,
0.2525743544101715,
0.22677326202392578,
-0.121566146612... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#configure-the-new-field-in-data-pool-configuration-document | Configure the new field in data pool configuration document
As soon as all these steps are finished the new field should appear in the select lists of the data pool configuration
document. Configure the new field there and the new options should appear in the frontend. | Configure the new field in data pool configuration document | [
-0.3184469938278198,
-0.18292514979839325,
-0.26891234517097473,
-0.3625521659851074,
-0.004067755304276943,
-0.1784801483154297,
0.30482304096221924,
-0.042781177908182144,
0.014411170035600662,
0.289510577917099,
-0.23646953701972961,
0.3236798942089081,
0.3128267228603363,
0.26605826616... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Search_Index_Management/Extend_Search_Index#index-update-console-commands | Index Update Console Commands
For more details on how the index update console commands work take a look at the
Index Management section. | Index Update Console Commands | [
-0.046143874526023865,
0.021170660853385925,
-0.2833879292011261,
-0.18882349133491516,
0.015033797360956669,
0.23777823150157928,
0.17522478103637695,
-0.007468543481081724,
-0.06241535767912865,
0.3418339490890503,
-0.28121286630630493,
0.18470239639282227,
0.2524058222770691,
0.01629229... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Overwrite_Templates#overwrite-templates | Overwrite Templates | Overwrite Templates | [
0.20134411752223969,
-0.3661155104637146,
-0.21145989000797272,
-0.12094268202781677,
0.14429664611816406,
-0.042793817818164825,
0.24766364693641663,
-0.007993107661604881,
-0.19403588771820068,
0.08798708766698837,
-0.1710055023431778,
0.30553868412971497,
-0.07702188938856125,
0.0211673... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Overwrite_Templates#react-components | React components
Most of the HTML markup of the portal engine frontend is rendered via client side rendering (React / JSX components).
Take a look at the Customized Frontend Build and
Customize JSX Components section for a guide how to overwrite the corresponding JavaScript files. | React components | [
-0.04449092596769333,
-0.1489666849374771,
-0.21682442724704742,
-0.05278683826327324,
0.18209531903266907,
0.08668220043182373,
0.23319923877716064,
0.26375991106033325,
0.12296686321496964,
-0.15711086988449097,
0.039053115993738174,
0.1579890251159668,
0.5249935388565063,
0.354919105768... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Overwrite_Templates#twig-templates | Twig templates
Nevertheless, the portal engine also ships with a bunch of Twig templates located in src/Resources/views. The mechanism
to overwrite them is just the standard Symfony way of doing this which is described
here.
At certain places the portal engine adds Twig {% block %} statements which makes it possible to... | Twig templates | [
0.2698274254798889,
-0.14736875891685486,
-0.0783781036734581,
-0.010211573913693428,
0.032601747661828995,
-0.05781099572777748,
0.23549935221672058,
0.04841169714927673,
-0.20893463492393494,
-0.02168840914964676,
-0.12215283513069153,
0.32396677136421204,
0.33421629667282104,
-0.1145369... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Overwrite_Templates#example | Example
Extend the login template, remove the logo + background image and wrap the headline into a <div>.
# needs to be located at app/Resources/PimcorePortalEngineBundle/views/auth/login.html.twig
{% extends '@!PimcorePortalEngine/auth/login.html.twig' %}
{% block logo %}
{% endblock %}
{% block login_backgrou... | Example | [
-0.1474737673997879,
-0.20625275373458862,
-0.15704061090946198,
-0.016621818765997887,
0.08406802266836166,
-0.06731795519590378,
0.4059358835220337,
0.15558750927448273,
-0.2151389718055725,
-0.14460161328315735,
-0.03080224059522152,
-0.02925924025475979,
0.3422256112098694,
0.177800953... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Customize_Frontend_Build#customize-frontend-build | Customize Frontend Build
Most of the frontend parts of the portal engine are built with client side technologies. The JavaScript components are
built with the help of React whereas all CSS files are powered by SASS.
As all of these libraries consist of a lot of files and SASS needs to be compiled to CSS, the portal eng... | Customize Frontend Build | [
-0.19559511542320251,
-0.21982255578041077,
-0.18939025700092316,
0.2236606329679489,
0.20456860959529877,
-0.09507812559604645,
-0.06905581057071686,
0.41751912236213684,
-0.10879970341920853,
-0.010111638344824314,
-0.06991299986839294,
0.1217837929725647,
0.5703516602516174,
0.519327700... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Customize_Frontend_Build#create-your-own-customized-frontend-build | Create your own customized frontend build
The following steps are needed to create a customized frontend build. | Create your own customized frontend build | [
-0.26720836758613586,
-0.2025359570980072,
-0.2346114218235016,
-0.06158546358346939,
0.2182341367006302,
-0.2140820026397705,
0.3275339901447296,
-0.03638927638530731,
0.11029111593961716,
0.22352813184261322,
0.03314870595932007,
0.11904620379209518,
0.028493376448750496,
0.3752608299255... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Customize_Frontend_Build#step-1:-configure-a-customized-frontend-build-in-the-configuration-tree | Step 1: Configure a customized frontend build in the configuration tree
# put this into your yml config (i.e. config.yml)
pimcore_portal_engine:
customized_frontend_builds:
- my_portal
The build name (my_portal) will be the final build folder in the filesystem, therefore do not use spaces or special
chara... | Step 1: Configure a customized frontend build in the configuration tree | [
-0.33192047476768494,
-0.1697155088186264,
-0.15601328015327454,
-0.09429717808961868,
0.34313347935676575,
-0.30499589443206787,
0.039629459381103516,
0.03336101025342941,
-0.16098418831825256,
0.18187527358531952,
-0.1299152374267578,
0.5348974466323853,
0.301164835691452,
0.369315594434... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Customize_Frontend_Build#step-2:-install-node.js | Step 2: Install Node.js
To be able to create webpack builds it's needed to install Node.js as you will need the tools
npm and npx. You will need at least npm version 6 to make
it up and running. | Step 2: Install Node.js | [
-0.3260123133659363,
-0.023866228759288788,
-0.2463846057653427,
0.016093658283352852,
0.21201610565185547,
0.009085575118660927,
-0.02122757025063038,
0.431924045085907,
0.28673210740089417,
0.14431113004684448,
0.14878401160240173,
0.3013109862804413,
0.09472376108169556,
0.5025222301483... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Customize_Frontend_Build#step-3:-setup-your-development-environment | Step 3: Setup your development environment
Npm is a package manager (similar to composer) and uses a file called package.json to handle all the dependencies.
Therefore, it's needed setting up a suitable package.json into the root directory of your project.
The portal engine provides a console command to support your wi... | Step 3: Setup your development environment | [
-0.4091491401195526,
0.2384093552827835,
-0.26991474628448486,
-0.07527277618646622,
0.1658724844455719,
-0.08568072319030762,
-0.17762789130210876,
0.24704596400260925,
-0.144147127866745,
-0.005403413902968168,
0.22151248157024384,
0.5087870359420776,
0.14915849268436432,
0.3148729801177... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Customize_Frontend_Build#step-4:-create-some-customized-files | Step 4: Create some customized files
If your build name is my_portal, the correct place to put all the files which you would like to replace or add into your
final build would be the directory {PROJECT_ROOT}/public/portal-engine/my_portal (for Pimcore 6: {PROJECT_ROOT}/web/portal-engine/my_portal).
If needed, it's poss... | Step 4: Create some customized files | [
-0.18241991102695465,
0.011724320240318775,
-0.1559661477804184,
0.11824524402618408,
0.26997578144073486,
-0.08754792809486389,
-0.07936913520097733,
0.2722581923007965,
-0.35943952202796936,
-0.17225299775600433,
-0.1080678254365921,
0.3588016629219055,
0.48904481530189514,
0.42442873120... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Customize_Frontend_Build#step-5:-setup-the-customized-frontend-build-in-your-portal | Step 5: Setup the customized frontend build in your portal
Take a look at the portal/root document of your portal engine site. There is a setting called "Customized Frontend Build".
If you added your build into the configuration tree it should appear in the select box. Select it and save the document. | Step 5: Setup the customized frontend build in your portal | [
-0.2973739504814148,
-0.17246240377426147,
-0.23187488317489624,
-0.11940929293632507,
0.10829383134841919,
-0.20763562619686127,
0.09997151046991348,
0.1611921787261963,
-0.0041434550657868385,
0.10078154504299164,
-0.020258953794836998,
0.17461983859539032,
0.15094253420829773,
0.4039547... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Customize_Frontend_Build#step-6:-execute-the-development-build | Step 6: Execute the development build
The portal-engine:update:frontend-build will add some npm scripts to execute the build in the root folder of your project.
While developing execute the following if your build is called my_portal:
npm run dev_my_portal
This will create a development build and start a file watch. T... | Step 6: Execute the development build | [
-0.6468835473060608,
0.22590859234333038,
-0.2345774620771408,
-0.07378489524126053,
0.04261863976716995,
-0.1479005664587021,
0.18800248205661774,
0.3384508788585663,
-0.19135521352291107,
0.08348987251520157,
0.1104639545083046,
0.3792623281478882,
0.020169083029031754,
0.191089168190956... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Customize_Frontend_Build#step-7:-take-a-look-at-the-portal-frontend | Step 7: Take a look at the portal frontend
Your changes should be visible there! Yeah! | Step 7: Take a look at the portal frontend | [
-0.08561040461063385,
0.011472854763269424,
-0.30961087346076965,
-0.19312936067581177,
0.03705640509724617,
-0.329402357339859,
0.31584587693214417,
0.04336948320269585,
-0.11444766074419022,
0.09123793244361877,
-0.16460281610488892,
0.17830964922904968,
0.1647946685552597,
0.14815771579... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Customize_Frontend_Build#step-8:-execute-the-production-build | Step 8: Execute the production build
The development build is very helpful for development purposes, but you should never deploy the development build to a
production environment. An additional production build script exists to create a minified build without the debugging
stuff enabled.
npm run build_my_portal
All fi... | Step 8: Execute the production build | [
-0.5581151247024536,
0.12868134677410126,
-0.1510816067457199,
-0.1562851071357727,
0.04205210134387016,
-0.17848828434944153,
0.022238869220018387,
0.19095756113529205,
-0.4028981029987335,
0.08323492109775543,
0.029038773849606514,
0.5242980122566223,
0.2626417875289917,
0.33348166942596... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Customize_Frontend_Build#develop-for-the-core | Develop for the core
This would work quite the same way as mentioned above. For this purpose an additional option of the
portal-engine:update:frontend-build exists (--core-bundle-development).
bin/console portal-engine:update:frontend-build --core-bundle-development
This will install additional npm scripts to update t... | Develop for the core | [
-0.5546236038208008,
0.04144778102636337,
-0.2361731231212616,
-0.185277059674263,
0.10433831810951233,
0.019978761672973633,
0.03609132021665573,
0.3058430850505829,
-0.10768791288137436,
0.012186918407678604,
0.09517513960599899,
0.43140652775764465,
0.2108156383037567,
0.446332067251205... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Frontend_Architecture#frontend-folder-structure | Frontend folder structure
The following chapter contains a deep dive into the folder structure of the frontend application and some important
additional information. It provides an overview of the frontend architecture and should help you to locate the files
you need. | Frontend folder structure | [
0.18736138939857483,
-0.033830370754003525,
-0.24444617331027985,
0.3767549693584442,
0.3019291162490845,
-0.23826341331005096,
0.04084917530417442,
-0.15756510198116302,
0.04198356345295906,
0.14638298749923706,
-0.15127402544021606,
-0.12821383774280548,
0.2112123668193817,
0.11504227668... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Frontend_Architecture#the-assets-folder | The assets folder
The assets folder serves as root folder for the whole frontend application.
assets/fonts
Self-hosted web font files.
assets/icons
SVG icons
assets/images
Static images (e.g. placeholder image).
assets/scripts
JS files and JSX components. See The assets/scripts folder below for more details.
asse... | The assets folder | [
0.2660385072231293,
-0.27847930788993835,
-0.2475155144929886,
0.5063266158103943,
0.2033192664384842,
0.2009781152009964,
-0.0934930071234703,
0.13340146839618683,
0.22833628952503204,
-0.03982476890087128,
-0.14362578094005585,
-0.1740778535604477,
0.18889325857162476,
-0.068170495331287... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Frontend_Architecture#the-assetsscripts-folder | The assets/scripts folder
The assets/scripts is home for all JavaScript files. It contains all JSX components, the whole frontend
application logic and entry files for all pages.
components
Generic JSX components that are used throughout the whole application
consts
Global constants (e.g. media query breakpoints, fe... | The assets/scripts folder | [
0.15277358889579773,
-0.1537473052740097,
-0.19491088390350342,
0.42690595984458923,
0.06190537288784981,
0.17857509851455688,
0.03848433122038841,
0.3911701738834381,
0.03825950622558594,
-0.1857690066099167,
-0.33262836933135986,
0.02944790944457054,
0.45072486996650696,
0.26621171832084... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/Frontend_Architecture#feature-folders | Feature folders
The assets/scripts/features folder consists of multiple subfolders. Each of these subfolders contains all JSX
components and logic concerning one part (or feature) of the application. Every feature folder usually contains the
following content:
components folder
JSX components for a specific feature. ... | Feature folders | [
0.2738443613052368,
-0.14538080990314484,
-0.15214985609054565,
0.30538633465766907,
0.062081027776002884,
-0.34264490008354187,
0.11357797682285309,
0.3550310730934143,
0.034753840416669846,
-0.18505507707595825,
-0.1776817888021469,
0.3228575885295868,
0.4028242230415344,
0.2242210209369... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/JSX_Components#jsx-components | JSX Components
The portal engine is build with customization in mind and offers a very flexible way to customized the application.
This chapter contains a small introduction to React / JSX components and describes how you can customize the appearance,
markup and behaviour of JSX components. | JSX Components | [
0.0045496379025280476,
-0.028586730360984802,
-0.2210223376750946,
-0.017039377242326736,
0.08799333870410919,
-0.1193632036447525,
0.02021896280348301,
0.13602441549301147,
-0.21844783425331116,
-0.21542099118232727,
-0.09708917140960693,
0.11132588237524033,
0.4976324141025543,
0.3830302... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/JSX_Components#introduction-to-react--jsx-components | Introduction to React / JSX components
React embraces the fact that rendering logic is inherently coupled with other UI logic (like event handling and state
updates). Instead of separating by technology React encourages to combine Markup and UI Logic into encapsulated
components. JSX enables this by providing an easy w... | Introduction to React / JSX components | [
-0.21413764357566833,
-0.11457076668739319,
-0.24985884130001068,
0.05115992948412895,
0.033953506499528885,
-0.08438720554113388,
0.1159084364771843,
0.4612240791320801,
0.2078286111354828,
-0.044790130108594894,
-0.11676949262619019,
0.048434533178806305,
0.48118966817855835,
0.559029042... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/JSX_Components#customizing-jsx-components | Customizing JSX Components
The process of customizing any component can be broken down into four steps:
Create the file {PROJECT_ROOT}/public/portal-engine/{FRONTEND_BUILD_NAME}/{PATH_TO_FILE}
(for Pimcore 6 {PROJECT_ROOT}/web/portal-engine/{FRONTEND_BUILD_NAME}/{PATH_TO_FILE})
Import everything you want to reused fro... | Customizing JSX Components | [
-0.20343029499053955,
0.02735680155456066,
-0.1423042118549347,
0.07454749196767807,
0.2203388661146164,
-0.191520556807518,
0.030966568738222122,
0.15280672907829285,
-0.3851718604564667,
0.030816365033388138,
-0.33535122871398926,
0.5879899263381958,
0.4513772130012512,
0.422461271286010... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/JSX_Components#override-generic-jsx-components | Override generic JSX components
The easiest way to start customizing the application is by overwriting a generic component completely.
To overwrite a component we have to create the corresponding file
{PROJECT_ROOT}/public/portal-engine/{FRONTEND_BUILD_NAME}/{PATH_TO_FILE} (for Pimcore 6 {PROJECT_ROOT}/web/portal-engin... | Override generic JSX components | [
-0.09181616455316544,
-0.06800892949104309,
-0.1097896620631218,
-0.09177158772945404,
0.34954434633255005,
-0.24778811633586884,
0.06753771007061005,
0.4217740595340729,
-0.21632492542266846,
0.0870446115732193,
-0.1985347718000412,
0.48868969082832336,
0.2153761237859726,
0.2548707127571... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/JSX_Components#customization-through-subcomponents | Customization through subcomponents
Some components allow you to customize parts of component through subcomponents. Subcomponents can be
passed in through component props and usually end with the suffix Component.
If we look at the bundle source file of the Teaser component we find three of those subcomponents:
Image... | Customization through subcomponents | [
0.12695181369781494,
-0.08685491979122162,
-0.21766029298305511,
0.022243408486247063,
0.1394578367471695,
-0.021334215998649597,
0.33434897661209106,
0.2387460619211197,
-0.2400560826063156,
0.14437638223171234,
-0.04533161222934723,
-0.1135152280330658,
0.3803038001060486,
-0.04251431673... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/JSX_Components#override-connected-components | Override connected components
A lot of non-generic components from the feature subfolder are connected to the global application store and have to
be treated a bit differently if you want to customize them. While you can just overwrite the default export of a
generic component you have to reconnect connected components... | Override connected components | [
-0.2502025365829468,
-0.024623041972517967,
-0.10423638671636581,
-0.33456483483314514,
0.15842927992343903,
-0.11785474419593811,
0.1746824085712433,
0.16177134215831757,
0.008984614163637161,
-0.1449897438287735,
-0.29551929235458374,
0.25953924655914307,
0.5545300841331482,
0.2957318723... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/JSX_Components#adding-new-features | Adding new features
If you want to take it a step further you can customize mapStateToProps and mapDispatchToProps too. This allows
you to add new features or change the behaviour of a component completely. The following example illustrates this:
import React from 'react';
import {connect} from "react-redux"... | Adding new features | [
-0.3266478478908539,
-0.1055772453546524,
-0.215498149394989,
-0.3463345468044281,
-0.2151685655117035,
-0.2486335188150406,
-0.04115386679768562,
0.20024144649505615,
0.054675545543432236,
-0.1887044459581375,
-0.1559564471244812,
0.22538886964321136,
0.36039528250694275,
0.23215204477310... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance/JSX_Components#customizing-other-parts-of-the-application | Customizing other parts of the application
This chapter showed you how you can customize the appearance and behaviour of JSX components, but you don't have to stop
there. You can use the same technique of importing, customizing and exporting to customize almost every part of the
application. | Customizing other parts of the application | [
0.06538409739732742,
-0.11966804414987564,
-0.31754380464553833,
-0.19865301251411438,
0.3538838326931,
-0.13592369854450226,
0.2607306241989136,
0.267031729221344,
-0.10393913835287094,
0.25739070773124695,
-0.1688886433839798,
0.20663480460643768,
0.49798062443733215,
0.10077997297048569... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance#customize-appearance | Customize Appearance
The appearance of the portal engine can be customized in multiple different ways. The simplest way is to customize the
look and feel by modifying the provided style options in the
portal config document.
This chapter describes how to do more advanced customizations via code changes. | Customize Appearance | [
0.1141429916024208,
0.02691967785358429,
-0.20608888566493988,
0.10915817320346832,
-0.0007448180695064366,
0.017750056460499763,
-0.037317775189876556,
0.19510911405086517,
-0.5524967312812805,
0.05129963532090187,
-0.08831553161144257,
0.23876090347766876,
0.433726966381073,
0.1255172044... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_Appearance#documentation-parts | Documentation Parts
Overwrite Templates
Customize Frontend Build
Frontend Folder Structure
Customize JSX Components
| Documentation Parts | [
0.12414887547492981,
0.04705594480037689,
-0.24558457732200623,
-0.017681824043393135,
0.19154489040374756,
-0.03659757971763611,
0.24121665954589844,
0.339855432510376,
-0.20454615354537964,
0.08786951005458832,
0.13467024266719818,
0.13175570964813232,
0.5267705321311951,
0.3028418719768... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/External_Authentication_Service#external-authentication-services | External Authentication Services
The portal engine provides several events to make it possible to integrate
external authentication services via the login form.
Pimcore\Bundle\PortalEngineBundle\Event\Auth\LoginCheckPasswordEvent
Pimcore\Bundle\PortalEngineBundle\Event\Auth\LoginFieldTypeEvent
Pimcore\Bundle\PortalEng... | External Authentication Services | [
-0.2946206331253052,
-0.17295514047145844,
-0.049984410405159,
0.008290097117424011,
-0.014201301150023937,
-0.23181559145450592,
0.038238510489463806,
-0.24474839866161346,
-0.21156734228134155,
0.05783909186720848,
0.009454801678657532,
0.23819568753242493,
0.2552594244480133,
0.21804000... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/External_Authentication_Service#example | Example
This example event subscriber will allow Pimcore admin users to login
to the portal engine as admin users too.
<?php
namespace AppBundle\EventListener;
use Pimcore\Bundle\PortalEngineBundle\Event\Auth\LoginCheckPasswordEvent;
use Pimcore\Bundle\PortalEngineBundle\Event\Auth\LoginFieldTypeEvent;
use Pimcore... | Example | [
-0.25214096903800964,
0.14537829160690308,
-0.013218197040259838,
0.16950052976608276,
0.17543134093284607,
-0.31521427631378174,
0.1978486031293869,
-0.08985918015241623,
-0.3204458951950073,
0.21911565959453583,
-0.17114152014255524,
0.33110275864601135,
-0.0010047171963378787,
0.0255240... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Name_Extractor#name-extractor-for-pimcore-elements | Name Extractor for Pimcore Elements
The name extractor is used to extract a name for data objects and assets. This name will be displayed and used at the
following positions in the frontend:
Displayed within the data pool listings.
Displayed for relations of elements on data object detail pages.
Used within the full t... | Name Extractor for Pimcore Elements | [
0.015272482298314571,
-0.08498373627662659,
-0.1265893280506134,
0.29209932684898376,
0.0651574432849884,
-0.2701755464076996,
0.041120197623968124,
0.17554844915866852,
-0.38428929448127747,
0.5618426203727722,
-0.30755433440208435,
0.4400814473628998,
0.1868506819009781,
0.05218355357646... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Name_Extractor#example | Example
This example event subscriber will append the production year to the name of Car data objects.
<?php
namespace AppBundle\EventListener;
use Pimcore\Bundle\PortalEngineBundle\Event\DataObject\ExtractNameEvent;
use Pimcore\Model\DataObject\Car;
use Symfony\Component\EventDispatcher\EventSubscriberInterface;
... | Example | [
-0.18091028928756714,
0.34801384806632996,
-0.02474544569849968,
0.20963357388973236,
0.12793654203414917,
-0.29298144578933716,
0.17671148478984833,
0.09722815454006195,
-0.1568012535572052,
0.5259578227996826,
-0.049231354147195816,
0.5023999810218811,
0.030965382233262062,
0.10930036008... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Name_Extractor#update-elasticsearch-index | Update Elasticsearch Index
If you change the logic for the name extraction process do not forget to update the index (at least for the affected elements).
# update all index mappings and put all elements in the queue (restrictable with corresponding command options and arguments)
bin/console portal-engine:update:index
... | Update Elasticsearch Index | [
-0.010960821993649006,
-0.019181856885552406,
-0.27535533905029297,
-0.08953142911195755,
-0.03827039524912834,
-0.11565206944942474,
-0.022548936307430267,
0.2767806947231293,
-0.2350236028432846,
0.38755592703819275,
-0.07823406159877777,
0.29082196950912476,
0.19393639266490936,
-0.1253... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Main_Image_Extractor#main-image-extractor-for-data-objects | Main Image Extractor for Data Objects
The main image extractor is used to extract the main image of a data object. The main image will be visible for example
in the data pool listings and in the download cart.
By default, the first found image of the data object will be used (depending on the class definition layout). ... | Main Image Extractor for Data Objects | [
-0.2095964252948761,
-0.5232470631599426,
-0.10244181752204895,
0.5338068008422852,
-0.08697810769081116,
-0.011786529794335365,
-0.09259232878684998,
-0.10660171508789062,
0.025955533608794212,
0.3275855481624603,
-0.1740235984325409,
-0.033008873462677,
0.23256327211856842,
0.17781372368... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Main_Image_Extractor#change-behaviour-via-event | Change Behaviour via Event
The Pimcore\Bundle\PortalEngineBundle\Event\DataObject\ExtractMainImageEvent can be used to customize the logic. | Change Behaviour via Event | [
-0.290054053068161,
0.08790178596973419,
-0.19631868600845337,
0.20558896660804749,
0.003616808447986841,
-0.4176196753978729,
0.16928930580615997,
-0.06569096446037292,
-0.18101470172405243,
0.22306841611862183,
-0.15781909227371216,
0.2848597466945648,
0.07862972468137741,
0.245566546916... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Main_Image_Extractor#example | Example
<?php
namespace AppBundle\EventListener;
use Pimcore\Bundle\PortalEngineBundle\Event\DataObject\ExtractMainImageEvent;
use Pimcore\Model\Asset;
use Pimcore\Model\Asset\Image;
use Pimcore\Model\DataObject\Car;
use Pimcore\Model\DataObject\Data\ImageGallery;
use Symfony\Component\EventDispatcher\EventSubscri... | Example | [
-0.46978288888931274,
-0.165593221783638,
-0.1605294644832611,
0.2755607068538666,
-0.018159974366426468,
-0.20303505659103394,
0.3178064525127411,
0.25241732597351074,
0.0280907079577446,
0.2395426332950592,
-0.0038660136051476,
0.17471395432949066,
0.010187583975493908,
-0.10311004519462... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Data_Exporter#data-exporter | Data Exporter
The Portal Engine ships with a service which can make structured data of data objects and assets downloadable via the
frontend (for example as CSV or JSON file).
If setup correctly the structured download format will be provided at all places where downloads are possible
(single download, multi download, ... | Data Exporter | [
-0.28967127203941345,
0.04157119244337082,
-0.22442491352558136,
0.18812471628189087,
0.13872753083705902,
-0.01796366460621357,
0.1711699217557907,
0.3836017847061157,
-0.1462853103876114,
-0.04135812073945999,
-0.14135682582855225,
0.1989491879940033,
0.07441947609186172,
0.6812590360641... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Data_Exporter#enable-download-format-in-the-data-pool-config | Enable download format in the data pool config
To provide a download format in the frontend it's needed that the format is activated in the "Available Download Formats"
config option of the related data pool configuration document. | Enable download format in the data pool config | [
-0.5513163805007935,
-0.3156639635562897,
-0.1952010989189148,
-0.24218183755874634,
0.2520982027053833,
-0.022558528929948807,
0.04687504470348358,
0.2804085314273834,
0.018239328637719154,
0.21573986113071442,
-0.3641332685947418,
0.06779784709215164,
0.3037230670452118,
0.22292707860469... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Data_Exporter#provide-your-own-download-format-implementation | Provide your own download format implementation
As mentioned above, it is possible to create your own download formats if needed. To add a new format add a service which
implements the DownloadFormatInterface into the service container configuration.
If your download format is suitable for some data objects or assets o... | Provide your own download format implementation | [
-0.33909499645233154,
-0.013666749931871891,
-0.19331325590610504,
0.020023617893457413,
0.18766459822654724,
-0.25790244340896606,
0.09210047870874405,
0.2243860960006714,
-0.1449579894542694,
0.11847341060638428,
-0.253518670797348,
0.17391574382781982,
0.04972447454929352,
0.37375420331... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Add_Area_Bricks#add-additional-area-bricks | Add additional Area Bricks
Area bricks are principally implemented the same way as described in the
Pimcore documentation.
The only difference is that the area brick class needs to extend the Pimcore\Bundle\PortalEngineBundle\Document\AbstractAreaBrick
class. As soon as a service with this parent class is registered in... | Add additional Area Bricks | [
-0.007196624297648668,
0.004311129916459322,
-0.12076757103204727,
0.08763115108013153,
-0.15404900908470154,
-0.10782395303249359,
0.3621205687522888,
-0.2589292824268341,
0.11795444041490555,
0.24264614284038544,
-0.18159137666225433,
0.5615515112876892,
0.1328386813402176,
0.05943440645... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/PreCondition_Service#precondition-service-for-data-pools | Precondition Service for Data Pools
Data pool workspaces and permissions provide a good way to configure which assets and data objects should be visible in
the portal engine frontend. Nevertheless, depending on the use case this might not be enough.
If you would like to add your individual filter logic which should be ... | Precondition Service for Data Pools | [
-0.3101305663585663,
0.19949793815612793,
-0.15333819389343262,
-0.07146765291690826,
-0.06871639937162399,
-0.3455248475074768,
0.2645672559738159,
0.25295713543891907,
-0.15142002701759338,
0.07237400859594345,
-0.3856603503227234,
0.034075748175382614,
0.10963200032711029,
0.09513653069... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/PreCondition_Service#sample-service | Sample Service
class ActualCars implements PreConditionServiceHandlerInterface
{
public function addPreCondition(Search $search)
{
$search->addQuery(new TermQuery("standard_fields.objectType.raw", "Actual-Car"));
}
}
| Sample Service | [
-0.1704109162092209,
-0.128583163022995,
-0.05926591157913208,
-0.21169349551200867,
-0.059701960533857346,
-0.20495793223381042,
-0.1386917680501938,
0.31353873014450073,
0.0968116745352745,
0.05789601057767868,
-0.14583289623260498,
0.07513796538114548,
-0.0653231143951416,
0.15253011882... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/PreCondition_Service#sample-service-definition | Sample Service Definition
AppBundle\PortalEngine\PreConditionService\ActualCars:
tags:
- { name: pimcore.portal_engine.pre_condition_service_handler }
The search can be modified using the ONGR ElasticsearchDSL query builder library. | Sample Service Definition | [
-0.08980433642864227,
-0.08831363916397095,
-0.20438924431800842,
-0.20379804074764252,
0.009411339648067951,
-0.08433420956134796,
-0.07475049793720245,
0.2693250775337219,
-0.05968845263123512,
-0.0944921225309372,
-0.02295217663049698,
0.321534663438797,
-0.10994331538677216,
0.16746929... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Events#events | Events
Within the portal engine the following events are triggered to allow influencing certain behaviors. All of these events
are triggered via the Symfony event dispatcher. Therefore, the related
Symfony Events and Event Listeners documentation is a good starting
point if you do not know how it works already.
The eve... | Events | [
0.08234965056180954,
-0.050412487238645554,
-0.03688358515501022,
0.23407088220119476,
-0.0598997101187706,
-0.19211935997009277,
0.20942449569702148,
-0.12238825857639313,
-0.14894802868366241,
0.17366084456443787,
0.010202370584011078,
0.21431340277194977,
0.13611340522766113,
-0.0572200... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Events#list-of-events | List of Events
Take a look at the event PHP classes. You will find a hint for the purpose of the events as PHP doc. Additionally, the
getters and setters describe which attributes can be influenced by event listeners. | List of Events | [
-0.13500405848026276,
-0.22908085584640503,
-0.27730822563171387,
0.47104743123054504,
0.017627345398068428,
-0.24969471991062164,
0.007871675305068493,
0.009671596810221672,
0.07906312495470047,
0.3980242908000946,
0.10307247936725616,
0.0717233270406723,
-0.18974384665489197,
-0.09555979... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Events#asset | Asset
Pimcore\Bundle\PortalEngineBundle\Event\Asset\ExtractMappingEvent
Pimcore\Bundle\PortalEngineBundle\Event\Asset\ExtractNameEvent
Pimcore\Bundle\PortalEngineBundle\Event\Asset\UpdateIndexDataEvent
Pimcore\Bundle\PortalEngineBundle\Event\Asset\Upload\PreAssetCreateEvent
Pimcore\Bundle\PortalEngineBundle\E... | Asset | [
-0.3274402320384979,
0.1047995463013649,
-0.23627309501171112,
0.1149309054017067,
0.0510527566075325,
-0.08609603345394135,
0.20936648547649384,
0.24856384098529816,
-0.19172172248363495,
0.20250093936920166,
-0.017480384558439255,
0.38832107186317444,
0.081119105219841,
0.057496789842844... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Events#data-object | Data Object
Pimcore\Bundle\PortalEngineBundle\Event\DataObject\ExtractMainImageEvent
Pimcore\Bundle\PortalEngineBundle\Event\DataObject\ExtractMappingEvent
Pimcore\Bundle\PortalEngineBundle\Event\DataObject\ExtractNameEvent
Pimcore\Bundle\PortalEngineBundle\Event\DataObject\UpdateIndexDataEvent
| Data Object | [
-0.2763177752494812,
0.064871646463871,
-0.18962424993515015,
0.5121641159057617,
0.04759396240115166,
-0.08082439750432968,
-0.025945745408535004,
0.10934630036354065,
-0.13803894817829132,
0.17578373849391937,
-0.09048730134963989,
0.4015185236930847,
0.04424609988927841,
0.2707923054695... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Events#auth | Auth
Pimcore\Bundle\PortalEngineBundle\Event\Auth\LoginCheckPasswordEvent
Pimcore\Bundle\PortalEngineBundle\Event\Auth\LoginFieldTypeEvent
Pimcore\Bundle\PortalEngineBundle\Event\Auth\LoginGetUserEvent
Pimcore\Bundle\PortalEngineBundle\Event\Auth\LoginPasswordChangeableEvent
Pimcore\Bundle\PortalEngineBundle\... | Auth | [
-0.338570773601532,
-0.1733786016702652,
-0.1631408929824829,
0.1965908408164978,
0.041946083307266235,
0.007576479576528072,
0.19873806834220886,
-0.01441933773458004,
-0.13717985153198242,
-0.0012122944463044405,
0.04277792572975159,
0.13173025846481323,
0.1397765725851059,
0.10726901143... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Events#download | Download
Pimcore\Bundle\PortalEngineBundle\Event\Download\DownloadAssetEvent
Pimcore\Bundle\PortalEngineBundle\Event\Download\DownloadAssetPathInZipEvent
Pimcore\Bundle\PortalEngineBundle\Event\Download\DownloadSourcesEvent
Pimcore\Bundle\PortalEngineBundle\Event\Download\DownloadTypesEvent
Pimcore\Bundle\Por... | Download | [
-0.4241696000099182,
-0.031735945492982864,
-0.22665265202522278,
0.28050073981285095,
0.10471653193235397,
0.036447666585445404,
-0.06587255001068115,
0.13593779504299164,
-0.22427180409431458,
0.11225882917642593,
-0.05425092950463295,
0.2652871310710907,
-0.025425277650356293,
0.1717492... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Events#element | Element
Pimcore\Bundle\PortalEngineBundle\Event\Element\VersionHistoryEvent
| Element | [
-0.5918984413146973,
-0.056808389723300934,
-0.20917978882789612,
0.09572596848011017,
-0.11547074466943741,
0.013091592118144035,
-0.07960153371095657,
0.11640173196792603,
-0.08172067254781723,
0.07511851191520691,
0.05640842765569687,
0.30813929438591003,
-0.06853155046701431,
0.3108364... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Events#permission | Permission
Pimcore\Bundle\PortalEngineBundle\Event\Permission\DataPoolAccessEvent
Pimcore\Bundle\PortalEngineBundle\Event\Permission\DataPoolCreateItemEvent
Pimcore\Bundle\PortalEngineBundle\Event\Permission\DataPoolDeleteItemEvent
Pimcore\Bundle\PortalEngineBundle\Event\Permission\DataPoolDownloadAccessEvent
... | Permission | [
-0.2664637863636017,
0.16308197379112244,
-0.21344584226608276,
-0.037625279277563095,
0.07933960109949112,
-0.11591879278421402,
0.19055256247520447,
0.06035138666629791,
-0.16087706387043,
0.08170942962169647,
-0.06376562267541885,
0.1808849573135376,
0.12962606549263,
-0.027409516274929... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior/Events#search | Search
Pimcore\Bundle\PortalEngineBundle\Event\Search\FilterableFieldsEvent
Pimcore\Bundle\PortalEngineBundle\Event\Search\ListableFieldsEvent
Pimcore\Bundle\PortalEngineBundle\Event\Search\SearchQueryEvent
Pimcore\Bundle\PortalEngineBundle\Event\Search\SortableFieldsEvent
| Search | [
-0.3798925578594208,
-0.18184331059455872,
-0.28171175718307495,
0.1261257529258728,
0.007769303862005472,
-0.10517396777868271,
-0.1617393046617508,
0.2147570252418518,
-0.13513271510601044,
0.10282865911722183,
-0.16284435987472534,
0.3582472801208496,
-0.1644437313079834,
0.139149919152... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior#customize-and-extend-behavior | Customize and Extend Behavior
In this chapter you will find more information about how to customize
and extend certain PHP parts of the portal engine. If you would like to
learn more about customizing the javascript take a look at
Customize Frontend Build. | Customize and Extend Behavior | [
-0.08745132386684418,
-0.13145682215690613,
-0.2914838194847107,
-0.13215921819210052,
0.09222973883152008,
-0.09402886033058167,
0.10112757980823517,
0.1811435967683792,
-0.23899085819721222,
0.2174300104379654,
0.12430734932422638,
0.11974627524614334,
0.18202748894691467,
0.233531206846... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation/Customize_and_Extend_Behavior#documentation-parts | Documentation Parts
External Authentication Service
Name Extractor for Pimcore Elements
Main Image Extractor for Data Objects
Data Exporter
Add additional Area Bricks
Precondition Service for Data Pools
Events
| Documentation Parts | [
-0.08307886123657227,
-0.2186872512102127,
-0.33040088415145874,
0.23507140576839447,
0.0643874928355217,
0.0759684219956398,
0.3701675534248352,
-0.02299230359494686,
-0.03763313591480255,
0.14436273276805878,
-0.1549951136112213,
0.28589364886283875,
0.3862522542476654,
0.459842085838317... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation#development-documentation | Development Documentation
The portal engine offers quite a lot of configuration possibilities through its administration features.
Further more it was implemented with project specific customization requirements in mind.
As the portal engine is a regular Symfony bundle it is possible to extend its parts like described
... | Development Documentation | [
-0.16470371186733246,
0.04138932004570961,
-0.18239443004131317,
0.008282515220344067,
-0.1764967143535614,
-0.21682490408420563,
0.24650277197360992,
-0.019783057272434235,
-0.3431999385356903,
0.11578162759542465,
-0.048266779631376266,
0.19881512224674225,
0.048365622758865356,
0.142288... |
https://pimcore.com/docs/platform//Portal_Engine/Development_Documentation#documentation-parts | Documentation Parts
Extending Search Index:
Describes how to add additional data attributes to the Elasticsearch index.
Customize Appearance:
Describes how to change the appearance of the portal engine via twig templates and customized frontend builds.
Customize and Extend Behavior:
Describes how to customize the b... | Documentation Parts | [
0.30490532517433167,
-0.17561137676239014,
-0.24973106384277344,
-0.019572477787733078,
-0.08228641003370285,
0.33971187472343445,
-0.1820804625749588,
0.21540579199790955,
-0.23179325461387634,
0.05975378304719925,
-0.04882562905550003,
0.282636433839798,
0.15928331017494202,
-0.161555692... |
https://pimcore.com/docs/platform//Portal_Engine#portal_engine | Portal_Engine
| Portal_Engine | [
-0.21954871714115143,
-0.16760264337062836,
-0.3173447549343109,
0.20311714708805084,
-0.03203878179192543,
-0.30285975337028503,
0.08978885412216187,
0.13591234385967255,
-0.5643825531005859,
-0.2195623368024826,
0.1941748857498169,
0.22069311141967773,
0.019099410623311996,
0.28691881895... |
https://pimcore.com/docs/platform//Portal_Engine#title:-portal-engine | title: Portal Engine | title: Portal Engine | [
0.12201502919197083,
0.028794925659894943,
-0.3405243754386902,
-0.036372922360897064,
-0.08267369866371155,
-0.045403774827718735,
0.1588984578847885,
0.09000418335199356,
-0.39556649327278137,
-0.08056948333978653,
0.19566263258457184,
0.15393735468387604,
-0.006202705670148134,
0.232483... |
https://pimcore.com/docs/platform//Portal_Engine#pimcore-portal-engine | Pimcore Portal Engine
Pimcore Portal Engine allows creating outstanding Asset Experience Portals and Product Experience Portals just by configuration - no coding needed.
The created portals provide lots of out-of-the box features and allow UI customization by configuration. Additionally, it is possible to further adapt... | Pimcore Portal Engine | [
-0.2569778859615326,
-0.17126041650772095,
-0.23551036417484283,
0.021660661324858665,
-0.10079711675643921,
-0.11753343045711517,
0.08145362138748169,
0.05479477718472481,
-0.33856335282325745,
-0.09727109223604202,
-0.2635214030742645,
0.4832988381385803,
-0.08476676791906357,
0.59266400... |
https://pimcore.com/docs/platform//Portal_Engine#features-in-a-nutshell | Features in a Nutshell
Multiple portals configuration in one system for different target groups.
Data visualization from Assets and Data Objects managed in Pimcore.
Searching, filtering for, and navigating through data.
Management of Assets by uploading, updating, deleting and editing Assets metadata.
Different format... | Features in a Nutshell | [
-0.22107702493667603,
-0.44844111800193787,
-0.2440759241580963,
0.15902014076709747,
-0.03230149298906326,
-0.12364962697029114,
0.2760973274707794,
-0.03475971519947052,
-0.3921505808830261,
-0.04361811652779579,
-0.4234822392463684,
0.24998623132705688,
0.12665502727031708,
0.5142869949... |
https://pimcore.com/docs/platform//Portal_Engine#documentation-overview | Documentation Overview
Installation (for administrators and developers)
Administration of Portals (for administrators and developers)
User Documentation for Portals (for users)
Development Documentation (for developers)
| Documentation Overview | [
0.24730315804481506,
-0.3039746880531311,
-0.2256382703781128,
0.141256645321846,
0.012061327695846558,
0.30635884404182434,
0.1587696671485901,
-0.2162938117980957,
-0.2088516503572464,
-0.06873996555805206,
0.1243211105465889,
-0.0009951612446457148,
0.28199249505996704,
0.01263647153973... |
https://pimcore.com/docs/platform//Datahub/Installation_and_Upgrade/Upgrade_Notes#upgrade-notes | Upgrade Notes | Upgrade Notes | [
-0.02674354985356331,
-0.12655343115329742,
-0.3046375811100006,
0.17332887649536133,
0.3031214475631714,
0.11353010684251785,
-0.2813548445701599,
0.009953399188816547,
-0.2989424765110016,
0.19082218408584595,
0.041895221918821335,
0.150481715798378,
-0.06226081773638725,
0.0015277648344... |
https://pimcore.com/docs/platform//Datahub/Installation_and_Upgrade/Upgrade_Notes#1.6.0 | 1.6.0
[General] If you want to use Datahub 1.6 and Pimcore 11, please make sure to require the pimcore/admin-ui-classic-bundle.
[Config Location] Change default directory for configurations to var/config/data_hub
When using Pimcore 11, configurations from datahub-configurations.php are no longer used. To migrate thos... | 1.6.0 | [
-0.43354228138923645,
0.05531347915530205,
-0.08108948171138763,
-0.048508211970329285,
-0.21844378113746643,
-0.21820557117462158,
0.00904036033898592,
0.29915985465049744,
0.02977875992655754,
0.23863185942173004,
-0.43957382440567017,
0.43732357025146484,
-0.048457980155944824,
0.417252... |
https://pimcore.com/docs/platform//Datahub/Installation_and_Upgrade/Upgrade_Notes#1.5.0 | 1.5.0
When "Skip Permission Check" is active in a GraphQL configuration, the "Workspaces" settings are also skipped
It is possible to add more than one API key per configuration now. Therefore, the API keys get stored as an array
in the configuration. Configurations from previous versions are still... | 1.5.0 | [
0.0017877270001918077,
0.17512668669223785,
-0.09776567667722702,
-0.05455228313803673,
-0.2860490679740906,
-0.34258925914764404,
0.006228737998753786,
0.2893979847431183,
0.5965602993965149,
0.40588611364364624,
-0.1835097223520279,
0.21225591003894806,
-0.14795634150505066,
0.4960264563... |
https://pimcore.com/docs/platform//Datahub/Installation_and_Upgrade#installation | Installation | Installation | [
-0.06728437542915344,
-0.4834894835948944,
-0.3417288661003113,
0.20734061300754547,
0.06259846687316895,
0.09173910319805145,
-0.07573223114013672,
-0.07214274257421494,
0.15155638754367828,
0.1816904991865158,
-0.07461769878864288,
0.14365136623382568,
0.041423697024583817,
0.05546558648... |
https://pimcore.com/docs/platform//Datahub/Installation_and_Upgrade#bundle-installation | Bundle Installation | Bundle Installation | [
-0.15236809849739075,
-0.5798049569129944,
-0.25142624974250793,
0.26133793592453003,
0.05988699570298195,
0.1664704829454422,
0.09695267677307129,
-0.017498914152383804,
-0.08696809411048889,
0.0494609996676445,
0.04989751800894737,
0.18994802236557007,
-0.19939713180065155,
0.22001001238... |
https://pimcore.com/docs/platform//Datahub/Installation_and_Upgrade#for-pimcore->=-10.6 | For Pimcore >= 10.6
To install Pimcore Datahub for Pimcore 10.6 or higher, follow the three steps below:
Install the required dependencies:
composer require pimcore/data-hub
Make sure the bundle is enabled in the config/bundles.php file. The following lines should be added:
use Pimcore\Bundle\DataHubBundle\Pimc... | For Pimcore >= 10.6 | [
-0.346911758184433,
-0.06691014766693115,
-0.16547589004039764,
0.06937213242053986,
-0.1355854570865631,
-0.13723668456077576,
0.09421356767416,
0.18179336190223694,
-0.2941319942474365,
0.27205362915992737,
-0.23085293173789978,
0.49249500036239624,
-0.045762065798044205,
0.1566227823495... |
https://pimcore.com/docs/platform//Datahub/Installation_and_Upgrade#for-pimcore-11 | For Pimcore 11
You need to follow the steps mentioned above and additionally run the following command:
composer require pimcore/admin-ui-classic-bundle
| For Pimcore 11 | [
-0.3934876322746277,
-0.08261220157146454,
-0.14979122579097748,
0.02371276170015335,
0.18444740772247314,
-0.16008318960666656,
0.08403971791267395,
-0.0007112571038305759,
-0.09843407571315765,
0.22060109674930573,
-0.15307468175888062,
0.492026686668396,
-0.010796979069709778,
0.1577836... |
https://pimcore.com/docs/platform//Datahub/Installation_and_Upgrade#for-older-versions | For Older Versions
To install the Datahub bundle for older versions of Pimcore, please run the following commands instead:
# For Pimcore >= 10.2:
composer require pimcore/data-hub
# For Pimcore < 10.2 replace the first line with:
# composer require pimcore/data-hub:~1.0.11
bin/console pimcore:bundle:enable Pimco... | For Older Versions | [
-0.4461374282836914,
-0.0785674974322319,
-0.24135513603687286,
-0.021649127826094627,
-0.09352154284715652,
-0.11182335019111633,
0.22856469452381134,
0.1844385415315628,
-0.2709198594093323,
0.2065843641757965,
-0.162961944937706,
0.42085424065589905,
-0.05662398412823677,
0.058666806668... |
https://pimcore.com/docs/platform//Datahub/Installation_and_Upgrade#required-backend-user-permission | Required Backend User Permission
To access Datahub, user needs to meet one of following criteria:
be an admin
have plugin_datahub_config permission
| Required Backend User Permission | [
0.04007749632000923,
-0.045947980135679245,
-0.13985176384449005,
-0.12001735717058182,
-0.042452722787857056,
-0.2118745893239975,
0.38838139176368713,
-0.0013060488272458315,
0.037005458027124405,
0.26619336009025574,
-0.08788122236728668,
0.07496705651283264,
0.09684185683727264,
0.4350... |
https://pimcore.com/docs/platform//Datahub/Basic_Principle#basic-principle | Basic Principle
Pimcore Datahub allows defining multiple endpoints that allow data delivery and consumption. These endpoints are configured via so called configurations that can be added in the Pimcore admin user interface: | Basic Principle | [
-0.2104489505290985,
-0.33748507499694824,
-0.25893184542655945,
-0.03882436454296112,
-0.1673235446214676,
-0.37385818362236023,
0.09591709077358246,
-0.35129374265670776,
-0.11722417175769806,
0.12702728807926178,
-0.4103028476238251,
0.35989952087402344,
0.12216006219387054,
0.509351134... |
https://pimcore.com/docs/platform//Datahub/Basic_Principle#adding-a-new-configuration | Adding a New Configuration
Open the Datahub configuration panel:
Choose an endpoint technology:
Get the configuration done by defining the followings:
General settings
Schema configuration
Security definitions
Additional settings
Here you can find an example for GraphQL. | Adding a New Configuration | [
-0.37410879135131836,
-0.08660903573036194,
-0.18765570223331451,
-0.3580624759197235,
-0.25786468386650085,
-0.3312489986419678,
0.19035789370536804,
-0.04342667758464813,
0.3332670331001282,
0.07760875672101974,
-0.07608696073293686,
0.2022220343351364,
0.09329486638307571,
0.49912771582... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Configuration/General_Settings#general-settings | General Settings
| General Settings | [
-0.3088560104370117,
-0.827970564365387,
-0.15244489908218384,
-0.012208961881697178,
0.28401845693588257,
0.1131628155708313,
0.14906837046146393,
0.030590586364269257,
-0.23434776067733765,
0.11129002273082733,
0.11940033733844757,
-0.3453328311443329,
-0.16182532906532288,
0.20797936618... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Configuration/General_Settings#some-aspects: | Some Aspects:
Active: You can temporarily disable the configuration using the checkbox.
SQL Condition: You can add a condition all data object queries have to satisfy in addition to
the workspace settings.
| Some Aspects: | [
-0.181300088763237,
-0.11305108666419983,
-0.21990631520748138,
-0.09290839731693268,
-0.3444269895553589,
-0.39129650592803955,
0.0891856849193573,
0.28152376413345337,
0.1378883421421051,
0.3278637230396271,
-0.042896419763565063,
-0.01387536246329546,
-0.16938093304634094,
0.03608867153... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Configuration/Schema_Settings#schema-settings | Schema Settings
Schema settings define which data entities (Data Object classes, Assets, Documents) should be exposed via the endpoint. For Assets and Documents, default schemas are provided, for Data Object classes the schema can be defined in the field configuration.
| Schema Settings | [
-0.152866929769516,
-0.39117905497550964,
-0.10978394001722336,
0.137716606259346,
0.15481078624725342,
-0.12094064056873322,
-0.06810276955366135,
-0.09292961657047272,
0.039318714290857315,
-0.13967463374137878,
0.07313255220651627,
-0.026392318308353424,
0.2839986979961395,
0.1467489600... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Configuration/Schema_Settings#query-schema | Query Schema
Here you can configure which Data Objects Classes can be exposed. | Query Schema | [
-0.2213141769170761,
-0.020514627918601036,
-0.3163394033908844,
0.3635048568248749,
0.1293477863073349,
-0.35805821418762207,
0.17471525073051453,
0.1822526603937149,
-0.030884839594364166,
0.08335068821907043,
-0.2131485491991043,
0.21222591400146484,
0.01388191245496273,
0.1520971357822... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Configuration/Schema_Settings#available-fields-configuration | Available Fields Configuration
When adding a new entity with the Add button, you can access the Available Fields Configuration window with a right-click on the Settings icon. You can then define all the target Data Object Class fields you want to make available.
In addition, you can employ a set of operators.
Please n... | Available Fields Configuration | [
-0.17866292595863342,
0.01091653574258089,
-0.13546247780323029,
-0.004765636753290892,
0.30626726150512695,
-0.07559595257043839,
0.03196892887353897,
0.06888154149055481,
0.044708892703056335,
0.3179725408554077,
-0.20217041671276093,
0.19370561838150024,
0.00737859308719635,
0.164006680... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Configuration/Schema_Settings#mutation-schema | Mutation Schema
Here you can decide if Data Objects for the selected class can be created, updated or deleted from the endpoint.
:::caution
Be aware that a Data Object deleted from an endpoint will be definitively deleted of Pimcore.
::: | Mutation Schema | [
-0.1302318274974823,
-0.15263697504997253,
-0.11101739853620529,
0.09344060719013214,
0.011904620565474033,
-0.640116810798645,
-0.06264150887727737,
-0.2519603669643402,
-0.16311883926391602,
0.011715708300471306,
-0.30240193009376526,
0.5655564069747925,
0.038605768233537674,
0.127685278... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Configuration/Schema_Settings#available-fields-configuration | Available Fields Configuration
As for the Query Schema field, you can select the fields you want to expose and/or make available for changes in the Available Fields Configuration you can open by clicking on the Settings icon. | Available Fields Configuration | [
-0.13459300994873047,
-0.1550484150648117,
-0.273049533367157,
-0.03360981494188309,
-0.04298326373100281,
-0.11941315233707428,
0.01309044100344181,
-0.06448082625865936,
-0.003964576404541731,
0.2697547376155853,
-0.12282833456993103,
0.14184802770614624,
0.25230467319488525,
0.245196178... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Configuration/Schema_Settings#generic-types | Generic Types
Here you can define which data types can be created, read, updated or deleted from an endpoint. | Generic Types | [
-0.011660223826766014,
-0.3146003782749176,
-0.24039772152900696,
-0.07509071379899979,
0.13792535662651062,
-0.39048922061920166,
0.1354086548089981,
-0.15540863573551178,
0.15205398201942444,
0.008712342008948326,
-0.045840073376894,
0.12144085019826889,
-0.062093235552310944,
0.24006898... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Configuration/Security_Settings#security-settings | Security Settings | Security Settings | [
-0.17879705131053925,
-0.504928469657898,
-0.286807119846344,
0.07237983494997025,
0.07486748695373535,
0.06826233118772507,
0.3136926591396332,
-0.27247902750968933,
-0.234796404838562,
0.16001522541046143,
0.016263140365481377,
-0.14073918759822845,
-0.013562438078224659,
0.1653488725423... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Configuration/Security_Settings#authentication | Authentication
Here you can define how users are authenticated when accessing the endpoint. | Authentication | [
0.03631587326526642,
-0.19799095392227173,
-0.29950788617134094,
-0.3123023808002472,
-0.14135709404945374,
-0.439075231552124,
0.30835121870040894,
-0.3365415334701538,
0.11817653477191925,
0.11111192405223846,
0.033600274473428726,
0.1040509045124054,
0.08952067792415619,
0.1202389523386... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Configuration/Security_Settings#supported-methods | Supported Methods
API Key: needs to be sent with every request.
... more to come
| Supported Methods | [
0.1443461924791336,
-0.28508782386779785,
-0.1553107351064682,
-0.24072757363319397,
-0.00045811536256223917,
-0.25173428654670715,
0.10938845574855804,
0.1679806411266327,
0.12578660249710083,
0.30470848083496094,
0.3297790288925171,
0.42514488101005554,
0.16999918222427368,
0.29553079605... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Configuration/Security_Settings#introspection-settings | Introspection Settings
Introspection provides an information about queries which are supported by GraphQl schema. This is currently enabled by default. It can be disabled via security settings or in the symfony configuration tree:
pimcore_data_hub:
graphql:
allow_introspection: false
| Introspection Settings | [
-0.34478524327278137,
-0.1103799045085907,
-0.13817110657691956,
0.13850988447666168,
-0.32813188433647156,
-0.49880310893058777,
0.009206748567521572,
0.05322672054171562,
0.1268283724784851,
0.342611700296402,
-0.23207654058933258,
0.2130061537027359,
0.19639542698860168,
0.1303013265132... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.