url stringlengths 50 196 | text stringlengths 3 17.2k | heading stringlengths 2 103 | embeddings list |
|---|---|---|---|
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore#updating-pimcore | Updating Pimcore | Updating Pimcore | [
-0.2810118496417999,
-0.17329102754592896,
-0.2864556908607483,
0.014452464878559113,
-0.05430994927883148,
-0.22743982076644897,
-0.1776028722524643,
-0.012656846083700657,
-0.48310989141464233,
0.19854845106601715,
-0.13407352566719055,
0.4056268334388733,
0.15816202759742737,
0.10483969... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore#our-backward-compatibility-promise | Our Backward Compatibility Promise
Since we're building on top of Symfony and in an app, Pimcore and Symfony code get mixed together, it makes sense that we're adopting the same backward compatibility promise for PHP code.
For further information on how you can ensure that your application won't break when upgrading to... | Our Backward Compatibility Promise | [
-0.3143731355667114,
0.0532224178314209,
-0.24003148078918457,
-0.1774994283914566,
0.12189289182424545,
-0.3115478456020355,
0.02806953527033329,
0.24395354092121124,
-0.14759358763694763,
0.3408479392528534,
0.2925638258457184,
0.10951073467731476,
0.06518794596195221,
-0.194873988628387... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore#upgrading-within-version-11 | Upgrading within Version 11
Carefully read our Upgrade Notes before any update.
Check your version constraint for pimcore/pimcore in your composer.json and adapt it if necessary to match with the desired target version.
Run COMPOSER_MEMORY_LIMIT=-1 composer update
Clear the data cache bin/console pimcore:cache:clear
... | Upgrading within Version 11 | [
-0.44447192549705505,
-0.03527141734957695,
-0.23493064939975739,
0.1198730394244194,
0.13895268738269806,
-0.2838297188282013,
-0.3387351334095001,
0.25745096802711487,
-0.5377105474472046,
0.3772713243961334,
-0.05708535015583038,
0.4052982032299042,
-0.028606006875634193,
0.211203545331... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Updating_Pimcore#upgrading-from-earlier-versions | Upgrading from earlier Versions
Upgrade from Version 6 to Version 10
Preparing for Version 11
Upgrade from Version 10 to Version 11
| Upgrading from earlier Versions | [
-0.3649442791938782,
-0.3013860285282135,
-0.3868638873100281,
-0.06309610605239868,
0.19029758870601654,
0.028490623459219933,
-0.03531902655959129,
0.2433534860610962,
-0.05663033947348595,
0.17310307919979095,
0.11919821798801422,
0.15942539274692535,
0.025104280561208725,
0.14562714099... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#upgrade-notes | Upgrade Notes | Upgrade Notes | [
-0.02674354985356331,
-0.12655343115329742,
-0.3046375811100006,
0.17332887649536133,
0.3031214475631714,
0.11353010684251785,
-0.2813548445701599,
0.009953399188816547,
-0.2989424765110016,
0.19082218408584595,
0.041895221918821335,
0.150481715798378,
-0.06226081773638725,
0.0015277648344... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#pimcore-11.0.7 | Pimcore 11.0.7
Putting null to the Pimcore\Model\DataObject\Data::setIndex() method is deprecated now. Only booleans are allowed.
| Pimcore 11.0.7 | [
-0.4470316469669342,
0.0033783733379095793,
-0.11696533858776093,
0.04015973210334778,
-0.08566884696483612,
-0.2509649395942688,
0.5399138331413269,
0.28437983989715576,
-0.12456975877285004,
0.22217071056365967,
-0.18621836602687836,
0.4348629117012024,
0.04958583787083626,
0.32424375414... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#pimcore-11.0.0 | Pimcore 11.0.0 | Pimcore 11.0.0 | [
-0.3840812146663666,
-0.35940149426460266,
-0.20955835282802582,
0.17022286355495453,
-0.04995088279247284,
-0.3113858997821808,
-0.04787704348564148,
-0.029604805633425713,
-0.49038979411125183,
0.32757675647735596,
-0.13590633869171143,
0.4610854387283325,
-0.03770364448428154,
0.3090666... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#api | API | API | [
-0.01116925198584795,
-0.14446185529232025,
-0.4370565116405487,
0.16454941034317017,
-0.14709721505641937,
-0.35483381152153015,
-0.04585418477654457,
0.15700805187225342,
0.3246474266052246,
0.19345740973949432,
0.15055255591869354,
0.3016805648803711,
0.10647429525852203,
0.248325765132... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[general]-: | [General] :
Attention: Added native php types for argument types, property types, return types and strict type declaration where possible. Double check your classes which are extending from Pimcore classes and adapt if necessary.
| [General] : | [
-0.2882656753063202,
-0.26851144433021545,
-0.22105297446250916,
0.11882618814706802,
0.2893691062927246,
-0.44411590695381165,
-0.014662484638392925,
0.3034987151622772,
-0.2371641993522644,
0.14245736598968506,
-0.03777005523443222,
0.3898475766181946,
0.0235623586922884,
0.1510104387998... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[bootstrap]-: | [Bootstrap] :
Relying on Pimcore\Bootstrap::bootstrap() for autoloading classes will not work anymore.
Removed unused constant PIMCORE_APP_BUNDLE_CLASS_FILE
| [Bootstrap] : | [
-0.2331862598657608,
-0.12771935760974884,
-0.18885914981365204,
0.0038262824527919292,
0.49987906217575073,
-0.13701210916042328,
0.0449846126139164,
0.22310547530651093,
-0.11805091798305511,
0.04674285650253296,
0.06901527941226959,
0.3944917619228363,
0.002865081187337637,
0.3038112223... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[events]-: | [Events] :
Event pimcore.element.note.postAdd has been removed. Use pimcore.note.postAdd instead. Note: The event type changed from ElementEvent to ModelEvent.
Report Event pimcore.admin.reports.save_settings has been renamed to pimcore.reports.save_settings.
Moved SEARCH_LIST_BEFORE_FILTER_PREPARE, SEARCH_LIST_BEFORE... | [Events] : | [
-0.42835649847984314,
-0.09287527203559875,
-0.12574875354766846,
-0.17524513602256775,
0.17493093013763428,
-0.17150413990020752,
0.01806536503136158,
0.20781950652599335,
0.049068354070186615,
0.04541679099202156,
-0.42947301268577576,
0.26041674613952637,
-0.19134807586669922,
0.1384214... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[installer]-: | [Installer] :
Removed --ignore-existing-config option from the pimcore:install command. The system.yaml file is not used anymore and therefore this flag became obsolete. See preparing guide
Changed the return type of Pimcore\Extension\Bundle\Installer\InstallerInterface::getOutput to BufferedOutput | NullOutput.
Addi... | [Installer] : | [
-0.3969498872756958,
-0.3370985984802246,
0.02978208288550377,
-0.12914419174194336,
0.05722394958138466,
-0.16277951002120972,
0.10722316056489944,
-0.12384152412414551,
-0.17692193388938904,
0.250670850276947,
0.0551992692053318,
0.5151394009590149,
-0.013773464597761631,
0.2199136167764... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[logging]-: | [Logging] :
Removed constant PIMCORE_PHP_ERROR_LOG
Bumped monolog/monolog to ^3.2 and symfony/monolog-bundle to ^3.8 (which adds support for monolog v3). Please adapt your custom implementation accordingly, eg. log records are now LogRecord Objects instead of array.
Removed the ability to use the pimcore_log GET para... | [Logging] : | [
-0.16325199604034424,
-0.20841996371746063,
-0.07461560517549515,
-0.035595525056123734,
-0.03183244541287422,
-0.3555304706096649,
0.25719520449638367,
0.256098210811615,
-0.09047014266252518,
0.01579023338854313,
-0.11073409020900726,
0.38311609625816345,
-0.2203471064567566,
-0.08358889... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[miscellaneous]-: | [Miscellaneous] :
Marked Pimcore\Model\User\AbstractUser and Pimcore\Model\User\UserRole classes as abstract.
Marked Pimcore\File as internal. This class shouldn't be used anymore, use Symfony\Component\Filesystem instead.
| [Miscellaneous] : | [
-0.12052178382873535,
0.24195419251918793,
-0.08646135777235031,
0.1366826444864273,
0.2963133156299591,
-0.2675751745700836,
0.3148379623889923,
0.19207161664962769,
-0.19992226362228394,
0.2959689199924469,
-0.12156566232442856,
0.11875871568918228,
-0.09265530109405518,
-0.0718606114387... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[further-removed-api-features]-: | [Further Removed API Features] :
Removed getChilds, setChilds and hasChild use getChildren, setChildren and hasChildren instead.
Removed PhpArrayTable class
Removed deprecated PhpArrayFileTable.
Removed Pimcore\Db\Helper::insertOrUpdate() method, please use Pimcore\Db\Helper::upsert() instead.
Removed deprecated Pimco... | [Further Removed API Features] : | [
-0.15013287961483002,
-0.0007831818656995893,
-0.28937599062919617,
0.09895909577608109,
0.06144287437200546,
-0.26244261860847473,
-0.07514938712120056,
0.44129079580307007,
-0.21952496469020844,
0.20556387305259705,
-0.09768298268318176,
0.5312103629112244,
0.08526331186294556,
0.0122501... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[further-relevant-third-party-dependency-upgrades]-: | [Further relevant Third Party Dependency Upgrades] :
Bumped friendsofsymfony/jsrouting-bundle to version ^3.2.1
Bumped Symfony packages to "^6.2".
Cleanup unused Symfony packages from composer.json, eg. form, web-link, see also #13097
Bumped mjaschen/phpgeo to "^4.0".
Bumped codeception/codecepti... | [Further relevant Third Party Dependency Upgrades] : | [
-0.26942968368530273,
-0.05212315917015076,
-0.08595988899469376,
0.18303333222866058,
0.0849432498216629,
-0.3049938976764679,
0.18951056897640228,
0.4758932590484619,
-0.07845721393823624,
0.1891496181488037,
-0.1809140294790268,
0.4558347463607788,
0.002597142942249775,
0.05960326641798... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#admin-ui | Admin UI | Admin UI | [
-0.02806149795651436,
-0.4005594849586487,
-0.35120853781700134,
0.05608655512332916,
0.20957593619823456,
-0.1186603456735611,
0.221607968211174,
-0.057643670588731766,
0.271919846534729,
0.20985664427280426,
0.12294799834489822,
0.0131558021530509,
0.04396658018231392,
0.3126578032970428... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[general]-: | [General] :
Removed adminer as built-in database management tool.
Removed deprecated Admin Event classes: Pimcore\Event\Admin\*, Pimcore\Event\AdminEvents, Pimcore\Event\Model\*.
Changed the navigation building process. It is easier to add main and submenus. For details please see Adding Custom Main Navigation Items
| [General] : | [
-0.09439021348953247,
-0.05969390273094177,
-0.24622437357902527,
0.18835408985614777,
0.03143260255455971,
0.01597466692328453,
-0.30976173281669617,
0.22249194979667664,
-0.09667360037565231,
0.10411756485700607,
-0.19218795001506805,
0.0823192223906517,
0.012418602593243122,
0.070779822... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[authentication]-: | [Authentication] :
Removed support old authentication system (not setting security.enable_authenticator_manager: true in security.yaml).
Removed BruteforceProtection, use Symfony defaults now
Removed PreAuthenticatedAdminToken
Admin Login Events
Removed AdminEvents::LOGIN_CREDENTIALS event.
Removed AdminEvents::LOGIN... | [Authentication] : | [
-0.11860159039497375,
-0.027807557955384254,
-0.1228095069527626,
-0.03179839625954628,
0.23699334263801575,
-0.3054571747779846,
0.18098828196525574,
0.16065412759780884,
-0.20962770283222198,
0.16603636741638184,
-0.08979220688343048,
0.1673475205898285,
0.20750278234481812,
0.0012199950... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[js]-: | [JS] :
Packaged some JS libraries with encore
Removed deprecated JS functions (ts() and pimcore.helpers.addCsrfTokenToUrl())
Removed Plugin Broker BC layer for JS events
| [JS] : | [
-0.23943336308002472,
-0.33050215244293213,
-0.22531449794769287,
-0.0135037861764431,
0.03425123170018196,
-0.2850905656814575,
-0.019011542201042175,
0.28842106461524963,
-0.30498743057250977,
0.17556431889533997,
0.006279557012021542,
0.5359963178634644,
0.07425513118505478,
0.551825523... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[security]-: | [Security] :
Enabled Content Security Policy by default.
Implemented Symfony HTML sanitizer for WYSIWYG editors. Please make sure to sanitize your persisted data with help of this script.
Also, when using API to set WYSIWYG data, please pass encoded characters for html entities <,>, & etc.
The data is encode... | [Security] : | [
0.04557051882147789,
0.09046608209609985,
-0.12217056006193161,
-0.06453205645084381,
0.25534147024154663,
-0.13350623846054077,
0.36613965034484863,
0.3762218952178955,
0.10032255947589874,
0.2650805115699768,
0.13738778233528137,
0.08499899506568909,
0.09603873640298843,
-0.0225394759327... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#bundles | Bundles | Bundles | [
-0.17685015499591827,
-0.5897424817085266,
-0.28009840846061707,
0.34388604760169983,
0.1460387259721756,
-0.018008003011345863,
0.24503110349178314,
0.1689995527267456,
-0.27876654267311096,
0.23702654242515564,
-0.12841898202896118,
0.22574253380298615,
-0.14708077907562256,
0.2037694752... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[bundles-general]-: | [Bundles General] :
Removed support for loading bundles through extensions.php.
Removed Extension Manager(Tools -> Bundles & Bricks option) from Admin UI.
Removed commands: pimcore:bundle:enable, pimcore:bundle:disable.
Removed dontCheckEnabled config support from Areablock editable.
The default behaviour of as... | [Bundles General] : | [
-0.3312496542930603,
-0.00601361645385623,
-0.13722394406795502,
0.1058499664068222,
0.18826153874397278,
-0.21843942999839783,
0.1678418219089508,
0.24491265416145325,
-0.07263168692588806,
0.10384771227836609,
-0.007629832718521357,
0.3826601803302765,
0.04487761855125427,
-0.34238946437... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[extracted-core-functionality]-: | [Extracted Core Functionality] :
Functionality that was moved into its own bundle inside pimcore/pimcore repository and needs to be enabled during Pimcore install or in config/bundles.php:
[Application Logger] Application logger has been moved into PimcoreApplicationLoggerBundle. Please pay attention to the new nam... | [Extracted Core Functionality] : | [
0.08481848984956741,
-0.039046257734298706,
-0.26059457659721375,
0.0024817700032144785,
-0.041984885931015015,
-0.10786434262990952,
-0.1482732743024826,
0.3841557800769806,
-0.299609512090683,
0.05622843652963638,
-0.40875378251075745,
0.39627140760421753,
-0.016541576012969017,
0.037604... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#core | Core | Core | [
-0.30787238478660583,
-0.853767454624176,
-0.2857811748981476,
0.3956694006919861,
0.07500457763671875,
0.0036216049920767546,
-0.16554659605026245,
0.019875219091773033,
-0.054483573883771896,
0.18118171393871307,
-0.29007554054260254,
0.3230917453765869,
0.12825645506381989,
-0.047544501... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[commands]-: | [Commands] :
Removed webmozarts/console-parallelization dependency to make parallelization optional. If you still want to use parallelization for console commands, please add the dependency to your own composer.json.
Removed the deprecated Parallelization::configureParallelization() method.
Removed the deprecated trai... | [Commands] : | [
-0.3962690830230713,
-0.16855540871620178,
-0.21250386536121368,
-0.10276208072900772,
0.011027495376765728,
-0.026915734633803368,
0.08851514011621475,
0.3995475471019745,
-0.29640427231788635,
0.33738964796066284,
-0.20652909576892853,
0.25641298294067383,
0.07540648430585861,
-0.3869317... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[configuration]-: | [Configuration] :
Pimcore\Config\Config has been removed, see #12477. Please use the returned array instead, e.g.
$web2printConfig = Config::getWeb2PrintConfig();
$web2printConfig = $web2printConfig['chromiumSettings'];
Removed legacy callback from LocationAwareConfigRepository. Therefore, configurations in the old... | [Configuration] : | [
-0.1489349603652954,
0.022024517878890038,
-0.0870838537812233,
-0.059460874646902084,
0.17285187542438507,
-0.22048015892505646,
0.22996969521045685,
0.4169642925262451,
-0.2710326611995697,
0.006370642688125372,
-0.2348003387451172,
0.2608104944229126,
0.08474364131689072,
0.082914434373... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[corebundle]-: | [CoreBundle] :
Please update CoreBundle config resource path from @PimcoreCoreBundle/Resources/config/... to @PimcoreCoreBundle/config/.. in your project configurations.
Priority of PimcoreCoreBundle has been changed to -10 to make sure that it is loaded after default bundles.
| [CoreBundle] : | [
-0.41157829761505127,
-0.2331777662038803,
-0.14698496460914612,
0.08422885090112686,
0.18387901782989502,
-0.14274261891841888,
-0.04245731234550476,
0.0907394140958786,
-0.3496509790420532,
0.17960205674171448,
-0.041144635528326035,
0.7425443530082703,
0.07667222619056702,
0.17288348078... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[environment]-: | [Environment] :
Removed symfony/dotenv dependency to make loading of .env files optional. please add the requirement to your composer.json, if you still want to use .env files.
Removed PIMCORE_SKIP_DOTENV_FILE environment var support. You still can use environment specific file like .env.test or .env.prod for environm... | [Environment] : | [
-0.3037289083003998,
-0.09949038922786713,
-0.14095430076122284,
-0.03712497279047966,
0.2713340222835541,
-0.32934266328811646,
0.24909040331840515,
0.13470135629177094,
-0.0744769349694252,
0.2823646068572998,
0.12231708317995071,
0.3632138669490814,
0.0025366488844156265,
0.269319444894... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[gotenberg]-: | [Gotenberg] :
Introducing support for Gotenberg as PDF generation, conversion, merge etc.. tool
[Asset] Added adapter (as alternative to LibreOffice) for preview generation of supported document type assets and set it as default adapter.
[Web2Print] Added settings option, configuration and processor for PDF preview an... | [Gotenberg] : | [
-0.26515722274780273,
-0.28858035802841187,
-0.2406247854232788,
-0.23335322737693787,
-0.2737550735473633,
0.0016941814683377743,
0.051596008241176605,
0.7004395127296448,
-0.055318109691143036,
0.07356917858123779,
-0.17329099774360657,
0.38625553250312805,
0.007451604586094618,
0.269589... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[maintenance]-: | [Maintenance] :
Removed --async & --force option from pimcore:maintenance command. Please make sure to setup to messenger:consume pimcore_maintenance independent
| [Maintenance] : | [
-0.31808891892433167,
-0.21259647607803345,
-0.17055174708366394,
-0.09981101751327515,
0.180227592587471,
-0.2718125581741333,
0.24668361246585846,
-0.003980378154665232,
-0.11908645182847977,
0.256997287273407,
0.023091046139597893,
0.2611972391605377,
-0.01809348352253437,
-0.0913476869... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[migrations]-: | [Migrations] :
Removed executeMigrationsUp from Pimcore\Composer.
Pimcore does not run core migrations after composer update automatically anymore.
Make sure that migrations are executed by running the command bin/console doctrine:migrations:migrate --prefix=Pimcore\\Bundle\\CoreBundle.
| [Migrations] : | [
-0.5038673877716064,
0.12669157981872559,
-0.14069299399852753,
-0.04751450568437576,
0.09672969579696655,
-0.2999591827392578,
-0.0999811664223671,
0.050233423709869385,
-0.4585604667663574,
0.2285621613264084,
-0.08230972290039062,
0.5368534922599792,
-0.01429380290210247,
0.089699208736... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[naming]-: | [Naming] :
Renamed master, blacklist and whitelist to main, blocklist, allowlist
| [Naming] : | [
0.16389387845993042,
-0.254906564950943,
-0.3084241449832916,
0.013527117669582367,
0.26631438732147217,
0.21204210817813873,
0.2484085112810135,
0.1719307154417038,
0.392871230840683,
0.05176277458667755,
-0.26544684171676636,
-0.031475730240345,
-0.15979716181755066,
0.09463725239038467,... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[permissions]-: | [Permissions] :
Permission for DataObjects Classes has been structured in a more granular way to have more control. Field collections, objects bricks, classification stores and quantity value units now have their own permission.
| [Permissions] : | [
0.09375768154859543,
0.33222782611846924,
-0.17679427564144135,
0.028882356360554695,
0.20981493592262268,
-0.19978930056095123,
0.5301458835601807,
0.09944784641265869,
-0.2014736384153366,
0.23791006207466125,
-0.2286231368780136,
0.23324249684810638,
-0.14210161566734314,
-0.15242716670... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[sessions]-: | [Sessions] :
Removed AdminSessionHandler and AdminSessionListener. The session is now handled by Symfony.
Removed SessionConfiguratorInterface & SessionConfigurator so services with tag pimcore.session.configurator will not register session bags anymore.
Removed parameter pimcore.admin.session.attribute_bags
Targ... | [Sessions] : | [
-0.09750877320766449,
-0.08787650614976883,
-0.060817766934633255,
0.2155994325876236,
0.23249685764312744,
-0.3077899217605591,
0.21561019122600555,
0.054158154875040054,
-0.1043204516172409,
0.013049107044935226,
-0.2324119508266449,
0.11875822395086288,
0.03496042266488075,
0.1484263092... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#ecommerce | Ecommerce | Ecommerce | [
0.28516629338264465,
-0.4171285331249237,
-0.46548354625701904,
0.10774678736925125,
0.10931551456451416,
-0.270105242729187,
0.21587739884853363,
-0.14441309869289398,
0.04533495381474495,
-0.030584298074245453,
0.048446595668792725,
0.14364364743232727,
0.08401373773813248,
0.48516800999... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[ecommerce-general]-: | [Ecommerce General] :
Ecommerce bundle has been moved into a package pimcore/ecommerce-bundle. If you wish to continue using the ecommerce framework, then please require the package in your composer.json and install it after enabling in config/bundles.php.
The constructor of the following services has been changed, pl... | [Ecommerce General] : | [
-0.04562820494174957,
-0.03468332439661026,
-0.24003814160823822,
0.060951970517635345,
0.018977772444486618,
-0.0679120272397995,
-0.10569498687982559,
0.16185852885246277,
-0.0696602389216423,
-0.09758539497852325,
0.01261975895613432,
0.41817405819892883,
-0.12529101967811584,
0.2363391... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[indexservice]-: | [IndexService] :
Please make sure to rebuild your product index to make sure changes apply accordingly (this is relevant for mysql and elasticsearch indices). As an alternative you could manually rename and remove o_ from all index columns/fields.
| [IndexService] : | [
0.05786344036459923,
-0.05227121338248253,
-0.2168750762939453,
-0.3132080137729645,
0.0673818290233612,
-0.14042732119560242,
0.3834897577762604,
0.26104944944381714,
0.1204637885093689,
0.21585987508296967,
0.03899011388421059,
0.2785867750644684,
-0.11139214783906937,
0.233867347240448,... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[product-interfaces]-: | [Product Interfaces] :
Changed return type-hints of CheckoutableInterface methods getOSPrice, getOSPriceInfo, getOSAvailabilityInfo, getPriceSystemName, getAvailabilitySystemName, getPriceSystemImplementation, getAvailabilitySystemImplementation to be non-nullable.
| [Product Interfaces] : | [
0.05483594164252281,
-0.38806605339050293,
-0.16125555336475372,
0.03151171654462814,
0.3077758550643921,
-0.3980104923248291,
0.4134362041950226,
0.29010841250419617,
0.18819864094257355,
0.1812705397605896,
-0.17802992463111877,
0.7240352034568787,
0.14560985565185547,
0.4673775434494018... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#elements | Elements | Elements | [
-0.09101356565952301,
-0.7061284184455872,
-0.44083482027053833,
0.20507001876831055,
0.22138217091560364,
-0.02869785577058792,
0.18110832571983337,
0.2561376988887787,
0.24615514278411865,
0.5161216259002686,
-0.1284516602754593,
0.011162884533405304,
-0.11443860083818436,
0.231973767280... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[all]-: | [All] :
Added setParentId, setType and setParent methods to Pimcore\Model\Element\ElementInterface
Removed fallback to parent id 1, when an element with a non-existing parent id gets created.
Passing $force parameter as boolean is not valid anymore in getById, getByPath, getElementById methods. Instead, please pass i... | [All] : | [
-0.24985940754413605,
-0.058127716183662415,
-0.18502476811408997,
0.09481649100780487,
0.2144962102174759,
-0.23819373548030853,
0.2953123450279236,
0.3272288143634796,
-0.1664792150259018,
0.10221648961305618,
-0.25834381580352783,
0.43713968992233276,
0.1196351870894432,
0.3941146433353... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[dataobjects][assets][documents]-: | [DataObjects][Assets][Documents] :
Datetime values for scheduled tasks, application logger and notifications are now displayed in the local timezone.
| [DataObjects][Assets][Documents] : | [
-0.15674352645874023,
0.11036266386508942,
-0.22559741139411926,
-0.016275744885206223,
0.14545191824436188,
-0.18000277876853943,
0.29740598797798157,
0.11472168564796448,
-0.14938212931156158,
0.23444926738739014,
0.08151828497648239,
0.4264780879020691,
-0.21764309704303741,
-0.15569321... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[dataobjects][documents]-: | [DataObjects][Documents] :
Calling getChildren/getSiblings on AbstractObject, Document and Asset now returns unloaded listing. If the list is not traveresed immediately, then it is required to call load() explicitily.
Removed deprecated methods getObject() and setObject() on the classes Pimcore\Model\Document\Link and... | [DataObjects][Documents] : | [
-0.2994714081287384,
-0.08301873505115509,
-0.1874990463256836,
0.2696165442466736,
0.2947201430797577,
-0.179879292845726,
0.21341371536254883,
0.321605384349823,
-0.027426205575466156,
0.050477445125579834,
-0.3020547032356262,
0.4477185010910034,
0.05750913918018341,
-0.1165733039379119... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#assets | Assets
Refactored Pimcore\Model\Asset::getMetadata method to allow listing of all metadata entries filtered by a specific language. Prior this version, the language filter was only available when a specific metadata name was defined in the parameters. Added native type hints and related tests.
Removed the deprecated m... | Assets | [
-0.11697457730770111,
0.09956427663564682,
-0.24729560315608978,
0.10937090218067169,
0.033026449382305145,
-0.3216439485549927,
0.20765899121761322,
0.6425760388374329,
-0.19923928380012512,
-0.0027083514723926783,
-0.4867435097694397,
0.4507129192352295,
-0.12667866051197052,
0.024938808... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[image-optimizer]-: | [Image Optimizer] :
Removed all the Image Optimizer services (e.g. PngCrushOptimizer, JpegoptimOptimizer etc.) as image optimization is done by the new package spatie/image-optimizer.
| [Image Optimizer] : | [
0.024783002212643623,
-0.24712015688419342,
-0.21069729328155518,
-0.06420637667179108,
0.20283271372318268,
-0.11659491062164307,
0.2262580245733261,
0.35291188955307007,
-0.2290838360786438,
0.2723141014575958,
0.05196220427751541,
0.38690683245658875,
-0.07732359319925308,
-0.1003584563... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[webdav]-: | [WebDAV] :
WebDAV url has been changed from https://YOUR-DOMAIN/admin/asset/webdav to https://YOUR-DOMAIN/asset/webdav
As result of this change, the following changes are required in your nginx configuration:
# Assets
....
location ~* ^(?!/admin)(.+?)....
New:
# Assets
....
location ~* ^(?!/admin|/asset/webdav)(.+?)... | [WebDAV] : | [
-0.018652314320206642,
0.09023857861757278,
-0.16563481092453003,
-0.238877534866333,
0.21593742072582245,
-0.21282395720481873,
0.34857431054115295,
0.47449854016304016,
0.08811596035957336,
0.014362527057528496,
-0.010972639545798302,
0.04322657361626625,
0.23928971588611603,
-0.24990355... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#data-objects | Data Objects
Remove "generate type declarations" in class definitions
Removed method_exists bc layer, please use the corresponding interfaces instead. For details please see #9571
isEqual() for advanced relational field types does not check for type equality of meta fields anymore, see #12595
Added return... | Data Objects | [
-0.3485862910747528,
0.1489010900259018,
-0.24514023959636688,
0.04459978640079498,
0.1718510240316391,
-0.30808019638061523,
0.0331619456410408,
0.5884522199630737,
-0.4011349081993103,
0.17186963558197021,
-0.2556760609149933,
0.5903365015983582,
-0.12113180011510849,
0.461700975894928,
... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[class-definitions]-: | [Class Definitions] :
Class Resolver does not catch exceptions anymore.
| [Class Definitions] : | [
-0.16631880402565002,
0.056561727076768875,
-0.16870741546154022,
0.006474476773291826,
0.3318506181240082,
-0.2620195746421814,
0.05172903090715408,
0.06118223816156387,
-0.238687664270401,
0.2495284229516983,
0.32537412643432617,
0.0631980374455452,
-0.239615336060524,
-0.406896203756332... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[classsavedinterface]-: | [ClassSavedInterface] :
Removed method_exists bc layer. Please add the corresponding ClassSavedInterface interface to your custom field definitions. For more details check the 10.6.0 patch notes.
| [ClassSavedInterface] : | [
-0.21384678781032562,
-0.27938640117645264,
-0.12178466469049454,
0.12587633728981018,
0.0996171087026596,
-0.4269716143608093,
0.533589780330658,
0.20163072645664215,
0.1619451493024826,
0.32532745599746704,
0.07820932567119598,
0.5505704879760742,
-0.08561379462480545,
0.2092968970537185... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[csv-export]-: | [CSV Export] :
Changed encoding of table data-types to json_encode from base64_encoded.
| [CSV Export] : | [
-0.028044044971466064,
-0.08062659949064255,
-0.2824053168296814,
0.10922128707170486,
0.3431779742240906,
0.018495505675673485,
0.052447907626628876,
0.6672911643981934,
0.11705352365970612,
0.2504124641418457,
0.12384948134422302,
0.2068929374217987,
0.1024501770734787,
0.471008032560348... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[customlayouts]-: | [CustomLayouts] :
Removed command pimcore:deployment:custom-layouts-rebuild as CustomLayouts are migrated to LocationAwareConfigRepository.
| [CustomLayouts] : | [
-0.12787503004074097,
-0.3199397027492523,
-0.18373167514801025,
-0.08485818654298782,
0.13648247718811035,
-0.23028697073459625,
0.3363344967365265,
0.10143443942070007,
-0.3702985346317291,
0.13629281520843506,
-0.22984962165355682,
0.3282533586025238,
0.27375221252441406,
0.035912264138... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[relations]-: | [Relations] :
Add possibility to inline download asset from relations
Add confirm dialog to empty button of relations and add possibility to disable clear relations in the class layout.
| [Relations] : | [
-0.08245332539081573,
-0.02125919610261917,
-0.16143271327018738,
0.3016938269138336,
0.025256261229515076,
-0.11561363190412521,
0.16773127019405365,
0.40195944905281067,
0.19258086383342743,
0.19452910125255585,
-0.3645685613155365,
0.05350716784596443,
0.24670098721981049,
0.08443275094... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[urlslug]-: | [UrlSlug] :
Removed index column and index index from object_url_slugs table as it was not being used anywhere.
Allow processing unpublished fallback document is now default behaviour, removed the related configuration options and usages (allow_processing_unpublished_fallback_document, ElementListener::FORCE_ALLOW_PRO... | [UrlSlug] : | [
0.14266885817050934,
-0.10524661839008331,
-0.045623138546943665,
-0.1408860683441162,
-0.03584139421582222,
-0.29859593510627747,
0.24640101194381714,
0.281300812959671,
-0.0008558776462450624,
0.23290595412254333,
-0.12035641074180603,
0.28376463055610657,
-0.18119122087955475,
-0.020723... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#documents | Documents
Removed the functionality to input metadata html tags in Settings section of the document.
Removed $types property from Pimcore\Model\Document. Use getTypes method instead.
Removed pimcore:document:types from config. The types will be represented by the keys of the type_definitions:map
Removed deprecated Pi... | Documents | [
-0.07160555571317673,
-0.09149845689535141,
-0.057246189564466476,
-0.13964195549488068,
-0.031876642256975174,
-0.10998523235321045,
-0.12639009952545166,
0.39813193678855896,
-0.48303481936454773,
-0.1388750970363617,
-0.3097454607486725,
0.5779853463172913,
0.11889728903770447,
0.118100... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[areabricks]-: | [Areabricks] :
The default template location of AbstractTemplateAreabrick is now TEMPLATE_LOCATION_GLOBAL.
| [Areabricks] : | [
-0.06626152992248535,
-0.30633336305618286,
-0.07944868505001068,
-0.025726232677698135,
0.02895241789519787,
-0.1749543696641922,
0.39221030473709106,
0.13704527914524078,
0.02561764232814312,
0.20944106578826904,
-0.162476047873497,
0.48210880160331726,
0.10668660700321198,
-0.1403737217... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[controllers]-: | [Controllers] :
Removed deprecated SensioFrameworkExtraBundle which affects the following:
@Template annotation must be replaced with #[Template] attribute. Template guessing based on controller::action is not supported anymore.
@ResponseHeader annotation must be replaced with #[ResponseHeader] attribute. Removed d... | [Controllers] : | [
-0.23943299055099487,
-0.34716498851776123,
-0.12051231414079666,
0.029144292697310448,
0.28377410769462585,
-0.24291302263736725,
0.24616803228855133,
0.29764190316200256,
-0.27591899037361145,
0.32826074957847595,
-0.06084778904914856,
0.6033920645713806,
0.2991528809070587,
0.0842790454... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[chromium]-: | [Chromium] :
Added support to run chromium in Docker container and work via websocket for web2print and page previews, along of running it by a local binary.
| [Chromium] : | [
-0.2747630774974823,
-0.4359420835971832,
-0.22666288912296295,
-0.33213934302330017,
-0.1884535253047943,
-0.042880017310380936,
0.22769224643707275,
0.4200981557369232,
0.41713351011276245,
0.06994999945163727,
-0.2506011426448822,
0.23352664709091187,
-0.07109159231185913,
0.35885533690... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[doctype]-: | [DocType] :
staticGeneratorEnabled is now a boolean instead of an integer
| [DocType] : | [
-0.10190777480602264,
0.34309718012809753,
-0.15192365646362305,
-0.08558555692434311,
0.37044277787208557,
-0.3297470808029175,
0.49838894605636597,
0.1533161848783493,
-0.26379597187042236,
0.00406743586063385,
-0.0685795396566391,
0.5716528296470642,
-0.015493514016270638,
-0.3344687819... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[document-editables]-: | [Document Editables] :
Removed method_exists bc layer for getDataEditmode(), rewriteIds() & load(), please use the corresponding interfaces EditmodeDataInterface, IdRewriterInterface & LazyLoadingInterface instead.
| [Document Editables] : | [
-0.16083787381649017,
-0.1880519539117813,
-0.12733156979084015,
-0.0114129688590765,
0.1888648122549057,
-0.22160062193870544,
0.5782436728477478,
0.23203101754188538,
-0.15909326076507568,
0.04456449672579765,
-0.2716367244720459,
0.4277620017528534,
0.10505356639623642,
0.07403257489204... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[navigation]-: | [Navigation] :
Calling the method Pimcore\Navigation\Builder::getNavigation() using extra arguments is
Methods Pimcore\Navigation::setDefaultPageType, Pimcore\Navigation::getDefaultPageType, Pimcore\Navigation\Container::_sort() and Pimcore\Navigation\Page::_normalizePropertyName()` have been marked as internal.
| [Navigation] : | [
0.01412290520966053,
-0.2822352349758148,
-0.18031355738639832,
0.05897920951247215,
0.23052458465099335,
-0.1796768605709076,
0.10244406014680862,
0.3010287582874298,
-0.47384902834892273,
0.31914788484573364,
-0.24501903355121613,
0.4299924075603485,
0.1354869157075882,
-0.07393121719360... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[sites]-: | [Sites] :
Calling absolute path from a site is not possible anymore. If the absolute path is called, a 404 error will be returned instead.
Default Site Id has been updated from default to 0. Please update configs using default site id accordingly.
| [Sites] : | [
-0.18833313882350922,
-0.18430134654045105,
-0.098223976790905,
-0.21093079447746277,
0.20736239850521088,
-0.20164553821086884,
-0.0074586342088878155,
0.25064903497695923,
-0.15149110555648804,
0.09642037749290466,
-0.011193368583917618,
0.30747494101524353,
-0.10771413892507553,
-0.1417... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[video-editable]-: | [Video Editable] :
Removed deprecated and legacy <iframe> attributes: frameborder, webkitAllowFullScreen, mozallowfullscreen, and allowfullscreen for YouTube, Vimeo, and DailyMotion embeds.
| [Video Editable] : | [
-0.02818976901471615,
-0.5448136329650879,
-0.12391513586044312,
-0.4357841908931732,
0.3097389042377472,
-0.055222850292921066,
0.2364869862794876,
0.3554202616214752,
-0.1770014613866806,
0.05909571796655655,
0.05518467351794243,
0.12562374770641327,
-0.060691650956869125,
-0.00350252212... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#infrastructure | Infrastructure | Infrastructure | [
-0.20296359062194824,
0.061224356293678284,
-0.32469069957733154,
0.3107423484325409,
0.20065434277057648,
-0.6611206531524658,
0.5084475874900818,
-0.08411116153001785,
-0.06507208198308945,
0.09361770749092102,
0.09197836369276047,
0.08933310955762863,
0.07109135389328003,
0.170090943574... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[php-options]-: | [PHP Options] :
Removed setting following options: memory_limit, max_execution_time, max_input_time and display_errors
| [PHP Options] : | [
-0.2761264443397522,
-0.4128429591655731,
-0.297309547662735,
0.12322603166103363,
0.13723032176494598,
-0.14899195730686188,
-0.07144622504711151,
0.32814016938209534,
-0.07091912627220154,
0.3409391939640045,
0.1607811003923416,
-0.0566350482404232,
-0.18298111855983734,
-0.0400662869215... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[php]-: | [PHP] :
The minimum supported PHP version is now 8.1 and added support for 8.2
| [PHP] : | [
-0.3130910098552704,
-0.15981711447238922,
-0.33804938197135925,
-0.05932366102933884,
0.02230323664844036,
-0.10709311068058014,
0.006185382604598999,
0.5798556208610535,
0.16599798202514648,
0.31806790828704834,
0.32241517305374146,
-0.1470065861940384,
-0.23458616435527802,
-0.076343402... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[symfony]-: | [Symfony] :
Replace deprecated Symfony\Component\HttpFoundation\RequestMatcher with Symfony\Component\HttpFoundation\ChainRequestMatcher
| [Symfony] : | [
-0.02086545340716839,
0.200375497341156,
-0.1872708946466446,
-0.14295020699501038,
-0.02220340073108673,
-0.28179749846458435,
0.1288721114397049,
0.21208296716213226,
0.005611954256892204,
0.05294571816921234,
0.05722285062074661,
0.08448516577482224,
0.1254127323627472,
-0.2739455103874... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#tools | Tools | Tools | [
-0.09034060686826706,
-0.5674020051956177,
-0.3732592761516571,
0.08780279755592346,
-0.04837917163968086,
0.10574958473443985,
0.1443120390176773,
0.16692142188549042,
0.070025235414505,
0.31390073895454407,
0.18174350261688232,
0.3262505829334259,
-0.21953456103801727,
0.1776081770658493... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[application-logger]-: | [Application Logger] :
Removed deprecated PIMCORE_LOG_FILEOBJECT_DIRECTORY constant, since flysystem is used to save/get fileobjects. Please make sure to adapt your code and migrate your fileobjects manually.
Table names of archive tables are now named with year-month rather than month-year see #8237.
| [Application Logger] : | [
-0.27854493260383606,
0.39132818579673767,
-0.07246807217597961,
0.06355221569538116,
0.187686488032341,
-0.1579677313566208,
0.08232361078262329,
0.4316384792327881,
-0.2181243598461151,
0.08878953009843826,
-0.08742788434028625,
0.6453946232795715,
-0.1457998901605606,
0.0119888577610254... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[cache]-: | [Cache] :
Removed psr/simple-cache dependency, due to the lack of usage in the Core.
Responses containing a header Cache-Control: no-cache, Cache-Control: private or Cache-Control: no-store will no longer be cached by the full page cache.
Removed the Pimcore\Cache\Runtime cache helper and Pimcore\Cache\RuntimeCacheTra... | [Cache] : | [
-0.24520207941532135,
-0.25849682092666626,
-0.11183962225914001,
0.07292565703392029,
0.10997509211301804,
0.021873200312256813,
-0.042177796363830566,
0.3743174374103546,
-0.17577092349529266,
0.16573964059352875,
-0.15393711626529694,
0.33060476183891296,
0.2753429412841797,
-0.04727728... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[console]-: | [Console] :
Methods execInBackgroundUnix & execInBackgroundWindows visibility changed from protected to private and for getSystemEnvironment from public to private.
| [Console] : | [
-0.15993034839630127,
-0.2994416058063507,
-0.08921606838703156,
0.05438416823744774,
0.15896858274936676,
-0.3692452609539032,
0.46234819293022156,
0.19717425107955933,
-0.20911410450935364,
0.38242393732070923,
-0.27475404739379883,
0.3350163698196411,
0.31345653533935547,
-0.40005958080... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[email]-: | [Email] :
Removed the deprecated methods setBodyHtml(), setBodyText(), createAttachment() and setSubject(). Use html(),
Bumped league/html-to-markdown to ^5.1.
| [Email] : | [
-0.16356375813484192,
-0.25617584586143494,
-0.1280272752046585,
0.035443972796201706,
0.28718531131744385,
-0.13683103024959564,
0.06821012496948242,
0.48697495460510254,
-0.11113669723272324,
0.06490670144557953,
0.0851353257894516,
0.1831396371126175,
0.19159820675849915,
0.010687588714... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[translations]-: | [Translations] :
Translations Domains needs to be registered in order to be considered as valid. If you are using custom domains
site_1
site_2
pimcore:
translations:
domains:
- site_1
- site_2
Added Symfony's html sanitizer to \Pimcore\Model\Translation\Dao::save method.
| [Translations] : | [
-0.07524196058511734,
-0.07739539444446564,
-0.10535138845443726,
0.13022468984127045,
0.22738541662693024,
-0.3052279055118561,
0.4374852478504181,
0.09289471060037613,
-0.052016761153936386,
0.18934842944145203,
-0.2993842661380768,
-0.048250775784254074,
0.3322295546531677,
-0.105777256... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade/Upgrade_Notes#[workflows]-: | [Workflows] :
Removed classes Pimcore\Model\Workflow, Pimcore\Model\Workflow\Dao, Pimcore\Model\Workflow\Listing\Dao and Pimcore\Model\Workflow\Listing.
| [Workflows] : | [
-0.21377773582935333,
-0.15418998897075653,
-0.26831185817718506,
0.03402579203248024,
0.34257766604423523,
-0.0979013592004776,
0.2727183699607849,
0.34193554520606995,
0.12985144555568695,
0.12945660948753357,
-0.16838589310646057,
0.37531623244285583,
-0.09157394617795944,
0.09751470386... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade#installation,-setup-and-upgrade | Installation, Setup and Upgrade | Installation, Setup and Upgrade | [
-0.011524313129484653,
-0.25366389751434326,
-0.2932986915111542,
0.19087384641170502,
0.2143167406320572,
0.10328014194965363,
-0.04307671636343002,
-0.09366483241319656,
-0.1423661857843399,
0.08455119282007217,
0.03984846547245979,
0.0846593901515007,
0.05008677393198013,
0.182941690087... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade#general-topics | General Topics
Installation Guide
Apache Configuration
Nginx Configuration
File Permissions
Database Setup
Additional Tools Installation
Updating Pimcore
Upgrade Notes
| General Topics | [
-0.15982121229171753,
-0.1349688023328781,
-0.32731181383132935,
-0.10726991295814514,
-0.08664300292730331,
-0.07727746665477753,
0.04813876748085022,
0.003024178324267268,
-0.29799240827560425,
-0.10416475683450699,
-0.012194911949336529,
-0.008047775365412235,
0.25313007831573486,
0.279... |
https://pimcore.com/docs/platform//Pimcore/Installation_and_Upgrade#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/Best_Practice/Implementing_Product_Information_Management#implementing-product-information-management | Implementing Product Information Management
The concept of PIM encompasses a set of technologies and procedures that allow centralized management of product data and their distribution across different channels. In many common scenarios, information relating to products may come from multiple sources, potentially with ... | Implementing Product Information Management | [
0.08949191868305206,
-0.39418286085128784,
-0.18941965699195862,
0.08468178659677505,
-0.0840144008398056,
-0.2754700183868408,
0.36690109968185425,
-0.1681416928768158,
-0.37809473276138306,
0.022338183596730232,
0.08616185933351517,
0.2075549215078354,
0.17430251836776733,
0.522012531757... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Implementing_Product_Information_Management#defining-the-product-entity | Defining the Product Entity
In the previous section, you learned about the concept of Product Information Management. As the name suggests, in a PIM system, it’s mandatory to create a class that represents the products, and this is what we are going to do in this section.
Pimcore does not set any constraints as far as ... | Defining the Product Entity | [
-0.11166918277740479,
-0.14960592985153198,
-0.16734367609024048,
0.20187731087207794,
0.048896413296461105,
-0.45663169026374817,
0.3610682189464569,
0.03545830398797989,
-0.4285021424293518,
0.17422734200954437,
-0.1715458631515503,
0.3330400288105011,
0.046493034809827805,
0.36879914999... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Implementing_Product_Information_Management#creating-product-variants | Creating Product Variants
In the previous section, you have seen how to define a Product entity and an example of product object creation. In this section, you will learn how to enable the inheritance for the Product class to create product variants and define configurable products. Later in this section, we will see s... | Creating Product Variants | [
-0.14580494165420532,
-0.5486981868743896,
-0.09935527294874191,
0.14529012143611908,
-0.04766315594315529,
-0.45955199003219604,
0.35085785388946533,
-0.11352184414863586,
-0.5036063194274902,
0.47872355580329895,
0.014471304602921009,
0.631077766418457,
-0.07009144872426987,
0.3694570660... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Implementing_Product_Information_Management#object-listing | Object Listing
In the previous example, we have seen how to retrieve the variants of a specific product, using the methods that retrieve the product children. In this example, we will see how to retrieve variants in generic listing methods.
In the following code snippet, you can see how product variants can be retrieve... | Object Listing | [
0.005019372794777155,
-0.6695177555084229,
-0.14584538340568542,
0.39449742436408997,
-0.14767079055309296,
-0.2932737171649933,
0.19199973344802856,
-0.05357343330979347,
-0.13092343509197235,
-0.001962219597771764,
-0.4079560935497284,
0.3314674198627472,
-0.013434495776891708,
0.0957879... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Implementing_Product_Information_Management#creating-a-new-variant | Creating a new Variant
In the previous examples, you learned how to query for existing variants. In this example, you will learn how to create a product variant.
In the following code snippet, you will see how to create a variant for an existing product:
<?php
use Pimcore\Model\DataObject\Product;
use Pimcore\Model\... | Creating a new Variant | [
-0.124383345246315,
-0.5561932921409607,
-0.09106924384832382,
0.15257740020751953,
-0.27647238969802856,
-0.3467535972595215,
0.1853371560573578,
0.01438180822879076,
-0.31220880150794983,
0.23779191076755524,
-0.09073030203580856,
0.4717596471309662,
-0.04704694822430611,
0.4016073048114... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Implementing_Product_Information_Management#creating-a-bundle-product | Creating a Bundle Product
In the previous section, you learned how to enable and create product variants and how to practically use them in code examples. In this section, you will learn how to define bundle products.
In marketing, the concept of Product Bundling is a practice of offering a set of individual products o... | Creating a Bundle Product | [
-0.03585125505924225,
-0.7150228023529053,
0.05471716448664665,
-0.09197194874286652,
-0.29200848937034607,
0.09601787477731705,
0.270122230052948,
-0.05129939317703247,
-0.44684460759162903,
0.047233324497938156,
0.18792587518692017,
0.12682749330997467,
-0.14002487063407898,
0.5207036137... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Implementing_Product_Information_Management#defining-bundle-products | Defining bundle products
In this section, you will learn how to modify the Product class to be able to define bundle products. The easiest solution is to create a self-referenced relation attribute with the Product class itself. This will let you choose the products that will form the bundle from the previously created... | Defining bundle products | [
-0.2141302078962326,
-0.2854802906513214,
-0.06194392591714859,
0.2912452518939972,
0.04492757469415665,
-0.148345485329628,
0.37227123975753784,
-0.06484560668468475,
-0.17770856618881226,
0.2911192774772644,
-0.16443908214569092,
0.43964722752571106,
-0.040737684816122055,
0.318302184343... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Implementing_Product_Information_Management#creating-an-event-listener | Creating an Event Listener
In the previous section, you learned how to define bundle products. In common scenarios, the price of a bundle product is less than the sum of the individual price of the products it’s composed of. It may be useful to automatically calculate the price of a bundle product with a predefined rul... | Creating an Event Listener | [
-0.4413086175918579,
-0.14144182205200195,
0.01996109075844288,
0.20759379863739014,
-0.17732234299182892,
-0.31979408860206604,
0.1887538731098175,
-0.12795765697956085,
-0.45820173621177673,
0.18755747377872467,
-0.11292553693056107,
0.5132241249084473,
-0.24143736064434052,
0.3554735481... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Implementing_Product_Information_Management#managing-different-product-types | Managing different Product Types
In the previous section, you learned how to define bundle products. In this section, you will learn how to manage different types of products without creating a different class for each product type. If you need to manage a heterogeneous set of products, such as shirts and shoes, you wi... | Managing different Product Types | [
-0.0010366641217842698,
-0.3943568170070648,
-0.08653224259614944,
0.5082398653030396,
0.22934195399284363,
-0.1291327029466629,
0.541541337966919,
-0.021705083549022675,
0.14638060331344604,
0.2043600231409073,
-0.1577097773551941,
0.35413965582847595,
-0.22760966420173645,
0.316546022891... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Implementing_Product_Information_Management#working-with-workflows | Working with workflows
A workflow consists of a sequence of processes and tasks that represent the work that must be done to reach a common goal. Typically, we may think about workflows as a graph.
Pimcore Workflow Management provides configuration of multiple workflows on Assets, Documents, and DataObjects, to support... | Working with workflows | [
-0.059069760143756866,
-0.2990074157714844,
-0.16851164400577545,
-0.06387237459421158,
-0.27038466930389404,
-0.4052312672138214,
0.4599332809448242,
-0.07573870569467545,
-0.11263211816549301,
0.12736327946186066,
-0.0000487759753013961,
0.2466789186000824,
0.18808287382125854,
0.3961722... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Implementing_Product_Information_Management#configuring-a-custom-layout | Configuring a Custom Layout
As mentioned before, in the various places of a workflow we can show a custom view for the element. This is made possible by configuring custom layouts on the corresponding class.
To create a custom layout, just open the class definition and click on the Configure custom layouts button. When... | Configuring a Custom Layout | [
-0.0007520580547861755,
-0.39138805866241455,
-0.2069273442029953,
-0.021982209756970406,
-0.12888208031654358,
-0.24890021979808807,
0.517443060874939,
0.019157560542225838,
0.07432863116264343,
0.35262271761894226,
-0.11663033813238144,
0.2914183437824249,
0.06586010009050369,
0.19094388... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Implementing_Product_Information_Management#configuring-a-pimcore-workflow | Configuring a Pimcore Workflow
In the previous section, you learned how to configure custom layouts for Pimcore classes. In this section, you will learn how to configure Pimcore workflows and how to use the previously created custom layouts.
As with many other services, Pimcore workflows must be defined in the config.y... | Configuring a Pimcore Workflow | [
-0.245491161942482,
-0.24200952053070068,
-0.16067086160182953,
-0.09460335969924927,
-0.043406665325164795,
-0.30383414030075073,
0.5003699064254761,
0.07296623289585114,
-0.06259256601333618,
0.26176437735557556,
-0.09170522540807724,
0.6004054546356201,
0.03736892342567444,
0.3287277221... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Implementing_Product_Information_Management#summary | Summary
In this tutorial, you learned the concept of Product Information Management by defining a Product entity and providing practical examples. In the first section of the chapter, you first learned what a PIM is and which are its main features. Then, you learned how to create and configure a Product class, accordin... | Summary | [
-0.08187641948461533,
-0.35594189167022705,
-0.1138678789138794,
0.16930603981018066,
0.023693017661571503,
-0.16927671432495117,
0.30068865418434143,
-0.16860339045524597,
-0.5530347228050232,
0.19329921901226044,
-0.19519610702991486,
0.4882775843143463,
-0.0051164645701646805,
0.4299693... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Implementing_Product_Information_Management#learn-more | Learn more
This was a sample chapter from the book Modernizing Enterprise CMS Using Pimcore by Daniele Fontani, Marco Guiducci, Francesco Minà available at Packt Publishing (2021). You can purchase the full book here. | Learn more | [
-0.1876254379749298,
-0.16918551921844482,
-0.3239814043045044,
-0.18943072855472565,
0.005795908160507679,
-0.30641329288482666,
0.17478442192077637,
-0.09719949215650558,
-0.07207972556352615,
0.2910695970058441,
-0.2894960045814514,
0.26731938123703003,
0.08412506431341171,
0.5089063048... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Multilanguage_Setup#multilanguage-i18n-websites | Multilanguage i18n Websites | Multilanguage i18n Websites | [
0.17138396203517914,
-0.28044643998146057,
-0.3784984052181244,
0.17697913944721222,
-0.09683705121278763,
0.02277611754834652,
0.4333338737487793,
0.01404484361410141,
0.08591218292713165,
-0.0650802031159401,
-0.33390355110168457,
-0.4836508333683014,
0.20222952961921692,
0.1087785810232... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Multilanguage_Setup#best-practice-for-multi-language-websites | Best practice for multi-language websites
Every document has one single language/locale assigned. As a consequence of that, Pimcores best practice in terms of
building multi-language websites is to build a document subtree per language.
This has several advantages:
Localized document keys, URLs and navigation structu... | Best practice for multi-language websites | [
-0.13136379420757294,
-0.27953243255615234,
-0.20730803906917572,
0.25651925802230835,
-0.3078887462615967,
-0.23966842889785767,
0.10160626471042633,
0.016970206052064896,
-0.3717486262321472,
0.26441335678100586,
-0.17547878623008728,
0.05829218402504921,
0.20397290587425232,
0.051301121... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Multilanguage_Setup#localization-tool | Localization Tool
The localization tool for Pimcore documents is a comfort tool which supports creation and management of the same document
for multiple languages. It can be accessed in the editor button row of every document.
Following features are supported:
Creating new documents for another language - either an ... | Localization Tool | [
-0.24494920670986176,
-0.3613739609718323,
-0.1163393184542656,
0.03634120523929596,
-0.19562335312366486,
-0.05481826886534691,
-0.09651442617177963,
0.05697803199291229,
-0.29051488637924194,
0.2730672061443329,
-0.27891671657562256,
0.307839572429657,
0.21718023717403412,
-0.06269823759... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Multilanguage_Setup#content-inheritance | Content Inheritance
Content inheritance is a Pimcore feature to save duplicate data maintenance within documents. This feature is quite handy
in multi language document structures in order to maintain language independent content only once.
For details see Document Inheritance / Content Main Document. | Content Inheritance | [
-0.10137999802827835,
-0.3054152727127075,
-0.10318212956190109,
0.13928493857383728,
0.05932603031396866,
0.16023455560207367,
0.09439326822757721,
0.09593796730041504,
-0.3460569679737091,
0.32047039270401,
0.0054640197195112705,
0.2727038562297821,
0.10712161660194397,
-0.34309199452400... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Adding_Button_To_Object_Editor#add-a-button-to-object-editor | Add a Button to Object Editor
Sometimes it might be useful to add additional buttons to the object editor (or any other editor) in Pimcore Backend
Interface. In terms of product for example to add a download button for a product data sheet - like the following
screen shot shows.
Solution
Create a bundle with a Pimco... | Add a Button to Object Editor | [
-0.3070625066757202,
-0.3388381898403168,
-0.1478596329689026,
-0.1018606647849083,
-0.09399392455816269,
-0.2774704396724701,
0.20482157170772552,
0.17354601621627808,
-0.05449758470058441,
0.10481157898902893,
-0.21038800477981567,
0.7715559005737305,
0.14109990000724792,
0.6017445325851... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Build_Role_Rights_System_for_Frontends#build-role-&-rights-system-for-frontends | Build Role & Rights System for Frontends
A common use case for Pimcore applications are portals with user logins and a complex permission structure like for
example b2b portals.
One way of archiving this is to leverage Symfony Security functionality with access control configuration
and ACLs as described here.
But,... | Build Role & Rights System for Frontends | [
-0.05384048447012901,
-0.057529423385858536,
-0.07063837349414825,
0.41452378034591675,
-0.1523161083459854,
-0.33134061098098755,
0.06443313509225845,
-0.14332400262355804,
-0.15757879614830017,
-0.041124649345874786,
-0.24498695135116577,
-0.01628296822309494,
0.03701942414045334,
0.4604... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Build_Role_Rights_System_for_Frontends#setup-user-authentication-with-symfony-security-and-pimcore-objects | Setup User Authentication with Symfony Security and Pimcore Objects
See the Pimcore docs
for how to integrate Pimcore objects with Symfony Security in general. Here you see how to authenticate against a Pimcore
user object. | Setup User Authentication with Symfony Security and Pimcore Objects | [
-0.11878503859043121,
0.18233728408813477,
-0.13208045065402985,
0.04647831991314888,
-0.015324695035815239,
-0.41810405254364014,
0.33628222346305847,
-0.3434353470802307,
-0.19075323641300201,
0.3444615602493286,
-0.11879491060972214,
0.14082308113574982,
0.11114096641540527,
0.099302552... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Build_Role_Rights_System_for_Frontends#configure-user-permissions-with-pimcore-objects | Configure User Permissions with Pimcore Objects
Use the Frontend Permission Toolkit for configuring permissions
directly within the user objects by using the new data type permissionResource.
A permissionResource represents one specific user right (e.g. login, show prices, order, etc.) and can have the
values allow, d... | Configure User Permissions with Pimcore Objects | [
-0.029423780739307404,
-0.1826178878545761,
-0.1700897514820099,
0.040098145604133606,
-0.026732537895441055,
-0.28645071387290955,
0.20381294190883636,
-0.10364297777414322,
-0.10550487041473389,
0.08735167980194092,
-0.2972099781036377,
0.2113095074892044,
-0.05802442878484726,
0.0143276... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Build_Role_Rights_System_for_Frontends#integrate-user-permissions-in-your-frontend-implementation | Integrate User Permissions in your Frontend Implementation
There are several ways how to integrate the configured user permissions into the Frontend:
Use the Frontend Permission Toolkit Service in your application code to check if user is allowed for a certain resource:
//get user object from Symfony
$userObj... | Integrate User Permissions in your Frontend Implementation | [
-0.02872382663190365,
0.1154523715376854,
-0.10455308109521866,
0.12414468079805374,
-0.07098542898893356,
-0.44025829434394836,
0.15378598868846893,
-0.07996682822704315,
0.057285524904727936,
0.33615612983703613,
-0.10157214850187302,
0.041675809770822525,
0.018259288743138313,
-0.106004... |
https://pimcore.com/docs/platform//Pimcore/Best_Practice/Building_Custom_Rest_APIs#how-to-build-a-custom-rest-api-endpoint | How to Build a Custom REST API Endpoint
Pimcore offers a bundle called Datahub, offering a highly configurable GraphQL interface on most Pimcore entities.
However a common use case for applications build with Pimcore is integrating with external systems,
which requires custom response from API endpoints.
One way to ach... | How to Build a Custom REST API Endpoint | [
-0.12642160058021545,
-0.18513375520706177,
-0.16053980588912964,
0.0038562847767025232,
-0.47400909662246704,
-0.4578458368778229,
-0.11645609140396118,
-0.022783486172556877,
0.1833888292312622,
0.10902068018913269,
-0.15464554727077484,
0.5431679487228394,
0.12406466156244278,
0.5569089... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.