url stringlengths 50 196 | text stringlengths 3 17.2k | heading stringlengths 2 103 | embeddings list |
|---|---|---|---|
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#composer | Composer
Please visit the official install guide for Composer: https://getcomposer.org/ | Composer | [
-0.5087305307388306,
-0.08842393755912781,
-0.3105264902114868,
0.05655345320701599,
0.24588511884212494,
-0.16406939923763275,
-0.19921085238456726,
-0.05012286454439163,
-0.1439559906721115,
0.3987889289855957,
-0.03131111338734627,
0.16533291339874268,
-0.213316410779953,
-0.02820514142... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#ffmpeg | FFMPEG
Please keep in mind that many Linux/GNU distributions ship FFMPEG only with free codecs,
so they do not support commonly used video codecs such as mpeg4 and many others.
sudo apt-get install ffmpeg
| FFMPEG | [
-0.49983277916908264,
-0.18997226655483246,
-0.20282228291034698,
-0.23613214492797852,
0.3652273416519165,
-0.05028332769870758,
-0.10849282145500183,
0.27808240056037903,
-0.08348895609378815,
0.1420835554599762,
-0.08026966452598572,
0.14329974353313446,
-0.1681642383337021,
0.120561026... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#pdf-generation | PDF Generation
It's possible to either choose to install LibreOffice/Chromium or to use them via Gotenberg (Docker-powered API). | PDF Generation | [
-0.309047132730484,
-0.16621658205986023,
-0.3112258017063141,
-0.06694966554641724,
-0.10115315020084381,
-0.04224955663084984,
0.2248876541852951,
0.41164568066596985,
0.13373294472694397,
0.32744309306144714,
0.010375072248280048,
0.31064340472221375,
0.07177028059959412,
0.318444579839... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#libreoffice,-pdftotext,-inkscape,-... | LibreOffice, pdftotext, Inkscape, ...
apt-get install libreoffice libreoffice-script-provider-python libreoffice-math xfonts-75dpi poppler-utils inkscape libxrender1 libfontconfig1 ghostscript
| LibreOffice, pdftotext, Inkscape, ... | [
-0.2564851939678192,
-0.14402732253074646,
-0.20521409809589386,
0.1621195524930954,
-0.01697387732565403,
0.1040421649813652,
0.06837533414363861,
0.4374579191207886,
0.1190226599574089,
0.2789047956466675,
0.0070116762071847916,
0.24427735805511475,
0.14606477320194244,
0.452482849359512... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#chromium-(chrome-headless) | Chromium (Chrome Headless)
First of all, you need to add and install the required library via composer:
composer require chrome-php/chrome
You can then directly install and use the Chromium binary locally or use it in Docker Container, accessing it via WebSocket connection. | Chromium (Chrome Headless) | [
-0.36938440799713135,
-0.3605140447616577,
-0.27621373534202576,
-0.23170611262321472,
0.10402193665504456,
-0.0032886858098208904,
0.1659572571516037,
0.38675475120544434,
0.3397258222103119,
0.3493083417415619,
-0.0321136936545372,
0.013197395019233227,
-0.26057422161102295,
0.0708681121... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#locally | Locally
Please follow the steps on https://www.chromium.org/getting-involved/download-chromium for installing Chromium locally. | Locally | [
-0.21773125231266022,
-0.2105092853307724,
-0.27066758275032043,
-0.2318209558725357,
0.21100562810897827,
-0.13070006668567657,
0.12067361921072006,
0.1427774280309677,
0.20812982320785522,
0.2731606960296631,
-0.05168559029698372,
0.04941130429506302,
0.041418638080358505,
0.181129261851... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#docker | Docker
Add a new service as:
chrome:
image: browserless/chrome
and set accordingly:
config pimcore.chromium.uri value (e.g. ws://chrome:3000/)
web2print settings hostUrl as the Docker web server service (e.g. http://nginx:80)
| Docker | [
-0.2569904625415802,
-0.26078757643699646,
-0.1958436220884323,
-0.4763577878475189,
0.08578602969646454,
-0.08932188153266907,
0.544687032699585,
0.28898128867149353,
0.004305508453398943,
0.1848011314868927,
-0.16752572357654572,
0.2991577982902527,
0.07318945229053497,
0.195255681872367... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#gotenberg | Gotenberg
To install it, please add it in your Docker Compose services stack as https://gotenberg.dev/docs/get-started/docker-compose#quick-start.
Configure the Docker services accordingly:
pimcore.gotenberg.base_url which by default to http://gotenberg:3000
pimcore.documents.preview_url_prefix for example to nginx... | Gotenberg | [
-0.5115814805030823,
0.15554292500019073,
-0.24668718874454498,
-0.29930198192596436,
-0.12160778790712357,
-0.1892189234495163,
0.008195966482162476,
0.29107794165611267,
-0.42748695611953735,
0.3291501998901367,
-0.031273044645786285,
0.160983607172966,
0.0533529557287693,
0.081900008022... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#image-optimizers | Image Optimizers | Image Optimizers | [
-0.14792776107788086,
-0.39905381202697754,
-0.409785658121109,
0.14121413230895996,
-0.08539017289876938,
-0.2888830900192261,
0.09592752158641815,
0.12447396665811539,
-0.0540083572268486,
0.3602510690689087,
0.10366971790790558,
0.2566823363304138,
-0.19732427597045898,
-0.0349301509559... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#jpegoptim | JPEGOptim
wget https://github.com/imagemin/jpegoptim-bin/raw/main/vendor/linux/jpegoptim -O /usr/local/bin/jpegoptim
chmod 0755 /usr/local/bin/jpegoptim
| JPEGOptim | [
-0.05534149706363678,
0.009074858389794827,
-0.16584956645965576,
-0.07407670468091965,
0.09194863587617874,
-0.029323827475309372,
0.5795819759368896,
0.263676255941391,
-0.06547902524471283,
0.25876474380493164,
-0.08474185317754745,
0.28487008810043335,
-0.04441619664430618,
-0.09063467... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#pngquant | PngQuant
apt-get install pngquant
| PngQuant | [
-0.23133815824985504,
-0.012915674597024918,
-0.262696236371994,
0.191165953874588,
-0.010799446143209934,
0.021505407989025116,
0.2347090244293213,
0.22692960500717163,
-0.1426662653684616,
0.09389074146747589,
-0.03325754404067993,
-0.07926606386899948,
0.06757508218288422,
-0.1311582326... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#optipng | OptiPng
apt-get install optipng
| OptiPng | [
-0.4617290198802948,
-0.8982707858085632,
-0.22204308211803436,
-0.0917375236749649,
0.2678784728050232,
-0.14255578815937042,
-0.15742287039756775,
0.12289983034133911,
-0.20138035714626312,
0.323020339012146,
0.02917778491973877,
0.36893776059150696,
-0.04985545575618744,
-0.310898631811... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#exiftool | Exiftool
apt-get install libimage-exiftool-perl
| Exiftool | [
-0.21017390489578247,
-0.2932412922382355,
-0.12259657680988312,
0.20373879373073578,
-0.06954263895750046,
-0.08705291152000427,
-0.010811835527420044,
0.4251377582550049,
-0.2447752207517624,
0.3533133864402771,
0.039936602115631104,
-0.03455060347914696,
-0.1282893866300583,
0.104411423... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#webp | WebP
Install webp for WebP-Support
apt-get install webp
| WebP | [
-0.13781289756298065,
-0.20072685182094574,
-0.3248702585697174,
-0.1499565839767456,
-0.001383603666909039,
0.040903545916080475,
-0.0387415736913681,
0.32028254866600037,
0.1943492591381073,
0.05501303821802139,
0.10169344395399094,
0.1433780938386917,
-0.15660443902015686,
0.20967470109... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#graphviz | Graphviz
Install graphviz for Workflow
apt-get install graphviz
| Graphviz | [
-0.25786980986595154,
-0.2547668516635895,
-0.3453839123249054,
-0.17697317898273468,
0.025790685787796974,
-0.13015028834342957,
0.048135191202163696,
0.48744410276412964,
0.3099968135356903,
0.36553987860679626,
0.30099502205848694,
0.4340057373046875,
-0.12936441600322723,
0.47947189211... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Additional_Tools_Installation#check-your-installation-(requires-pimcoresystem-info-bundle-package) | Check your installation (requires pimcore/system-info-bundle package)
You can check system requirements via Admin UI Tools / System Info & Tools / System-Requirements Check menu.
Or via following CLI command:
bin/console pimcore:system:requirements:check
| Check your installation (requires pimcore/system-info-bundle package) | [
-0.549804151058197,
-0.4110870063304901,
-0.21138271689414978,
0.08276043087244034,
0.2562372386455536,
-0.1767904907464981,
-0.008522392250597477,
0.030041290447115898,
-0.10932095348834991,
0.19115889072418213,
0.06104642525315285,
0.32934489846229553,
0.09156092256307602,
0.108742378652... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Cluster_Setup#cluster-setup | Cluster Setup
To be done ... | Cluster Setup | [
-0.25885632634162903,
-0.4716479480266571,
-0.34792032837867737,
0.07877950370311737,
-0.18109486997127533,
-0.26125240325927734,
0.3284611999988556,
0.03443627059459686,
0.10772979259490967,
0.31238436698913574,
-0.0697498768568039,
0.1042073592543602,
-0.029586061835289,
0.27453199028968... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Cluster_Setup#filesystem | Filesystem
To be done ...
Do not use rsync or other nasty solutions to share the data between the application servers. | Filesystem | [
-0.0648682489991188,
-0.03166407719254494,
-0.3211137652397156,
0.052762486040592194,
-0.03742120414972305,
-0.15913817286491394,
0.15178029239177704,
0.019923781976103783,
-0.005213940516114235,
0.31753212213516235,
0.016789903864264488,
0.13815951347351074,
0.0026556209195405245,
0.14818... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#performance-best-practice-guide | Performance Best-Practice Guide
When developing a high traffic web application, it is a common practice to focus on performance measures and
incorporate changes to make the application even more performant. A highly optimized website drives more traffic
at zero additional cost and increases the user experience a lot.
T... | Performance Best-Practice Guide | [
-0.19841080904006958,
-0.28470873832702637,
-0.3219676911830902,
-0.06303262710571289,
-0.21611559391021729,
-0.24346132576465607,
-0.12169179320335388,
0.18954695761203766,
-0.13980545103549957,
0.013128779828548431,
-0.09613830596208572,
-0.011862993240356445,
0.2635331451892853,
-0.0660... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#php-8-opcache-&-jit-compiler | PHP 8 Opcache & JIT compiler
As you know, PHP is an interpreted language, which means the interpreter parses, compiles and executes
the code (opcode) everytime, when executing PHP scripts. This may result in wastage of CPU resources and
execution time. This is where the OPcache extension comes in to play:
“OPcache... | PHP 8 Opcache & JIT compiler | [
-0.35445070266723633,
-0.14518553018569946,
-0.24399980902671814,
0.12585653364658356,
-0.08059938251972198,
0.01779799722135067,
0.15044499933719635,
0.7123469710350037,
0.2914734184741974,
0.40198472142219543,
-0.08509156107902527,
0.048826754093170166,
-0.06689219176769257,
-0.294027328... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#benchmarks: | Benchmarks:
On running command, ab -n 100 -c 20 http://localhost/en
Before Changes (OPcache on but JIT off)
Time taken for tests: 1.061 seconds
Time per request: 212.203 [ms] (mean)
Time per request: 10.610 [ms] (mean, across all concurrent requests)
Connection Times (ms)
min mean[+/-sd]... | Benchmarks: | [
-0.6082648634910583,
-0.10038528591394424,
-0.25323811173439026,
-0.507781445980072,
-0.4967297315597534,
-0.5503590106964111,
0.43086495995521545,
0.08563165366649628,
0.13828739523887634,
0.21277496218681335,
0.06853463500738144,
0.050056956708431244,
0.18687467277050018,
0.3106221556663... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#symfony-performance-best-practices | Symfony Performance Best Practices
As Pimcore is based on Symfony framework for backend requests processing, it is highly recommended
to comply with Symfony Performance Best Practices. | Symfony Performance Best Practices | [
-0.1878373622894287,
-0.16885970532894135,
-0.17650385200977325,
0.05387706309556961,
-0.11898745596408844,
-0.543093740940094,
0.015035176649689674,
0.012073252350091934,
-0.19176313281059265,
0.04700978100299835,
-0.14875546097755432,
0.14759966731071472,
0.2658570110797882,
-0.072432361... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#benchmarks: | Benchmarks:
On running command, ab -n 100 -c 20 http://localhost/en
Before Changes
Time taken for tests: 1.100 seconds
Time per request: 219.904 [ms] (mean)
Time per request: 10.995 [ms] (mean, across all concurrent requests)
Connection Times (ms)
min mean[+/-sd] median max
Connect: ... | Benchmarks: | [
-0.7079004049301147,
-0.17277753353118896,
-0.26604926586151123,
-0.4487329423427582,
-0.4250054657459259,
-0.5425058007240295,
0.42710965871810913,
0.05774873495101929,
0.11607003957033157,
0.18532364070415497,
0.10128945112228394,
-0.16547974944114685,
0.15913142263889313,
0.299350976943... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#opcache-preloading | Opcache Preloading
Opcache preloading was introduced in PHP 7.4, a feature that could improve the performance of your application
significantly, by preloading commonly used framework files and keeping the generated byte-code in memory.
In order to enable OPcache preloading, configure these settings in your php.ini:
opc... | Opcache Preloading | [
-0.47276896238327026,
-0.19573360681533813,
-0.1723552942276001,
-0.007009176071733236,
0.021629272028803825,
-0.19243796169757843,
-0.10736411809921265,
0.5025416612625122,
0.02548886090517044,
0.2751714885234833,
-0.0783679261803627,
0.2531728744506836,
0.0398523174226284,
-0.14735352993... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#benchmarks: | Benchmarks:
On running command, ab -n 100 -c 20 http://localhost/en/shop/Products/Cars/Economy-Cars/Fiat-500~p104
Before Changes
Time taken for tests: 0.577 seconds
Time per request: 115.394 [ms] (mean)
Time per request: 5.770 [ms] (mean, across all concurrent requests)
Connection Times (ms)
... | Benchmarks: | [
-0.7065695524215698,
-0.05197399482131004,
-0.2512587606906891,
-0.1007063016295433,
-0.22968168556690216,
-0.3831467032432556,
0.49079087376594543,
0.07832081615924835,
-0.0047954972833395,
0.1707431524991989,
-0.012719493359327316,
-0.07000726461410522,
0.41449102759361267,
0.48189997673... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#mysqlmariadb-optimizations | MySQL/MariaDB Optimizations
Pimcore uses Data Access Object or DAO pattern to isolate the business logic from low level data access operations.
These data access operations play a vital role in performance of Pimcore application features
requiring read & write to/from the database. Therefore, it is important to tun... | MySQL/MariaDB Optimizations | [
-0.5503443479537964,
-0.22100457549095154,
-0.22282999753952026,
0.2846798300743103,
-0.08156446367502213,
-0.5721495151519775,
-0.19981718063354492,
-0.03101493790745735,
-0.25294387340545654,
0.19843019545078278,
-0.5085800290107727,
0.20541928708553314,
0.3836134672164917,
-0.0158045403... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#mysql-composite-index | MySQL Composite Index
If you are using Data Objects or custom database tables for data persistence, then it is beneficial to optimize these
tables to have composite indices, so that query optimizer uses the composite index for queries that
matches all columns in the index rather than searching the complete table.
You c... | MySQL Composite Index | [
-0.34418249130249023,
-0.11718042939901352,
-0.20641744136810303,
0.20656469464302063,
-0.2022179514169693,
0.179534450173378,
0.09312780946493149,
0.2810913920402527,
-0.10608397424221039,
0.21584834158420563,
-0.0027796325739473104,
-0.07775311917066574,
0.15335975587368011,
-0.048209905... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#mysql-buffer-pool | MySQL Buffer Pool
The buffer pool is an area in main memory where InnoDB caches table and index data as it is accessed.
The main purpose of buffer pool is to improve the response time of data retrieval.
The server system variable innodb_buffer_pool_size can be set from 70-80% of the total available
memory on a dedicate... | MySQL Buffer Pool | [
-0.334358274936676,
-0.31468451023101807,
-0.2416408360004425,
0.08792407810688019,
-0.12522004544734955,
0.14914631843566895,
-0.11009420454502106,
0.2414223998785019,
-0.04382915049791336,
0.2912873327732086,
-0.2796078026294708,
-0.13707280158996582,
0.1356913298368454,
-0.4560456573963... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#benchmarks: | Benchmarks:
On running command, ab -n 100 -c 20 http://localhost/en/shop/Products/Cars/Economy-Cars~c547
Before Changes
Time taken for tests: 2.515 seconds
Time per request: 503.024 [ms] (mean)
Time per request: 25.151 [ms] (mean, across all concurrent requests)
Connection Times (ms)
min ... | Benchmarks: | [
-0.5787408351898193,
-0.11501933634281158,
-0.31675127148628235,
-0.18870441615581512,
-0.3248157799243927,
-0.4468417465686798,
0.4362510144710541,
0.08977973461151123,
0.054765112698078156,
0.1758784055709839,
0.02529849298298359,
-0.03148718923330307,
0.29856330156326294,
0.449436277151... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#pimcore-caching-(redis) | Pimcore Caching (Redis)
Pimcore uses extensively caches for different types of data.
The primary cache is a pure object cache where every element (document, asset, object) in Pimcore is cached
as it is (serialized objects).
This Primary Cache is utilizing the Pimcore\Cache interface to store the objects.
Pimcore\Cache ... | Pimcore Caching (Redis) | [
-0.41336339712142944,
-0.20184896886348724,
-0.19122707843780518,
0.0380711667239666,
-0.13585367798805237,
-0.1222904697060585,
-0.012452303431928158,
0.27894169092178345,
-0.020498206838965416,
0.04047835245728493,
-0.2418937385082245,
0.17950975894927979,
0.28971603512763977,
-0.0472358... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#benchmarks: | Benchmarks:
On running command, ab -n 100 -c 20 http://localhost/en/shop/Products/Cars~c390
Before Changes
Time taken for tests: 6.495 seconds
Time per request: 1299.007 [ms] (mean)
Time per request: 64.950 [ms] (mean, across all concurrent requests)
Connection Times (ms)
min mean[+/-sd... | Benchmarks: | [
-0.5738480091094971,
-0.14018774032592773,
-0.3095747232437134,
-0.24062703549861908,
-0.3709714710712433,
-0.5000554323196411,
0.46142035722732544,
0.07275644689798355,
0.029967602342367172,
0.16153928637504578,
0.03243832662701607,
-0.057939764112234116,
0.2608132064342499,
0.41603937745... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#pimcore-full-page-cache | Pimcore Full Page Cache
Pimcore full page cache enables you to cache the content returned by a controller action.
With this cache, the same content does not need to be generated each and every time the
same controller action is invoked. A request processed through the MVC framework is cached and
stored in the cache poo... | Pimcore Full Page Cache | [
-0.1346050500869751,
-0.3381624221801758,
-0.18467578291893005,
0.0894269347190857,
-0.05555933713912964,
-0.21247796714305878,
-0.20764420926570892,
0.22096683084964752,
-0.20683160424232483,
0.1231086403131485,
-0.19532251358032227,
0.2898462414741516,
0.2519783079624176,
0.1080789715051... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#benchmarks: | Benchmarks:
On running command, ab -n 100 -c 20 http://localhost/en
Before Changes
Time taken for tests: 0.704 seconds
Time per request: 140.810 [ms] (mean)
Time per request: 7.040 [ms] (mean, across all concurrent requests)
Connection Times (ms)
min mean[+/-sd] median max
Connect: ... | Benchmarks: | [
-0.735325813293457,
-0.2308381199836731,
-0.23880915343761444,
-0.2945230007171631,
-0.4129868745803833,
-0.6086184978485107,
0.4009550213813782,
-0.08760173618793488,
-0.14732462167739868,
0.09052575379610062,
-0.13640275597572327,
-0.04529818519949913,
0.339912474155426,
0.23492830991744... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#static-page-generator | Static-Page-Generator
Pimcore offers a static page generator service, which generates static HTML files out of pages (documents).
These static files can be delivered directly by Apache/Nginx instead of going through
complete PHP driven MVC cycle on a frontend request. This feature is not recommended for a page with dyn... | Static-Page-Generator | [
-0.1485288143157959,
-0.27597370743751526,
-0.19745640456676483,
-0.07514432072639465,
-0.04523300752043724,
-0.2503264546394348,
-0.04411216825246811,
0.3015977442264557,
-0.3578667640686035,
0.05096022039651871,
0.06593761593103409,
0.3187224268913269,
0.11085096746683121,
0.267505705356... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#enable-static-page-generator-for-a-document: | Enable Static Page generator for a Document:
To enable automatic static page generation for a document, go to Document -> Settings -> Static Page Generator.
Mark enable checkbox and define optional lifetime for static pages (which regenerates static page after lifetime)
and save document. | Enable Static Page generator for a Document: | [
-0.10517904907464981,
-0.35093116760253906,
-0.16236332058906555,
-0.041861649602651596,
0.0910911113023758,
-0.052415329962968826,
0.09526074677705765,
0.1412428915500641,
-0.0733330026268959,
0.33524876832962036,
0.16144758462905884,
0.26312339305877686,
0.16733993589878082,
-0.061340186... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#benchmarks: | Benchmarks:
On running command, ab -n 100 -c 20 http://localhost/en/Magazine
Before Changes
Time taken for tests: 0.803 seconds
Time per request: 160.651 [ms] (mean)
Time per request: 8.033 [ms] (mean, across all concurrent requests)
Connection Times (ms)
min mean[+/-sd] median max
Con... | Benchmarks: | [
-0.5683181881904602,
-0.10490387678146362,
-0.20630404353141785,
-0.485432893037796,
-0.36260339617729187,
-0.40763309597969055,
0.4679514467716217,
-0.014971451833844185,
-0.13356922566890717,
0.15700362622737885,
0.048856355249881744,
-0.10333817452192307,
0.21650460362434387,
0.17151015... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#in-template-caching | In-Template Caching
Pimcore provides a Twig extension pimcore_cache for in-template caching, which is used to cache some parts
directly in the template, independent of the global caching functionality.
This can be useful for templates which needs a lot
of calculation or require a huge amount of objects e.g., Navigation... | In-Template Caching | [
-0.3599614202976227,
-0.2637733519077301,
-0.12909314036369324,
-0.08991964161396027,
0.03947465494275093,
-0.09020840376615524,
-0.09334646165370941,
0.3779601454734802,
-0.1681731939315796,
0.01690736413002014,
-0.16970868408679962,
0.3720164895057678,
0.15998323261737823,
0.040327306836... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#benchmarks: | Benchmarks:
On running command, ab -n 100 -c 20 http://localhost/en/Magazine
Before Changes
Time taken for tests: 0.808 seconds
Time per request: 161.603 [ms] (mean)
Time per request: 8.080 [ms] (mean, across all concurrent requests)
Connection Times (ms)
min mean[+/-sd] median max
Con... | Benchmarks: | [
-0.5755251049995422,
-0.09435134381055832,
-0.20821426808834076,
-0.4982919692993164,
-0.3558145761489868,
-0.42029398679733276,
0.47330060601234436,
-0.017300505191087723,
-0.12620660662651062,
0.16202722489833832,
0.047530725598335266,
-0.10179813206195831,
0.21289530396461487,
0.1808644... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#varnish-cache | Varnish Cache
The Varnish Cache is a so-called caching reverse proxy, that is placed in front of a server,
which is responsible for delivering website content.
On initial request, the varnish cache saves a copy of the server reponse in memory.
In the event of subsequent requests, the response is sent directly from the ... | Varnish Cache | [
0.05499812588095665,
-0.5705504417419434,
-0.17759543657302856,
0.06927575170993805,
-0.35163888335227966,
0.06479020416736603,
-0.38498324155807495,
-0.03235510364174843,
-0.03740513324737549,
0.002219629008322954,
0.10789825022220612,
-0.02063547819852829,
0.48901915550231934,
-0.3242806... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Performance_Guide#edge-side-includes-(esi) | Edge Side Includes (ESI)
Edge Side Includes is a markup to manage page fragments, which can be cached and merged into one page.
These fragments can have individual cache policies and can be shared on multiple pages.
Varnish supports 2 main ESI tags, which are:
esi:include
esi:remove
Symfony has a built-in support for ... | Edge Side Includes (ESI) | [
-0.14495523273944855,
-0.7168895602226257,
-0.18595939874649048,
0.055654797703027725,
-0.25298818945884705,
0.14013083279132843,
-0.01964586041867733,
0.20169341564178467,
0.32288557291030884,
0.021962646394968033,
0.04716947302222252,
0.3073013722896576,
0.20672914385795593,
0.1351357400... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting/Fix_Performance_Issues_on_Windows#fix-performance-issues-on-windows | Fix Performance Issues on Windows
It is highly recommended not to use Windows based systems in production!
In times of Docker, the host operating system shouldn't really matter - at least in theory. Our experience shows, that
Docker in combination with a Windows host system has its problems – especially performance w... | Fix Performance Issues on Windows | [
-0.5932519435882568,
-0.05515188351273537,
-0.22315077483654022,
-0.0240692850202322,
0.10506962239742279,
-0.29282069206237793,
0.3607421815395355,
0.1552419513463974,
0.17398779094219208,
0.2829468548297882,
-0.20769506692886353,
0.40082740783691406,
-0.06211475655436516,
-0.027843318879... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting#system-setup-&-hostinginfrastructure-topics | System Setup & Hosting/Infrastructure Topics | System Setup & Hosting/Infrastructure Topics | [
-0.112706758081913,
-0.223804771900177,
-0.341190904378891,
0.2452814280986786,
-0.03920046612620354,
-0.19480185210704803,
0.34971535205841064,
-0.24292664229869843,
0.038960058242082596,
-0.10392183065414429,
0.0564974769949913,
-0.15898260474205017,
0.0013313445961102843,
0.284455865621... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting#general-topics | General Topics
Installation Guide
Apache Configuration
Nginx Configuration
Database Setup
Additional Tools Installation
| General Topics | [
-0.09531278908252716,
-0.14718778431415558,
-0.34010517597198486,
-0.0591711550951004,
-0.11115877330303192,
0.05472907796502113,
0.0576886422932148,
0.03776685521006584,
-0.15787702798843384,
-0.1760924607515335,
-0.015435341745615005,
-0.16322019696235657,
0.2749185860157013,
0.199186757... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/System_Setup_and_Hosting#advanced-topics | Advanced Topics
Cluster Setup
Performance Guide
| Advanced Topics | [
-0.38062646985054016,
-0.5754050016403198,
-0.3528692126274109,
0.22833557426929474,
-0.17796404659748077,
-0.22120670974254608,
0.26109451055526733,
-0.13617157936096191,
-0.049646660685539246,
0.09180790930986404,
-0.044588565826416016,
0.15779326856136322,
0.09688004851341248,
0.2932841... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#upgrading-pimcore-from-version-6.x-to-version-10 | Upgrading Pimcore from Version 6.x to Version 10 | Upgrading Pimcore from Version 6.x to Version 10 | [
-0.5103806257247925,
0.02655074931681156,
-0.3021947741508484,
-0.04337061941623688,
0.1403590887784958,
-0.22890567779541016,
-0.09437122195959091,
0.2701743245124817,
-0.2524455785751343,
0.12278170883655548,
-0.32194995880126953,
0.693880021572113,
0.11749294400215149,
-0.02929316088557... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#system-requirement-changes | System Requirement changes
PHP >=8.0 <8.2
Apache >= 2.4
Composer >= 2.0
As Pimcore 6.x works only with PHP < 8.0 and Pimcore 10 works only with PHP >=8.0 <8.2, a switch of PHP version is needed during the upgrade process.
| System Requirement changes | [
-0.48023465275764465,
-0.08352295309305191,
-0.19430164992809296,
0.13280735909938812,
0.011615651659667492,
-0.32911720871925354,
-0.0923241451382637,
0.23763419687747955,
-0.2564365565776825,
0.2453671246767044,
-0.10174975544214249,
0.4556931257247925,
0.11452917754650116,
-0.1014646515... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#database-requirement-changes | Database Requirement changes
MariaDB >= 10.3
MySQL >= 8.0
| Database Requirement changes | [
-0.4072055518627167,
-0.04740605130791664,
-0.3326696753501892,
-0.0016849769745022058,
-0.03592032939195633,
-0.05228010565042496,
-0.21986304223537445,
0.29601532220840454,
0.1348082572221756,
0.03553536906838417,
-0.3010403513908386,
0.11498774588108063,
-0.11648910492658615,
-0.2796163... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#preparatory-work | Preparatory Work
If you're on a version between 6.0.0 and 6.8.x, then please update to 6.9.x first and then continue with the upgrade steps.
Check if all of your used Bundles are compatible with Pimcore X
If you're using REST Webservices or the PHP templating engine,
upgrade to Datahub and Twig templates
or consider u... | Preparatory Work | [
-0.06988836079835892,
0.10275690257549286,
-0.12939448654651642,
-0.11581286787986755,
0.1598823070526123,
-0.14336039125919342,
0.07834107428789139,
0.3456597328186035,
-0.5944443345069885,
0.28890132904052734,
-0.2977251410484314,
0.6797162294387817,
0.10142973065376282,
0.05463290214538... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#important-changes-to-do-prior-the-update!-(to-do-with-php-<-8.0) | IMPORTANT CHANGES TO DO PRIOR THE UPDATE! (TO DO WITH PHP < 8.0) | IMPORTANT CHANGES TO DO PRIOR THE UPDATE! (TO DO WITH PHP < 8.0) | [
-0.07380221039056778,
0.06778454780578613,
-0.39755377173423767,
-0.06840462237596512,
-0.06992042064666748,
-0.1273682564496994,
-0.03296351432800293,
0.3970593810081482,
-0.1487576961517334,
0.03456549346446991,
0.14403845369815826,
-0.09121653437614441,
-0.19422197341918945,
-0.05224334... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#update-folder-structure | Update folder structure
Update your project folder structure as per Symfony Flex guidelines. See demo changes here | Update folder structure | [
-0.128550186753273,
0.11373089998960495,
-0.2131454348564148,
0.20571677386760712,
0.14066430926322937,
-0.1878547966480255,
0.13307319581508636,
0.3578163981437683,
-0.07802554965019226,
0.34380021691322327,
-0.020977888256311417,
0.1290995329618454,
0.09667124599218369,
0.074551276862621... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#migrate-legacy-modulecontrolleraction-configurations-to-new-controller-references | Migrate legacy module/controller/action configurations to new controller references
You can use ./bin/console migration:controller-reference to migrate your existing Documents, Static routes and Document Types to the new controller references in the format: AppBundle\Controller\FooController::barAction. | Migrate legacy module/controller/action configurations to new controller references | [
-0.19045302271842957,
0.0532250851392746,
-0.043389659374952316,
-0.1495255082845688,
0.26681074500083923,
-0.15593084692955017,
0.13298916816711426,
0.5583580732345581,
-0.2178444117307663,
-0.061193156987428665,
-0.2284466028213501,
0.4912004768848419,
-0.19756020605564117,
0.21852329373... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#migrate-versions-to-be-compatible-with-pimcore-x | Migrate versions to be compatible with Pimcore X
Documents:
If you wish to carry forward Document version files from 6.x to Pimcore X, then it is required run command pimcore:documents:migrate-elements to migrate deprecated property elements to editables. (only relevant for versions created before 6.7)
Data Objects:
Pl... | Migrate versions to be compatible with Pimcore X | [
-0.5156539082527161,
0.16880878806114197,
-0.18069535493850708,
-0.028671402484178543,
0.0019320243736729026,
-0.06984583288431168,
-0.1340474933385849,
0.36188551783561707,
-0.23382790386676788,
-0.009944903664290905,
-0.3307930827140808,
0.6492423415184021,
0.08002077043056488,
0.0230527... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#ensure-your-database-configuration-includes-the-following-definitions: | Ensure your database configuration includes the following definitions:
doctrine:
dbal:
connections:
default:
mapping_types:
enum: string
bit: boolean
| Ensure your database configuration includes the following definitions: | [
-0.17335541546344757,
-0.08689964562654495,
-0.13970932364463806,
0.09190214425325394,
0.11884277313947678,
-0.2772044539451599,
0.026012711226940155,
0.3635610044002533,
-0.2817358076572418,
0.11906805634498596,
-0.0031215189956128597,
0.19758667051792145,
0.13171572983264923,
0.219646722... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#cleanup-your-composer.json | Cleanup your composer.json
composer remove --no-update wikimedia/composer-merge-plugin doctrine/migrations php-http/guzzle6-adapter
composer require --no-update php-http/guzzle7-adapter:^0.1.1
Update composer.json as per skeleton
Remove
"autoload": {
"classmap": [
"app/AppKernel.php&... | Cleanup your composer.json | [
-0.12545424699783325,
0.24791021645069122,
-0.11112837493419647,
0.09727850556373596,
0.32465964555740356,
-0.13363030552864075,
-0.04073921963572502,
0.25068235397338867,
-0.19968152046203613,
0.11376259475946426,
-0.2262633889913559,
0.490912526845932,
0.13067413866519928,
0.149286121129... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#file--folder-changes | File / Folder changes
Move configs from app/config/*.yml to config/*.yaml
Move templates from app/Resources/views to templates and bundles templates from app/Resources/XYZBundle/views to templates/bundles/XYZBundle
Move app/AppKernel.php to src/Kernel.php and edit it to have namespace App; and class name Kernel (add... | File / Folder changes | [
-0.11736692488193512,
0.17835712432861328,
-0.14683133363723755,
0.1621200144290924,
0.2791007161140442,
-0.2024170160293579,
-0.055724430829286575,
0.3463236391544342,
-0.38928547501564026,
0.032148297876119614,
-0.1298728883266449,
0.5294079780578613,
0.06463637948036194,
0.2909281253814... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#add-.env-environment-file | Add .env environment file
Add .env file to project root, if not exists already. | Add .env environment file | [
-0.3378208577632904,
-0.023695671930909157,
-0.22797971963882446,
-0.1970096081495285,
0.1824331432580948,
-0.14462915062904358,
0.06991853564977646,
0.314471572637558,
-0.00031325913732871413,
0.31922319531440735,
0.25176185369491577,
0.23697464168071747,
-0.008603539317846298,
0.24871911... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#migrate-php-templates-to-twig | Migrate PHP templates to Twig
Since Pimcore X supports only Symfony 5, which dropped the support for PHP templates, it is required to update your PHP templates to Twig.
If you are using enterprise edition, then it is still possible to support PHP templates by installing pimcore/php-templating-engine-bundle.
You can use... | Migrate PHP templates to Twig | [
-0.3512973487377167,
-0.21874041855335236,
-0.13463172316551208,
-0.14657048881053925,
0.3267955780029297,
-0.2824791371822357,
0.12444693595170975,
0.30512386560440063,
-0.3008570969104767,
0.24975872039794922,
-0.16819149255752563,
0.38972604274749756,
0.20089443027973175,
0.047799538820... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#adapt-system-settings | Adapt System settings
Due to change in Pimcore config that no extra keys are allowed under pimcore node anymore, it is required to adapt system settings as per system.template.yaml (default path <Pimcore root>/var/config/system.yaml) and config.yaml (default path after adapting folder structure <Pimcore root&g... | Adapt System settings | [
-0.03350212052464485,
-0.1936689019203186,
-0.02663806825876236,
0.04187965765595436,
0.2482747733592987,
-0.07263507694005966,
0.02106896974146366,
0.0663120374083519,
-0.0468621551990509,
0.14341740310192108,
-0.09258244186639786,
0.4858063757419586,
0.048759736120700836,
0.1524703353643... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#adapt-security-config | Adapt Security config
It is not longer possible to merge security configurations from multiple locations, including bundles. Instead you have to move them to one single config file, e.g. config/packages/security.yaml. Check bin/console debug:config security firewalls to find firewall configurations which have to be mov... | Adapt Security config | [
-0.277535617351532,
-0.1397937685251236,
-0.08874804526567459,
-0.14939190447330475,
0.04183891788125038,
-0.06961562484502792,
0.4403451681137085,
-0.07253963500261307,
-0.027395326644182205,
0.1489044427871704,
-0.25510528683662415,
0.16955189406871796,
0.2963351607322693,
0.155878871679... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#flush-your-tmp-directories | Flush your /tmp directories
rm -r var/tmp
rm -r public/var/tmp
| Flush your /tmp directories | [
-0.13647323846817017,
-0.3236573338508606,
-0.26302430033683777,
0.20886766910552979,
0.3650382459163666,
0.1679685115814209,
0.08007867634296417,
0.3210010230541229,
0.013517719693481922,
0.24007557332515717,
-0.36560922861099243,
0.0801449716091156,
-0.0342387817800045,
-0.18193040788173... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#flush-your-recycle-bin | Flush your recycle-bin
Migrating the items in the recycle-bin is not supported.
To have a clear start with Pimcore 10 we recommend to flush it before migration.
rm -r var/recyclebin
TRUNCATE TABLE recyclebin;
| Flush your recycle-bin | [
-0.2894461452960968,
-0.0973268672823906,
-0.1179247796535492,
-0.08155396580696106,
0.2845246493816376,
-0.19318337738513947,
0.07203991711139679,
0.3031892478466034,
-0.40037545561790466,
0.20971772074699402,
-0.4410031735897064,
0.7071863412857056,
0.06092742830514908,
0.314840167760849... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#decompress-your-zipped-version-data | Decompress your zipped version data
Pimcore X doesn't support compressed version data anymore, run the following command to recursively
decompress them:
gzip -d -r var/versions/ | Decompress your zipped version data | [
-0.5243951678276062,
-0.1317460685968399,
-0.2149064987897873,
0.14328837394714355,
0.12128102779388428,
-0.06483811140060425,
-0.24891482293605804,
0.3961973488330841,
-0.3733445107936859,
0.26643621921539307,
-0.2743547856807709,
0.5248677730560303,
0.16177016496658325,
0.169958561658859... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#move-user-images | Move user images
The default location of the user images has changed, simply move the contents over to the new location:
mkdir var/admin
mv var/user-image var/admin/user-image
| Move user images | [
0.21350711584091187,
0.059795722365379333,
-0.24924665689468384,
0.16981849074363708,
0.2591564357280731,
0.1134704202413559,
0.24841049313545227,
0.09476127475500107,
-0.02145504578948021,
0.23506738245487213,
-0.20632189512252808,
-0.14505551755428314,
0.07612660527229309,
-0.16986891627... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#move-custom-logo | Move custom logo
The location of the custom logo has changed, simply move it over to the new location:
mkdir var/admin
mv var/config/custom-logo.* var/admin/custom-logo.image
| Move custom logo | [
0.04025009647011757,
-0.1883959174156189,
-0.16592004895210266,
0.2527409791946411,
0.03384045884013176,
-0.047519296407699585,
0.16424477100372314,
0.009087774902582169,
-0.06326618045568466,
0.05284205079078674,
0.16968311369419098,
-0.011584103107452393,
0.2042635977268219,
0.0375982187... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#update-your-.htaccess-or-your-nginx-configuration | Update your .htaccess or your Nginx configuration
Updated .htaccess is available here.
Updated Nginx configuration is available here.
| Update your .htaccess or your Nginx configuration | [
-0.07845566421747208,
-0.093594029545784,
-0.3107815682888031,
-0.2017674744129181,
0.194874107837677,
-0.1503314971923828,
0.19469591975212097,
0.1861424297094345,
-0.11847178637981415,
0.1986524611711502,
-0.10204072296619415,
-0.16104184091091156,
0.17717434465885162,
0.1520351767539978... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#switch-composer-and-php-version,-and-do-the-update! | SWITCH COMPOSER AND PHP VERSION, AND DO THE UPDATE!
Ensure Composer is updated to version >= 2.0
Switch PHP version to PHP >=8.0 <8.2
Run composer update (COMPOSER_MEMORY_LIMIT=-1 composer update)
| SWITCH COMPOSER AND PHP VERSION, AND DO THE UPDATE! | [
-0.3510274887084961,
-0.06216571107506752,
-0.2923939824104309,
0.23959513008594513,
0.11679495871067047,
-0.14970314502716064,
-0.10358020663261414,
0.28265273571014404,
0.043282125145196915,
0.4951733350753784,
0.1474205106496811,
0.05401681363582611,
-0.24651983380317688,
-0.10508677363... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#changes-to-do-after-the-update!-(to-do-with-php->=8.0-<8.2) | CHANGES TO DO AFTER THE UPDATE! (TO DO WITH PHP >=8.0 <8.2) | CHANGES TO DO AFTER THE UPDATE! (TO DO WITH PHP >=8.0 <8.2) | [
-0.10842584073543549,
0.060217563062906265,
-0.42158544063568115,
-0.05464544892311096,
-0.055916979908943176,
-0.1070798709988594,
-0.06616847962141037,
0.5278753042221069,
-0.04661451280117035,
0.009718378074467182,
0.14381732046604156,
-0.061973948031663895,
-0.18717923760414124,
-0.097... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V10#verify-migrations-execution | Verify migrations execution
By default, Composer update runs Pimcore migrations automatically, however it is better to check if all migrations are executed for smooth transition.
To verify, run command: ./bin/console doctrine:migrations:up-to-date --prefix=Pimcore\\Bundle\\CoreBundle.
If you see message, [ERROR] Out-of... | Verify migrations execution | [
-0.4862917363643646,
0.1716637760400772,
-0.12946996092796326,
0.031199602410197258,
-0.04938933625817299,
-0.2734646797180176,
-0.13998332619667053,
0.048673246055841446,
-0.5591477751731873,
0.2533908486366272,
0.04664013162255287,
0.41410306096076965,
0.15638893842697144,
-0.01776784099... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Preparing_for_V11#preparing-pimcore-for-version-11 | Preparing Pimcore for Version 11 | Preparing Pimcore for Version 11 | [
-0.5389359593391418,
-0.20647893846035004,
-0.27920231223106384,
0.1419113725423813,
-0.016453657299280167,
-0.21581383049488068,
-0.22700469195842743,
0.19920772314071655,
-0.358682245016098,
0.2217666208744049,
-0.15963736176490784,
0.4315497875213623,
-0.035721827298402786,
0.2118597179... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Preparing_for_V11#upgrade-to-pimcore-10.6 | Upgrade to Pimcore 10.6
Upgrade to version 10.6.x, if you are using a lower version.
| Upgrade to Pimcore 10.6 | [
-0.5213025212287903,
-0.31817948818206787,
-0.201032355427742,
0.03165591135621071,
0.09128571301698685,
-0.29731225967407227,
0.17355747520923615,
0.24226322770118713,
-0.2271297723054886,
0.40610572695732117,
-0.11346027255058289,
0.46058985590934753,
0.11737604439258575,
0.0552107989788... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Preparing_for_V11#migrate-php-templates-to-twig | Migrate PHP Templates to Twig
With Pimcore 11, it is required to update your PHP templates to Twig.
:::caution
Be aware that Pimcore 11 does not support installing pimcore/php-templating-engine-bundle anymore. The migration to Twig is then required even for enterprise customers.
:::
You can use a RegEx to replace strin... | Migrate PHP Templates to Twig | [
-0.28468990325927734,
-0.17654238641262054,
-0.13510335981845856,
-0.04678137227892876,
0.3254711329936981,
-0.21818776428699493,
0.1637975126504898,
0.253773033618927,
-0.31134092807769775,
0.23174352943897247,
-0.1792963296175003,
0.366323322057724,
0.22919246554374695,
0.091208331286907... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Preparing_for_V11#code-changes | Code Changes
[Type hints] Check and add return type hints for classes extending Pimcore classes or implementing interfaces provided by Pimcore, based on the source phpdoc or comments on the methods.
The return types will be added to Pimcore classes, so you must add return types to your classes extending Pimcore.
You ... | Code Changes | [
-0.10768076032400131,
0.0989498719573021,
-0.08360644429922104,
0.10981567203998566,
0.19134926795959473,
-0.506819486618042,
0.15381371974945068,
0.16982805728912354,
-0.31152552366256714,
0.2926103472709656,
-0.1026725322008133,
0.3495539426803589,
0.01447212789207697,
0.2124219387769699... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Preparing_for_V11#migrations | Migrations
Make sure that migrations are executed.
How to handle them highly depends on your deployment process.
You can manually call bin/console doctrine:migrations:migrate at any time or add it in your deployment pipeline.
If you are sure you can run all available migrations after composer update, including bundles ... | Migrations | [
-0.33176708221435547,
0.32210132479667664,
-0.24168312549591064,
-0.1871541440486908,
0.23948462307453156,
-0.3108961284160614,
0.035280823707580566,
-0.00009822018910199404,
-0.5602437853813171,
0.10801125317811966,
0.14272774755954742,
0.17294669151306152,
0.02800443023443222,
0.00224952... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Preparing_for_V11#configuration-adaptions | Configuration Adaptions
[Security] Enable New Security Authenticator and adapt your security.yaml file as per changes here:
security:
enable_authenticator_manager: true
Points to consider when moving to new Authenticator:
New authentication system works with password hasher factory instead of encoder factory.
B... | Configuration Adaptions | [
-0.207351416349411,
0.05287100747227669,
-0.0612817257642746,
-0.26048359274864197,
0.1343817114830017,
-0.18851451575756073,
0.4149813652038574,
0.24976520240306854,
-0.2035992592573166,
0.08245067298412323,
-0.18342676758766174,
0.13762615621089935,
0.1360413134098053,
0.0653389915823936... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Preparing_for_V11#migrate-o_-prefix-properties-in-the-stored-data | Migrate o_ prefix properties in the stored data
As o_ prefix will be removed from data objects system properties in v11. It is recommended to migrate the stored data to use new properties (without o_ prefix).
Please adapt and use these scripts to migrate versions and recycle-bin data. | Migrate o_ prefix properties in the stored data | [
-0.25444296002388,
-0.06864109635353088,
-0.2238980084657669,
0.0684896856546402,
0.09427687525749207,
-0.17845264077186584,
0.038107238709926605,
0.3701927065849304,
0.061175018548965454,
0.20885692536830902,
-0.09096869826316833,
0.24069876968860626,
0.10037034004926682,
0.39754876494407... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Preparing_for_V11#additional-things-to-consider | Additional Things to Consider
[Web2Print] Please keep in mind that the deprecated processor HeadlessChrome needs to be replaced with the new processor Chrome in Pimcore 11.
[Config] pimcore.assets.image.focal_point_detection was removed
[Composer] Please make sure to add the pimcore/compatibility-bridge-v10 to your co... | Additional Things to Consider | [
-0.3452718257904053,
-0.03812199831008911,
-0.06924549490213394,
-0.021895216777920723,
0.09273993223905563,
-0.1659930944442749,
0.15185245871543884,
0.31044819951057434,
-0.39516741037368774,
0.1833662986755371,
-0.06773018836975098,
0.5281181931495667,
0.1737510859966278,
0.147827237844... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#upgrading-pimcore-from-version-10.x-to-version-11 | Upgrading Pimcore from Version 10.x to Version 11 | Upgrading Pimcore from Version 10.x to Version 11 | [
-0.4697907567024231,
0.0519014373421669,
-0.28258490562438965,
0.06891836225986481,
0.0843200758099556,
-0.18930687010288239,
-0.17778359353542328,
0.21616116166114807,
-0.2761824131011963,
0.2461003065109253,
-0.14718136191368103,
0.4831995368003845,
0.0675964504480362,
0.1817935705184936... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#tasks-to-do-prior-the-update | Tasks to Do Prior the Update | Tasks to Do Prior the Update | [
-0.24246470630168915,
-0.13754510879516602,
-0.28856104612350464,
-0.19699116051197052,
-0.015593609772622585,
0.023004969581961632,
-0.1047980934381485,
0.1280808001756668,
-0.15487906336784363,
-0.09545125812292099,
0.3053000271320343,
0.08142933994531631,
0.001118122017942369,
0.1186900... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#migrate-system-settings | Migrate System Settings
System settings are using LocationAwareConfigRepository in Pimcore 11. To keep your specific settings, please follow the steps below: | Migrate System Settings | [
-0.3706463873386383,
0.14624464511871338,
-0.0214652419090271,
-0.11766770482063293,
0.23626865446567535,
-0.1877942979335785,
0.08895613998174667,
0.11142347753047943,
-0.5124227404594421,
0.19266019761562347,
-0.4831135869026184,
0.2679721415042877,
0.27490684390068054,
0.091872356832027... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#database | Database
Make sure to change the type from json_array to json when upgrading to 11, since the type json_array is removed in doctrine/dbal 3.
Use the following script to list the columns which contains the json_array.
mysqldump -u <USERNAME> -p <PASSWORD> --no-data <DATABASENAME> | grep -i json_array
| Database | [
0.0669744685292244,
0.1956678032875061,
-0.21059437096118927,
0.37329453229904175,
0.05482393503189087,
-0.07433954626321793,
-0.13934534788131714,
0.6778608560562134,
-0.07115115225315094,
0.13745304942131042,
-0.15346086025238037,
0.2703118920326233,
-0.256212055683136,
-0.12001673877239... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#appearance-&-branding | Appearance & Branding
Appearance & Branding settings will be separated from the system settings in Pimcore 11 and stored in var/config/admin_system_settings/admin_system_settings.yaml by default. Please copy every relevant settings from var/config/system.yaml into var/config/admin_system_settings/admin_system_s... | Appearance & Branding | [
-0.2391756922006607,
-0.32063978910446167,
0.03604041412472725,
0.36047452688217163,
0.4377780854701996,
-0.044976480305194855,
0.12836076319217682,
-0.1254698932170868,
-0.4005225896835327,
0.11209850013256073,
-0.16884228587150574,
0.3123790919780731,
0.2331797182559967,
0.23279857635498... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#system-settings | System Settings
Please copy all relevant settings from var/config/system.yaml into var/config/system_settings/system_settings.yaml.
To save system settings into the settings store, please add the following to your configuration:
pimcore:
config_location:
system_settings:
write_target:
... | System Settings | [
-0.5608119964599609,
-0.33484652638435364,
-0.038161154836416245,
-0.14739878475666046,
0.5010483860969543,
-0.0407131128013134,
0.06574573367834091,
-0.029898321256041527,
-0.23145681619644165,
0.05115124210715294,
-0.12531857192516327,
0.45821961760520935,
0.08336231857538223,
0.13573762... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#configuration-storage-settings | Configuration Storage Settings
As some features were moved to separate bundles, their configuration storage settings might need to be moved. This is a two steps process:
Remove settings before the update.
Re-Add settings after the extracted bundles installation.
The relevant configs are:
# pimcore_custom_reports:
# ... | Configuration Storage Settings | [
-0.32588282227516174,
-0.21504460275173187,
-0.07538188248872757,
0.058952830731868744,
0.20090845227241516,
0.01604929380118847,
0.004366815090179443,
0.24953404068946838,
-0.369836688041687,
0.1185484454035759,
-0.25653329491615295,
0.4583205282688141,
0.16782183945178986,
0.286836445331... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#web2print | Web2Print
If you are using the Web2Print functionality, set the flag "Enable Web2Print documents in default documents view" to true to ensure the PimcoreWebToPrintBundle gets installed by default.
If you are not using Web2Print functionality, set the flag to false. | Web2Print | [
-0.28656816482543945,
-0.2664942741394043,
-0.045901648700237274,
-0.17152367532253265,
-0.29979774355888367,
-0.07028760015964508,
0.24355360865592957,
0.1037912517786026,
-0.25971534848213196,
0.2065485268831253,
0.06880102306604385,
0.5585045218467712,
0.20355817675590515,
0.32768696546... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#wysiwyg-editor | WYSIWYG-Editor
Please add all html tags with attributes you want to allow to the html_sanitizer like described here | WYSIWYG-Editor | [
0.0835144892334938,
-0.007945545017719269,
-0.24741145968437195,
-0.2686844766139984,
0.31208303570747375,
0.01660415530204773,
0.2417389452457428,
0.3033783733844757,
0.3147893249988556,
0.19457177817821503,
-0.03188632056117058,
0.14868609607219696,
-0.17326365411281586,
0.20205000042915... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#update-pimcore-via-composer | Update Pimcore via Composer
Update Pimcore to Pimcore 11 via composer statement composer require -W pimcore/pimcore:^11.0 pimcore/admin-ui-classic-bundle.
Depending on your setup, it might be necessary to include additional dependencies in the update statement and/or to clean up the composer.lock file and the vendor fo... | Update Pimcore via Composer | [
-0.34775540232658386,
0.13605757057666779,
-0.13548347353935242,
-0.03400696814060211,
0.1103704497218132,
-0.15954038500785828,
-0.03393169865012169,
0.16999627649784088,
-0.19027122855186462,
0.17967158555984497,
0.0058311522006988525,
0.4272916913032532,
0.09479179978370667,
0.040885005... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#tasks-to-do-after-the-update | Tasks to Do After the Update | Tasks to Do After the Update | [
-0.21772249042987823,
-0.011994117870926857,
-0.3294467329978943,
-0.12338957190513611,
0.13788223266601562,
0.08263927698135376,
-0.1191183403134346,
0.17175057530403137,
-0.17198434472084045,
-0.14891797304153442,
0.20317216217517853,
0.20335601270198822,
-0.005251981783658266,
0.1623928... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#admin-bundle | Admin Bundle
Register the admin-ui-classic-bundle in Kernel (and adapt method signature if necessary):
src/Kernel.php
public function registerBundlesToCollection(BundleCollection $collection): void
{
// pimcore bundles
$collection->addBundle(new \Pimcore\Bundle\AdminBundle\PimcoreAdminBundle(), 60);
}
| Admin Bundle | [
-0.3825186789035797,
-0.23240627348423004,
-0.06439995020627975,
0.13240946829319,
0.1726265698671341,
-0.07598160952329636,
0.1220843493938446,
0.08932552486658096,
-0.11197146028280258,
0.1592446267604828,
0.009131976403295994,
0.45935946702957153,
0.0017212110105901957,
0.18703663349151... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#some-code-changes | Some Code Changes
Update config/packages/security.yaml to the latest format. As reference use security.yaml of our skeleton.
Update references from @PimcoreCoreBundle/Resources/config/... to @PimcoreCoreBundle/config/...
especially in config/routes.yaml (you probably also need to change routing.yml to routing.yaml th... | Some Code Changes | [
-0.2308243364095688,
-0.10999933630228043,
-0.10820486396551132,
-0.03363986685872078,
0.21406236290931702,
-0.3295004367828369,
0.18837407231330872,
0.015064057894051075,
-0.3438015878200531,
0.17979560792446136,
0.04884572699666023,
0.5011510848999023,
0.25523072481155396,
0.185739696025... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#install-extracted-bundles-via-composer-if-necessary | Install Extracted Bundles via Composer if Necessary
Add the extracted bundles (such as PimcoreEcommerceFrameworkBundle or PimcorePersonalizationBundle) via composer if necessary.
composer require pimcore/system-info-bundle pimcore/file-explorer-bundle pimcore/personalization-bundle pimcore/google-marketing-bundle pimco... | Install Extracted Bundles via Composer if Necessary | [
-0.25224989652633667,
-0.028518935665488243,
-0.14113393425941467,
0.18474487960338593,
-0.0393153615295887,
0.11926402151584625,
-0.10925191640853882,
0.04932252690196037,
-0.347217857837677,
0.245916947722435,
-0.24136364459991455,
0.5710361003875732,
-0.033441126346588135,
0.25557336211... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#activate-extracted-bundles-in-configbundles.php-if-necessary | Activate Extracted Bundles in config/bundles.php if Necessary
Update config/bundles.php and add all the needed extracted bundles to the array:
\Pimcore\Bundle\EcommerceFrameworkBundle\PimcoreEcommerceFrameworkBundle::class => ['all' => true],
\Pimcore\Bundle\PersonalizationBundle\PimcorePersonalizationBundle... | Activate Extracted Bundles in config/bundles.php if Necessary | [
-0.26598355174064636,
-0.06232320889830589,
-0.18482500314712524,
0.20915235579013824,
0.02583085559308529,
-0.085536427795887,
0.10546886175870895,
0.19896666705608368,
-0.3044777810573578,
0.1928289830684662,
-0.22460457682609558,
0.4726475477218628,
0.08305045962333679,
0.25738057494163... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#configuration-storage-settings---part-2 | Configuration Storage Settings - Part 2
Reactivate the configuration storage settings for the extracted bundles as needed:
#custom_reports
pimcore_custom_reports:
config_location:
custom_reports:
...
#web_to_print
pimcore_web_to_print:
config_location:
web_to_print:
...
#static_routes
pimcore... | Configuration Storage Settings - Part 2 | [
-0.3481089174747467,
-0.3215808570384979,
-0.07415374368429184,
0.12727715075016022,
0.12987269461154938,
0.003323329845443368,
0.06682100892066956,
0.2839210331439972,
-0.36482301354408264,
0.18638020753860474,
-0.2903307378292084,
0.38610169291496277,
0.19540491700172424,
0.2078611701726... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#migrations | Migrations
As soon as the Symfony container can be built again, you can execute all the migrations:
bin/console doctrine:migrations:migrate
| Migrations | [
-0.27031219005584717,
0.28385457396507263,
-0.23143835365772247,
-0.14083246886730194,
0.2022886723279953,
-0.18440614640712738,
0.22658565640449524,
0.2561623156070709,
-0.2845586836338043,
0.2703038454055786,
-0.02011912688612938,
-0.026537420228123665,
0.07289618998765945,
-0.0151888169... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#web2print | Web2Print
If you do not use the Web2Print functionality, then please make sure to run the following command and queries to clean up your system:
bin/console pimcore:documents:cleanup printpage printcontainer
DELETE FROM `users_permission_definitions` WHERE `key` = 'web2print_settings';
UPDATE `users` SET `permissions`... | Web2Print | [
-0.050961777567863464,
-0.14070206880569458,
-0.1407681405544281,
-0.1783536821603775,
0.026194855570793152,
-0.013105704449117184,
0.2579103112220764,
0.12540686130523682,
-0.17931325733661652,
0.15867844223976135,
-0.05818380415439606,
0.3443828225135803,
0.041114214807748795,
0.07212827... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#newsletters | Newsletters
If you do not use the Newsletter functionality, then please make sure to run the following command to clean up your system:
bin/console pimcore:documents:cleanup newsletter
| Newsletters | [
-0.10319742560386658,
-0.07766604423522949,
-0.16762879490852356,
0.034130167216062546,
0.16230101883411407,
0.021059954538941383,
-0.05662361532449722,
0.1931578367948532,
-0.1889633983373642,
0.2939267158508301,
-0.06195541098713875,
0.3601948618888855,
0.09731034189462662,
-0.0714301764... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#remove-orphaned-custom-settings | Remove orphaned custom settings
Since the facedetect support was removed in v11, we recommend to remove the corresponding custom settings
in the database. You can do that by running the following commands:
bin/console pimcore:assets:remove-custom-setting faceCoordinates
bin/console pimcore:assets:remove-custom-setting ... | Remove orphaned custom settings | [
-0.13101458549499512,
-0.4216562807559967,
-0.09593959152698517,
0.05323626846075058,
0.07275138050317764,
-0.10082057863473892,
0.3612602949142456,
0.13624973595142365,
-0.1518012136220932,
0.16543543338775635,
-0.10853327065706253,
0.19540756940841675,
0.24642719328403473,
-0.02943429164... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#rebuild-classes,-objectbricks,-fieldcollections-and-customlayouts | Rebuild classes, objectBricks, fieldCollections and customLayouts
Make sure you ran the following commands to rebuild the classes, objectBricks, fieldCollections and customLayouts:
bin/console doctrine:migration:exec 'Pimcore\Bundle\CoreBundle\Migrations\Version20230412105530'
| Rebuild classes, objectBricks, fieldCollections and customLayouts | [
-0.2712763249874115,
0.06102476641535759,
-0.11546020954847336,
0.1950766146183014,
0.22513620555400848,
-0.12291517853736877,
0.00515788933262229,
0.20092593133449554,
-0.3941167891025543,
0.07898423075675964,
-0.09910077601671219,
0.5208311080932617,
0.02845584787428379,
0.09580679982900... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#additional-cleanups | Additional Cleanups
Remove var/config/system.yaml after migrating all settings.
| Additional Cleanups | [
-0.23377639055252075,
-0.20707447826862335,
-0.14858974516391754,
-0.10211943835020065,
0.5457485318183899,
0.03359918296337128,
0.21640194952487946,
0.24107366800308228,
-0.005616225302219391,
0.07340257614850998,
-0.03781912475824356,
0.12157625705003738,
0.05186299979686737,
-0.03672367... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#server-configuration | Server Configuration
WebDav: please keep in mind that the nginx configuration has changed due to the WebDav path being moved. Please adapt your configuration accordingly by following the instruction under the WebDav section in the upgrade notes page.
| Server Configuration | [
-0.02726013958454132,
-0.015132960863411427,
-0.1475706249475479,
-0.18660977482795715,
0.12831759452819824,
-0.2829563319683075,
0.2954394221305847,
0.32821494340896606,
-0.09474682807922363,
-0.014475550502538681,
0.0705241709947586,
0.06794451922178268,
0.11939038336277008,
0.0243909712... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore/Vto_V11#update-symfony-messenger-worker-configuration | Update Symfony Messenger Worker Configuration
With Pimcore 11, certain Symfony Messenger tasks were moved to a separate receiver. Make sure you adapt your Symfony Messenger worker configuration (e.g. your supervisor configuration here so that all receivers are consumed. Newly added consumers are:
pimcore_scheduled_ta... | Update Symfony Messenger Worker Configuration | [
-0.06784176081418991,
0.011810127645730972,
-0.06611699610948563,
-0.0872388482093811,
0.1618318110704422,
-0.35096538066864014,
0.32818153500556946,
0.13272637128829956,
-0.08895636349916458,
0.36014440655708313,
-0.24173077940940857,
0.2889197766780853,
-0.022474054247140884,
-0.07497376... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.