url stringlengths 50 196 | text stringlengths 3 17.2k | heading stringlengths 2 103 | embeddings list |
|---|---|---|---|
https://pimcore.com/docs/platform//Datahub_Webhooks/Installation#required-bundles | Required Bundles
This bundle depends on Pimcore Datahub bundle. This needs to be installed first. | Required Bundles | [
-0.3271258473396301,
-0.21303868293762207,
-0.19423209130764008,
-0.01872885785996914,
-0.07750827074050903,
-0.005332225002348423,
0.2224234789609909,
0.13292168080806732,
-0.18985703587532043,
0.07080167531967163,
-0.11254754662513733,
0.26534873247146606,
0.07108276337385178,
0.33809244... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Installation#installation-process | Installation Process
To install Pimcore Webhooks, follow the three steps below:
Install the required dependencies:
composer require pimcore/data-hub-webhooks --with-all-dependencies
Make sure the bundle is enabled in the config/bundles.php file. The following lines should be added:
use Pimcore\Bundle\DataHubWebhoo... | Installation Process | [
-0.16788971424102783,
-0.32429489493370056,
-0.14452840387821198,
0.0956360250711441,
-0.2034515142440796,
-0.03871333971619606,
0.2653903663158417,
-0.06006363034248352,
-0.10861673951148987,
0.08509791642427444,
-0.24713188409805298,
0.4506731629371643,
-0.10630851984024048,
0.1641133874... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Installation#bundle-configuration | Bundle Configuration | Bundle Configuration | [
-0.1497521698474884,
-0.7734434604644775,
-0.1553780883550644,
0.29922330379486084,
0.2179914116859436,
0.0595809631049633,
0.41703736782073975,
-0.20630677044391632,
-0.17295368015766144,
0.117451973259449,
-0.02126796543598175,
0.16865700483322144,
-0.127521812915802,
0.2348327785730362,... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Installation#symfony-messenger-configuration | Symfony Messenger Configuration
Messages are dispatched via pimcore_datahub_webhooks transport. Please ensure you have workers processing this transport when using the bundle. See Symfony Messenger documentation for details. | Symfony Messenger Configuration | [
0.024963676929473877,
-0.32653212547302246,
-0.02304893545806408,
0.17279765009880066,
-0.058017048984766006,
-0.20303939282894135,
0.4271129071712494,
-0.18131746351718903,
-0.11627475172281265,
0.18796823918819427,
-0.061424992978572845,
0.2048804610967636,
0.13994042575359344,
0.0135895... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration/Events_and_Schema#events-&-schema-tab | Events & Schema Tab
In the Events & Schema tab, you can configure the events you want to subscribe to and the data (payload) sent to each of your subscribers. | Events & Schema Tab | [
-0.12816189229488373,
-0.19011889398097992,
-0.1495281159877777,
-0.058235086500644684,
-0.02876005508005619,
-0.16254034638404846,
0.0872788205742836,
-0.1916133612394333,
0.06124498322606087,
0.2634161114692688,
-0.1583055555820465,
0.23513393104076385,
-0.042931608855724335,
0.356251507... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration/Events_and_Schema#events | Events
Select one or more events. Each time one of these events is triggered, a request will be sent to all the subscribers.
Note: Please make sure to configure the schema definition corresponding to the selected event(s) as described below. Otherwise, no requests will be sent to the subscribers.
The currently suppo... | Events | [
-0.10895295441150665,
-0.07218950241804123,
-0.07829205691814423,
-0.0355992391705513,
-0.1305679976940155,
-0.43549829721450806,
0.132612407207489,
-0.0911400318145752,
-0.013390219770371914,
0.2219049632549286,
-0.07555893808603287,
0.4751115143299103,
0.01897965371608734,
0.131612822413... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration/Events_and_Schema#schema-definition-documents | Schema Definition Documents
Document Types: Restrict event dispatching to your needed document types.
Include unpublished: Select this checkbox to include unpublished documents. Drafts will be included but not auto-saved versions.
:::info
The default available Document types are Snippet, Email, Folder, Hardlink an... | Schema Definition Documents | [
-0.12729403376579285,
-0.3988606929779053,
-0.050382088869810104,
0.06320127099752426,
-0.15768642723560333,
-0.05237412080168724,
-0.1617828607559204,
0.2828247845172882,
0.3149058222770691,
0.13716697692871094,
-0.06609059125185013,
0.3024154305458069,
-0.1263428032398224,
0.297076225280... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration/Events_and_Schema#schema-definition-assets | Schema Definition Assets
Asset Types: Restrict Asset based events to your needed Asset types.
Asset Data Settings:
Include Image Data: Select the image data to include. The list contains all available thumbnails, as well as the option to include the original data or no data at all.
Include Video Data: Select the... | Schema Definition Assets | [
-0.15480968356132507,
-0.32033470273017883,
-0.0925048291683197,
0.09567578136920929,
-0.020092735067009926,
-0.11449205130338669,
0.0410393662750721,
0.21211260557174683,
0.12180151045322418,
0.13972978293895721,
-0.10646569728851318,
0.05704475939273834,
-0.129592165350914,
0.24743524193... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration/Events_and_Schema#schema-definition-data-objects | Schema Definition Data Objects
Add Data Object classes to your request and select which data should be sent to the subscribers.
Settings: Click on the gear icon in the Settings column to select the contained fields among available ones in the left tree (see the Grid Configuration tab below).
Sample selected field... | Schema Definition Data Objects | [
0.042514462023973465,
-0.01681683026254177,
-0.09063751250505447,
0.13254690170288086,
-0.33142343163490295,
-0.0957232192158699,
-0.05121973901987076,
0.012108899652957916,
0.279885858297348,
0.16709166765213013,
-0.12131033837795258,
0.17670199275016785,
0.04346662387251854,
0.2893440425... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration/Events_and_Schema#schema-definition-workflows | Schema Definition Workflows
Workflows: Define the workflows that should be included for event dispatching.
| Schema Definition Workflows | [
-0.19870778918266296,
-0.2888084948062897,
-0.1994244009256363,
-0.10496287792921066,
-0.14106138050556183,
-0.3262251913547516,
0.07571686059236526,
0.024635713547468185,
0.22567954659461975,
0.14490918815135956,
0.2913494110107422,
0.12075891345739365,
-0.19386398792266846,
0.42659083008... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration/Workspaces#workspaces-tab | Workspaces Tab
In the Workspaces tab, you can limit the webhook configuration to include or exclude folders or folder structures.
Use the add button to add a new entry for each element type. Then just drag & drop a corresponding folder from the element trees.
Sample workspace with included folders for Documents, ... | Workspaces Tab | [
0.010502795688807964,
-0.24104562401771545,
-0.12900175154209137,
0.19403380155563354,
-0.2655063271522522,
-0.09111525118350983,
0.16532212495803833,
0.42990949749946594,
0.4048812687397003,
0.21101516485214233,
-0.48200148344039917,
0.09407057613134384,
-0.291960746049881,
0.431285858154... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration/Subscribers#subscribers-tab | Subscribers Tab
In the Subscribers tab, you can add one or more subscribers to your configuration. Each subscriber will receive a request with the information set in the Events and Schema tab.
| Subscribers Tab | [
-0.2212674766778946,
-0.1280543953180313,
-0.1852307766675949,
0.032260291278362274,
-0.06427719444036484,
-0.24862343072891235,
0.09710261970758438,
-0.26967668533325195,
0.03205334395170212,
0.4531134366989136,
-0.18874554336071014,
0.05531418323516846,
-0.010651525110006332,
0.245342314... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration/Subscribers#check-connectivity | Check connectivity
Use the button next to the input field to check the connectivity for all subscribers.
A basic request will be sent to the subscribers. If any error occurs, it will be displayed in a dialog box as below.
Note: Based on the connection timeout, the dialog can take a while to appear.
| Check connectivity | [
-0.10653437674045563,
-0.31855109333992004,
-0.12078923732042313,
-0.24010522663593292,
0.005673053674399853,
-0.10194361954927444,
0.18775776028633118,
-0.1634698063135147,
-0.047440800815820694,
0.1895318180322647,
0.18689632415771484,
0.15429751574993134,
0.28552091121673584,
-0.0354410... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration#general-tab | General Tab
The General tab allows to configure the webhook basic settings such as adding a description or choosing a log level depending on your needs.
Presentation of the General tab for a webhook configuration | General Tab | [
0.06434234231710434,
-0.9536398649215698,
-0.08362870663404465,
-0.2242504507303238,
-0.16160452365875244,
0.4884226620197296,
0.251897394657135,
-0.0737510398030281,
0.41579917073249817,
-0.02935020439326763,
-0.18512067198753357,
-0.3177957832813263,
0.3388480842113495,
0.406921237707138... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration#active | Active
The webhook execution will respect configurations marked as active. This option allows, for example, saving existing configurations without using them or deactivating them when they have to be modified. | Active | [
-0.2529643774032593,
-1.0060839653015137,
-0.054839104413986206,
-0.34788230061531067,
-0.23879824578762054,
-0.019517216831445694,
0.159097820520401,
-0.07710858434438705,
0.2756637930870056,
0.145051509141922,
-0.2730599045753479,
0.09322686493396759,
-0.21345511078834534,
0.255083084106... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration#log-level | Log Level
You can select a log level based on your needs, with or without combining different log levels. If this line stays empty, no log will be available.
Info: Logs all available information to the Logs tab in the configuration, including the requests, subscribers and http error codes.
Error: Logs errors and exc... | Log Level | [
-0.01622539944946766,
-0.40522682666778564,
-0.12450163066387177,
-0.11612046509981155,
-0.049742668867111206,
-0.009279122576117516,
0.22595934569835663,
-0.10369380563497543,
-0.03301965445280075,
0.1330876648426056,
0.04228011891245842,
-0.035073865205049515,
-0.024718785658478737,
0.03... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration#description | Description
This Description box allows to describe your configuration. | Description | [
-0.3635637164115906,
-0.5051847696304321,
-0.2798584997653961,
0.10546013712882996,
-0.05599866434931755,
-0.24140159785747528,
0.3231336772441864,
-0.07521697878837585,
-0.17541179060935974,
0.17951449751853943,
-0.0661473423242569,
-0.07907497137784958,
-0.01829090528190136,
0.2268376946... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Configuration#group | Group
This Group box allows to add a text to group the configurations in the Datahub tree view on the left. | Group | [
-0.5280548930168152,
-0.2025894969701767,
-0.23631392419338226,
-0.0740659087896347,
-0.1826271116733551,
0.05269590765237808,
0.3667854368686676,
0.05019941180944443,
-0.1630454659461975,
0.32377707958221436,
-0.3554327189922333,
0.1771519035100937,
0.020048173144459724,
0.354565858840942... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Example_Requests#request-structure | Request structure
The structure of the request sent to the subscribers has two important sections: | Request structure | [
0.3587058186531067,
-0.23147131502628326,
-0.2874360680580139,
0.21607737243175507,
-0.12108392268419266,
-0.3452140688896179,
-0.049533944576978683,
-0.14211930334568024,
-0.2604856491088867,
0.04220904782414436,
-0.12780289351940155,
-0.3377198874950409,
0.27341270446777344,
-0.140007108... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Example_Requests#general | General
The general section contains all basic data concerning the webhook.
For example the event which triggered the execution of the webhook or if only the version (draft) was saved.
...
"general": {
"eventName": "pimcore.dataobject.postUpdate",
"timestamp": 1653303523,... | General | [
-0.0075414120219647884,
-0.568130612373352,
-0.11145763099193573,
0.15405435860157013,
-0.08688261359930038,
-0.05369909107685089,
-0.13526172935962677,
0.07377678155899048,
-0.20840753614902496,
0.11415225267410278,
-0.08655406534671783,
0.13854043185710907,
0.11762285232543945,
0.3525974... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Example_Requests#subject | Subject
The subject section contains all information regarding the Data Object, Asset or Document based on the selected schema.
It also includes the binary data, if selected, as a base64 encoded string.
...
"subject": {
"id": 81,
"name": "Cobra 427",
"description... | Subject | [
0.3067135810852051,
-0.0432274304330349,
-0.1673898845911026,
0.3388719856739044,
0.0748087465763092,
-0.13726016879081726,
-0.09293779730796814,
0.12360521405935287,
-0.20958779752254486,
0.08246257901191711,
-0.06762037426233292,
0.303202360868454,
0.11580514162778854,
0.1617861986160278... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Example_Requests#samples | Samples | Samples | [
-0.16390453279018402,
-0.3209090828895569,
-0.3700988292694092,
0.029592743143439293,
-0.05186900496482849,
-0.1474957913160324,
0.3568430244922638,
0.32441404461860657,
-0.1570701003074646,
0.37480607628822327,
0.2585486173629761,
0.11548447608947754,
-0.28580111265182495,
0.1764257103204... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Example_Requests#data-objects | Data Objects
{
"general": {
"eventName": "pimcore.dataobject.postUpdate",
"timestamp": 1690975273,
"subjectType": "object",
"versionOnly": false
},
"subject": {
"id": 260,
"path": "/Pro... | Data Objects | [
-0.19801077246665955,
-0.06611179560422897,
-0.190482959151268,
0.4766414165496826,
-0.05831877514719963,
-0.25797179341316223,
-0.06422672420740128,
0.2285947948694229,
-0.4138448238372803,
0.14684709906578064,
0.15754498541355133,
0.4327661097049713,
0.16184502840042114,
0.37671017646789... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Example_Requests#assets | Assets
{
"general": {
"eventName": "pimcore.asset.postUpdate",
"timestamp": 1690975091,
"subjectType": "asset",
"versionOnly": false
},
"subject": {
"id": 83,
"path": "/Car Images/ferra... | Assets | [
-0.15705254673957825,
-0.05791551619768143,
-0.30046138167381287,
0.333690881729126,
-0.017146382480859756,
-0.12723374366760254,
0.052535250782966614,
0.3887094557285309,
-0.29265373945236206,
0.039182037115097046,
-0.00005298784526530653,
0.5671404600143433,
0.030754510313272476,
0.14831... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Example_Requests#documents | Documents
{
"general": {
"eventName": "pimcore.document.postUpdate",
"timestamp": 1690975115,
"subjectType": "document",
"versionOnly": false
},
"subject": {
"id": 65,
"path": "/en/News... | Documents | [
-0.13887056708335876,
-0.17553921043872833,
-0.254328191280365,
0.1381671279668808,
-0.18252485990524292,
-0.25403982400894165,
-0.12197210639715195,
0.2892446219921112,
-0.38221850991249084,
0.05074528977274895,
0.13471151888370514,
0.46215471625328064,
0.10009616613388062,
0.284879893064... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Extending#create-a-webhook-processor | Create a Webhook Processor
Extending or replacing existing processors is as easy as it gets. | Create a Webhook Processor | [
-0.23342928290367126,
-0.3434358239173889,
-0.3345528244972229,
-0.07227689772844315,
-0.14696696400642395,
-0.0035968997981399298,
0.1986459344625473,
0.18931378424167633,
0.4391023814678192,
0.16363383829593658,
-0.22198735177516937,
0.21484369039535522,
-0.05061167851090431,
0.436993837... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Extending#general | General
There are two different EventListener registered in services.yml. Each one of them listens to a specific set of events.
If one of these events is triggered, the EventListener calls the corresponding WebhookProcessor, which is responsible for executing the webhook. | General | [
0.17366592586040497,
-0.7117967009544373,
-0.09620435535907745,
0.09194052964448929,
-0.10725425183773041,
-0.10554701089859009,
0.32352906465530396,
-0.29306522011756897,
0.453384131193161,
0.13794471323490143,
-0.1964368224143982,
0.2131529599428177,
0.003950872458517551,
0.0261182300746... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Extending#event-listeners | Event Listeners | Event Listeners | [
-0.31686052680015564,
-0.5858033299446106,
-0.21910138428211212,
0.3890894949436188,
-0.13009588420391083,
-0.43715089559555054,
0.15680383145809174,
-0.15795601904392242,
0.11712950468063354,
0.5741210579872131,
-0.024416005238890648,
0.35257387161254883,
-0.5876039266586304,
-0.046179056... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Extending#elementeventlistener | ElementEventListener
Handles all events based on elements, e.g. postAdd and postUpdate events for Data Objects, Documents and Assets.
Pimcore\Bundle\DataHubWebhooksBundle\EventListener\ElementEventListener:
tags:
- { name: kernel.event_listener, event: pimcore.dataobject.postAdd, method: processEvent }
... | ElementEventListener | [
-0.4530704617500305,
-0.13277572393417358,
-0.1647643744945526,
0.15167082846164703,
-0.00016987942217383534,
-0.3235287368297577,
0.31924524903297424,
0.041122570633888245,
0.05356370657682419,
0.12740816175937653,
-0.16125832498073578,
0.39132776856422424,
-0.21148768067359924,
0.3199061... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Extending#workfloweventlistener | WorkflowEventListener
Handles all events based on workflows, e.g. workflow.entered event.
Pimcore\Bundle\DataHubWebhooksBundle\EventListener\WorkflowEventListener:
tags:
- { name: kernel.event_listener, event: workflow.entered, method: processEvent }
- { name: kernel.event_listener, event: workflow.... | WorkflowEventListener | [
-0.3819069266319275,
-0.1656467467546463,
-0.14890612661838531,
0.019078264012932777,
-0.1496877819299698,
-0.35770705342292786,
0.32953205704689026,
0.045638278126716614,
0.17676614224910736,
0.12964488565921783,
-0.16860705614089966,
0.6681602597236633,
-0.28162655234336853,
0.4424601197... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Extending#webhook-processor | Webhook Processor
The webhook processor is responsible for gathering the payload data and sending the request to all subscribers.
Every WebhookProcessor available needs to be based on the WebhookProcessorInterface.
AbstractWebhookProcessor: Provides basic functionalities that are shared between all processors.
Asset... | Webhook Processor | [
0.09947698563337326,
-0.2920887768268585,
-0.045439720153808594,
-0.08143766224384308,
-0.1268444061279297,
-0.12029250711202621,
0.33233675360679626,
0.020696915686130524,
0.050167620182037354,
0.2246297299861908,
-0.24969813227653503,
0.499784380197525,
0.17039085924625397,
0.22359487414... |
https://pimcore.com/docs/platform//Datahub_Webhooks/Extending#webhookprocessorinterface | WebhookProcessorInterface
The three following methods need to be used in your php file for implementing the WebhookProcessorInterface:
WebhookProcessorInterface::fire() - responsible for executing the actual webhook based on the configuration in the Datahub.
WebhookProcessorInterface::matchByEvent() - checks if the... | WebhookProcessorInterface | [
-0.16720660030841827,
-0.40454310178756714,
-0.06827983260154724,
0.05750007927417755,
-0.4017154574394226,
-0.21047692000865936,
0.39884448051452637,
0.13521167635917664,
0.33113619685173035,
0.2511630952358246,
-0.036883629858493805,
0.16554419696331024,
-0.10398954153060913,
0.280653119... |
https://pimcore.com/docs/platform//Datahub_Webhooks#datahub-webhooks | Datahub Webhooks
This extension adds Webhook functionality to Pimcore Datahub for Assets, Documents, Data Objects and workflows, and provides an option for clients to subscribe to events happening within Pimcore.
The requests to the subscribed endpoints can be configured in details for complete control of the shared in... | Datahub Webhooks | [
-0.37648722529411316,
-0.37654781341552734,
-0.1395924687385559,
-0.06259669363498688,
-0.5275974869728088,
-0.11530525982379913,
0.19163376092910767,
0.11230824142694473,
0.05639432370662689,
-0.018381932750344276,
-0.4579017162322998,
0.4823543429374695,
0.029834715649485588,
0.449634879... |
https://pimcore.com/docs/platform//Datahub_Webhooks#features-in-a-nutshell | Features in a Nutshell
Send requests to your configured subscribers for a variation of events such as:
Added, updated and deleted events for all kind of elements (Data Objects, Assets and Documents).
Entered and completed events for workflows.
Configure the payload sent to your subscribers:
Define included element... | Features in a Nutshell | [
0.1838189661502838,
-0.286452978849411,
-0.11261852830648422,
-0.04032698646187782,
-0.22404909133911133,
-0.33883851766586304,
0.12111829966306686,
-0.03132370114326477,
-0.08035904914140701,
0.03770207241177559,
-0.042423199862241745,
0.16379839181900024,
-0.09170567244291306,
0.44403275... |
https://pimcore.com/docs/platform//Datahub_Webhooks#documentation-overview | Documentation Overview
Installation
Configuration
Events and Schema
Workspaces
Subscribers
Example Requests
Extending
| Documentation Overview | [
0.1243174821138382,
-0.003094201209023595,
-0.14251810312271118,
-0.032069891691207886,
-0.22927771508693695,
-0.11341992765665054,
0.21737325191497803,
-0.2186533361673355,
-0.023429445922374725,
0.2519325613975525,
0.13251829147338867,
0.04837458208203316,
0.021676141768693924,
0.1019803... |
https://pimcore.com/docs/platform//Datahub_Webhooks#further-information | Further Information
On other Pimcore Datahub adapters:
Datahub (GraphQL API)
Data Importer
Datahub Simple Rest API
Datahub File Export
Datahub Productsup
Datahub CI Hub
| Further Information | [
-0.3565506935119629,
-0.18730388581752777,
-0.24612359702587128,
-0.12297090888023376,
-0.14060737192630768,
-0.18279504776000977,
0.41265323758125305,
0.15338896214962006,
0.17102093994617462,
0.22364279627799988,
-0.42868104577064514,
0.42446234822273254,
0.15998126566410065,
0.879325032... |
https://pimcore.com/docs/platform//Enterprise_Metadata/Installation/Update#upgrade-information | Upgrade Information
Following steps are necessary during updating to newer versions. | Upgrade Information | [
-0.22016730904579163,
-0.21716107428073883,
-0.18844935297966003,
0.06598692387342453,
0.05852506309747696,
-0.04944508150219917,
0.04977540299296379,
0.07004286348819733,
-0.2696684002876282,
-0.04550585895776749,
-0.05604716017842293,
0.030289839953184128,
0.19013381004333496,
0.06546622... |
https://pimcore.com/docs/platform//Enterprise_Metadata/Installation/Update#upgrade-to-1.1.0 | Upgrade to 1.1.0
Make sure to run all bundle migrations with bin/console pimcore:bundle:migrate -b PimcoreAssetMetadataClassDefinitionsBundle.
| Upgrade to 1.1.0 | [
-0.4569850265979767,
-0.10285022109746933,
-0.15400166809558868,
0.04188849776983261,
0.2527353763580322,
-0.17560741305351257,
0.149154394865036,
0.22669900953769684,
-0.3644838035106659,
0.26959866285324097,
-0.07038114219903946,
0.470653235912323,
-0.008963488973677158,
0.21543213725090... |
https://pimcore.com/docs/platform//Enterprise_Metadata/Installation/Update#upgrade-to-pimcore-x | Upgrade to Pimcore X
Update to latest (allowed) bundle version in Pimcore 6.9 and execute all migrations.
Then update to Pimcore X.
| Upgrade to Pimcore X | [
-0.5807572603225708,
-0.20940947532653809,
-0.1540290266275406,
0.007363408338278532,
0.04493528977036476,
-0.16714733839035034,
0.046648457646369934,
0.2623489201068878,
-0.2353164553642273,
0.23198316991329193,
-0.19107705354690552,
0.5369307398796082,
-0.01311113778501749,
0.18771138787... |
https://pimcore.com/docs/platform//Enterprise_Metadata/Installation#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//Enterprise_Metadata/Installation#minimum-requirements | Minimum Requirements
Pimcore >= 6.7
| Minimum Requirements | [
-0.4841349124908447,
-0.5690585970878601,
-0.2449079304933548,
0.06886682659387589,
-0.08408880233764648,
-0.13660620152950287,
-0.2170119285583496,
0.2113972008228302,
-0.07787146419286728,
0.18828794360160828,
0.04754984751343727,
0.309885710477829,
-0.08823506534099579,
0.09737259894609... |
https://pimcore.com/docs/platform//Enterprise_Metadata/Installation#installation-process | Installation Process | Installation Process | [
0.08020234853029251,
-0.4312822222709656,
-0.29270926117897034,
0.10546649992465973,
-0.1146225556731224,
0.020290104672312737,
-0.026727845892310143,
-0.1865369826555252,
0.10249292105436325,
0.14968742430210114,
-0.0016273048240691423,
0.1121966689825058,
0.1848244071006775,
-0.010504826... |
https://pimcore.com/docs/platform//Enterprise_Metadata/Installation#for-pimcore->=-10.5 | For Pimcore >= 10.5
To install Pimcore Enterprise Asset Metadata for Pimcore 10.5 or higher, follow the three steps below:
Install the required dependencies:
composer require pimcore/asset-metadata-class-definitions
Make sure the bundle is enabled in the config/bundles.php file. The following lines should be add... | For Pimcore >= 10.5 | [
-0.32817208766937256,
0.13399389386177063,
-0.11146090179681778,
0.1249520480632782,
0.14390243589878082,
-0.11603393405675888,
0.11971009522676468,
0.1375531107187271,
-0.3823404610157013,
0.141954243183136,
-0.1509290486574173,
0.5551058650016785,
-0.03173248842358589,
0.1473034620285034... |
https://pimcore.com/docs/platform//Enterprise_Metadata/Installation#for-older-versions | For Older Versions
To install the Enterprise Asset Metadata bundle for older versions of Pimcore, please run the following commands instead:
composer require pimcore/asset-metadata-class-definitions
bin/console pimcore:bundle:enable PimcoreAssetMetadataClassDefinitionsBundle
bin/console pimcore:bundle:install PimcoreAs... | For Older Versions | [
-0.3810518682003021,
0.14143165946006775,
-0.16614173352718353,
0.0672602504491806,
0.1604231894016266,
-0.08417659997940063,
0.21085847914218903,
0.07852204144001007,
-0.31307685375213623,
0.12980049848556519,
-0.05623885989189148,
0.44806841015815735,
-0.04969432204961777,
0.144954055547... |
https://pimcore.com/docs/platform//Enterprise_Metadata/Installation#required-backend-user-permission | Required Backend User Permission
To define Asset metadata class definitions, user needs to meet one of following criteria:
be an admin or
have classes permission
| Required Backend User Permission | [
0.1119164302945137,
0.07003690302371979,
-0.16345281898975372,
0.1404208093881607,
0.02074514888226986,
-0.3978614807128906,
0.5129520893096924,
0.003014800138771534,
-0.1407150775194168,
0.1674039661884308,
0.26106569170951843,
0.17610204219818115,
-0.08325643092393875,
-0.056272793561220... |
https://pimcore.com/docs/platform//Enterprise_Metadata/Technical_Details#technical-details | Technical Details | Technical Details | [
-0.028801435604691505,
-0.7137026190757751,
-0.3666444420814514,
0.2147451490163803,
-0.1116277351975441,
-0.20152825117111206,
0.09879325330257416,
-0.41248559951782227,
-0.43829959630966187,
0.2336549162864685,
-0.1288434863090515,
0.11225755512714386,
0.05166516453027725,
0.276295244693... |
https://pimcore.com/docs/platform//Enterprise_Metadata/Technical_Details#migration-of-existing-data | Migration of existing Data
To add metadata collections to assets based on existing metadata, use following command.
It will check for existing metadata entries if they have a prefix like License.something and then
adds the corresponding collection (in this case License) to the asset.
php bin/console asset-metadata-clas... | Migration of existing Data | [
-0.049586065113544464,
0.2633204758167267,
-0.22499826550483704,
0.04848917946219444,
0.04304972290992737,
-0.04836438596248627,
0.23541900515556335,
0.3815988302230835,
-0.21045653522014618,
-0.171719029545784,
-0.009024364873766899,
0.3656187057495117,
-0.025899644941091537,
-0.215787872... |
https://pimcore.com/docs/platform//Enterprise_Metadata/Technical_Details#assign-collections-to-an-asset-programmatically | Assign collections to an asset programmatically
To assign metadata collections to assets, use the Collections model as follows:
$col = new Pimcore\AssetMetadataClassDefinitionsBundle\Model\Collections();
// assign Asset ID
$col->setAssetId(290);
// or assign Asset directly
$asset = new \Pimcore\Model\Asset();
$asse... | Assign collections to an asset programmatically | [
-0.1853713095188141,
0.4895130395889282,
-0.09629064798355103,
0.1434897631406784,
0.22342969477176666,
0.020123878493905067,
0.1655375361442566,
0.1445283740758896,
-0.534932017326355,
0.11955912411212921,
-0.20840196311473846,
0.5872047543525696,
0.009077014401555061,
-0.2486492693424224... |
https://pimcore.com/docs/platform//Enterprise_Metadata/Technical_Details#get-collections-from-an-asset-programmatically | Get collections from an asset programmatically
$asset = Pimcore\Model\Asset::getById(290);
$collections = \Pimcore\AssetMetadataClassDefinitionsBundle\Model\Collections::getByAssetId($asset->getId());
$collectionNames = $collections->getCollections();
| Get collections from an asset programmatically | [
-0.27654945850372314,
0.2539612948894501,
-0.22015433013439178,
0.5928617715835571,
0.20939259231090546,
0.03733142837882042,
0.17108787596225739,
0.3931787312030792,
-0.5051659941673279,
0.2875651717185974,
-0.41117027401924133,
0.5050234198570251,
-0.007528049871325493,
-0.40324038267135... |
https://pimcore.com/docs/platform//Enterprise_Metadata/Technical_Details#add-a-definition-programmatically | Add a definition programmatically
$configuration = new \Pimcore\AssetMetadataClassDefinitionsBundle\Model\Configuration();
$configuration->setName("License");
$configuration->setPrefix("License");
$configuration->setIcon("/bundles/pimcoreadmin/img/object-icons/02_red.svg");
$pane... | Add a definition programmatically | [
-0.466572105884552,
-0.012918034568428993,
-0.05778001993894577,
0.2314368635416031,
0.166975736618042,
-0.17962591350078583,
0.2536466419696808,
-0.04454388841986656,
-0.3250572979450226,
0.3016926050186157,
0.06236947327852249,
0.44938546419143677,
0.03215135261416435,
0.0413668192923069... |
https://pimcore.com/docs/platform//Enterprise_Metadata#enterprise_metadata | Enterprise_Metadata
| Enterprise_Metadata | [
-0.12577243149280548,
0.03528892621397972,
-0.2633039057254791,
0.291492223739624,
0.1031045913696289,
-0.15802326798439026,
0.3888327181339264,
0.06709347665309906,
-0.015132335014641285,
-0.004166249185800552,
0.10796396434307098,
0.23844894766807556,
-0.2820643484592438,
0.5727739930152... |
https://pimcore.com/docs/platform//Enterprise_Metadata#title:-enterprise-asset-metadata | title: Enterprise Asset Metadata | title: Enterprise Asset Metadata | [
0.07479770481586456,
0.1053762212395668,
-0.3585317134857178,
0.05561113357543945,
0.12937089800834656,
0.09335760772228241,
0.4763640761375427,
0.14411093294620514,
0.016006655991077423,
0.12459371984004974,
0.04495720565319061,
0.19089634716510773,
-0.1587078720331192,
0.1663169115781784... |
https://pimcore.com/docs/platform//Enterprise_Metadata#pimcore-enterprise-asset-metadata | Pimcore Enterprise Asset Metadata
This extension adds Enterprise Asset Metadata. It allows configuring Asset metadata similarly to Data Object class definitions and adds additional data types for Asset metadata to Pimcore. | Pimcore Enterprise Asset Metadata | [
-0.18494032323360443,
-0.13956744968891144,
-0.11442113667726517,
0.10436359792947769,
0.10969340801239014,
0.01388650480657816,
0.12136851251125336,
0.0002880727406591177,
-0.18310843408107758,
0.07069733738899231,
-0.2816620171070099,
0.4125951826572418,
-0.05806037038564682,
0.341170430... |
https://pimcore.com/docs/platform//Enterprise_Metadata#features-in-a-nutshell | Features in a Nutshell
Introduction of Data Objects like visualization of Asset metadata.
Definition of Asset metadata structure in Asset class definitions (similarly to class definitions).
Possibility to assign multiple Asset metadata class definitions to each Asset.
Additional data types like multi-select, many-to-m... | Features in a Nutshell | [
-0.006694273091852665,
-0.3002118766307831,
-0.1679309904575348,
0.310532808303833,
0.15882346034049988,
-0.04722253233194351,
0.07800088822841644,
-0.01635449007153511,
-0.3827904760837555,
0.12654507160186768,
-0.12378112971782684,
0.1946079432964325,
-0.06911717355251312,
0.333501487970... |
https://pimcore.com/docs/platform//Enterprise_Metadata#asset-metadata-definition | Asset Metadata Definition
Required Permission: classes.
See System Permissions for details.
| Asset Metadata Definition | [
-0.07600605487823486,
0.12880925834178925,
-0.16608653962612152,
0.1720326840877533,
0.2112039178609848,
0.010585459880530834,
0.4889656901359558,
0.09201017022132874,
-0.23319266736507416,
0.09049366414546967,
-0.014403860084712505,
0.2873646914958954,
-0.11981689929962158,
-0.34462586045... |
https://pimcore.com/docs/platform//Enterprise_Metadata#asset-metadata-editor | Asset Metadata Editor
| Asset Metadata Editor | [
-0.1186196580529213,
0.08005665242671967,
-0.2844565808773041,
0.08347135037183762,
0.1746513843536377,
-0.07220010459423065,
0.2690722942352295,
0.2463558167219162,
-0.38948434591293335,
0.26749521493911743,
-0.11049146205186844,
0.322986364364624,
-0.3488117456436157,
-0.0363363362848758... |
https://pimcore.com/docs/platform//Enterprise_Metadata#documentation-overview | Documentation Overview
Installation
Technical Details
| Documentation Overview | [
-0.10909582674503326,
-0.5192082524299622,
-0.20288494229316711,
0.09491240233182907,
-0.09869600087404251,
0.011010011658072472,
0.07369623333215714,
-0.2901648283004761,
-0.32741767168045044,
0.09884368628263474,
-0.07169685512781143,
0.16568930447101593,
0.21580208837985992,
0.036801077... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#mercure-setup | Mercure Setup | Mercure Setup | [
-0.3991734981536865,
-0.332731693983078,
-0.12494481354951859,
0.1877817064523697,
0.13555754721164703,
-0.18548937141895294,
0.41818028688430786,
-0.32258981466293335,
0.26383084058761597,
0.36840787529945374,
-0.2675155997276306,
0.07052202522754669,
0.20800305902957916,
0.20344771444797... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#start-and-configure-mercure | Start and Configure Mercure
It is recommended to use an up-to-date instance of Mercure, e.g. via their docker container. For details see
Mercure docs. | Start and Configure Mercure | [
-0.3708210289478302,
-0.20911173522472382,
-0.27752578258514404,
-0.11171229928731918,
0.11264310032129288,
-0.2401784211397171,
0.40935948491096497,
0.008479153737425804,
0.29645994305610657,
0.5140933394432068,
-0.15863633155822754,
0.2195136845111847,
0.013521939516067505,
0.14337562024... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#configuration | Configuration
Following Mercure configuration aspects need to be considered
Add same JWT key to MERCURE_PUBLISHER_JWT_KEY and MERCURE_SUBSCRIBER_JWT_KEY
Activate anonymous to allow Pimcore Admin UI to connect to Mercure
| Configuration | [
-0.16461917757987976,
0.03963838890194893,
0.01732657290995121,
-0.07744994014501572,
0.35922592878341675,
-0.42045339941978455,
0.4046146273612976,
-0.1281122863292694,
0.1984313726425171,
0.24105164408683777,
-0.4658955931663513,
0.43680477142333984,
0.35438233613967896,
0.40761375427246... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#configure-mercure-urls-(optional) | Configure Mercure URLs (optional)
It is possible to configure URLs for accessing Mercure server-side (for updating state information within application
services) and client-side (for getting updates in Pimcore admin interface) via symfony configuration tree as follows:
pimcore_direct_edit:
mercure_settings:
... | Configure Mercure URLs (optional) | [
-0.19931431114673615,
-0.07452580332756042,
0.01591961458325386,
-0.019323214888572693,
0.21361809968948364,
-0.4794822633266449,
0.1909729540348053,
-0.023529693484306335,
0.06166726350784302,
0.3085103929042816,
-0.4197186231613159,
0.5175918340682983,
0.38717007637023926,
0.053088538348... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#example-configuration-with-docker-compose | Example Configuration with docker compose
Following there are configuration snippets for a setup with docker compose.
In that case, Mercure is only exposed via nginx reverse proxy that runs under https. Internal communication runs via
http (which is handy when using self-signed certificates in development context). | Example Configuration with docker compose | [
-0.42758771777153015,
-0.05075749382376671,
-0.15762299299240112,
-0.06631066650152206,
-0.035532813519239426,
-0.4998883605003357,
0.42953240871429443,
-0.19133351743221283,
0.12003573030233383,
0.27776575088500977,
-0.27518337965011597,
0.062355730682611465,
0.4159214198589325,
0.2249766... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#docker-compose.yaml | docker-compose.yaml
Add mercure to your docker compose file and make sure to add the configuration for JWT keys and anonymous directives.
# add here all the other necessary containers...
# configure ngnix to run under https
nginx:
image: nginx:stable-alpine
ports:
- 443:443
depends_on:
-... | docker-compose.yaml | [
-0.2952843904495239,
0.18198689818382263,
-0.15203729271888733,
-0.21071955561637878,
0.08704400062561035,
-0.3232254683971405,
0.28456640243530273,
0.14602167904376984,
0.11751065403223038,
0.3319055438041687,
-0.29726359248161316,
0.255275696516037,
0.1842060536146164,
0.3540754616260528... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#nginx.conf | nginx.conf
Configure reverse proxy in ngnix to route mercure traffic accordingly.
server {
# (...)
location /hub {
proxy_pass http://mercure.local/.well-known;
}
# Thumbnails
# (...)
}
| nginx.conf | [
-0.12822537124156952,
0.016228696331381798,
-0.10330706089735031,
-0.26484420895576477,
-0.02620488591492176,
-0.18708966672420502,
0.15712551772594452,
0.13037244975566864,
0.010207075625658035,
0.19672472774982452,
-0.39934277534484863,
0.3440273404121399,
0.31886568665504456,
0.28465968... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#config.yaml | config.yaml
Configure Pimcore application with JWT key as well as the client side and server side URLs for mercure.
parameters:
mercure:
hub:
jwt_key: '<YOUR_JWT_KEY>'
pimcore_direct_edit:
mercure_settings:
# URL of mercure accessible for client.
client_side_url: ... | config.yaml | [
-0.12437919527292252,
-0.3809863030910492,
0.03386616334319115,
-0.2138046771287918,
0.1865866631269455,
-0.2619381844997406,
0.2668951153755188,
-0.16529782116413116,
0.16816926002502441,
0.14266636967658997,
-0.2814790606498718,
0.5630568861961365,
0.35291412472724915,
0.3272290229797363... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#check-if-mercure-is-running | Check if Mercure is running
To see if Mercure is up and available, call https://your-app-domain.com/hub/.well-known/mercure (or client_side_url
you configured in configuration). This request should return the text
Missing "topic" parameter.
Also execute curl https://your-app-domain.com/hub/.well-known/mercu... | Check if Mercure is running | [
-0.04915555566549301,
-0.42485952377319336,
-0.0780462995171547,
-0.1420380175113678,
0.10719362646341324,
-0.21166378259658813,
0.44050365686416626,
-0.21338695287704468,
0.11817947775125504,
0.2830832898616791,
0.12801024317741394,
0.41085943579673767,
0.22241589426994324,
0.157834857702... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#additional-aspects | Additional Aspects | Additional Aspects | [
-0.2713933289051056,
-0.6477962732315063,
-0.35366424918174744,
-0.12036912888288498,
0.03410140424966812,
-0.0491328239440918,
0.10865748673677444,
-0.16502223908901215,
-0.5326923727989197,
0.2507374584674835,
-0.3109005093574524,
0.1296793669462204,
-0.04814445972442627,
0.2962698340415... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#running-mercure-with-external-url | Running Mercure with external URL
When running Mercure as external service with external URL, make sure to configure CSP properly. | Running Mercure with external URL | [
-0.20965418219566345,
-0.20047502219676971,
-0.05535914748907089,
-0.05883214622735977,
0.29455021023750305,
-0.2830280363559723,
0.33457446098327637,
-0.041853535920381546,
0.29714909195899963,
0.38783323764801025,
-0.22259412705898285,
0.14406812191009521,
0.28232696652412415,
0.15075631... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#pimcore-configuration | Pimcore Configuration
pimcore_admin:
admin_csp_header:
additional_urls:
connect-src:
- 'https://<MERCURE_URL>/.well-known/mercure'
| Pimcore Configuration | [
-0.2818581759929657,
-0.21734105050563812,
-0.056487031280994415,
-0.12916254997253418,
0.20879802107810974,
-0.3462902307510376,
-0.007119443733245134,
-0.009434530511498451,
-0.0930524691939354,
0.08759415149688721,
-0.30027642846107483,
0.2947666049003601,
0.3626982867717743,
0.00350234... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#mercure-configuration | Mercure Configuration
Sample based on docker compose, important part is the cors_origins directive.
mercure.local:
image: dunglas/mercure
restart: unless-stopped
environment:
# All other necessary configs ...
# ...
# Add anomyous directives and cors configuration
MERCURE_EX... | Mercure Configuration | [
-0.33055028319358826,
-0.09112240374088287,
-0.10709221661090851,
-0.19913987815380096,
0.14974167943000793,
-0.525358259677887,
0.45299768447875977,
-0.13236412405967712,
0.0043915328569710255,
0.18618102371692657,
-0.40581852197647095,
0.21841195225715637,
0.2135511189699173,
0.142780765... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#webserver-reverse-proxy | Webserver Reverse Proxy
When you are using Mercure default URLs, you might need to configure a reverse proxy to make sure the Mercure requests are
routed correctly to the Mercure instance.
Also, keep in mind, that communication needs to be HTTPS. Thus, it might be useful to place the Mercure server behind a reverse
pro... | Webserver Reverse Proxy | [
-0.009956249967217445,
-0.0524168536067009,
-0.03590011969208717,
-0.031235190108418465,
0.05347408726811409,
-0.28638023138046265,
0.34553417563438416,
-0.15263716876506805,
0.0649481788277626,
0.26365935802459717,
-0.17198459804058075,
-0.03214959427714348,
0.41779589653015137,
-0.042647... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#apache-reverse-proxy | Apache Reverse Proxy
For apache for example enable http_proxy in apache and add the following reverse proxy in your apache config:
ProxyPass /hub/ http://localhost:3000/
ProxyPassReverse /hub/ http://localhost:3000/
| Apache Reverse Proxy | [
-0.2508985996246338,
-0.2917499840259552,
-0.23466691374778748,
-0.2813377380371094,
-0.14705584943294525,
-0.03828280791640282,
0.039422377943992615,
0.30152085423469543,
0.17971143126487732,
0.06924828141927719,
-0.1293725222349167,
0.07828249037265778,
0.256253719329834,
-0.052658610045... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#nginx-reverse-proxy | Nginx Reverse Proxy
For Nginx use following configuration:
location /hub {
proxy_pass http://localhost:3000/.well-known;
}
| Nginx Reverse Proxy | [
-0.10381438583135605,
-0.22320282459259033,
-0.24242016673088074,
-0.3262788653373718,
0.09011624753475189,
-0.1561381071805954,
0.1341055929660797,
0.26876965165138245,
0.05923903360962868,
0.22393065690994263,
-0.24816027283668518,
0.049891743808984756,
0.3207904100418091,
0.082631975412... |
https://pimcore.com/docs/platform//Direct_Edit/Installation/Mercure_Setup#legacy-fallback | Legacy Fallback
The mercure binary is shipped because of BC reasons only. It is not recommended to use it, is not tested
and thus might not work anymore. It also may contain security vulnerabilities.
As fallback, the bundle ships with an executable of Mercure. To run this Mercure executable, use following command:
./... | Legacy Fallback | [
-0.3274580240249634,
-0.1198766827583313,
0.027583694085478783,
-0.21031060814857483,
-0.127632737159729,
-0.1443750113248825,
0.34675368666648865,
0.010152413509786129,
0.32953932881355286,
0.18222090601921082,
-0.22869379818439484,
0.41342559456825256,
0.14160573482513428,
0.088361561298... |
https://pimcore.com/docs/platform//Direct_Edit/Installation#installation-&-configuration | Installation & Configuration | Installation & Configuration | [
-0.08407901972532272,
-0.5389963388442993,
-0.24936506152153015,
0.2518001198768616,
0.0990651398897171,
0.01379796676337719,
-0.043544329702854156,
-0.26268699765205383,
-0.07168625295162201,
0.09602484107017517,
-0.0895838588476181,
0.10074362903833389,
0.11090346425771713,
0.15462833642... |
https://pimcore.com/docs/platform//Direct_Edit/Installation#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//Direct_Edit/Installation#for-pimcore->=-10.5 | For Pimcore >= 10.5
To install Pimcore Direct Edit for Pimcore 10.5 or higher, follow the three steps below:
Install the required dependencies:
composer require pimcore/direct-edit
Make sure the bundle is enabled in the config/bundles.php file. The following lines should be added:
use Pimcore\Bundle\DirectEditB... | For Pimcore >= 10.5 | [
-0.21518386900424957,
-0.30747830867767334,
-0.1010235846042633,
-0.06650226563215256,
-0.053842831403017044,
-0.14188246428966522,
0.015671128407120705,
-0.00262748752720654,
-0.2890230417251587,
0.1547073870897293,
-0.1841326653957367,
0.6386098265647888,
-0.0825764462351799,
0.230126336... |
https://pimcore.com/docs/platform//Direct_Edit/Installation#for-older-versions | For Older Versions
To install the Direct Edit bundle for older versions of Pimcore, please run the following commands instead:
composer require pimcore/direct-edit
bin/console pimcore:bundle:enable PimcoreDirectEditBundle
bin/console pimcore:bundle:install PimcoreDirectEditBundle
| For Older Versions | [
-0.23314180970191956,
-0.29653266072273254,
-0.15856026113033295,
-0.16339263319969177,
0.008653967641294003,
-0.08696085214614868,
0.1110018864274025,
-0.06086291745305061,
-0.3286016285419464,
0.1698790043592453,
-0.26438748836517334,
0.6397994756698608,
-0.021374400705099106,
0.21958553... |
https://pimcore.com/docs/platform//Direct_Edit/Installation#maintenance-commands | Maintenance Commands
Add the following command to your crontab, to ensure cleanup of inactive tokens after x hours.
~/www/bin/console pimcore:direct-edit:cleanup --hours=x
| Maintenance Commands | [
-0.12011334300041199,
-0.04105810448527336,
-0.17558951675891876,
-0.19629746675491333,
-0.058973364531993866,
-0.2502334713935852,
0.10826754570007324,
0.05432092398405075,
-0.2665497660636902,
0.2793325185775757,
0.10771054774522781,
0.5006347298622131,
-0.06241155043244362,
-0.059735067... |
https://pimcore.com/docs/platform//Direct_Edit/Installation#jwt-key | JWT Key
A valid JWT key is necessary for proper Mercure communication. Currently, Pimcore Direct Edit bundle uses same key for
subscriber and publisher. Use your preferred password generator to create a secure and valid JWT key, which is used
by the application to encrypt JWT tokens and payloads.
Keep the jwt_key priv... | JWT Key | [
0.05005205050110817,
-0.2715906500816345,
0.08549845963716507,
-0.017137613147497177,
0.11964733153581619,
-0.3239661455154419,
0.07321102917194366,
-0.16832870244979858,
0.17768853902816772,
0.36439141631126404,
-0.25943395495414734,
0.37061816453933716,
0.3843018412590027,
0.353940665721... |
https://pimcore.com/docs/platform//Direct_Edit/Installation#mercure-setup | Mercure Setup
The bundle uses Mercure for server-client communication during file editing. Thus, Mercure
needs to be up and running to allow direct file editing.
For Mercure setup instruction, see https://mercure.rocks/docs/hub/install.
The simplest way to setup Mercure is using the docker image and setup a reverse pro... | Mercure Setup | [
-0.20516373217105865,
-0.19941309094429016,
-0.04650302231311798,
-0.10359948873519897,
-0.09100089967250824,
-0.15137936174869537,
0.35615113377571106,
0.017402583733201027,
0.040001243352890015,
0.2806975841522217,
-0.35325053334236145,
0.46139997243881226,
0.1778748333454132,
0.21257571... |
https://pimcore.com/docs/platform//Direct_Edit/Installation#install-pimcore-direct-edit-client | Install Pimcore Direct Edit Client
Install Pimcore Direct Edit client on every device where you want you use the direct edit feature.
To install it, download latest and run the setup:
Windows Installer
MacOS Installer
(ZIP)
| Install Pimcore Direct Edit Client | [
-0.13654381036758423,
-0.4038815200328827,
-0.22360527515411377,
-0.40423402190208435,
0.13627488911151886,
-0.20247013866901398,
0.36286523938179016,
0.028834247961640358,
-0.12038242816925049,
0.26009348034858704,
-0.2738076448440552,
0.3407825231552124,
-0.050492145121097565,
0.21181957... |
https://pimcore.com/docs/platform//Direct_Edit/Installation#compatibility | Compatibility | Compatibility | [
-0.29827648401260376,
-0.5355115532875061,
-0.3468138873577118,
0.2494826465845108,
0.14635387063026428,
-0.1738303154706955,
0.06529161334037781,
0.3433960974216461,
0.18732869625091553,
0.16614265739917755,
-0.052713096141815186,
0.29572594165802,
0.009705880656838417,
0.2179772704839706... |
https://pimcore.com/docs/platform//Direct_Edit/Installation#https-only | HTTPS only
Only webservers running via HTTPS are supported. This also applies to development systems. | HTTPS only | [
-0.3051288425922394,
-0.33409345149993896,
-0.2771559953689575,
-0.06777341663837433,
0.19240599870681763,
-0.23085962235927582,
0.3070842921733856,
-0.005894246511161327,
0.2170819342136383,
0.010568782687187195,
0.15742118656635284,
-0.004904935602098703,
0.1301911324262619,
0.0317554250... |
https://pimcore.com/docs/platform//Direct_Edit/Installation#use-self-signed-certificates | Use self-signed certificates
To allow self-signed certificates to work with the Direct Edit Client, create a file certificate-paths.txt in
tmp folder of the client and add a list of paths to root certificates (one per line)
that should be used for verifying the certificates.
Restart client after changing that file!
| Use self-signed certificates | [
0.10061658173799515,
-0.15929654240608215,
-0.020398449152708054,
-0.06682249903678894,
-0.04733024165034294,
-0.26894617080688477,
0.3814942240715027,
-0.0014892512699589133,
0.013099778443574905,
0.23399347066879272,
0.044893208891153336,
0.32181715965270996,
0.04330857843160629,
0.19016... |
https://pimcore.com/docs/platform//Direct_Edit/Installation#supported-operating-systems-for-desktop-client | Supported Operating Systems for Desktop Client
Windows 10
MacOS
| Supported Operating Systems for Desktop Client | [
-0.3934955894947052,
-0.3736362159252167,
-0.26707080006599426,
-0.1410917192697525,
0.29984429478645325,
-0.09396238625049591,
0.3517550528049469,
0.12582404911518097,
0.2871023416519165,
0.016580859199166298,
-0.2148374617099762,
0.3428114354610443,
-0.19266119599342346,
0.32352104783058... |
https://pimcore.com/docs/platform//Direct_Edit/Installation#browser-compatibility | Browser Compatibility
The application has been tested with the following browsers:
Chrome Version 83.0.4103.106 (Official Build) (32-Bit) ✅
Firefox Browser 77.0.1 (64-bit) ✅
Microsoft Edge Version 83.0.478.54 (Official Build) (64-Bit) ✅
Safari 131.1 (on MacOS) ✅
Chrome Version 83.0.4103.116 (64 Bit) (on MacOS) ✅
| Browser Compatibility | [
-0.3731101155281067,
-0.3328385353088379,
-0.21034123003482819,
-0.12030651420354843,
-0.016539402306079865,
-0.29969140887260437,
0.1894705444574356,
0.18114472925662994,
0.10940482467412949,
0.02660631388425827,
-0.04345165938138962,
0.3285401463508606,
-0.11353699117898941,
0.1316149830... |
https://pimcore.com/docs/platform//Direct_Edit/Pimcore_Direct_Edit_Client#pimcore-direct-edit-client | Pimcore Direct Edit Client
Pimcore Direct Edit Client is a desktop client that is necessary to allow local file edits.
It is an electron application that listens to all direct edit requests and handles all client-side
interactions like downloading assets data, launching the associated application, watching
for changes ... | Pimcore Direct Edit Client | [
0.179123654961586,
-0.16533945500850677,
-0.136977881193161,
-0.16274558007717133,
-0.05642611160874367,
-0.20600610971450806,
0.1688326895236969,
0.02050996571779251,
-0.11817479878664017,
0.17367251217365265,
-0.39663979411125183,
0.4083825945854187,
0.18399149179458618,
0.09315802901983... |
https://pimcore.com/docs/platform//Direct_Edit/Pimcore_Direct_Edit_Client#installation | Installation
To install it, download latest and run the setup:
Windows Installer
MacOS Installer
(ZIP)
The installation process will install the client typically in the user's
C:\Users\youruser\AppData\Local\Programs\pimcore-direct-edit-client\ directory.
A file protocol handler (pimcorefile) will be added to t... | Installation | [
-0.11504000425338745,
-0.15136845409870148,
-0.09846953302621841,
-0.12715092301368713,
-0.241190105676651,
-0.2606678605079651,
0.061590179800987244,
-0.269840270280838,
-0.27933913469314575,
0.22533006966114044,
-0.25014758110046387,
0.5541539788246155,
-0.06655237078666687,
0.1793957203... |
https://pimcore.com/docs/platform//Direct_Edit/Pimcore_Direct_Edit_Client#debugging | Debugging
In C:\Users\<your-user>\AppData\Roaming\Pimcore File Edit Client\logs\main.log you
will find a log file that may be helpful to analyse a running application. | Debugging | [
-0.37646278738975525,
-0.3892940282821655,
-0.12810467183589935,
0.12840807437896729,
0.21403227746486664,
-0.34129032492637634,
0.13479948043823242,
-0.056743521243333817,
-0.31186163425445557,
0.2099081575870514,
0.002385040046647191,
0.1876641809940338,
-0.04602649062871933,
-0.14596733... |
https://pimcore.com/docs/platform//Direct_Edit/Integrate_into_Custom_Application#integrate-direct-edit-button-into-custom-application | Integrate Direct Edit Button into Custom Application | Integrate Direct Edit Button into Custom Application | [
-0.0012068436481058598,
-0.511623203754425,
-0.24167951941490173,
-0.16820448637008667,
-0.006092475261539221,
-0.1763720065355301,
0.09125786274671555,
-0.005138816311955452,
0.4140344262123108,
0.017661606892943382,
-0.234841451048851,
0.44855883717536926,
-0.11292146146297455,
0.2121559... |
https://pimcore.com/docs/platform//Direct_Edit/Integrate_into_Custom_Application#1-create-a-custom-permission-service | 1 Create a custom Permission Service
Create a Permission service that implements the PermissionServiceInterface.
getApplicationPrefix return a unique application prefix.
getUserId return a unique user id
mapPimcoreUserId optionally map to a pimcore user that will be used vor the version files. Return 0 (system-user) if... | 1 Create a custom Permission Service | [
-0.10268102586269379,
0.08457105606794357,
-0.23419736325740814,
-0.15697364509105682,
-0.17289826273918152,
-0.2898668050765991,
0.44296807050704956,
0.13272546231746674,
-0.21225382387638092,
0.27487313747406006,
-0.1628880798816681,
0.29227206110954285,
-0.223016619682312,
-0.0650802403... |
https://pimcore.com/docs/platform//Direct_Edit/Integrate_into_Custom_Application#2-create-a-new-controller-and-implement-routes | 2 Create a new Controller and implement routes
In your Controller you will need to set a prefix and implement the routes. You can simply use the FileEditControllerTrait if you dont need something custom.
Use your Permission Service and inject it
AppBundle\Controller\DirectEdit\FrontendDirectEditController:
... | 2 Create a new Controller and implement routes | [
-0.12168867141008377,
-0.0374624989926815,
-0.15259122848510742,
-0.18838851153850555,
-0.04228213056921959,
-0.2881228029727936,
0.310208797454834,
0.04156152158975601,
-0.10137834399938583,
0.10461578518152237,
-0.17970000207424164,
0.21652743220329285,
-0.06174449622631073,
0.1069901064... |
https://pimcore.com/docs/platform//Direct_Edit/Integrate_into_Custom_Application#use-it-in-the-frontend | Use it in the Frontend
You will need bootstrap and JQuery available in your frontend.
Configure the script by setting a variable:
var pimcoredirectedit = {
routePrefix: '...',
applicationPrefix: '...',
userId: '...'
}
Pass the prefix of your route, your application prefix and the current user id.
Add the j... | Use it in the Frontend | [
-0.2883533537387848,
-0.1327713578939438,
-0.1696285754442215,
-0.34021762013435364,
0.10966749489307404,
-0.4227112829685211,
0.42403683066368103,
-0.0668603777885437,
-0.3364991843700409,
0.008689207024872303,
0.03651000186800957,
0.541809618473053,
0.02820625528693199,
0.347366094589233... |
https://pimcore.com/docs/platform//Direct_Edit#direct_edit | Direct_Edit
| Direct_Edit | [
0.2589758038520813,
-0.6699838638305664,
-0.2755243480205536,
-0.08459930121898651,
0.05521474406123161,
-0.10489895194768906,
0.15481863915920258,
0.08846188336610794,
0.006717940792441368,
0.04233962669968605,
-0.25408709049224854,
0.21231144666671753,
-0.048389799892902374,
0.2554809451... |
https://pimcore.com/docs/platform//Direct_Edit#title:-direct-edit | title: Direct Edit | title: Direct Edit | [
0.5337197780609131,
-0.3865639269351959,
-0.33151939511299133,
-0.2638144791126251,
0.06198817864060402,
-0.01911749131977558,
0.18438667058944702,
-0.13153666257858276,
0.10294835269451141,
0.17868471145629883,
-0.13071666657924652,
0.18873879313468933,
-0.08938378095626831,
0.14574815332... |
https://pimcore.com/docs/platform//Direct_Edit#pimcore-direct-edit | Pimcore Direct Edit
Pimcore Direct Edit allows you editing Pimcore Assets locally in your preferred editor and upload them right away back to Pimcore. | Pimcore Direct Edit | [
-0.07988189905881882,
-0.1362595558166504,
-0.24989400804042816,
-0.3039941191673279,
-0.08449971675872803,
-0.15620382130146027,
-0.0011675746645778418,
0.013209695927798748,
-0.3707379698753357,
0.10914357006549835,
-0.41299566626548767,
0.5033534169197083,
0.06512817740440369,
0.3553314... |
https://pimcore.com/docs/platform//Direct_Edit#features-in-a-nutshell | Features in a Nutshell
This extension consists of two parts:
The Pimcore Direct Edit Bundle needs to be installed into Pimcore and provides all the necessary server-side features like:
New button in the Asset detail page for starting local editing.
APIs for Pimcore Direct Edit Client to download or re-upload Asset.
... | Features in a Nutshell | [
-0.07231064140796661,
-0.3967582583427429,
-0.17344973981380463,
-0.14158794283866882,
-0.34208863973617554,
-0.020229410380125046,
0.25790566205978394,
0.08824139833450317,
-0.25226566195487976,
0.193763867020607,
-0.22117970883846283,
0.5272237062454224,
-0.02239985391497612,
0.260547071... |
https://pimcore.com/docs/platform//Direct_Edit#sample-screenshots | Sample Screenshots | Sample Screenshots | [
-0.06957903504371643,
-0.7448546290397644,
-0.38956040143966675,
0.19074846804141998,
-0.18730346858501434,
-0.03116479702293873,
0.18209485709667206,
0.14241550862789154,
-0.17040811479091644,
0.27986299991607666,
0.006960348691791296,
0.10540270805358887,
0.20186689496040344,
0.007883513... |
https://pimcore.com/docs/platform//Direct_Edit#open-edit-button-in-asset-detail-page | Open Edit Button in Asset detail page
| Open Edit Button in Asset detail page | [
-0.05676337704062462,
-0.18249109387397766,
-0.3117363452911377,
-0.05466369166970253,
-0.1758209466934204,
0.0010066457325592637,
0.3236478269100189,
0.2572365701198578,
-0.249309703707695,
0.07482762634754181,
-0.15616413950920105,
0.3365734815597534,
0.10974157601594925,
0.1785745322704... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.