url stringlengths 50 196 | text stringlengths 3 17.2k | heading stringlengths 2 103 | embeddings list |
|---|---|---|---|
https://pimcore.com/docs/platform//Headless_Documents/Configuration#configuration | Configuration
By default, headless template and brick configurations are stored in Symfony config yaml files (under var/config/headless_templates & var/config/headless_bricks). It is also possible to store these configurations in settingsStore(database layer). | Configuration | [
-0.10525809228420258,
-0.2936204671859741,
-0.028640389442443848,
0.09843761473894119,
-0.050155095756053925,
0.0966774970293045,
0.47420915961265564,
-0.08575570583343506,
0.3284386396408081,
0.17920245230197906,
-0.2157503217458725,
-0.013675777241587639,
0.12983979284763336,
-0.21119388... |
https://pimcore.com/docs/platform//Headless_Documents/Configuration#example-config-for-template-and-brick-are: | Example Config for Template and Brick Are:
pimcore_headless_documents:
config_location:
headless_templates:
write_target:
type: 'symfony-config'
options:
directory: '/var/www/html/var/config/headless_templates'
pimcore_headless_documents:
... | Example Config for Template and Brick Are: | [
-0.3505258858203888,
-0.31402161717414856,
0.09389402717351913,
-0.03896990790963173,
0.20230348408222198,
-0.011797593906521797,
0.3782729208469391,
0.14385955035686493,
0.18387162685394287,
-0.1246163472533226,
-0.454649418592453,
0.29874685406684875,
0.22453762590885162,
-0.044324882328... |
https://pimcore.com/docs/platform//Headless_Documents/Configuration#grouping | Grouping
It is possible to group configurations on editing interface with group property as follows:
pimcore_headless_documents:
templates:
test:
group: Test
layout: simple
...
pimcore_headless_documents:
bricks:
area1:
group: Test
typ... | Grouping | [
-0.6102478504180908,
-0.3996219038963318,
-0.059181470423936844,
0.021143697202205658,
-0.04802212491631508,
0.06375814974308014,
0.561555802822113,
0.34907302260398865,
-0.11620324850082397,
0.22802560031414032,
-0.5709678530693054,
0.5840144157409668,
0.08736564218997955,
0.0673153400421... |
https://pimcore.com/docs/platform//Headless_Documents/Configuration#custom-views-&-perspective | Custom Views & Perspective
Just like other document types, you can hide/show headless documents from context menu in perspectives custom view with following configuration:
[
'treetype' => 'document',
'name' => 'Basic Examples',
...
'treeContextMenu' => [
'document' => [
... | Custom Views & Perspective | [
-0.167971670627594,
-0.12899306416511536,
-0.1333426535129547,
0.16706715524196625,
-0.2588194012641907,
-0.028583884239196777,
0.15467557311058044,
0.47025203704833984,
-0.08854207396507263,
0.14593902230262756,
-0.1509115844964981,
0.21581228077411652,
0.04679751768708229,
-0.13957709074... |
https://pimcore.com/docs/platform//Headless_Documents/Headless_Documents#headless-documents | Headless Documents
A Headless document type represents a typical web-page, which can be rendered only in Admin UI. The content structure is defined by the template configuration, which defines the layout and editables to be rendered on the document.
This Headless Document is purely based on template configuration to re... | Headless Documents | [
-0.03685375303030014,
-0.6144421100616455,
0.03797219321131706,
-0.05795273557305336,
0.08801694959402084,
0.08492514491081238,
0.07275502383708954,
0.26759594678878784,
0.13944938778877258,
0.019282396882772446,
0.04601661115884781,
0.08460330963134766,
0.2801520526409149,
-0.140088766813... |
https://pimcore.com/docs/platform//Headless_Documents/Headless_Documents#template-configuration-interface: | Template Configuration Interface:
Once the template configuration is ready, the next step is to add a headless document and select the template in document settings.
Save And Reload:
| Template Configuration Interface: | [
-0.25280269980430603,
-0.4017007648944855,
-0.05599692463874817,
-0.34159019589424133,
-0.052729204297065735,
0.019808530807495117,
0.1350923627614975,
0.11411845684051514,
0.013529234565794468,
0.2752809226512909,
0.04891626909375191,
0.2879095673561096,
0.1805511862039566,
0.066738359630... |
https://pimcore.com/docs/platform//Headless_Documents/Headless_Bricks#headless-bricks | Headless Bricks
Headless Bricks are extension of Pimcore area-bricks, with an exception that you don't need to define a brick class implementing AreabrickInterface to register brick on the system and use it on the document. Instead, just define brick structure on Symfony Configuration either in var/config/headless_bric... | Headless Bricks | [
-0.20098848640918732,
-0.11290290951728821,
0.02350560948252678,
0.044851548969745636,
-0.09015168994665146,
-0.06852525472640991,
0.728411078453064,
0.1869395673274994,
0.48626139760017395,
0.254279226064682,
-0.20284795761108398,
0.27863410115242004,
-0.04969293996691704,
-0.205760180950... |
https://pimcore.com/docs/platform//Headless_Documents/Headless_Bricks#brick-configuration-interface: | Brick Configuration Interface:
Bricks configuration example:
var/config/headless_bricks/teasers.yaml
pimcore_headless_documents:
bricks:
teasers:
type: brick
items:
teaser_1:
type: snippet
teaser_2:
type: snippe... | Brick Configuration Interface: | [
-0.3751775622367859,
-0.37707966566085815,
-0.09022807329893112,
0.15124166011810303,
0.1074947640299797,
0.20324257016181946,
0.5591727495193481,
0.17478205263614655,
0.2681615352630615,
0.1632135808467865,
-0.09910891205072403,
0.4110819697380066,
-0.009431721642613411,
-0.10547232627868... |
https://pimcore.com/docs/platform//Headless_Documents#headless_documents | Headless_Documents
| Headless_Documents | [
-0.2692309319972992,
-0.046197403222322464,
-0.09268946200609207,
-0.041208233684301376,
-0.07757147401571274,
0.08245107531547546,
0.296549916267395,
0.51068115234375,
0.009593211114406586,
0.21032686531543732,
0.3234715759754181,
-0.004028310067951679,
-0.14728429913520813,
-0.3934557437... |
https://pimcore.com/docs/platform//Headless_Documents#title:-headless-documents | title: Headless Documents | title: Headless Documents | [
0.1339602768421173,
0.05014978349208832,
-0.13000132143497467,
-0.2793784439563751,
-0.12466803938150406,
0.2249707132577896,
0.36291688680648804,
0.2801077663898468,
0.10288666933774948,
0.3599948287010193,
0.36572980880737305,
-0.01478640828281641,
-0.11862581968307495,
-0.54741561412811... |
https://pimcore.com/docs/platform//Headless_Documents#pimcore-headless-documents | Pimcore Headless Documents
This extension adds a new Document type "Headless Document" for managing website data in a headless manner. It means, you don't have to work with view template files for managing unstructured data of a website. | Pimcore Headless Documents | [
-0.22064347565174103,
-0.29804959893226624,
-0.13454961776733398,
-0.24928738176822662,
-0.015431881882250309,
0.08230970799922943,
0.057912491261959076,
0.48737552762031555,
-0.056808557361364365,
0.04240746051073074,
-0.29060128331184387,
0.34602317214012146,
-0.20980554819107056,
0.1252... |
https://pimcore.com/docs/platform//Headless_Documents#features-in-a-nutshell | Features in a Nutshell
Headless Document is rendered only in Admin UI, based on the template configuration provided in the Document settings.
Template configuration can be yaml file, stored in default location var/config/headless_templates or in settings store database layer.
Possibility to use Pimcore inbuilt & ... | Features in a Nutshell | [
-0.20465773344039917,
-0.4715932309627533,
-0.10967112332582474,
-0.03635862469673157,
0.0076205232180655,
0.08471183478832245,
0.19873467087745667,
0.1609007567167282,
0.07610058784484863,
0.08043394982814789,
-0.11502131819725037,
0.4280301034450531,
0.20819132030010223,
0.17113822698593... |
https://pimcore.com/docs/platform//Headless_Documents#documentation-overview | Documentation Overview
Installation
Headless Documents
Headless Bricks
Layouts
Adding a Custom Layout
Configuration
| Documentation Overview | [
-0.2554321587085724,
-0.31913018226623535,
-0.11244168132543564,
-0.00975734181702137,
-0.12692153453826904,
0.35490408539772034,
0.48342862725257874,
0.04172763600945473,
0.1532246172428131,
0.09046760201454163,
-0.18747764825820923,
0.11626773327589035,
0.07754189521074295,
-0.1198905780... |
https://pimcore.com/docs/platform//OpenID_Connect/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//OpenID_Connect/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//OpenID_Connect/Installation#for-pimcore->=-10.5 | For Pimcore >= 10.5
To install Pimcore OpenID Connect for Pimcore 10.5 or higher, follow the three steps below:
Install the required dependencies:
composer require pimcore/openid-connect
Make sure the bundle is enabled in the config/bundles.php file. The following lines should be added:
use Pimcore\Bundle\OpenI... | For Pimcore >= 10.5 | [
-0.45877453684806824,
0.05520184710621834,
-0.06241416558623314,
-0.05123913288116455,
-0.042371589690446854,
-0.23474547266960144,
0.23306415975093842,
0.017177781090140343,
-0.18446260690689087,
0.03634200245141983,
-0.1471174955368042,
0.45003676414489746,
0.3183525800704956,
0.15547153... |
https://pimcore.com/docs/platform//OpenID_Connect/Installation#for-older-versions | For Older Versions
To install the OpenID Connect bundle for older versions of Pimcore, please run the following commands instead:
composer require pimcore/openid-connect
bin/console pimcore:bundle:enable PimcoreOpenIdConnectBundle
bin/console pimcore:bundle:install PimcoreOpenIdConnectBundle
| For Older Versions | [
-0.5592061877250671,
0.07385101914405823,
-0.11660777777433395,
-0.07887430489063263,
-0.014234687201678753,
-0.21139810979366302,
0.290882408618927,
-0.047839950770139694,
-0.20404280722141266,
0.0686977431178093,
-0.1711897999048233,
0.3895384669303894,
0.2618178129196167,
0.123317845165... |
https://pimcore.com/docs/platform//OpenID_Connect/Installation#possible-configuration-clashes | Possible Configuration Clashes
The route pimcore_openidconnect_buttoninjection_script needs to be accessible publicly for the Pimcore public domain
for the login buttons to show up.
If other modules or implementations add additional firewall configurations, make sure the route is still public accessible.
For example, w... | Possible Configuration Clashes | [
-0.20985405147075653,
-0.19408516585826874,
0.03575070574879646,
0.047835927456617355,
0.10056287050247192,
-0.32984480261802673,
0.6582292914390564,
-0.0795254036784172,
0.03721976280212402,
0.05992269888520241,
-0.2160634845495224,
0.14914025366306305,
0.3435506820678711,
0.1628784388303... |
https://pimcore.com/docs/platform//OpenID_Connect/Configuration#configuration | Configuration
Configuration takes places in configuration files or can be applied directly in Pimcore
backend userinterface.
| Configuration | [
-0.21948114037513733,
-0.2298651486635208,
-0.21673527359962463,
-0.24673056602478027,
0.09394658356904984,
-0.28485673666000366,
0.18579015135765076,
-0.28854963183403015,
-0.3428189754486084,
0.4439983367919922,
-0.2421189844608307,
0.28438514471054077,
0.30878734588623047,
0.24706913530... |
https://pimcore.com/docs/platform//OpenID_Connect/Configuration#configuration-options | Configuration Options | Configuration Options | [
-0.27143460512161255,
-0.7654924988746643,
-0.3034636974334717,
0.02972421795129776,
0.2190430760383606,
0.023244395852088928,
0.2333752065896988,
-0.14333032071590424,
-0.26916584372520447,
0.3120940029621124,
-0.12152465432882309,
0.1505872905254364,
-0.08230088651180267,
0.2361281514167... |
https://pimcore.com/docs/platform//OpenID_Connect/Configuration#providers | Providers
It is possible to configure multiple OpenID Connect providers in parallel. For each provider
and separate login button will be displayed on Pimcore login page. This login button
redirects to OpenID Connect provider and starts the OpenID flow.
Each provider has to have a unique name.
On provider side, you norm... | Providers | [
-0.3336394429206848,
-0.034632012248039246,
-0.0235705878585577,
0.028285646811127663,
0.024371961131691933,
-0.32990047335624695,
0.3743055462837219,
-0.21293504536151886,
-0.2627216875553131,
0.0016078900080174208,
-0.32866522669792175,
0.20518256723880768,
0.4695209264755249,
0.46484372... |
https://pimcore.com/docs/platform//OpenID_Connect/Configuration#default-provider | Default Provider
Optionally it is possible to configure a default provider with its name. Once set, Pimcore automatically
redirects to the providers login page (or directly logs in the current user) instead of redirecting to the
Pimcore login page.
If default provider is set, it is still possible to open Pimcore login ... | Default Provider | [
-0.2417633980512619,
-0.2202615886926651,
0.06771943718194962,
-0.2671559154987335,
0.07974877953529358,
-0.32854700088500977,
0.21209535002708435,
-0.30025750398635864,
-0.3396031856536865,
0.16960525512695312,
-0.06530339270830154,
0.23201704025268555,
0.25780779123306274,
0.186229884624... |
https://pimcore.com/docs/platform//OpenID_Connect/Configuration#configuration-storage | Configuration Storage
The configuration user interface utilizes the LocationAwareConfigRepository for storing the configuration. In the symfony tree the
storage location can be configured, possible values are
symfony-config - write configs as Symfony Config as YAML files to /var/config/oidc/pimcore_open_id_connect.ya... | Configuration Storage | [
-0.32778146862983704,
-0.038566526025533676,
0.01624133065342903,
0.02302052080631256,
0.027129223570227623,
-0.15999945998191833,
0.29689544439315796,
-0.14195597171783447,
-0.1822977066040039,
0.12126940488815308,
-0.40015584230422974,
0.17936432361602783,
0.36858299374580383,
0.12605062... |
https://pimcore.com/docs/platform//OpenID_Connect/Configuration#example | Example
pimcore_open_id_connect:
config_location:
open_id_connect:
write_target:
type: 'symfony-config'
options:
directory: '/var/www/html/var/config/oidc'
Additionally, it is also possible to define the configuration directly in a symfony con... | Example | [
-0.42010778188705444,
-0.12855754792690277,
0.071614570915699,
-0.15631113946437836,
0.09538619965314865,
-0.16714462637901306,
0.2849569618701935,
-0.04795629158616066,
0.12995481491088867,
0.08134894073009491,
-0.4210207462310791,
0.34432098269462585,
0.28321173787117004,
0.2017093300819... |
https://pimcore.com/docs/platform//OpenID_Connect/Configuration#sample-configuration-file | Sample Configuration File
pimcore_open_id_connect:
default_provider: onelogin
providers:
onelogin:
client_id: <CLIENT_ID>
client_secret: <CLIENT_SECRET>
url_discovery: https://<USERNAME>.onelogin.com/oidc/2/.well-known/openid-configuration
o... | Sample Configuration File | [
-0.3145928382873535,
-0.18802647292613983,
-0.02793862670660019,
-0.08325789868831635,
0.10771515220403671,
-0.19904440641403198,
0.3683849275112152,
0.0347035713493824,
-0.11050254106521606,
0.14551712572574615,
-0.20091983675956726,
0.14017675817012787,
0.4801939129829407,
0.307933390140... |
https://pimcore.com/docs/platform//OpenID_Connect/Configuration#debugging | Debugging
The bundle provides a debug window for setting up the OpenId Connect integrations. It is located in the settings menu of
the toolbar in the users sub menu. The debug window lists all the configured providers, allows to send test sign-on
requests and see the response of the providers in order to setup the clai... | Debugging | [
-0.3850618898868561,
0.01831023022532463,
0.011037295684218407,
0.09580975770950317,
-0.199974924325943,
0.1501374989748001,
0.35857751965522766,
0.07228106260299683,
0.029360726475715637,
-0.020272620022296906,
0.0625496432185173,
0.16656626760959625,
0.42508354783058167,
0.06803120672702... |
https://pimcore.com/docs/platform//OpenID_Connect/Technical_Detail_Aspects#technical-detail-aspects | Technical Detail Aspects
Following aspects might be important to know in order to better understand how the integration works. | Technical Detail Aspects | [
-0.0822385624051094,
-0.43409302830696106,
-0.3260745704174042,
-0.191507488489151,
-0.23131448030471802,
-0.2986864149570465,
0.03492632508277893,
-0.5066585540771484,
0.16582004725933075,
0.2321636974811554,
-0.06350965052843094,
0.25072067975997925,
0.13017889857292175,
0.37468284368515... |
https://pimcore.com/docs/platform//OpenID_Connect/Technical_Detail_Aspects#user-mapping | User Mapping
For each SSO user, also a Pimcore user is created. As username the prefered_username field of the OpenID Connect
standard is used.
After every SSO login, Pimcore checks if the corresponding user already exists. If not, it creates a new user in the
oidc folder, sets a random default password and assings rol... | User Mapping | [
0.22149057686328888,
-0.030549364164471626,
-0.11857139319181442,
0.014357703737914562,
-0.18780988454818726,
-0.36972469091415405,
0.25336650013923645,
-0.4122351408004761,
0.026857225224375725,
0.21249721944332123,
-0.41662365198135376,
0.19035907089710236,
0.3677409887313843,
0.22491846... |
https://pimcore.com/docs/platform//OpenID_Connect/Technical_Detail_Aspects#role-mapping | Role Mapping
Every SSO user is assigned to roles if they are delivered by the OpenID Connect provider and if the corresponding role
exists in Pimcore (matched by its name).
The users roles are updated after every login of the user. | Role Mapping | [
0.20371665060520172,
0.022569362074136734,
-0.11446844041347504,
-0.10245981812477112,
-0.09839357435703278,
-0.3124995827674866,
0.34612587094306946,
-0.3439888656139374,
-0.006680953316390514,
0.1411704123020172,
-0.35784855484962463,
0.03827325254678726,
0.6378026008605957,
0.4597766101... |
https://pimcore.com/docs/platform//OpenID_Connect/Technical_Detail_Aspects#configuration-caching | Configuration Caching
Configuration (via the discovery endpoint) and cerfitication information is cached for every OpenID Connect provider
for 24h.
To clear this cache, clear the Pimcore cache with the tag oidc (e.g. via bin/console pimcore:cache:clear --tags=oidc). | Configuration Caching | [
-0.38752102851867676,
0.06557276099920273,
-0.03319737687706947,
0.03483586758375168,
0.03192392364144325,
-0.3041174113750458,
0.4089204668998718,
-0.05128224566578865,
-0.15881958603858948,
0.009715653024613857,
-0.19061671197414398,
0.18226128816604614,
0.5381081700325012,
0.19090984761... |
https://pimcore.com/docs/platform//OpenID_Connect/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//OpenID_Connect/Upgrade_Notes#1.1.0 | 1.1.0
[Plugins] Replaced plugins backend UI with JS event listener.
[Session] Replaced SessionConfigurator with OpenSessionBagListener and added related deprecation triggers.
[Session] Deprecated Configurator::SESSION_BAG_NAME, use OpenSessionBagListener::SESSION_BAG_NAME instead.
[Session] Replaced usage of deprecate... | 1.1.0 | [
-0.26537439227104187,
-0.18755917251110077,
-0.047253839671611786,
0.05737895518541336,
0.08387614786624908,
-0.3129168152809143,
0.09387438744306564,
0.3789612352848053,
-0.24941280484199524,
0.13426095247268677,
-0.19750379025936127,
0.33848077058792114,
0.03374120593070984,
0.1387299150... |
https://pimcore.com/docs/platform//OpenID_Connect#openid_connect | OpenID_Connect
| OpenID_Connect | [
-0.50173020362854,
-0.046810295432806015,
-0.13867133855819702,
0.03705938160419464,
0.11163977533578873,
-0.38286691904067993,
0.480751633644104,
0.03497478738427162,
0.11803264170885086,
-0.1853601187467575,
-0.035388316959142685,
-0.0047186799347400665,
0.4954685568809509,
0.42884123325... |
https://pimcore.com/docs/platform//OpenID_Connect#title:-openid-connect | title: OpenID Connect | title: OpenID Connect | [
-0.23035788536071777,
0.06471240520477295,
-0.21941566467285156,
-0.17608462274074554,
0.04176933690905571,
-0.12933000922203064,
0.47544416785240173,
-0.09888225048780441,
0.19097882509231567,
-0.11987614631652832,
-0.05399153009057045,
-0.003196392208337784,
0.37470367550849915,
0.344016... |
https://pimcore.com/docs/platform//OpenID_Connect#pimcore-openid-connect | Pimcore OpenID Connect
Pimcore OpenID Connect allows to configure SSO for Pimcore backend login with
an OpenID Connect provider.
Sample OpenID Connect provider | Pimcore OpenID Connect | [
-0.5137770175933838,
-0.07752075046300888,
-0.08584052324295044,
-0.34752357006073,
0.002534867962822318,
-0.37081071734428406,
0.49015891551971436,
-0.10636115819215775,
-0.18863549828529358,
-0.0016121469670906663,
-0.13994385302066803,
0.154798224568367,
0.5119727849960327,
0.6226261854... |
https://pimcore.com/docs/platform//OpenID_Connect#features-in-a-nutshell | Features in a Nutshell
Configure one or multiple OpenID Connect providers to Pimcore backend login.
Optionally hide Pimcore login screen and directly redirect to default provider.
| Features in a Nutshell | [
-0.37169986963272095,
-0.18748626112937927,
-0.07842914015054703,
-0.203579843044281,
-0.006803069729357958,
-0.31768983602523804,
0.4072498083114624,
-0.2756514549255371,
-0.18151891231536865,
-0.004543299321085215,
-0.2014651745557785,
0.2544250190258026,
0.4110681712627411,
0.4908052086... |
https://pimcore.com/docs/platform//OpenID_Connect#documentation-overview | Documentation Overview
Installation
Configuration
Technical Aspects
Upgrade Notes
| Documentation Overview | [
-0.1142040491104126,
-0.3753119111061096,
-0.232757106423378,
-0.05254634842276573,
0.05940074473619461,
0.159539595246315,
-0.07761038094758987,
-0.20577894151210785,
-0.40011709928512573,
-0.0027171410620212555,
-0.01130445022135973,
0.15263889729976654,
0.07836171239614487,
0.1570688039... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration/Configuration#configuration | Configuration
Configuration takes places in configuration files or can be applied directly in Pimcore
backend userinterface.
| Configuration | [
-0.21948114037513733,
-0.2298651486635208,
-0.21673527359962463,
-0.24673056602478027,
0.09394658356904984,
-0.28485673666000366,
0.18579015135765076,
-0.28854963183403015,
-0.3428189754486084,
0.4439983367919922,
-0.2421189844608307,
0.28438514471054077,
0.30878734588623047,
0.24706913530... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration/Configuration#configuration-storage | Configuration Storage
The configuration user interface utilizes the LocationAwareConfigRepository for storing the configuration.
In the symfony tree the storage location can be configured, possible values are
symfony-config - write configs as Symfony Config as YAML files to /var/config/translations-provider
setting... | Configuration Storage | [
-0.15910513699054718,
0.018399842083454132,
-0.0362493172287941,
0.0749729573726654,
0.22118531167507172,
-0.16030067205429077,
0.1704784631729126,
-0.1327635496854782,
-0.36498671770095825,
0.33182331919670105,
-0.24914653599262238,
0.08510109037160873,
0.2961619794368744,
-0.016278445720... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration/Configuration#example | Example
pimcore_translations_provider_interface:
config_location:
translations_provider_interface:
write_target:
type: 'symfony-config'
options:
directory: '/var/www/html/var/config/translations-provider'
Additionally, it is also possible to de... | Example | [
-0.30807021260261536,
0.1344534456729889,
0.011500909924507141,
-0.0726005956530571,
0.17825323343276978,
-0.2571934461593628,
0.25427481532096863,
-0.04092680290341377,
-0.2861383855342865,
0.34734046459198,
-0.07028306275606155,
0.34300243854522705,
0.2560374438762665,
-0.039680514484643... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration/Commands#important-commands | Important Commands
Following commands are provided by the bundle.
Most of them need to be executed on regular base (depending on use case) via cron jobs. There is no
automatic execution.
| Important Commands | [
-0.08649805933237076,
-0.3075275123119354,
-0.15602701902389526,
-0.09526994079351425,
-0.0624677911400795,
0.13938337564468384,
0.1704953908920288,
-0.09935814887285233,
-0.15167173743247986,
0.16709250211715698,
0.15578918159008026,
0.3801959455013275,
-0.17535458505153656,
0.06002419441... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration/Commands#create-a-translation-job | Create a translation job
This scans the translations_interface_bundle__data_changed table for
modifications and prepares translation jobs suitable for transmission to the translation provider.
php bin/console translations-provider-interface-bundle:jobs -c
Generated jobs can be found in the translations_interface_bundl... | Create a translation job | [
-0.19280055165290833,
0.3746948540210724,
-0.2121741771697998,
0.08922787755727768,
0.009633048437535763,
-0.24301128089427948,
0.2819277048110962,
0.02739505097270012,
-0.26918289065361023,
0.4509258270263672,
0.24560391902923584,
0.16228662431240082,
0.11378291249275208,
-0.0579752996563... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration/Commands#submit-a-job | Submit a job
Process the open jobs and submit them for translation.
php bin/console translations-provider-interface-bundle:jobs -o
| Submit a job | [
-0.19398654997348785,
0.26397445797920227,
-0.311856210231781,
0.03879518806934357,
0.011294164694845676,
-0.2270866483449936,
0.2505071461200714,
-0.018596433103084564,
-0.27344509959220886,
0.29356101155281067,
0.1473941206932068,
-0.03677685558795929,
0.1878199726343155,
0.0800506547093... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration/Commands#receive-the-translation | Receive the translation
This will fetch the translation if already available.
php bin/console translations-provider-interface-bundle:jobs -s
The completed translation will be stored again in the translations_interface_bundle__jobs
table but not processed until the following command is executed. | Receive the translation | [
-0.25765883922576904,
0.18139886856079102,
-0.2621026039123535,
0.05074680969119072,
-0.05708659067749977,
-0.10192091763019562,
0.09512089192867279,
-0.044466037303209305,
-0.27749499678611755,
0.44834837317466736,
0.2016228437423706,
0.036180656403303146,
0.13843445479869843,
-0.03899181... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration/Commands#process-the-received-translation | Process the received translation
This will process the translations and update the Pimcore objects accordingly.
php bin/console translations-provider-interface-bundle:jobs -r
| Process the received translation | [
-0.24691453576087952,
0.17146921157836914,
-0.20415279269218445,
0.1273811310529709,
-0.0380975641310215,
-0.3637581765651703,
0.0314684696495533,
-0.08474427461624146,
-0.4690399765968323,
0.3560550808906555,
0.009600704535841942,
0.2919948399066925,
0.33445650339126587,
0.125524774193763... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration/Commands#reset-failed-jobs | Reset failed jobs
Reset all jobs to the state they had before the error.
php bin/console translations-provider-interface-bundle:jobs -f
Maximum failing attempts can be configured via config
pimcore_translations_provider_interface:
settings:
error_threshold: 4 # default 10
| Reset failed jobs | [
-0.4166845381259918,
0.1567031294107437,
-0.15954862534999847,
-0.16482728719711304,
0.05245615541934967,
-0.4851929843425751,
0.3389008045196533,
-0.011532952077686787,
-0.30467456579208374,
0.4176172614097595,
0.18238477408885956,
0.10834523290395737,
0.1803915798664093,
-0.0486011691391... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration/Commands#checking-for-redeliveries | Checking for redeliveries
A Project director user can re-open an already delivered translation job an change the translation.
Use the following command to check for redeliveries.
php bin/console translations-provider-interface-bundle:jobs --check-redeliveries
Jobs not older that 60 days will be checked for updates. Yo... | Checking for redeliveries | [
-0.29973694682121277,
0.3816860020160675,
-0.1989544928073883,
-0.013891479931771755,
-0.0035303770564496517,
-0.5090251564979553,
0.12978923320770264,
-0.18976333737373352,
-0.38586005568504333,
0.521719217300415,
0.22366750240325928,
0.15377016365528107,
0.229026660323143,
-0.09699957072... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration#installation-and-configuration | Installation and Configuration | Installation and Configuration | [
-0.032902296632528305,
-0.4798862338066101,
-0.26170942187309265,
0.2767668664455414,
0.11351562291383743,
0.03320053592324257,
-0.016319455578923225,
-0.239933043718338,
-0.06732313334941864,
0.11178846657276154,
-0.10553950071334839,
0.12544715404510498,
0.07521870732307434,
0.1444275826... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration#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//Translation_Provider_Interfaces/Installation_and_Configuration#for-pimcore->=-10.5 | For Pimcore >= 10.5
To install Pimcore Translations Provider Interfaces for Pimcore 10.5 or higher, follow the three steps below:
Install the required dependencies:
composer require pimcore/translations-provider-interfaces
Make sure the bundle is enabled in the config/bundles.php file. The following lines should... | For Pimcore >= 10.5 | [
-0.30621078610420227,
0.10986369848251343,
-0.11521592736244202,
0.03242700174450874,
0.03525485098361969,
-0.2738266587257385,
0.17163731157779694,
-0.021792113780975342,
-0.47931593656539917,
0.43168532848358154,
-0.033772844821214676,
0.488644540309906,
0.2598911225795746,
-0.0226321760... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration#for-older-versions | For Older Versions
To install the Translations Provider Interfaces bundle for older versions of Pimcore, please run the following commands instead:
# install package (add to composer.json)
composer require pimcore/translations-provider-interfaces
bin/console pimcore:bundle:enable PimcoreTranslationsProviderInterfaceBun... | For Older Versions | [
-0.29189515113830566,
0.11006338149309158,
-0.1523337960243225,
0.01255751308053732,
0.08832813054323196,
-0.23522727191448212,
0.21722814440727234,
-0.08085406571626663,
-0.4640498161315918,
0.3913263976573944,
-0.008994844742119312,
0.45698773860931396,
0.2447703629732132,
-0.06239585205... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Installation_and_Configuration#setup-before-starting | Setup before starting
Depending on usage, desired workflow and used translation providers, additional configuration
might be needed. This might include
Setting configurations in configuration tree
Defining parameters - see parameters.yml for available parameters
Setting up manual triggering or
automatic change detecti... | Setup before starting | [
-0.19566680490970612,
-0.022632909938693047,
-0.21107730269432068,
-0.2688126564025879,
0.031057169660925865,
-0.3382289707660675,
0.3972932696342468,
-0.0785006508231163,
-0.05030204355716705,
0.4398581087589264,
0.394548624753952,
0.27690762281417847,
0.11033178120851517,
0.0964788869023... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation_Workflow/Manual_Trigger#manual-trigger | Manual Trigger
Besides automatic change detection, it is also possible to add items to the translation queue manually.
Currently only data objects are supported.
Be aware, that this just adds items to the translation queue. Execution of the command for creating
translation jobs is still necessary. See Commands for det... | Manual Trigger | [
-0.23806777596473694,
0.06307118386030197,
-0.1499129682779312,
-0.19635191559791565,
0.0098808528855443,
-0.3286935091018677,
0.2789458632469177,
-0.16522440314292908,
0.20356027781963348,
0.46818459033966064,
0.20976004004478455,
0.3609229624271393,
-0.05654382333159447,
0.12384889274835... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation_Workflow/Manual_Trigger#configuration | Configuration
Required configuration:
pimcore_translations_provider_interface:
settings:
# Default provider used in the Pimcore Backend UI.
default_provider: "translations-provider.translationscom"
# Comma separated list of user names or user email addresses for error notification.... | Configuration | [
-0.12406906485557556,
-0.11243754625320435,
-0.1434454470872879,
0.0020081072580069304,
0.18361222743988037,
-0.16722151637077332,
0.2952166795730591,
-0.0722680389881134,
-0.3074810802936554,
0.4526611566543579,
-0.11196129024028778,
0.2268921583890915,
0.24522823095321655,
-0.00941228866... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation_Workflow/Manual_Trigger#ui-options | UI Options
Trigger translation in context menu of trees
Either (multi-select) tree items
or do it via the grid
and choose source language and target languages.
| UI Options | [
-0.12738977372646332,
0.002920344704762101,
-0.24084116518497467,
0.05412191152572632,
0.12693139910697937,
-0.1876712143421173,
-0.046140290796756744,
0.035671208053827286,
-0.18537414073944092,
0.3390354514122009,
-0.18276803195476532,
0.27153441309928894,
0.1803535521030426,
0.143719613... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation_Workflow/Manual_Trigger#notifications | Notifications
Configured users will receive a notification whenever a submission fails.
| Notifications | [
0.03144390881061554,
-0.14905083179473877,
-0.20817476511001587,
-0.2262757569551468,
-0.20848967134952545,
-0.15457689762115479,
0.3507749140262604,
-0.21775151789188385,
-0.07879802584648132,
0.4277801215648651,
0.4041139781475067,
-0.13488493859767914,
-0.3122682273387909,
-0.0462116524... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation_Workflow/Automatic_Change_Detection#automatic-change-detection | Automatic Change Detection
Automatic change detection consists of two parts:
Data changed handler that handles a change a creates a changed item in the queue.
Event listener (or custom business logic) that triggers the data changed handler.
| Automatic Change Detection | [
0.17045259475708008,
-0.22385963797569275,
-0.25214695930480957,
0.2176465392112732,
-0.32771122455596924,
-0.3457561135292053,
0.21171753108501434,
-0.33610251545906067,
0.233108788728714,
-0.023763762786984444,
0.40654030442237854,
0.3044966161251068,
-0.30806657671928406,
0.335642486810... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation_Workflow/Automatic_Change_Detection#data-changed-handler | Data Changed Handler
Data changed handler define how change of data should be handled in terms of creating change items in
the translation queue.
They define aspects like source and target languages, translation provider, checks if relevant data really changed and
also if and what related elements should be considered ... | Data Changed Handler | [
-0.1037842258810997,
0.2505100667476654,
-0.1300821453332901,
0.26283422112464905,
0.000222792848944664,
-0.3400234878063202,
0.4742147624492645,
-0.05126137286424637,
-0.2691411077976227,
0.32925814390182495,
0.04072589799761772,
0.2715676426887512,
0.03125426545739174,
0.0425600856542587... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation_Workflow/Automatic_Change_Detection#further-customization | Further customization
In order to add related elements to a job, the getRelatedElements method has to be overridden. Simply return an array
containing all elements that are related to the object that was saved. This way the next time a job is created, the related
elements will be within the same job as the saved elemen... | Further customization | [
0.12689177691936493,
0.12801337242126465,
-0.18697255849838257,
-0.05496721342206001,
0.15137030184268951,
-0.24540866911411285,
0.29547959566116333,
0.09603801369667053,
0.02165360376238823,
0.17589835822582245,
-0.2578742504119873,
0.18927302956581116,
0.15039436519145966,
-0.08166065067... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation_Workflow/Automatic_Change_Detection#event-listeners | Event Listeners
If you want to enable automatic translation every time an object is saved, configure event listeners that trigger the
registered data changed handlers.
This bundle ships with a default implementation for such an event listener. To activate it, add following
service definition:
services:
Pimcore\Tran... | Event Listeners | [
-0.38349923491477966,
0.12564238905906677,
-0.0844523087143898,
-0.060912370681762695,
0.18659202754497528,
-0.2652677893638611,
0.12833817303180695,
-0.09984724223613739,
-0.3702344596385956,
0.5556188225746155,
0.010439328849315643,
0.3321652114391327,
0.03998793289065361,
0.031787823885... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation_Workflow#translation-workflow | Translation Workflow | Translation Workflow | [
0.10418246686458588,
-0.23593062162399292,
-0.34441033005714417,
-0.19318349659442902,
-0.04931304603815079,
-0.2554653584957123,
0.3126487135887146,
-0.02820531278848648,
-0.15184682607650757,
0.17948400974273682,
0.1332135945558548,
-0.026538453996181488,
0.10813315212726593,
0.085099339... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation_Workflow#collecting | Collecting
Changed items are collected into a queue (translations_interface_bundle__data_changed
table). Collection takes place via
Manual triggering
Event listener for automatic change detection
| Collecting | [
0.07219751924276352,
-0.019748663529753685,
-0.23155421018600464,
0.23079131543636322,
-0.21663914620876312,
-0.21971672773361206,
0.12152224779129028,
-0.22348999977111816,
0.00683135399594903,
0.2263120412826538,
0.05984537675976753,
0.4509884715080261,
0.1851077377796173,
-0.04439158365... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation_Workflow#creating-translation-jobs | Creating Translation Jobs
Once changes are collected, one or more items are combined to one translation job. Translation job
creation is always done via following command
php bin/console translations-provider-interface-bundle:jobs -c
Generated jobs can be found in the translations_interface_bundle__jobs table.
However... | Creating Translation Jobs | [
-0.02522248588502407,
0.3037748634815216,
-0.17571620643138885,
0.06711610406637192,
-0.18961790204048157,
-0.09516944736242294,
0.22913987934589386,
-0.01031605526804924,
-0.32227960228919983,
0.4149429202079773,
0.2894124388694763,
0.0204839576035738,
0.3532346785068512,
-0.1549280732870... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation_Workflow#translation-jobs-workflow | Translation Jobs Workflow
Once translation jobs are created, they follow following workflow. Transitions are possible via
translation jobs dashboard or via commands.
| Translation Jobs Workflow | [
0.05540083721280098,
0.12239529937505722,
-0.26981738209724426,
-0.18118800222873688,
-0.11343962699174881,
-0.3128240704536438,
0.3268410563468933,
-0.26032474637031555,
-0.11930704861879349,
0.30357638001441956,
0.19428566098213196,
0.020977983251214027,
0.37288641929626465,
0.0477743186... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation_Workflow#error-notifications | Error Notifications
In case of submission errors a notification (via the Notification Center) will be sent to
The submitter for manually triggered translation requests (see below)
an additional list of recipients as defined in the config. Example:
pimcore_translations_provider_interface:
settings:
# Comma... | Error Notifications | [
0.14353016018867493,
-0.14524483680725098,
-0.08409848809242249,
0.11440716683864594,
0.06832423806190491,
-0.1421823501586914,
0.10885851085186005,
-0.288259357213974,
-0.3996177315711975,
0.4734821021556854,
0.10732383280992508,
0.21368339657783508,
0.2398342490196228,
-0.230381965637207... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translations_Jobs_Dashboard#translation-jobs-dashboard | Translation Jobs Dashboard
Dashboard to see all translation jobs and manually trigger workflow transitions of single jobs.
| Translation Jobs Dashboard | [
-0.46122682094573975,
0.00003526948785292916,
-0.30870604515075684,
-0.25609293580055237,
-0.07949244230985641,
-0.17898817360401154,
0.3497050106525421,
0.17231552302837372,
0.0544988289475441,
0.3651879131793976,
0.046858709305524826,
0.1312474012374878,
0.08889704197645187,
0.2468910664... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translations_Jobs_Dashboard#error-simulation | Error Simulation
Available when Pimcore in DEBUG MODE this provides possibility to simulate communication errors with translation provider.
Once activated, all requests will result in an error. | Error Simulation | [
-0.22597329318523407,
-0.5113333463668823,
-0.10241477936506271,
0.043797120451927185,
0.030208218842744827,
-0.32083603739738464,
0.2594136595726013,
-0.11598099768161774,
-0.41389724612236023,
0.6390109062194824,
-0.09077147394418716,
0.2690659165382385,
0.20642533898353577,
-0.042140565... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation.com#translation.com | Translation.com
Following information apply to translation.com adapter. | Translation.com | [
0.009047561325132847,
-0.4032049775123596,
-0.32193049788475037,
0.05226558819413185,
0.09955621510744095,
-0.1397223025560379,
0.338248074054718,
-0.11329243332147598,
-0.06535273790359497,
0.34140533208847046,
-0.08617118000984192,
-0.03244107961654663,
0.2277749925851822,
0.063128292560... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Translation.com#setup | Setup
Following steps are necessary for setup the adapter:
Configure translations.com project director access credentials in configuration
pimcore_translations_provider_interface:
settings:
project_shortcode: Pimcore
translations_com:
project_director:
url: "https://gl-conn... | Setup | [
-0.4124099612236023,
-0.057718005031347275,
-0.012029795907437801,
0.07181572914123535,
0.10717787593603134,
-0.41865846514701843,
0.4247409999370575,
-0.12278120964765549,
-0.14999370276927948,
0.35951128602027893,
0.019439976662397385,
0.39931821823120117,
0.280828595161438,
0.0426391884... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Xplanation#xplanation | XPlanation
Following information apply to XPlanation adapter. | XPlanation | [
-0.22348670661449432,
-0.5623875856399536,
-0.21612806618213654,
0.20119093358516693,
0.2334338128566742,
-0.26953786611557007,
0.4538247287273407,
-0.140121191740036,
0.0535104013979435,
0.226585254073143,
-0.07867790758609772,
0.28992271423339844,
0.18580910563468933,
0.10387638211250305... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Xplanation#setup | Setup
When using default Xplanation translation provider service, following settings are available in configuration:
pimcore_translations_provider_interface:
# Configuration of xplanation settings
xplanation:
# Authentication key of xplanation
key: ~
# Authentication ... | Setup | [
-0.19361832737922668,
-0.008641860447824001,
-0.08981037139892578,
-0.11819031834602356,
0.3377951383590698,
-0.4245685040950775,
0.2543319761753082,
-0.15885941684246063,
-0.40711671113967896,
0.7316154837608337,
0.008438065648078918,
0.34358900785446167,
0.3209027945995331,
-0.0413840785... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Xplanation#workflow-simulation | Workflow Simulation
It is possible to simulate XPlanation translation workflow with the command bin/console translations-provider-interface-bundle:simulation.
To activate simulation, also following parameter need to be set:
parameters:
simulation.enabled: false # Enable the simulation
simulation.simulate-can... | Workflow Simulation | [
-0.2985372543334961,
0.029525313526391983,
-0.16311170160770416,
-0.21259526908397675,
-0.1778601109981537,
-0.21482150256633759,
0.354367196559906,
0.01826777309179306,
-0.07972061634063721,
0.5743643641471863,
0.14022254943847656,
0.2861717641353607,
0.030245086178183556,
0.0820056796073... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/DeepL#deepl | DeepL | DeepL | [
-0.21319110691547394,
-0.36725372076034546,
-0.22931347787380219,
0.38155049085617065,
-0.36073774099349976,
-0.3928912580013275,
-0.04852718859910965,
0.09472045302391052,
-0.08077764511108398,
0.09126268327236176,
-0.1236034706234932,
0.1555081158876419,
-0.32380732893943787,
0.067022897... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/DeepL#setup | Setup
Create or use an existing DeepL API Account, get necessary configuration values from it and apply
it via configuration user interface or via configuration file as follows.
pimcore_translations_provider_interface:
deepl:
api_url: '<TRANSLATE>' # e.g. https://api-free.deepl.com/v2/translate
... | Setup | [
-0.16608870029449463,
-0.17096595466136932,
-0.14885744452476501,
0.04131215065717697,
-0.16100545227527618,
-0.1889895647764206,
-0.23353993892669678,
0.12358580529689789,
-0.20566093921661377,
0.26601025462150574,
-0.09503962844610214,
0.4515557587146759,
0.06856783479452133,
0.193086147... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/DeepL#glossary | Glossary
The adapter supports usage of glossary during translation process but there is no user interface to create glossary entries.
To use glossaries, you have to create them directly via DeepL API so that they will be used during translation process.
Details see DeepL Docs. | Glossary | [
-0.1918504387140274,
-0.3421795964241028,
-0.19903331995010376,
0.26609233021736145,
0.023756472393870354,
0.07049084454774857,
0.14699624478816986,
-0.18320979177951813,
0.2208063304424286,
0.37906697392463684,
-0.1782640516757965,
0.19000089168548584,
-0.10661961883306503,
0.169822543859... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Development_Details/Database_Model#database-model | Database Model
Table
Description
translations_interface_bundle__data_changed
Tracks data changes on Pimcore element item level. Acts as a source for the jobs table.
translations_interface_bundle__jobs
Formatted (for a specific translations provider) and chunked data changes used for processing the translations... | Database Model | [
-0.21836738288402557,
-0.03737609088420868,
-0.21985724568367004,
0.3519802987575531,
-0.10169009864330292,
0.05396033450961113,
0.1604890078306198,
-0.05062447488307953,
-0.3173578679561615,
-0.07662331312894821,
-0.03527204319834709,
0.3382163643836975,
0.3466815650463104,
0.470377385616... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Development_Details#development-details | Development Details | Development Details | [
-0.02537638694047928,
-0.2884541153907776,
-0.45756226778030396,
0.20831260085105896,
-0.13089774549007416,
-0.4546503722667694,
0.24140456318855286,
-0.20009246468544006,
-0.5428919792175293,
0.1761464774608612,
0.073187455534935,
-0.05486028268933296,
-0.1053479015827179,
0.3626109659671... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Development_Details#general-aspects | General Aspects
Services for translation adapters and data changed handler are registered automatically when they implement the respecting
interfaces DataChangedHandlerInterface and TranslationsProviderInterface.
Register process implemented by
automatically tagging all services that implement the mentioned interfaces... | General Aspects | [
-0.1633438915014267,
-0.2259421944618225,
-0.0793868750333786,
0.039991069585084915,
0.11587612330913544,
-0.21828912198543549,
0.5541953444480896,
-0.25847935676574707,
0.10680344700813293,
0.3110176920890808,
0.17884188890457153,
0.2904275953769684,
0.38889506459236145,
0.258378416299819... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces/Development_Details#translation-providers | Translation Providers
Translation providers are implemented and configured as services. This bundle ships with default service configurations
of the two supported translation providers:
services:
translations-provider.translationscom:
class: Pimcore\TranslationsProviderInterfaceBundle\TranslationsProvider\... | Translation Providers | [
-0.12632855772972107,
0.16528911888599396,
-0.14408525824546814,
0.07010229676961899,
0.13422460854053497,
-0.14693550765514374,
0.25593385100364685,
-0.142591193318367,
-0.6134322285652161,
0.5632479786872864,
0.0933777317404747,
0.16283290088176727,
0.30654335021972656,
-0.00492804963141... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces#translation_provider_interfaces | Translation_Provider_Interfaces
| Translation_Provider_Interfaces | [
-0.08212407678365707,
-0.08641761541366577,
-0.2927403151988983,
0.16276569664478302,
0.29695993661880493,
-0.36944398283958435,
0.5788918137550354,
-0.10732613503932953,
-0.17889583110809326,
0.3296213746070862,
0.07353246957063675,
0.34457436203956604,
0.2653229236602783,
0.2498250752687... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces#title:-translation-provider-interfaces | title: Translation Provider Interfaces | title: Translation Provider Interfaces | [
0.040692541748285294,
0.04986349120736122,
-0.28990060091018677,
0.008027391508221626,
0.1584150642156601,
-0.18227143585681915,
0.6177904605865479,
-0.1950675994157791,
0.016789637506008148,
0.3789524435997009,
0.08450457453727722,
0.29774829745292664,
0.23806121945381165,
0.1337020546197... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces#pimcore-translation-provider-interfaces | Pimcore Translation Provider Interfaces
This bundle allows you to create translation jobs, which are sent to external APIs for further processing. The processed jobs will then be fetched again in order to update any supported elements (see the list below).
Sample dashboard for translation jobs | Pimcore Translation Provider Interfaces | [
-0.185846745967865,
-0.0037350626662373543,
-0.2463523894548416,
-0.1151357889175415,
-0.1176498755812645,
-0.14614398777484894,
0.06321167200803757,
-0.20006439089775085,
-0.2600056827068329,
0.3309069871902466,
-0.15225492417812347,
0.2747021019458771,
0.45965179800987244,
0.359256982803... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces#features-in-a-nutshell | Features in a Nutshell | Features in a Nutshell | [
0.01706564985215664,
-0.7834231853485107,
-0.38337546586990356,
-0.06846539676189423,
0.11408670991659164,
-0.01618780940771103,
0.231790691614151,
-0.16248558461666107,
-0.26017799973487854,
0.162034273147583,
0.05158870667219162,
0.12481886893510818,
-0.22597558796405792,
0.5144364237785... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces#supported-elements | Supported Elements
Localized Fields of DataObjects
Content of Documents
Metadata of Assets
| Supported Elements | [
-0.20835018157958984,
0.03194436803460121,
-0.2901226878166199,
0.14638346433639526,
0.379106342792511,
-0.14800643920898438,
0.37404441833496094,
0.2996761202812195,
-0.06699305027723312,
0.1900407373905182,
-0.04493582993745804,
0.17955151200294495,
-0.07681375741958618,
0.09063141047954... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces#supported-translation-providers | Supported Translation Providers
This bundle supports multiple translation providers by configuring corresponding services:
translations.com
Xplanation (a LanguageWire company)
DeepL
| Supported Translation Providers | [
-0.04402673617005348,
-0.19604378938674927,
-0.2987312078475952,
0.07014531642198563,
-0.037967320531606674,
0.08029589056968689,
0.26914259791374207,
-0.11422692984342575,
-0.17566293478012085,
0.19637125730514526,
-0.10243181884288788,
-0.028281155973672867,
0.24624642729759216,
0.121921... |
https://pimcore.com/docs/platform//Translation_Provider_Interfaces#documentation-overview | Documentation Overview
Installation and Configuration
Translation Workflow
Translations Jobs Dashboard
Extending and further Customization
On translation provider specific aspects:
Translations.com
Xplanation
DeepL
| Documentation Overview | [
-0.13658133149147034,
-0.03818648308515549,
-0.33450591564178467,
-0.050980888307094574,
-0.1987842321395874,
0.0824715867638588,
0.2551581561565399,
-0.14479202032089233,
-0.17169348895549774,
0.3167778551578522,
0.010720168240368366,
0.10659832507371902,
0.27589714527130127,
0.1176935136... |
https://pimcore.com/docs/platform//Statistics_Explorer/Installation_and_Configuration/Upgrade#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//Statistics_Explorer/Installation_and_Configuration/Upgrade#upgrade-to-2.0.0 | Upgrade to 2.0.0
Removed support for Elasticsearch 6 and 7, added Elasticsearch 8 support
Changed elasticsearch client configuration, details see Configuration.
| Upgrade to 2.0.0 | [
-0.1338539570569992,
-0.09777815639972687,
-0.24483731389045715,
-0.2965239882469177,
-0.09934741258621216,
-0.12530389428138733,
0.043459512293338776,
0.48699432611465454,
0.08516451716423035,
-0.02730649895966053,
-0.030431708320975304,
0.2366500049829483,
-0.17350433766841888,
0.0191848... |
https://pimcore.com/docs/platform//Statistics_Explorer/Installation_and_Configuration/Upgrade#upgrade-to-1.3.0 | Upgrade to 1.3.0
Execute all migrations of the bundle.
| Upgrade to 1.3.0 | [
-0.30632397532463074,
-0.31076979637145996,
-0.2145196795463562,
-0.004786214791238308,
0.0983319878578186,
0.022054847329854965,
0.18367667496204376,
0.36072972416877747,
-0.19175446033477783,
0.2498684823513031,
-0.00790935568511486,
0.3611145615577698,
-0.20909972488880157,
0.1356191486... |
https://pimcore.com/docs/platform//Statistics_Explorer/Installation_and_Configuration/Upgrade#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//Statistics_Explorer/Installation_and_Configuration#installation-and-configuration | Installation and Configuration | Installation and Configuration | [
-0.032902296632528305,
-0.4798862338066101,
-0.26170942187309265,
0.2767668664455414,
0.11351562291383743,
0.03320053592324257,
-0.016319455578923225,
-0.239933043718338,
-0.06732313334941864,
0.11178846657276154,
-0.10553950071334839,
0.12544715404510498,
0.07521870732307434,
0.1444275826... |
https://pimcore.com/docs/platform//Statistics_Explorer/Installation_and_Configuration#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//Statistics_Explorer/Installation_and_Configuration#for-pimcore->=-10.5 | For Pimcore >= 10.5
To install Pimcore Statistics Explorer for Pimcore 10.5 or higher, follow the three steps below:
Install the required dependencies:
composer require pimcore/statistics-explorer
Make sure the bundle is enabled in the config/bundles.php file. The following lines should be added:
use Pimcore\Bu... | For Pimcore >= 10.5 | [
-0.5632727742195129,
0.10337911546230316,
-0.10849518328905106,
0.0848703533411026,
-0.07495041936635971,
-0.23072504997253418,
-0.0949477106332779,
0.041591476649045944,
-0.5029270648956299,
0.4703872501850128,
-0.08175825327634811,
0.4606173038482666,
0.09302234649658203,
0.0802942067384... |
https://pimcore.com/docs/platform//Statistics_Explorer/Installation_and_Configuration#for-older-versions | For Older Versions
To install the Statistics Explorer bundle for older versions of Pimcore, please run the following commands instead:
composer require pimcore/statistics-explorer
bin/console pimcore:bundle:enable PimcoreStatisticsExplorerBundle
bin/console pimcore:bundle:install PimcoreStatisticsExplorerBundle
| For Older Versions | [
-0.613527238368988,
0.11416701227426529,
-0.14075493812561035,
0.007415813859552145,
0.035148072987794876,
-0.1743117719888687,
-0.028352750465273857,
-0.016568055376410484,
-0.48945024609565735,
0.42761707305908203,
-0.028832659125328064,
0.4123709797859192,
0.104654461145401,
0.070920653... |
https://pimcore.com/docs/platform//Statistics_Explorer/Installation_and_Configuration#configuration | Configuration
The statistics explorer needs to be embedded into an existing host application that
provides the context in which the statistics explorer is executed.
The statistics explorer can be executed in multiple contexts within one host application and each
context is connected to user & login information.
The... | Configuration | [
-0.41836532950401306,
-0.16850540041923523,
0.034919314086437225,
0.2249634861946106,
-0.10241811722517014,
-0.17670069634914398,
0.07207636535167694,
-0.31174954771995544,
-0.33263707160949707,
0.442434698343277,
-0.0329321064054966,
0.25849995017051697,
0.3104291558265686,
0.029190151020... |
https://pimcore.com/docs/platform//Statistics_Explorer/Installation_and_Configuration#setup-user-provider | Setup User Provider
The host application needs to take about user authentication (e.g. via a symfony
firewall) and provide the statistics explorer the user information.
This is done by creating a service that is implementing the
UserProviderInterface and that is tagged with
the pimcore.statistics_explorer.user_provider... | Setup User Provider | [
-0.4813147783279419,
-0.07597637176513672,
-0.05159002169966698,
0.06744356453418732,
-0.03816463425755501,
-0.4500071108341217,
0.3374784588813782,
-0.2771371304988861,
-0.29561883211135864,
0.4196637272834778,
-0.25522682070732117,
0.32419732213020325,
0.29033204913139343,
0.078221306204... |
https://pimcore.com/docs/platform//Statistics_Explorer/Installation_and_Configuration#sample-user-provider-configuration | Sample User Provider Configuration
statistics_explorer.userprovider_portal:
autowire: true
autoconfigure: true
public: false
class: Pimcore\Bundle\StatisticsExplorerBundle\User\PimcoreUserProvider
tags:
- { name: 'pimcore.statistics_explorer.user_provider_context'... | Sample User Provider Configuration | [
-0.583030641078949,
0.12376400828361511,
-0.0672728419303894,
0.0006914121913723648,
0.355643630027771,
-0.15828633308410645,
0.1337459832429886,
-0.17515534162521362,
-0.44857707619667053,
0.30481261014938354,
-0.08163244277238846,
0.48752763867378235,
0.125823974609375,
0.383815765380859... |
https://pimcore.com/docs/platform//Statistics_Explorer/Installation_and_Configuration#setup-routes | Setup Routes
All controller actions of the statistics explorer need to be executed in the defined context
and most probably in the context of the corresponding firewall. To provide maximal flexibility,
the statistics explorer does not predefine any routes but allows you to define the route prefix(es)
in which the stati... | Setup Routes | [
-0.4260816276073456,
0.18281498551368713,
-0.0005702960770577192,
0.012707787565886974,
-0.05500167980790138,
-0.5701258182525635,
0.08905212581157684,
-0.22290144860744476,
-0.3606392741203308,
0.29425469040870667,
-0.14881837368011475,
0.44271761178970337,
0.3073316812515259,
0.188761442... |
https://pimcore.com/docs/platform//Statistics_Explorer/Installation_and_Configuration#setup-data-sources | Setup Data Sources
The last setup step is to configure data sources that should be used by the statistics explorer. Data sources
are symfony services that implement the StatisticsStorageAdapterInterface
and are tagged with the pimcore.statistics_explorer.data_source which defines the data source name and the
context in... | Setup Data Sources | [
-0.364387571811676,
0.38266098499298096,
0.010543902404606342,
0.03082774020731449,
-0.2230263203382492,
-0.23866185545921326,
0.13830862939357758,
-0.14634402096271515,
-0.3268304169178009,
0.3227798342704773,
-0.054442502558231354,
0.2125197798013687,
0.22567762434482574,
0.0950186401605... |
https://pimcore.com/docs/platform//Statistics_Explorer/Installation_and_Configuration#sample-data-source-configuration | Sample Data Source Configuration
datasources.data_objects_car:
class: Pimcore\Bundle\StatisticsExplorerBundle\StatisticsStorageAdapter\ElasticsearchAdapter
autowire: true
autoconfigure: true
public: false
arguments:
$esClient: '@pimcore.elasticsearch_client.defaul... | Sample Data Source Configuration | [
-0.5682563781738281,
0.18591679632663727,
-0.1380692422389984,
0.08021748065948486,
-0.0955207571387291,
-0.09865551441907883,
0.06574203073978424,
0.1515965759754181,
-0.47798967361450195,
0.17612899839878082,
-0.16623555123806,
0.5087922215461731,
0.20239455997943878,
0.03766341134905815... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.