url stringlengths 50 196 | text stringlengths 3 17.2k | heading stringlengths 2 103 | embeddings list |
|---|---|---|---|
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Building_Custom_Rest_APIs#example | Example
<?php
namespace App\Controller;
use Pimcore\Model\DataObject;
use Symfony\Component\HttpFoundation\JsonResponse;
use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\Routing\Annotation\Route;
use \Pimcore\Controller\FrontendController;
class CustomRestController extends FrontendController
{... | Example | [
-0.04209384694695473,
-0.0738472193479538,
-0.11926412582397461,
0.10267500579357147,
0.1596319079399109,
-0.19408005475997925,
0.05517800524830818,
0.2755802571773529,
-0.07500357925891876,
0.1919918805360794,
-0.1263270080089569,
0.45445773005485535,
0.32897794246673584,
-0.0219406634569... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Integrating_Commerce_Data_with_Content#integrating-commerce-data-with-content | Integrating Commerce Data With Content
Content commerce, shop everywhere, vanish separation of content and commerce - these are key phrases that popup with
every state-of-the-art e-commerce project. With its integrated approach Pimcore does exactly that and provides several
tools to provide the best experience for the ... | Integrating Commerce Data With Content | [
-0.12786804139614105,
-0.31968721747398376,
-0.24021016061306,
0.22767309844493866,
-0.09509129077196121,
-0.2925768792629242,
0.12999951839447021,
0.23078492283821106,
-0.16584311425685883,
-0.15748384594917297,
0.04926634579896927,
0.6025189161300659,
0.3521275818347931,
0.60461014509201... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Integrating_Commerce_Data_with_Content#create-area-brick-myproductteaser-with-renderlet | Create Area Brick MyProductTeaser with Renderlet
MyProductTeaser Implementation
<?php
namespace App\Document\Areabrick;
class MyProductTeaser extends AbstractAreabrick
{
/**
* {@inheritdoc}
*/
public function getName(): string
{
return 'My Product Teaser';
}
}
MyProductTeaser Te... | Create Area Brick MyProductTeaser with Renderlet | [
-0.2724570631980896,
-0.41888535022735596,
-0.2029763013124466,
0.3175763487815857,
-0.1698472797870636,
-0.4302029013633728,
0.5896725654602051,
0.299229234457016,
-0.06336748600006104,
0.18664482235908508,
-0.06463605910539627,
0.7088607549667358,
-0.1048685610294342,
0.23277978599071503... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Integrating_Commerce_Data_with_Content#create-controller-and-action-for-teaser-content | Create Controller and Action for Teaser Content
Controller Action
public function productCellAction(Request $request): Response
{
$id = $request->attribute->getInt('id');
$type = $request->attribute->get('type');
if ($type === 'object') {
$product = Product::getB... | Create Controller and Action for Teaser Content | [
0.03527380898594856,
-0.2943786084651947,
-0.21989215910434723,
0.14997051656246185,
-0.13441184163093567,
-0.1722945272922516,
0.122014619410038,
0.6262781023979187,
-0.13266761600971222,
0.20931024849414825,
-0.1514371931552887,
0.1588636338710785,
0.09549844264984131,
0.3101244866847992... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Primary-Replica_Database_Connection#how-to-configure-pimcore-to-use-a-primaryreplica-database-connection | How to Configure Pimcore To Use a Primary/Replica Database Connection
IMPORTANT: Please be aware that the primary/replica connection can only be used for a clustered MariaDB/MySQL environment, NOT
for a primary/replica server setup! Due to the extensive multi-layered, consistent and tagged caching of Pimcore
it is nece... | How to Configure Pimcore To Use a Primary/Replica Database Connection | [
-0.3479795455932617,
-0.14092803001403809,
-0.055076561868190765,
-0.16024798154830933,
-0.07473882287740707,
-0.10001600533723831,
-0.04738885164260864,
-0.29827216267585754,
-0.282731294631958,
0.04620029777288437,
-0.19445760548114777,
0.03864942491054535,
0.3688794672489166,
0.05187382... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Primary-Replica_Database_Connection#create-a-project-specific-database-connection-class | Create a Project specific Database Connection Class
Create a new class at src\Db\Connection.php, with the following content:
<?php
namespace App\Db;
use Doctrine\DBAL\Connections\PrimaryReadReplicaConnection;
class Connection extends PrimaryReadReplicaConnection
{
/**
* @param string|null $connectionName... | Create a Project specific Database Connection Class | [
-0.49506059288978577,
0.3540492057800293,
-0.08497639000415802,
-0.07550767809152603,
0.12034575641155243,
-0.2151348739862442,
-0.08238502591848373,
0.22327589988708496,
-0.6716859936714172,
0.22242659330368042,
-0.004934242926537991,
0.01754537969827652,
0.1937909871339798,
0.08211493492... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Primary-Replica_Database_Connection#configure-the-primaryreplica-connection | Configure the Primary/Replica Connection
The main database connection which you have configured for Pimcore is always the primary connection.
Then you can add as many replica hosts as you like, in the following example there's just one replica host,
where only the host is different (in our case replica1), all other opt... | Configure the Primary/Replica Connection | [
-0.25381171703338623,
-0.13328909873962402,
-0.0898844301700592,
0.021212805062532425,
-0.16373702883720398,
-0.20199473202228546,
-0.0845184326171875,
0.02044273354113102,
-0.5244101881980896,
0.30485716462135315,
-0.285305917263031,
-0.06688819080591202,
0.3650401532649994,
0.02972068078... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Modifying_Permissions_based_on_Object_Data#modifying-permissions-based-on-object-data | Modifying Permissions Based on Object Data
The event OBJECT_GET_PRE_SEND_DATA
can be used to manipulate the server response before object data is sent to Pimcore Backend UI when opening the detail
view of an Pimcore object.
Imagine following use case:
Your PIM system aggregates different sources (e.g. multiple ERP syst... | Modifying Permissions Based on Object Data | [
-0.04992428049445152,
0.06871266663074493,
-0.11233578622341156,
0.13484720885753632,
-0.21488209068775177,
-0.5443609952926636,
0.15183578431606293,
0.08782410621643066,
-0.40981149673461914,
0.02905118279159069,
-0.26998502016067505,
0.45529890060424805,
-0.09502913057804108,
0.359103918... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Object_Bricks_vs_Classification_Store#object-bricks-vs-classification-store | Object Bricks vs Classification Store
Pimcore offers many possibilities regarding data modeling for structured data (= Pimcore Data Objects).
Most of them are self-explanatory, while others often raise questions about when it makes most sense to use them and what
exactly is the difference between the individual choices... | Object Bricks vs Classification Store | [
-0.20146651566028595,
0.23544135689735413,
-0.15326595306396484,
0.17105437815189362,
0.060672301799058914,
-0.18809053301811218,
0.5755242705345154,
-0.04003940150141716,
0.12161216884851456,
0.16087093949317932,
-0.14413538575172424,
0.10054773092269897,
-0.08680316060781479,
0.370233148... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Object_Bricks_vs_Classification_Store#basic-goal | Basic goal
Object Bricks and Classification Store share a common goal, which is best explained with an example:
A shop has products of many different categories (eg shoes, tents, flashlights, etc.).
All these products have some attributes that are the same for all categories (eg name, photo, descriptive text, article
n... | Basic goal | [
-0.07909292727708817,
0.2332504838705063,
-0.09765347093343735,
0.263599157333374,
0.2928176522254944,
-0.04031074419617653,
0.6245210766792297,
0.15887437760829926,
0.18450473248958588,
0.0652812123298645,
-0.2369510382413864,
0.09988348931074142,
-0.09789813309907913,
0.32607418298721313... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Object_Bricks_vs_Classification_Store#technical-implementation-differences | Technical implementation differences
Object Bricks
Classification Store
Design options in the object editor
All layout options provided by ExtJS and Pimcore (Panels, Tabs, Regions, Fieldsets, Text Descriptions, ...)
All attributes are arranged among themselves in regions, little influence possibilities.
Ava... | Technical implementation differences | [
-0.1622050255537033,
-0.35765311121940613,
-0.2131764441728592,
0.20406481623649597,
-0.03596268966794014,
-0.30679911375045776,
0.11125139147043228,
0.09998124092817307,
-0.04542463272809982,
0.3066803812980652,
-0.5004026889801025,
0.27571243047714233,
0.06250810623168945,
0.573489665985... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Object_Bricks_vs_Classification_Store#when-do-you-use-something---a-checklist-and-a-rule-of-thumb? | When do you use something - a checklist and a rule of thumb? | When do you use something - a checklist and a rule of thumb? | [
0.21369487047195435,
-0.3937435448169708,
-0.21364068984985352,
-0.3391050696372986,
-0.10728742182254791,
-0.22786420583724976,
0.15254928171634674,
0.04571317881345749,
0.36060649156570435,
0.30488064885139465,
0.40280619263648987,
-0.04830801859498024,
-0.1285567581653595,
0.00539875682... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Object_Bricks_vs_Classification_Store#a-basic-rule-of-thumb-can-be | A basic rule of thumb can be
As long as a manageable number of categories with specific attributes is in place, rather use Object Bricks.
Once there will be a lot of categories (more than 30) with a lot of attributes, then rather use Classification Store.
| A basic rule of thumb can be | [
-0.13870146870613098,
0.18835702538490295,
-0.2355908304452896,
0.141744002699852,
0.1651410013437271,
-0.18223023414611816,
0.6508590579032898,
0.16155171394348145,
0.20929865539073944,
0.16462191939353943,
-0.09931019693613052,
-0.11918763816356659,
-0.06941639631986618,
0.13196530938148... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Object_Bricks_vs_Classification_Store#in-addition,-there-are-a-few-more-questions-which-can-help-you-make-a-decision | In addition, there are a few more questions which can help you make a decision
Are there relations in the attributes? → currently only works with Object Bricks
Do the attributes have to be created automatically (eg via interface)? → easier with Classification Store
But there is (unfortunately) no rule, which is alw... | In addition, there are a few more questions which can help you make a decision | [
-0.25986093282699585,
-0.16824255883693695,
-0.16519081592559814,
0.21078114211559296,
0.16795286536216736,
-0.3481910228729248,
0.5537233352661133,
-0.2307996153831482,
0.03317733854055405,
0.23261098563671112,
-0.158512681722641,
0.20959174633026123,
0.19586874544620514,
0.21401700377464... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Object_Data_Inheritance#object-data-inheritance-in-action | Object Data Inheritance in Action
Object Data Inheritance is a powerful feature to minimize the data maintenance effort for editors.
In our e-commerce demo we use data inheritance for fashion products with different colors and sizes - meaning
we have a generic article with all the generic information (like names, descr... | Object Data Inheritance in Action | [
0.08024418354034424,
-0.03992893546819687,
-0.16571786999702454,
0.22935837507247925,
0.07155274599790573,
-0.27558958530426025,
0.4801779091358185,
0.23042190074920654,
-0.13779155910015106,
0.21338233351707458,
0.046001363545656204,
0.18059752881526947,
-0.0650140643119812,
0.12491954118... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Open_By-External_Id#open-by-external-id | Open By External Id
There are 2 different approaches:
You can either hook directly into the the default Pimcore id resolver by using this event
Or add an independent menu entry and a shortcut similar to the default Open Data Object (ctrl + shift + o) to the admin ui.
Create a bundle with a Pimcore Backend Inter... | Open By External Id | [
-0.25651371479034424,
-0.1202809140086174,
-0.046180903911590576,
0.08725463598966599,
-0.10315379500389099,
-0.3074677586555481,
0.164973184466362,
0.2788770794868469,
0.10284274816513062,
0.1684405505657196,
-0.28461986780166626,
0.6006395816802979,
0.12451791763305664,
0.329430431127548... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Style_Backend_Depending_On_App-Env#style-backend-depending-on-the-application-environment | Style Backend Depending on the Application Environment
Sometimes it makes sense to style the Pimcore backend UI depending on the application environment (APP_ENV) so that
backend users can easily differentiate by the looks.
Imagine having additional environments for Staging and Testing and you want to give editors a hi... | Style Backend Depending on the Application Environment | [
-0.29223060607910156,
-0.08549287170171738,
-0.12517023086547852,
0.0947016254067421,
0.15351322293281555,
-0.6480890512466431,
0.40226683020591736,
0.12043355405330658,
-0.33100375533103943,
0.19808724522590637,
-0.07937944680452347,
0.4837189316749573,
0.32856717705726624,
0.049798052757... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Security_Concept#security-concept | Security Concept
We at Pimcore take security very seriously and recommend a multi-layer security concept to keep Pimcore-based solutions
safe.
As Pimcore is a framework and not an out-of-the box solution, this multi-layer security concept has parts that are
provided by the core framework itself, and parts that need to ... | Security Concept | [
-0.2775697112083435,
-0.3017852306365967,
-0.16900435090065002,
0.20418491959571838,
-0.4837791919708252,
-0.479615181684494,
0.3805571496486664,
-0.5793516039848328,
-0.491548627614975,
0.08367006480693817,
-0.105783611536026,
0.2801002562046051,
0.17511260509490967,
0.48418670892715454,
... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Security_Concept#pimcore-core-level | Pimcore Core Level | Pimcore Core Level | [
-0.5255488753318787,
-0.6454870700836182,
-0.2249959260225296,
0.3036457896232605,
0.1543818712234497,
-0.16743403673171997,
-0.09681499749422073,
-0.174317866563797,
-0.3584342896938324,
0.40821558237075806,
-0.24585391581058502,
0.6461649537086487,
0.06693261861801147,
0.4703173339366913... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Security_Concept#following-coding-standards-&-best-practices | Following Coding Standards & Best Practices
To minimize the risk of security issues, we follow established and proven php coding standards as well as industry best
practises. The coding standards are based on so called PSRs (PHP Standards Recommendations) developed by the
PHP Framework Interop Group (PHP-FIG) and a... | Following Coding Standards & Best Practices | [
-0.25464490056037903,
-0.49273398518562317,
-0.18265104293823242,
0.00012757655349560082,
-0.005926959216594696,
-0.6027490496635437,
0.06801722198724747,
-0.03932999446988106,
-0.24483121931552887,
0.387525737285614,
0.10909850895404816,
-0.020411647856235504,
0.14593037962913513,
-0.0682... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Security_Concept#dependency-management | Dependency Management
Pimcore is based on the Symfony framework (PHP industry standard framework) and multiple additional components and
dependencies. All Dependencies are managed through Composer (the standard PHP dependency management solution) which makes
it easy and comfortable to keep all dependencies of Pimcore a... | Dependency Management | [
-0.17737409472465515,
-0.1426745355129242,
-0.18354515731334686,
0.10056091845035553,
-0.16774840652942657,
-0.27727019786834717,
0.10942555218935013,
-0.20950618386268616,
-0.279041588306427,
0.05854679271578789,
0.08269869536161423,
0.3773968815803528,
-0.04235938936471939,
0.07600291073... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Security_Concept#content-security-policy | Content Security Policy
Pimcore provides a Content Security Policy handler, which enables an additional security layer to protect from certain attacks like Cross-Site Scripting (XSS) and data injection and so on, by adding Content-Security-Policy HTTP response header with nonce to every request in Admin interface. The ... | Content Security Policy | [
-0.06462033092975616,
-0.2791648209095001,
-0.12598443031311035,
-0.10515671223402023,
0.17391736805438995,
-0.38570207357406616,
0.13148172199726105,
0.07601463794708252,
0.1377546638250351,
0.190245121717453,
-0.19421881437301636,
0.2428581714630127,
0.10956773161888123,
0.29334896802902... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Security_Concept#handling-security-issues | Handling Security Issues
In the case of a security issue/vulnerability in the Pimcore core framework, we handle them with the following procedure:
Reporting Issue:
Report issue via Pimcore Security form, not via public
issue tracker (according guidelines also available at public issue tracker).
Resolving Issue:
Re... | Handling Security Issues | [
-0.08037623763084412,
-0.09476585686206818,
-0.11724508553743362,
0.03716197609901428,
-0.18226630985736847,
-0.3447130620479584,
0.13072381913661957,
-0.19385592639446259,
-0.46762704849243164,
0.10223212093114853,
0.15845660865306854,
0.4897997975349426,
0.12286588549613953,
0.2769086062... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Security_Concept#project-specific-level-(provided-by-integration-partner) | Project specific Level (provided by Integration Partner) | Project specific Level (provided by Integration Partner) | [
-0.07796104997396469,
-0.17978347837924957,
-0.23964045941829681,
0.14523911476135254,
-0.1572459638118744,
-0.4904801547527313,
0.29524630308151245,
-0.311126172542572,
-0.10891856253147125,
0.39073842763900757,
0.32680100202560425,
0.43830618262290955,
-0.13853511214256287,
0.84960740804... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Security_Concept#following-coding-standards-&-best-practices | Following Coding Standards & Best Practices
Same as for the core development, we recommend applying all the coding standards and best practises for solution development
too. | Following Coding Standards & Best Practices | [
0.06529880315065384,
-0.38922935724258423,
-0.37287479639053345,
-0.3319297730922699,
0.10179959982633591,
-0.20166070759296417,
0.0019061131170019507,
-0.02790551446378231,
0.0058214180171489716,
0.10545120388269424,
0.17985427379608154,
0.311554878950119,
0.1764538735151291,
0.3645909130... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Security_Concept#dependency-management | Dependency Management
Same as for the core development, we also recommend security checks for all the additional solution dependencies. Also
for solutions, all Symfony tools, like the Symfony Security Checker
can be utilized. | Dependency Management | [
0.15010938048362732,
-0.07808732986450195,
-0.2492133378982544,
-0.012674008496105671,
-0.2987830638885498,
-0.07769466936588287,
0.08665657788515091,
-0.0006657623453065753,
0.011770016513764858,
0.07431208342313766,
0.23723585903644562,
0.14038076996803284,
0.09933061897754669,
0.0923822... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Security_Concept#project-specific-penetration-testing | Project Specific Penetration Testing
Project specific penetration testing should uncover possible security issues in solution implementation. This testing
should be done on staging systems, without additional security layers such as WAF (Web Application Firewall) or IPS
(Intrusion Protection Systems) and should cover a... | Project Specific Penetration Testing | [
-0.27185770869255066,
-0.31267672777175903,
-0.19009172916412354,
-0.07463893294334412,
-0.5521964430809021,
-0.1542719602584839,
0.2418109029531479,
-0.18186083436012268,
0.030680900439620018,
0.1079542264342308,
0.3451611399650574,
0.22236710786819458,
0.17647162079811096,
0.408881872892... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Security_Concept#waf-&-ips-on-production-systems | WAF & IPS on production systems
Web Application Firewalls and Intrusion Protection Systems are systems that sit in front of the application, analyse all
traffic and try to filter malicious activities.
As standard php application, Pimcore supports all industry standard products such as ModSecurity, WAF safeguards of... | WAF & IPS on production systems | [
-0.19361230731010437,
-0.49054020643234253,
-0.2063308209180832,
-0.08219009637832642,
-0.4445410370826721,
-0.6788206100463867,
0.6096490621566772,
-0.3358883857727051,
-0.07105263322591782,
0.022870488464832306,
-0.029847249388694763,
0.018453609198331833,
0.38788536190986633,
0.38983741... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Showing_Custom_Layouts_based_on_Object_Data#showing-custom-layouts-based-on-object-data | Showing Custom Layouts Based on Object Data
The event OBJECT_GET_PRE_SEND_DATA
can be used to manipulate the server response before object data is sent to Pimcore Backend UI when opening the detail
view of an Pimcore object.
Imagine following use case:
Products (stored as Pimcore objects) are organized in a certain hie... | Showing Custom Layouts Based on Object Data | [
-0.22142677009105682,
-0.2471795231103897,
-0.041670627892017365,
0.7237081527709961,
-0.13102862238883972,
-0.5809808373451233,
0.08472693711519241,
0.25894391536712646,
-0.3987782597541809,
0.05572141334414482,
-0.04712315648794174,
0.39463284611701965,
-0.09305577725172043,
0.4173312783... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Using_Tags_for_Filtering#using-pimcore-tags-for-filtering-in-frontend | Using Pimcore Tags for Filtering in Frontend
The Pimcore Tags functionality is primarily designed
as Pimcore Backend UI functionality for tagging and filtering elements. Nevertheless sometimes it can be quite useful to implement custom frontend filtering functionality based on the Pimcore
Tags.
Following code snippets... | Using Pimcore Tags for Filtering in Frontend | [
-0.112834632396698,
-0.337857186794281,
-0.2469164878129959,
-0.07413312792778015,
0.016432713717222214,
-0.3962380886077881,
0.12378579378128052,
0.05807627737522125,
0.10452768951654434,
-0.035681433975696564,
-0.3854203522205353,
0.3907833993434906,
0.13440611958503723,
0.49106585979461... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Using_Tags_for_Filtering#preparing-data-for-template | Preparing Data for Template
Preparation of data for your template strongly depends on our template and how you want to visualize the tag hierarchy.
For example you can build a tag tree based on bootstrap treeview.
To do so you can use something similar to following snippets:
<?php
//prepare data for template in y... | Preparing Data for Template | [
-0.21207408607006073,
-0.26324787735939026,
-0.25815141201019287,
0.3274134397506714,
0.10671583563089371,
-0.1880146563053131,
-0.02958337962627411,
0.46180298924446106,
0.14322827756404877,
0.1667536199092865,
-0.3092506229877472,
0.42430973052978516,
0.026769908145070076,
0.355866640806... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Using_Tags_for_Filtering#filtering-elements-based-on-tags | Filtering Elements based on Tags
For filtering elements based on tags some advanced queries on the element listing are necessary. Have a look at the following example
for filtering and asset listing. Listings for other elements work the same way.
Important to know:
Tags and their hierarchy are stored in the table tags... | Filtering Elements based on Tags | [
-0.07445616275072098,
-0.2475569099187851,
-0.2781916558742523,
0.26968300342559814,
-0.007219288498163223,
-0.39700374007225037,
0.004582355730235577,
0.48021551966667175,
0.13054226338863373,
0.04309972748160362,
-0.4146159589290619,
0.33390945196151733,
-0.006091360934078693,
0.33639523... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Working_With_Runtime_Cache#working-with-runtime-cache | Working With Runtime Cache
Pimcore heavily uses runtime cache to cache API results for performance reasons. However, it is very crucial to understand that how to deal with cached results so that correct data should utilized from the API. Let's take few examples to understand similar situations:
//Delete item from the l... | Working With Runtime Cache | [
-0.2230699211359024,
0.14560538530349731,
-0.20997922122478485,
0.36811915040016174,
-0.13819673657417297,
-0.2204398810863495,
0.11040002852678299,
0.07619905471801758,
0.011141009628772736,
-0.005145569331943989,
-0.13232000172138214,
0.38951221108436584,
0.2987489402294159,
-0.158529952... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice#best-practice | Best Practice
:::info
Please note that due to the updating of this part of the documentation, some information is only valid for previous versions of Pimcore.
:::
First of all, Pimcore is more or less a standard Symfony application, so most of the Symfony
best-practices also apply for Pimcore.
It's highly recommended t... | Best Practice | [
0.032121025025844574,
-0.1388741433620453,
-0.10533042997121811,
-0.10904081165790558,
-0.25900283455848694,
-0.46321791410446167,
0.18475346267223358,
-0.12604738771915436,
-0.46918344497680664,
0.21464979648590088,
0.009538953192532063,
0.33794161677360535,
0.3336273729801178,
-0.1155828... |
https://pimcore.com/docs/platform//Pimcore#pimcore | Pimcore
| Pimcore | [
-0.3872295320034027,
-0.4330748915672302,
-0.21946707367897034,
0.1477033793926239,
0.10507593303918839,
-0.42271530628204346,
0.006459968630224466,
-0.14874570071697235,
-0.49566784501075745,
0.32509011030197144,
-0.1847187578678131,
0.5597527623176575,
0.06944258511066437,
0.235473394393... |
https://pimcore.com/docs/platform//Pimcore#title:-core-framework | title: Core Framework | title: Core Framework | [
-0.08561637252569199,
-0.3776698708534241,
-0.3761584460735321,
0.06489147245883942,
0.10059083998203278,
0.12059592455625534,
-0.2620745003223419,
-0.04634246230125427,
0.025492703542113304,
0.22039231657981873,
-0.13184185326099396,
0.20028676092624664,
-0.07894351333379745,
0.0926826521... |
https://pimcore.com/docs/platform//Pimcore#pimcore-core-framework-documentation | Pimcore Core Framework Documentation
This documentation section provides all information you need to use the Core Framework of Pimcore.
We've aimed this part of the documentation at a developer's audience.
Pimcore provides a fully flexible and extendable platform for managing and exploiting data of any type. The Core... | Pimcore Core Framework Documentation | [
0.006855409126728773,
-0.4321078658103943,
-0.2356909215450287,
0.2276696264743805,
0.01687672920525074,
-0.09922594577074051,
0.051087770611047745,
-0.19718994200229645,
-0.21250754594802856,
0.016567766666412354,
-0.3024772107601166,
0.33620503544807434,
-0.07838417589664459,
0.336236327... |
https://pimcore.com/docs/platform//Pimcore#documentation-overview | Documentation Overview
The Core Framework documentation is divided into three sections that aim to guide the reader through its first use of the platform:
See the Getting Started section for an overview of the Core Framework or information about the installation process and the MVC pattern integration within Pimcore.
... | Documentation Overview | [
-0.08782552182674408,
-0.5935690999031067,
-0.16794873774051666,
0.2803858518600464,
-0.005804011598229408,
0.06616883724927902,
-0.220877543091774,
-0.20111863315105438,
-0.5229097008705139,
0.07231149077415466,
-0.23149093985557556,
0.40242767333984375,
0.4230968654155731,
-0.01186180766... |
https://pimcore.com/docs/platform//Pimcore#getting-started | Getting Started
Overview
Getting Started
MVC
| Getting Started | [
-0.03146551176905632,
-0.2608869969844818,
-0.31361210346221924,
-0.10203561931848526,
0.32302433252334595,
-0.08475780487060547,
0.09670422226190567,
0.014220400713384151,
-0.11142885684967041,
-0.14333878457546234,
0.18458904325962067,
-0.182977557182312,
0.26604509353637695,
0.443075746... |
https://pimcore.com/docs/platform//Pimcore#element-types | Element Types
Documents - Managing Web Pages
Assets - Media Library / Digital Asset Management
Objects - Custom Data Models / Entities, PIM / MDM
| Element Types | [
0.08655554801225662,
-0.30841127038002014,
-0.33462202548980713,
0.044678013771772385,
0.16348515450954437,
0.12743298709392548,
0.4221830666065216,
0.07710584998130798,
0.052279695868492126,
-0.06289950013160706,
-0.15617762506008148,
0.028466174378991127,
-0.03453628346323967,
0.59054428... |
https://pimcore.com/docs/platform//Pimcore#platform-topics | Platform Topics
Multilanguage & Localization
Workflow Management
Tools & Features
Development Tools & Details
Extending & Advanced Topics
Deployment
Administration
Installation & Upgrade
| Platform Topics | [
0.09295603632926941,
-0.701572597026825,
-0.4010835289955139,
0.10132575035095215,
0.13593196868896484,
0.2090495377779007,
0.23630718886852264,
-0.01518318336457014,
-0.053885478526353836,
0.08392117917537689,
0.051704470068216324,
0.18367208540439606,
0.10926271229982376,
0.3390823602676... |
https://pimcore.com/docs/platform//Pimcore#additional-resources-for-getting-started-with-pimcore | Additional resources for getting started with Pimcore
Pimcore Demo Application: See Pimcore in action and also use it as a blueprint application
for your own implementations.
Pimcore Academy: The training platform Pimcore Academy offers on-demand video courses
about many Pimcore topics.
| Additional resources for getting started with Pimcore | [
-0.1443050503730774,
-0.2943444550037384,
-0.2159171998500824,
-0.03439027816057205,
-0.11465905606746674,
-0.0797920823097229,
0.30303192138671875,
-0.17087364196777344,
-0.2977280914783478,
0.08711126446723938,
0.020754657685756683,
0.3108779788017273,
0.019082773476839066,
0.22028239071... |
https://pimcore.com/docs/platform//Platform_Version/Setup#setup-and-working-with-platform-versions | Setup and working with Platform Versions
On technical level, the Platform Version comes as a composer dependency and can be added to the projects composer.json. | Setup and working with Platform Versions | [
-0.3133746385574341,
-0.2532382011413574,
-0.2485053986310959,
-0.1268509477376938,
0.11944123357534409,
-0.2717791497707367,
0.12393420189619064,
-0.1264835149049759,
-0.20060618221759796,
0.3885880708694458,
0.11278075724840164,
0.5979182720184326,
-0.2511335611343384,
0.1986719518899917... |
https://pimcore.com/docs/platform//Platform_Version/Setup#setup-platform-version | Setup Platform Version | Setup Platform Version | [
-0.32727181911468506,
-0.5568167567253113,
-0.20254859328269958,
-0.16879811882972717,
0.2739616632461548,
-0.0438385009765625,
0.2776954770088196,
0.01627637818455696,
-0.060192547738552094,
0.11110527813434601,
0.2568248510360718,
0.33499157428741455,
-0.17000147700309753,
0.215489998459... |
https://pimcore.com/docs/platform//Platform_Version/Setup#setup-with-existing-project | Setup with existing project
Use following steps to setup Pimcore Platform Version in an existing project:
Add Pimcore enterprise repository to project and setup authentication token (if not already done).
Install platform version via composer require pimcore/platform-version and follow steps described
below to instal... | Setup with existing project | [
-0.5151544809341431,
-0.19111882150173187,
-0.18310852348804474,
-0.011863093823194504,
-0.03422640264034271,
-0.30074819922447205,
0.16320013999938965,
-0.16291913390159607,
-0.33010751008987427,
0.2189536690711975,
-0.13113556802272797,
0.7165656685829163,
-0.015429393388330936,
0.433691... |
https://pimcore.com/docs/platform//Platform_Version/Setup#setup-with-new-project | Setup with new project
Use following steps to setup Pimcore Platform Version for a new project:
Get skeleton via composer create-project pimcore/skeleton my-project.
Rename composer.enterprise.json to composer.json (overwrite existing).
Add/update your enterprise repository to the composer.json with composer config re... | Setup with new project | [
-0.4532930254936218,
0.019752120599150658,
-0.17080757021903992,
-0.038564763963222504,
0.005436623003333807,
-0.28526121377944946,
0.13566187024116516,
-0.07349499315023422,
-0.2638951539993286,
0.19097045063972473,
-0.2250550240278244,
0.537141740322113,
0.04248054325580597,
0.3533717393... |
https://pimcore.com/docs/platform//Platform_Version/Setup#working-with-platform-version | Working with Platform Version
Once Pimcore Platform Version is set up, you can add included Pimcore modules with the matching version and update Pimcore
modules installed in the project. | Working with Platform Version | [
-0.4103817641735077,
-0.28441062569618225,
-0.25048258900642395,
-0.024118447676301003,
-0.02023075334727764,
-0.29660314321517944,
0.2444930225610733,
0.12167703360319138,
-0.3501107096672058,
0.1917063593864441,
-0.11683086305856705,
0.6162751913070679,
0.0017013181932270527,
0.283700376... |
https://pimcore.com/docs/platform//Platform_Version/Setup#install-tracked-pimcore-modules | Install tracked Pimcore modules
Use following command to install additional Pimcore modules to the project: composer require pimcore/<MODULE>.
Eventually adding :* as version contraint helps if composer doesn't find a matching version of the module.
| Install tracked Pimcore modules | [
-0.5511749386787415,
-0.13152971863746643,
-0.19399641454219818,
0.048005178570747375,
-0.015453490428626537,
-0.2794235944747925,
0.126897394657135,
0.09889636188745499,
-0.24849270284175873,
0.4131779074668884,
0.05000469833612442,
0.560003936290741,
-0.16971325874328613,
0.1628212332725... |
https://pimcore.com/docs/platform//Platform_Version/Setup#update-pimcore-modules | Update Pimcore modules | Update Pimcore modules | [
-0.2016475796699524,
-0.30544301867485046,
-0.28786683082580566,
0.15218837559223175,
0.08029233664274216,
-0.14137817919254303,
0.09451491385698318,
0.0032136773224920034,
-0.2788398563861847,
0.11152855306863785,
-0.17227467894554138,
0.45511218905448914,
0.034929390996694565,
0.11461457... |
https://pimcore.com/docs/platform//Platform_Version/Setup#update-pimcore-modules-to-new-bugfix-versions | Update Pimcore modules to new bugfix versions
Bugfix versions of Pimcore modules can be installed within a Platform Version via composer defaults.
composer update will install most up-to-date bugfix versions of all tracked Pimcore modules. | Update Pimcore modules to new bugfix versions | [
-0.4468117356300354,
-0.11954871565103531,
-0.20280447602272034,
0.0003373856598045677,
-0.15213368833065033,
-0.10529256612062454,
-0.03512771055102348,
0.18682315945625305,
-0.15664896368980408,
0.06040318310260773,
-0.08301076292991638,
0.5598809123039246,
0.07047964632511139,
0.1016467... |
https://pimcore.com/docs/platform//Platform_Version/Setup#update-to-new-platform-version | Update to new Platform Version
To update to a new Pimcore Platform version, use the command composer update pimcore/platform-version:2023.1.
Eventually adding pimcore/* is necessary for composer to resolve pimcore repository versions properly.
| Update to new Platform Version | [
-0.5487850308418274,
-0.09962546825408936,
-0.20026743412017822,
-0.04904557392001152,
-0.0004989767330698669,
-0.2242804318666458,
-0.07428291440010071,
0.20471301674842834,
-0.5333573222160339,
0.3865034282207489,
-0.009477265179157257,
0.5621735453605652,
0.06987525522708893,
0.06156549... |
https://pimcore.com/docs/platform//Platform_Version/Release_Notes/2023.1#release-2023.1 | Release 2023.1
Here you will find all the important new features and release notes of the Platform Version 2023.1 release. | Release 2023.1 | [
-0.2264663428068161,
-0.40876340866088867,
-0.2183057814836502,
-0.15597501397132874,
-0.10110776871442795,
-0.19072173535823822,
0.05716000869870186,
0.16844749450683594,
-0.4736872911453247,
0.22639331221580505,
0.1691179871559143,
0.37183287739753723,
-0.20194150507450104,
0.48118194937... |
https://pimcore.com/docs/platform//Platform_Version/Release_Notes/2023.1#important-notes | Important Notes
This release is a major release and contains Pimcore Core Framework 11 as well as updates for all the core extensions to be compatible. | Important Notes | [
-0.47927093505859375,
-0.30205240845680237,
-0.2767031192779541,
0.07198410481214523,
-0.1680031269788742,
-0.34778499603271484,
-0.38554850220680237,
0.22320449352264404,
-0.25668495893478394,
0.11052430421113968,
-0.244159534573555,
0.4185744524002075,
-0.0792415589094162,
0.355305284261... |
https://pimcore.com/docs/platform//Platform_Version/Release_Notes/2023.1#most-important-new-features-and-improvements | Most Important New Features and Improvements
For Pimcore Core Framework, Version 11 is all about:
Advancing code quality and structure.
Updating third-party dependencies of Pimcore.
Refactoring to reduce technical debt.
And it also adds some features like:
An abstraction layer for our WYSIWYG editor that allows you ... | Most Important New Features and Improvements | [
-0.35512152314186096,
-0.3394748270511627,
-0.17976747453212738,
0.08547551184892654,
-0.3550145626068115,
-0.0071015870198607445,
-0.5402200222015381,
0.3379395008087158,
-0.4355791509151459,
0.21816422045230865,
-0.12544456124305725,
0.3877183198928833,
0.06665767729282379,
0.17381291091... |
https://pimcore.com/docs/platform//Platform_Version/Release_Notes/2023.1#upgrade-notes | Upgrade Notes
Before updating, have a look at all the upgrade notes relevant to your system:
Pimcore Core Framework Upgrade Guide
and Upgrade Notes
Portal Engine
Datahub
Datahub File Export
Datahub Simple Rest API
Headless Documents
OpenId Connect
Statistics Explorer
Customer Management Framework
Adv... | Upgrade Notes | [
-0.4657425880432129,
0.0027843264397233725,
-0.30646029114723206,
-0.1361764520406723,
0.08595078438520432,
-0.10320588201284409,
-0.25185656547546387,
0.14326739311218262,
-0.1571885198354721,
-0.007955548353493214,
-0.21073010563850403,
0.2923833727836609,
0.16051030158996582,
0.34644484... |
https://pimcore.com/docs/platform//Platform_Version/Release_Notes/2023.2#release-2023.2 | Release 2023.2
Here you will find all the important new features and release notes of the Platform Version 2023.2 release. | Release 2023.2 | [
-0.21599991619586945,
-0.33422040939331055,
-0.2394961714744568,
-0.1349785178899765,
-0.1599969118833542,
-0.22508063912391663,
-0.029415510594844818,
0.14117014408111572,
-0.4794416129589081,
0.1323903501033783,
0.1462361365556717,
0.3306766450405121,
-0.17953909933567047,
0.428867578506... |
https://pimcore.com/docs/platform//Platform_Version/Release_Notes/2023.2#most-important-new-features | Most Important New Features | Most Important New Features | [
-0.13589447736740112,
-0.6284942030906677,
-0.40876027941703796,
-0.19212210178375244,
-0.12054698169231415,
0.1068965271115303,
-0.001290800399146974,
0.13102203607559204,
0.038780633360147476,
0.013384105637669563,
0.040860895067453384,
0.10309416055679321,
-0.16412746906280518,
0.435506... |
https://pimcore.com/docs/platform//Platform_Version/Release_Notes/2023.2#data-quality-management | Data Quality Management
A new Pimcore extension that allows to compute a data quality score for your Data Objects based on customized rules and visualize your data quality score in the Data Objects editor, grid and/or tree.
More Details see Data Quality Management Documentation. | Data Quality Management | [
-0.3804348111152649,
-0.11273931711912155,
-0.1433051973581314,
0.12635305523872375,
-0.10858048498630524,
-0.24344047904014587,
-0.20214439928531647,
-0.011592351831495762,
-0.6395444869995117,
0.3468078374862671,
0.0033508548513054848,
0.25009340047836304,
0.015721319243311882,
0.2722238... |
https://pimcore.com/docs/platform//Platform_Version/Release_Notes/2023.2#bookmark-lists | Bookmark Lists
As part of the new Backend Power Tools Pimcore extension, the Bookmark Lists allow to create bookmark lists for Assets, Data Objects, Documents and so organize content needed on a regular base.
More Details see Bookmark Lists Documentation. | Bookmark Lists | [
-0.07782545685768127,
-0.296970009803772,
-0.26351115107536316,
-0.08350928872823715,
-0.22041502594947815,
0.10321249812841415,
0.13453947007656097,
0.1672503501176834,
0.03845886141061783,
-0.09402047842741013,
-0.15288180112838745,
0.3555837869644165,
-0.09520073235034943,
0.15102042257... |
https://pimcore.com/docs/platform//Platform_Version/Release_Notes/2023.2#pimcore-datahub-webhooks | Pimcore Datahub Webhooks
A new Pimcore extension for the Datahub that allows to send requests to configured subscribers for a variation of events happening in Pimcore (adding, updating, deleting data, workflow transistions).
More Details see Datahub Webhooks Documentation. | Pimcore Datahub Webhooks | [
-0.1342165321111679,
-0.34318870306015015,
-0.12761755287647247,
-0.2003278285264969,
-0.472480833530426,
-0.10257117450237274,
0.25046640634536743,
-0.07664411514997482,
-0.02921866439282894,
0.008542768657207489,
-0.4658031761646271,
0.37532469630241394,
0.006533291656523943,
0.351306051... |
https://pimcore.com/docs/platform//Platform_Version/Release_Notes/2023.2#upgrade-notes | Upgrade Notes
Before updating, also have a look at the following upgrade notes if relevant to your system:
Consider the upgrade of Portal Engine to version 3.1.0, which will result in a Elastic Search index structure change. Details see corresponding upgrade notes.
| Upgrade Notes | [
0.03668107092380524,
-0.005005481652915478,
-0.2920660376548767,
-0.15688656270503998,
-0.03206195682287216,
-0.15036985278129578,
-0.1610231250524521,
0.3283209800720215,
-0.17413873970508575,
-0.02064269222319126,
-0.037730444222688675,
0.24915459752082825,
-0.07699223607778549,
0.083807... |
https://pimcore.com/docs/platform//Platform_Version/Release_Notes#release-notes | Release Notes
Following list inlcudes all available Platform Version release notes:
2023.1
2023.2
| Release Notes | [
-0.2580965757369995,
-0.4960262179374695,
-0.37610551714897156,
-0.11061114072799683,
0.012195511721074581,
-0.25426483154296875,
0.07709494978189468,
0.11985202133655548,
-0.27693748474121094,
0.295845627784729,
0.1688801646232605,
0.30748698115348816,
-0.21245114505290985,
0.349818527698... |
https://pimcore.com/docs/platform//Platform_Version#platform_version | Platform_Version
| Platform_Version | [
-0.3346550464630127,
-0.6847488880157471,
-0.31270459294319153,
-0.04513155296444893,
0.35740259289741516,
-0.2113264948129654,
0.25500723719596863,
0.1581542193889618,
-0.05304751172661781,
0.09062568098306656,
0.35945120453834534,
0.2858172357082367,
-0.16094346344470978,
0.1236070990562... |
https://pimcore.com/docs/platform//Platform_Version#title:-platform-version | title: Platform Version | title: Platform Version | [
-0.04040224105119705,
-0.5652815699577332,
-0.3205263316631317,
-0.2653757929801941,
0.2526592016220093,
-0.034380532801151276,
0.365067720413208,
-0.044595230370759964,
-0.07193625718355179,
0.26423561573028564,
0.1328338086605072,
0.25178006291389465,
-0.21626999974250793,
-0.02998814359... |
https://pimcore.com/docs/platform//Platform_Version#pimcore-platform-version | Pimcore Platform Version
The Pimcore platform consists of the Pimcore Core Framework and Core Extensions that can be added for your needs.
Each module (Core Framework and the Core Extensions) has its own repository, its own version and is released indepedently.
The dependencies and compatibilities of the modules are de... | Pimcore Platform Version | [
-0.23413881659507751,
-0.4998963177204132,
-0.3049609363079071,
0.04194241017103195,
-0.0822463110089302,
-0.2052365094423294,
0.03491406887769699,
-0.023044126108288765,
-0.38400617241859436,
0.1580776870250702,
-0.17952856421470642,
0.509782075881958,
-0.01786666363477707,
0.051088515669... |
https://pimcore.com/docs/platform//Platform_Version#benefits-in-a-nutshell | Benefits in a nutshell
Set of specific versions of all Pimcore modules which work together.
Explicitly tested and verifyed by Pimcore.
Combined release notes of all modules for every Platform Version release.
Pimcore documentation is based on Platform Version.
| Benefits in a nutshell | [
-0.3541165888309479,
-0.47748199105262756,
-0.22658880054950714,
0.04701457545161247,
-0.30029940605163574,
0.0006119640311226249,
0.12840794026851654,
0.1204603761434555,
-0.3622516691684723,
0.18760493397712708,
-0.06555753946304321,
0.5880208015441895,
-0.027961185202002525,
0.060323353... |
https://pimcore.com/docs/platform//Platform_Version#versioning-schema-and-release-cycles | Versioning Schema and Release Cycles
The versioning schema follows semantic versioning and is Major.Minor (e.g. 2023.1). | Versioning Schema and Release Cycles | [
-0.06527441740036011,
-0.4567134976387024,
-0.13018615543842316,
-0.20602115988731384,
-0.08843734115362167,
-0.3098900020122528,
-0.06952390819787979,
-0.03930152207612991,
0.16891352832317352,
0.08771812170743942,
0.12326710671186447,
-0.10397113859653473,
-0.2749415338039398,
0.48651584... |
https://pimcore.com/docs/platform//Platform_Version#key-rules: | Key rules:
Update major versions of modules
Major module version updates are only allowed with a major Platform Version.
Major Platform Version will be released once per year (2023.1, 2024.1, 2025.1, ...).
Update minor versions of modules
Minor module versions will be updated with new minor Platform Versions.
Up... | Key rules: | [
-0.3257678747177124,
-0.2964368462562561,
-0.2021765559911728,
0.07770383358001709,
0.002243609633296728,
-0.36784058809280396,
-0.03648911789059639,
-0.12762822210788727,
-0.14814983308315277,
0.07996714860200882,
-0.018203994259238243,
0.32358425855636597,
0.11871358007192612,
0.08869846... |
https://pimcore.com/docs/platform//Platform_Version#further-reads | Further Reads
Setup and working with Platform Versions
Release Notes
| Further Reads | [
-0.06263808906078339,
-0.3492620289325714,
-0.22260427474975586,
0.1841125339269638,
0.22909481823444366,
-0.022110316902399063,
0.08378949761390686,
-0.1494065523147583,
-0.10355529934167862,
0.14507600665092468,
0.04611803963780403,
0.262778103351593,
-0.06825391203165054,
0.067758806049... |
https://pimcore.com/docs/platform//Portal_Engine/Installation/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//Portal_Engine/Installation/Upgrade#upgrade-to-3.1.0 | Upgrade to 3.1.0
(only relevant if not already upgraded to version 2.6.0) [Indexing] - Filters based on the asset metadata with relations
to objects which have localized fields are now indexed with all the localized values. The index structure is therefore
changed (from single string to array) and it is necessary to r... | Upgrade to 3.1.0 | [
0.023270491510629654,
-0.04733877256512642,
-0.2088339775800705,
0.02548813819885254,
0.20182618498802185,
-0.1745586395263672,
0.28688666224479675,
0.4926292598247528,
0.06434590369462967,
0.2627556622028351,
-0.3091595470905304,
0.46870875358581543,
-0.011256374418735504,
-0.013553309254... |
https://pimcore.com/docs/platform//Portal_Engine/Installation/Upgrade#upgrade-to-3.0.0 | Upgrade to 3.0.0
BEFORE UPGRADE: First upgrade to last 2.5 version and make sure all migrations are executed properly.
BEFORE UPGRADE: Upgrade directly to 3.1.0 if you already upgraded to 2.6 versions.
BEFORE UPGRADE: Activate Generate Type Declarations for PortalUser and PortalUserGroup classes and save them to
re... | Upgrade to 3.0.0 | [
-0.13671721518039703,
0.03863406926393509,
-0.18947339057922363,
-0.037056099623441696,
-0.030896086245775223,
-0.2287817746400833,
-0.07990997284650803,
0.3152904808521271,
-0.5389326810836792,
0.024726852774620056,
-0.1265762448310852,
0.4293363392353058,
0.07049819082021713,
0.127342671... |
https://pimcore.com/docs/platform//Portal_Engine/Installation/Upgrade#upgrade-to-2.6.0 | Upgrade to 2.6.0
[Indexing] - Filters based on the asset metadata with relations to objects which have localized fields are now indexed with all the localized values.
The index structure is therefore changed (from single string to array) and it is necessary to run the migration that recreates all the indexes after upd... | Upgrade to 2.6.0 | [
-0.016241051256656647,
0.18864478170871735,
-0.22853823006153107,
0.08100907504558563,
0.2395266741514206,
-0.20725734531879425,
0.253732293844223,
0.47687670588493347,
0.14941948652267456,
0.18532422184944153,
-0.36876100301742554,
0.383850634098053,
-0.003306375117972493,
-0.204646497964... |
https://pimcore.com/docs/platform//Portal_Engine/Installation/Upgrade#upgrade-to-2.3 | Upgrade to 2.3
From now on, out of the box Statistics Explorer data sources and trackers use same ES configuration as portal engine itself.
If you want to change that, you need to overwrite service definition of pimcore.portal_engine.statistics_explorer.client_factory
| Upgrade to 2.3 | [
-0.40410569310188293,
0.23984195291996002,
-0.006251436658203602,
0.07357455044984818,
0.19516190886497498,
-0.304816871881485,
0.05319662019610405,
0.0042951335199177265,
-0.42641481757164,
0.19418549537658691,
-0.13329803943634033,
0.4513241648674011,
0.33433255553245544,
0.3746227622032... |
https://pimcore.com/docs/platform//Portal_Engine/Installation/Upgrade#upgrade-to-2.1.0 | Upgrade to 2.1.0
Execute all migrations of the bundle.
| Upgrade to 2.1.0 | [
-0.30486321449279785,
-0.22517378628253937,
-0.22189147770404816,
-0.0008420550730079412,
0.09858084470033646,
0.024963976815342903,
0.12212830781936646,
0.3841570317745209,
-0.15013310313224792,
0.192816361784935,
-0.02512246184051037,
0.34163495898246765,
-0.2216414511203766,
0.146467104... |
https://pimcore.com/docs/platform//Portal_Engine/Installation/Upgrade#upgrade-to-2.0.0 | Upgrade to 2.0.0
First upgrade to last 1.x version and make sure all migrations are executed properly.
Migrate Pimcore to Pimcore 6.9
Migrate controller references to new naming scheme (e.g. ), for example by using migration command
bin/console migration:controller-reference
Add following line to your firewalls confi... | Upgrade to 2.0.0 | [
-0.21513599157333374,
0.05608111992478371,
-0.16847170889377594,
-0.24387547373771667,
0.033951226621866226,
-0.2621743381023407,
0.08086804300546646,
0.14305751025676727,
-0.2103106677532196,
0.005453310441225767,
-0.2620169520378113,
0.5293335318565369,
0.17170172929763794,
0.09841142594... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#installation-of-portal-engine | Installation of Portal Engine
The installation of the Portal Engine follows standard composer procedures.
There are a couple of things to consider though. | Installation of Portal Engine | [
-0.2917722463607788,
0.2828572392463684,
-0.14771448075771332,
0.13261884450912476,
-0.12744282186031342,
-0.21358071267604828,
-0.14789119362831116,
-0.13620337843894958,
-0.452583909034729,
-0.02868729829788208,
-0.09766999632120132,
0.3091564476490021,
-0.033221010118722916,
0.084344372... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#prerequisites | Prerequisites | Prerequisites | [
-0.1466781347990036,
-0.381072461605072,
-0.31387925148010254,
-0.1381148248910904,
0.005634434521198273,
0.3179437220096588,
-0.015032433904707432,
0.06735622882843018,
-0.05055241659283638,
0.041386064141988754,
0.2557336390018463,
-0.27533799409866333,
0.051568225026130676,
-0.007126048... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#system-requirements | System Requirements
Before installing the Portal Engine, please be aware of the following requirements:
PHP >= 8.0
Pimcore >= 10.5
Elasticsearch 8
Mercure (optional for Pimcore Direct Edit)
MySQL/MariaDB innodb_default_row_format option needs to be set to "DYNAMIC" (which is the default value)
| System Requirements | [
-0.38492903113365173,
-0.041969992220401764,
-0.17985692620277405,
-0.0189296156167984,
-0.1348443180322647,
-0.09834010899066925,
-0.17326731979846954,
0.2640911340713501,
-0.30971190333366394,
-0.17510391771793365,
-0.07391346246004105,
0.38600385189056396,
0.08413755148649216,
0.0554498... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#required-bundles | Required Bundles
The Portal Engine requires a couple of bundles which need to be configured and installed first:
Enterprise Metadata Bundle
Statistics Explorer
Direct Edit (optional)
OpenId Connect (optional, if you like to use SSO via OpenID Connect)
Admin UI Classic Bundle (if using Pimcore 11 and it is not i... | Required Bundles | [
-0.3866218626499176,
0.11901899427175522,
-0.01752711646258831,
-0.08606461435556412,
0.04635290428996086,
0.03706586733460426,
0.09017707407474518,
0.09293194115161896,
-0.36752358078956604,
-0.13556282222270966,
0.014872599393129349,
0.3617710471153259,
0.48111748695373535,
0.41575491428... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#installation | Installation
As soon as all prerequisites are met, installation follows standard composer and Pimcore procedure, depending on the version you're working with: | Installation | [
-0.5349111557006836,
-0.030315198004245758,
-0.23656797409057617,
0.02533436194062233,
-0.12318526208400726,
-0.3093731105327606,
-0.27911844849586487,
-0.23766671121120453,
-0.36672577261924744,
0.22293886542320251,
0.009695952758193016,
0.3698367476463318,
-0.08706972748041153,
0.1489721... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#for-pimcore->=-10.5 | For Pimcore >= 10.5
Follow the three steps below:
Install the required dependencies:
composer require pimcore/portal-engine
Make sure the bundle is enabled in the config/bundles.php file. The following lines should be added:
use Pimcore\Bundle\PortalEngineBundle\PimcorePortalEngineBundle;
// ...
return [
/... | For Pimcore >= 10.5 | [
-0.4529271423816681,
0.03956003859639168,
-0.16116872429847717,
0.0690947026014328,
0.06000232696533203,
-0.18570421636104584,
0.027242043986916542,
0.09370924532413483,
-0.45667654275894165,
0.05098600685596466,
-0.07384046167135239,
0.5138786435127258,
0.17315666377544403,
0.173356950283... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#for-older-versions | For Older Versions
Please run the following commands instead:
composer require pimcore/portal-engine
# if on Pimcore 10.5 enable bundle before installing
bin/console pimcore:bundle:enable PimcorePortalEngineBundle
bin/console pimcore:bundle:install PimcorePortalEngineBundle
| For Older Versions | [
-0.5302359461784363,
0.06061771139502525,
-0.16636990010738373,
-0.018666647374629974,
0.0861433669924736,
-0.1622297316789627,
0.06345531344413757,
-0.009386328049004078,
-0.47966381907463074,
0.059763092547655106,
-0.08258692920207977,
0.5318684577941895,
0.1992131918668747,
0.1022626906... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#setup-elasticsearch | Setup Elasticsearch
Next step is to connect Elasticsearch to the Portal Engine. Elasticsearch client configuration takes place via
Pimcore Elasticsearch Client Bundle and has two parts:
Configuring an Elasticsearch client.
Define the client to be used by Portal Engine.
# Configure an Elasticsearch client
pimcore_ela... | Setup Elasticsearch | [
-0.3471255302429199,
0.22770409286022186,
-0.12763644754886627,
-0.2749261260032654,
-0.012919137254357338,
-0.2424156665802002,
0.025760363787412643,
-0.05216749757528305,
-0.3529185950756073,
0.00411654356867075,
-0.14778566360473633,
0.3871263861656189,
0.15742728114128113,
0.2353999167... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#define-index-prefix | Define Index Prefix
To avoid duplicate names or index interferences in Elasticsearch, it is necessary to define an index name prefix, which is added to all Elasticsearch indices created by Portal Engine. Default one is portalengine_.
This can be done by defining following parameter:
parameters:
pimcore_portal_engi... | Define Index Prefix | [
-0.07902368158102036,
-0.29270029067993164,
-0.15439006686210632,
-0.09605659544467926,
0.07752633094787598,
-0.19931946694850922,
0.09736911952495575,
0.23658570647239685,
-0.13859547674655914,
0.20881474018096924,
-0.07417358458042145,
0.31417664885520935,
0.1785239726305008,
-0.00490380... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#configure-symfony-firewall | Configure Symfony firewall
To configure the Symfony firewall for the portals, add following line to your firewalls configuration
in the security.yml of your app after the pimcore_admin firewall.
security:
firewalls:
pimcore_admin:
# ...
portal_engine: '%pimcore_portal_engine.firewall_se... | Configure Symfony firewall | [
-0.18909695744514465,
-0.007373762782663107,
-0.08610427379608154,
-0.18400074541568756,
0.08374245464801788,
-0.35203444957733154,
0.3673761487007141,
-0.20169061422348022,
-0.1701831817626953,
-0.05393499135971069,
-0.3621797263622284,
0.31099259853363037,
0.3551549017429352,
0.167855203... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#commands-after-installation | Commands after Installation
It is recommended to run following commands after installation (at least) once:
./bin/console portal-engine:update:index-recreate
./bin/console portal-engine:update:process-index-queue --processes=5
| Commands after Installation | [
-0.32034310698509216,
0.0013803819892928004,
-0.18148395419120789,
-0.12093356996774673,
0.08071880787611008,
0.0167177002876997,
0.02332054078578949,
0.05812612548470497,
-0.19587203860282898,
-0.10208514332771301,
0.01896863430738449,
0.3850933313369751,
0.289365291595459,
0.028156345710... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#follow-up-configuration | Follow-up Configuration
Portal Engine needs the following commands up and running permanently or regularly. | Follow-up Configuration | [
-0.2401571273803711,
0.058452531695365906,
-0.1827044039964676,
-0.2602289617061615,
0.05272936820983887,
-0.06826236844062805,
0.1589505970478058,
0.09197456389665604,
-0.38249632716178894,
-0.11500599980354309,
0.06843432039022446,
0.20891737937927246,
0.13477355241775513,
0.362341225147... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#index-updating-queue-cronjob | Index Updating Queue Cronjob
It is necessary to update the elastic search index on a regular basis. This can be done either via a command or
via the Symfony messaging queue. | Index Updating Queue Cronjob | [
0.07532569766044617,
0.09726550430059433,
-0.19084008038043976,
-0.2561361789703369,
-0.27334263920783997,
-0.20650598406791687,
0.06461508572101593,
0.20383799076080322,
0.07740726321935654,
0.3050227463245392,
0.14613986015319824,
0.05423973873257637,
0.061840593814849854,
-0.06765708327... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#command-based | Command Based
For command based queue processing, add the following cronjob to your crontab.
# it is ok to run it once a minute as it will be locked by a Symfony lock
* * * * * php /path/to/your/app/bin/console portal-engine:update:process-index-queue
# if needed it is possible to execute this with multiple parallel p... | Command Based | [
-0.23613862693309784,
0.08266168087720871,
-0.20274750888347626,
-0.17895203828811646,
-0.21846042573451996,
-0.17024901509284973,
0.26877495646476746,
0.08209626376628876,
-0.2311205267906189,
0.14901059865951538,
0.19728291034698486,
0.3270750641822815,
0.012206515297293663,
0.0065363072... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#symfony-messenger-based | Symfony Messenger Based
For Symfony Messenger based queue processing, at least following configuration needs to be done in Symfony configuration:
pimcore_portal_engine:
messenger_queue_processing:
activated: true
If activated, the processing is kicked off automatically with the portal_engine.index_update_q... | Symfony Messenger Based | [
-0.20402531325817108,
-0.25063619017601013,
-0.1401054710149765,
-0.05510909855365753,
-0.12516750395298004,
-0.285022109746933,
0.39251354336738586,
-0.09916722029447556,
-0.023335246369242668,
0.35155659914016724,
0.07147476822137833,
0.10442222654819489,
0.10476186871528625,
0.017318122... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#messaging-queue | Messaging Queue
Set up the Symfony Messenger messaging queue like described in the
Background Processes chapter. | Messaging Queue | [
-0.08897679299116135,
-0.273825466632843,
-0.2345055341720581,
-0.23244498670101166,
-0.14301717281341553,
-0.1401975005865097,
0.4775829017162323,
-0.0999838262796402,
-0.010856563225388527,
0.21828414499759674,
-0.029185911640524864,
-0.11179864406585693,
0.12737204134464264,
-0.03059965... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#(optional)-multi-node-setup | (optional) Multi-Node setup
When setting up the Portal Engine in a multi node setup, please first follow Pimcore instructions for multi-node setup
and shared storages.
In addition to the Pimcore instructions also consider /var/tmp/portal-engine/downloads which needs to be a shared tmp
folder and can be configured via f... | (optional) Multi-Node setup | [
-0.33156195282936096,
0.014726793393492699,
-0.0878734290599823,
0.13466022908687592,
0.1362392157316208,
-0.11500263959169388,
0.12027405202388763,
0.05459589138627052,
-0.3526945114135742,
-0.07554572075605392,
-0.32564371824264526,
0.5251330733299255,
0.2506725788116455,
0.3145399987697... |
https://pimcore.com/docs/platform//Portal_Engine/Installation#style-settings-feature | Style Settings Feature
If you are using the style settings feature
the location public/var/portal-engine needs to be shared along the nodes.
It contains some configuration files for webpack setup and customized frontend builds
for portals that are using the style settings feature. | Style Settings Feature | [
-0.20704807341098785,
-0.2591341435909271,
-0.12449431419372559,
0.04855775460600853,
0.22407670319080353,
0.10696253180503845,
0.1244889497756958,
0.2551664710044861,
-0.15846467018127441,
0.07485007494688034,
0.021559173241257668,
0.36981016397476196,
0.41926151514053345,
0.3320630192756... |
https://pimcore.com/docs/platform//Portal_Engine/Administration_of_Portals/Configuration/Portal_Setup_Wizard#portal-setup-wizard | Portal Setup Wizard
The portal engine ships with a wizard to support with initial portal setup. It helps to create the initial document
structure and setting the most important settings for the portal and each added data pool. Thus, it is highly
recommended using it for starting a new portal.
Once the wizard created ... | Portal Setup Wizard | [
-0.20080533623695374,
-0.15964573621749878,
-0.04548491910099983,
0.08057813346385956,
-0.30064156651496887,
0.01360069029033184,
-0.0705290138721466,
-0.1480681449174881,
-0.36368927359580994,
-0.22342228889465332,
-0.12430370599031448,
0.07646197825670242,
0.2912651598453522,
0.161562308... |
https://pimcore.com/docs/platform//Portal_Engine/Administration_of_Portals/Configuration/Data_Pool_Configurations/Asset_Data_Pools#asset-data-pool | Asset Data Pool
The asset data pool allows integrating Pimcore assets into a portal. Configurations are available for the grid
and the detail page. | Asset Data Pool | [
-0.47343483567237854,
-0.09233744442462921,
-0.2324981540441513,
0.0084387781098485,
-0.03803658112883568,
-0.0014095330843701959,
0.22705328464508057,
0.1524689644575119,
-0.2624095380306244,
0.051592014729976654,
-0.5226160287857056,
0.32199475169181824,
0.32682672142982483,
0.2527410387... |
https://pimcore.com/docs/platform//Portal_Engine/Administration_of_Portals/Configuration/Data_Pool_Configurations/Asset_Data_Pools#grid-configuration | Grid Configuration | Grid Configuration | [
-0.12352608889341354,
-0.3884175419807434,
-0.2761545181274414,
0.2870953381061554,
0.2056916207075119,
-0.01719813607633114,
0.5987547039985657,
-0.19728320837020874,
0.2865121364593506,
0.21948663890361786,
-0.023213854059576988,
0.009160869754850864,
0.10438220202922821,
0.2023217529058... |
https://pimcore.com/docs/platform//Portal_Engine/Administration_of_Portals/Configuration/Data_Pool_Configurations/Asset_Data_Pools#workspace-definition | Workspace Definition
The workspace concept similar to the workspace concept for defining permissions of Pimcore backend users. Workspaces
define the visible content and what operations should be allowed for the data pool. The definition is based on folders,
by default nothing is visible.
| Workspace Definition | [
-0.02940448373556137,
-0.028615351766347885,
-0.21507972478866577,
-0.11764604598283768,
-0.49816185235977173,
-0.3259611129760742,
0.268037885427475,
0.24926580488681793,
-0.24719107151031494,
0.3385353088378906,
-0.24316351115703583,
-0.10438446700572968,
0.0780860185623169,
-0.012600011... |
https://pimcore.com/docs/platform//Portal_Engine/Administration_of_Portals/Configuration/Data_Pool_Configurations/Asset_Data_Pools#available-permissions | Available permissions
View: Display assets.
Download: Allow downloading assets and their metadata.
Edit: Allow editing metadata of assets.
Update: Allow updating binary data of assets and relocating asset into another folder.
Create: Allow creating new assets (= upload new assets). Target folders for relocate action n... | Available permissions | [
0.06749079376459122,
0.11133252084255219,
-0.1786283552646637,
0.1029152125120163,
-0.07530903816223145,
-0.1095731183886528,
0.15795667469501495,
0.09513763338327408,
-0.1326991319656372,
-0.11866016685962677,
-0.555664598941803,
0.014016465283930302,
-0.20610164105892181,
-0.139652073383... |
https://pimcore.com/docs/platform//Portal_Engine/Administration_of_Portals/Configuration/Data_Pool_Configurations/Asset_Data_Pools#pre-condition-service | Pre Condition Service
The pre condition service is a custom extension point that allows further restricting displayed assets of the data pool.
Services can be added with custom services, see PreCondition Service
for details. | Pre Condition Service | [
-0.044405121356248856,
-0.4742982089519501,
-0.1819600760936737,
-0.23273910582065582,
-0.17291535437107086,
-0.08369287848472595,
0.039569903165102005,
0.3015715181827545,
0.14012478291988373,
0.07569170743227005,
-0.09002283215522766,
-0.21248957514762878,
0.06451661139726639,
-0.1560182... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.