heading stringlengths 2 103 | url stringlengths 50 196 | text stringlengths 3 17.2k | embeddings list |
|---|---|---|---|
Condition [Targeting] Check Weight of Assigned Target Group | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Action_Trigger_Service_Components#condition-[targeting]-check-weight-of-assigned-target-group | Condition [Targeting] Check Weight of Assigned Target Group
This condition can check how often the target group is assigned to the current user in the Targeting Storage (weight).
It always uses the target group stored by the Assigned Target Group trigger.
Optionally the condition can be restricted to certain target gro... | [
-0.12146656960248947,
-0.35375070571899414,
0.2030949890613556,
0.313323438167572,
-0.5372681021690369,
-0.2418719083070755,
-0.008396938443183899,
1.1042282581329346,
-0.399860143661499,
0.22675849497318268,
0.4308791160583496,
0.043454594910144806,
0.20837059617042542,
-0.304172545671463... |
Action [Targeting] Add tracked segment | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Action_Trigger_Service_Components#action-[targeting]-add-tracked-segment | Action [Targeting] Add tracked segment
This action adds the tracked segment (stored by the Segment Tracked trigger) to the customer object. It can be configured
if other segments from the same group should be removed and if the segment application counter should be increased.
Additionally it's possible to configure, if... | [
-0.19214655458927155,
0.5860885381698608,
-0.5181810855865479,
0.3928784430027008,
-0.3677902817726135,
-0.7925554513931274,
-0.00410936726257205,
0.048723869025707245,
0.5512678027153015,
0.4161335527896881,
-0.15417055785655975,
1.025914192199707,
0.29967910051345825,
0.08858658373355865... |
Action [Targeting] Add Target Group Segment | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Action_Trigger_Service_Components#action-[targeting]-add-target-group-segment | Action [Targeting] Add Target Group Segment
If there is a segment assigned to the current target group (stored by the Assigned Target Group trigger), this action adds
it to the customer object. It can be configured if other segments from the same group should be removed and if the
segment application counter should be ... | [
-0.3695611357688904,
0.49709588289260864,
-0.6064844131469727,
0.358896404504776,
-0.3592545688152313,
-0.9431318044662476,
0.015605754218995571,
0.4299631118774414,
0.48945680260658264,
0.43087121844291687,
0.08178546279668808,
0.8037505149841309,
0.20032618939876556,
0.03553196042776108,... |
Example Usecases | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Example_Usecases#example-usecases | Example Usecases
Following examples describe typical usecases for the Pimcore personalization engine in combination with the CMF. | [
0.5766466856002808,
-0.25125977396965027,
0.4478185176849365,
-0.14472047984600067,
-0.9469300508499146,
-0.34580519795417786,
-0.4167651832103729,
-0.7884112000465393,
0.7864471077919006,
0.5669329166412354,
0.389140784740448,
-0.14628125727176666,
0.679987370967865,
0.07652455568313599,
... |
Use Segments 1:1 as Target Groups | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Example_Usecases#use-segments-1:1-as-target-groups | Use Segments 1:1 as Target Groups
The most simple usecase is to use segments 1:1 as target groups. To do so, it is important to create customer segments
and link them to corresponding target groups by activating the checkbox Use As Target Group in segment objects. When
doing so, a target group with the same name is aut... | [
0.1797722727060318,
0.31873664259910583,
-0.11798801273107529,
0.37722668051719666,
-0.5018181800842285,
-0.7326000928878784,
0.16850443184375763,
0.24705475568771362,
0.8124165534973145,
0.2805880010128021,
0.3304447531700134,
0.46739906072616577,
0.3602052927017212,
0.21359089016914368,
... |
Initialize Target Groups based on Customer Object Data | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Example_Usecases#initialize-target-groups-based-on-customer-object-data | Initialize Target Groups based on Customer Object Data
Once the segments are stored in customer objects, the visitor storage should be preinitialised on the customers next
visit, thus the connected target groups should be assigned as the the customers visits the next time - also on another
device.
This can be done with... | [
-0.4555950164794922,
0.10843129456043243,
0.352430135011673,
-0.3401874601840973,
-0.4931892156600952,
-0.5802277326583862,
0.20578144490718842,
0.42638954520225525,
0.32547706365585327,
0.19725489616394043,
0.23990367352962494,
0.8888527750968933,
0.5309087038040161,
-0.19647911190986633,... |
Use Customer Segments as more fine-grained Profiling Entity | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Example_Usecases#use-customer-segments-as-more-fine-grained-profiling-entity | Use Customer Segments as more fine-grained Profiling Entity
There are situations, where customer segments are more fine-grained, where there is no 1:1 link between target groups
and segments, and where not every time a target group is assigned also the persistence in the customer object itself should
be updated.
Typica... | [
0.1958516240119934,
0.31380757689476013,
-0.2104223072528839,
0.0995146632194519,
-0.5887686014175415,
-0.9054112434387207,
-0.31157320737838745,
0.2723160684108734,
0.42992618680000305,
0.3051692247390747,
0.763555645942688,
0.318143367767334,
0.41280266642570496,
0.16824182868003845,
-... |
1) Tracking Customer Segments | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Example_Usecases#1)-tracking-customer-segments | 1) Tracking Customer Segments
Tracking customer segements means collecting customer segments based on the behavior of the visitor. E.g. when the
customer visits certain pages that contain certain information, corresponding customer segements can be tracked.
The collected customer segments are stored per customer and ca... | [
0.1049572303891182,
-0.10235408693552017,
-0.1991046965122223,
0.3103080093860626,
-0.23038716614246368,
-0.24087193608283997,
0.1102827936410904,
-0.380481481552124,
1.0935649871826172,
0.3042515516281128,
0.10873683542013168,
0.8778887391090393,
0.4129812717437744,
-0.18023692071437836,
... |
2) Calculate Target Groups based on Tracked Customer Segmentts | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Example_Usecases#2)-calculate-target-groups-based-on-tracked-customer-segmentts | 2) Calculate Target Groups based on Tracked Customer Segmentts
Once segments are tracked, they can be used for calculating target groups. For example, a target group should be assigned
every fifth time when a segment is tracked. To do so, a targeting rule with [CMF] Has Segment condition and
Assign Target Group is nece... | [
0.14427854120731354,
0.23195412755012512,
0.20283935964107513,
0.42429688572883606,
-0.40557578206062317,
-0.6258383393287659,
-0.003765212371945381,
0.33705243468284607,
0.28081458806991577,
0.3594571352005005,
0.5604258179664612,
0.41358354687690735,
0.07837817072868347,
-0.3216178715229... |
Apply Tracked Segments to Customer objects | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Example_Usecases#apply-tracked-segments-to-customer-objects | Apply Tracked Segments to Customer objects
The last use case is to save tracked segments to the customer object without assigning any target groups to the visitor.
This is especially useful when extracting relevant behavior information out of the visitors behavior and saving it to the
customer object for later segmenta... | [
0.009732366539537907,
0.20315878093242645,
-0.08480512350797653,
0.16287145018577576,
-0.705005943775177,
-0.7063860297203064,
-0.2575637400150299,
0.1514388769865036,
0.4295368790626526,
0.4834686517715454,
-0.11650929600000381,
0.8534992933273315,
0.21403393149375916,
-0.1348788887262344... |
Integration with Pimcore Targeting Engine | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization#integration-with-pimcore-targeting-engine | Integration with Pimcore Targeting Engine
The CMF is tightly integrated into the Pimcore personalization feature and connects the personalization for anonymous
users with the known users managed in CMF. This is provided by:
Connection between Customer Segments and Pimcore Target Groups
Adding additional conditions and... | [
0.17171990871429443,
-0.2517409026622772,
-0.664795458316803,
0.61196368932724,
-0.01935730129480362,
0.11174745857715607,
-0.1822223663330078,
-0.6133021712303162,
-0.014781035482883453,
0.04002918675541878,
0.24949268996715546,
0.41174519062042236,
0.2314852923154831,
-0.0084074083715677... |
Pimcore Target Groups and Customer Segments | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization#pimcore-target-groups-and-customer-segments | Pimcore Target Groups and Customer Segments
First of all one conceptual aspect has to be clarified:
In Pimcore there is the concept of Target Groups. Target groups are assigned to users based on their behavior only and
are not stored anywhere. Thus target groups sum up users with similar behaviour and are the entity to... | [
0.20798751711845398,
-0.06669382750988007,
0.16309338808059692,
0.17315377295017242,
-0.32521748542785645,
-0.35888680815696716,
0.07445324212312698,
-0.30077454447746277,
0.4590607285499573,
0.10360690206289291,
0.3669773042201996,
0.4173884391784668,
0.3448527157306671,
-0.04423033073544... |
Example Usecases | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization#example-usecases | Example Usecases
The the Example Usecases Page for a list of typical usecases that can be implemented with
CMF in combination with Pimcore targeting engine. | [
0.07094866782426834,
-0.3570832908153534,
0.43182119727134705,
0.0939323827624321,
-1.1713881492614746,
-0.44444540143013,
-0.705059826374054,
-0.4928213357925415,
0.8930053114891052,
0.6643782258033752,
0.25968870520591736,
0.013034242205321789,
1.0324264764785767,
0.39901629090309143,
... |
Detail Description of Additional Functionality | https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization#detail-description-of-additional-functionality | Detail Description of Additional Functionality
See the following sub chapters for detail description for relevant additional functionality of Pimcore targeting engine
and CMF Action Trigger Service.
Additional Targeting Rule Compontents
Additional Action Trigger Service Components
| [
0.3861463665962219,
-0.3715081512928009,
-0.2926889657974243,
-0.03580591827630997,
-0.14017526805400848,
0.0230699572712183,
-0.34123337268829346,
-0.3221172094345093,
0.48477309942245483,
0.7468404173851013,
-0.24745048582553864,
0.4429212212562561,
-0.1166413277387619,
-0.07385385036468... |
Customer_Management_Framework | https://pimcore.com/docs/platform//Customer_Management_Framework#customer_management_framework | Customer_Management_Framework
| [
-0.07294555753469467,
-0.19690915942192078,
-0.359774649143219,
0.14095288515090942,
-0.08925826847553253,
-0.5498838424682617,
0.11166176944971085,
-0.6294813752174377,
0.2835856080055237,
0.06113424152135849,
0.20868737995624542,
-0.024694247171282768,
-0.18240399658679962,
0.30217397212... |
title: Customer Management Framework | https://pimcore.com/docs/platform//Customer_Management_Framework#title:-customer-management-framework | title: Customer Management Framework | [
-0.09252622723579407,
-0.15994177758693695,
-0.20017696917057037,
0.4412561357021332,
-0.09152925759553909,
-0.5319796204566956,
-0.13074274361133575,
-0.7334352731704712,
0.3977396786212921,
0.04147166758775711,
0.08408521115779877,
0.3482397198677063,
-0.40710434317588806,
0.632971763610... |
Pimcore Customer Management Framework | https://pimcore.com/docs/platform//Customer_Management_Framework#pimcore-customer-management-framework | Pimcore Customer Management Framework
Pimcore allows to manage any kind of data - unstructured, digital assets and structured content. The most obvious structured content is product data and all data related to products like categories, technologies, brands, etc.
The built-in E-Commerce Framework supports building e-co... | [
0.36864325404167175,
-0.09232201427221298,
-0.15816883742809296,
0.1961008906364441,
-0.07049323618412018,
0.3139715790748596,
-0.11659872531890869,
-1.066884994506836,
0.6625305414199829,
0.6176404356956482,
0.12902578711509705,
0.2095433622598648,
0.3514922857284546,
-0.24035878479480743... |
Provided Functionality in a Nutshell | https://pimcore.com/docs/platform//Customer_Management_Framework#provided-functionality-in-a-nutshell | Provided Functionality in a Nutshell
Customer Data Management based on Pimcore Data Objects.
Storage of Customer Activities from different data feeds.
Customer Segmentation based on data, activities and other criteria.
Duplicate detection and merging.
Enhancement of Pimcore's on-site personalization.
Marketing Automat... | [
0.10718576610088348,
0.023841246962547302,
-0.3065212666988373,
-0.3291422128677368,
-0.4497475028038025,
0.6046470403671265,
-0.2985568642616272,
-0.306942880153656,
1.1255667209625244,
0.41800811886787415,
0.004214111249893904,
0.9498171806335449,
0.13063013553619385,
0.08746396005153656... |
Documentation Overview | https://pimcore.com/docs/platform//Customer_Management_Framework#documentation-overview | Documentation Overview
The following sections provide shortcuts into the documentation to start working with the Customer Management Framework (CMF) for Pimcore:
See the Getting Started section for an overview of the CMF Framework architecture or information about the installation process.
See the Customer-Related Dat... | [
0.41538357734680176,
-0.4676140248775482,
-0.2157198041677475,
-0.13175594806671143,
-0.3110513389110565,
0.10756116360425949,
0.19818556308746338,
-1.0577417612075806,
0.9898086190223694,
0.6523382663726807,
0.18952052295207977,
-0.11049282550811768,
0.11537835001945496,
0.011304129846394... |
Getting Started | https://pimcore.com/docs/platform//Customer_Management_Framework#getting-started | Getting Started
Architecture Overview
Installation and Configuration
| [
0.09602276980876923,
-0.04671015590429306,
-0.34381604194641113,
-0.8635175824165344,
-0.3000859022140503,
0.42983946204185486,
-0.4729170799255371,
-0.21046321094036102,
0.3672943115234375,
0.5427255034446716,
-0.10901185870170593,
-0.33136412501335144,
0.2694529891014099,
-0.000755277229... |
Customer-Related Data | https://pimcore.com/docs/platform//Customer_Management_Framework#customer-related-data | Customer-Related Data
Working with Customers
Working with Activities (ActivityManager, ActivityStore, ActivityView)
Working with Customer Segments
| [
0.01816633529961109,
0.17393280565738678,
-0.753095805644989,
0.15476791560649872,
-0.2884577512741089,
-0.42868345975875854,
0.35053834319114685,
-0.616211473941803,
1.0869617462158203,
0.349465012550354,
-0.6382569670677185,
0.8420482873916626,
0.00553900795057416,
-0.28239795565605164,
... |
Provided services | https://pimcore.com/docs/platform//Customer_Management_Framework#provided-services | Provided services
Customer Duplicates Service
Built-In Marketing Automation Engine
Newsletter System Integration
Rest API Webservice
Integration with Pimcore Targeting Engine
| [
0.15002334117889404,
0.03081350587308407,
-0.29875192046165466,
0.13692298531532288,
-0.986366868019104,
-0.2260853350162506,
-0.5949630737304688,
0.020268086344003677,
0.748971164226532,
0.35092103481292725,
-0.005104220472276211,
0.2667427062988281,
0.40287747979164124,
0.179525598883628... |
Contributing and Development | https://pimcore.com/docs/platform//Customer_Management_Framework#contributing-and-development | Contributing and Development
For details see our Contributing guide. | [
-0.14750996232032776,
-0.1187196895480156,
-0.753412663936615,
-0.3397100567817688,
-0.18838918209075928,
0.049867626279592514,
-0.3469782769680023,
0.2761552929878235,
0.4391913115978241,
0.3911707401275635,
-0.52118980884552,
0.02983568049967289,
0.6890997886657715,
-0.06138625741004944,... |
Google Analytics | https://pimcore.com/docs/platform//Google_Marketing/Analytics#google-analytics | Google Analytics
In order to use Google Analytics you have to install the PimcoreGoogleMarketingBundle.
Make sure to enable it in the bundles.php | [
0.3375930190086365,
0.3561781942844391,
-1.1102845668792725,
0.407552570104599,
-0.9453201293945312,
0.14717517793178558,
0.09155365824699402,
0.19814826548099518,
1.4094769954681396,
0.3921276926994324,
0.5627680420875549,
0.09859489649534225,
0.36372557282447815,
0.009718172252178192,
... |
Disabling the Google Analytics Code | https://pimcore.com/docs/platform//Google_Marketing/Analytics#disabling-the-google-analytics-code | Disabling the Google Analytics Code
Injecting the code can be disabled by calling disable() in the GoogleAnalyticsCodeListener. For example, in a controller
action in an autowired controller:
<?php
namespace App\Controller;
use Pimcore\Bundle\GoogleMarketingBundle\EventListener\Frontend\GoogleAnalyticsCodeListener... | [
-0.5821828246116638,
0.7845088243484497,
-0.6592111587524414,
0.39986902475357056,
-0.4569142758846283,
0.16011779010295868,
0.0824107676744461,
0.18381990492343903,
0.8520708084106445,
0.6001365184783936,
0.3916163146495819,
0.39541953802108765,
0.7397375106811523,
0.02940589375793934,
... |
Customizing the tracking code | https://pimcore.com/docs/platform//Google_Marketing/Analytics#customizing-the-tracking-code | Customizing the tracking code
If you want to influence the generated tracking code, you have multiple possibilities to do so. The tracker code is divided
into multiple code blocks which can be expanded and altered individually. As reference, please see:
the definition of available blocks in the Tracker implementation
... | [
0.043729234486818314,
-0.18500779569149017,
-0.6208387017250061,
-0.25563371181488037,
-0.39995938539505005,
-0.41046664118766785,
-0.10160040855407715,
0.18096080422401428,
0.28235316276550293,
0.3381427228450775,
0.4349864423274994,
0.5733650922775269,
0.36392149329185486,
-0.27447739243... |
Adding code to a block | https://pimcore.com/docs/platform//Google_Marketing/Analytics#adding-code-to-a-block | Adding code to a block
The central part of the Google tracking is the Pimcore\Bundle\GoogleMarketingBundle\Tracker\Tracker class which is defined as service and
which provides a addCodePart() method which allows you to add custom code snippets to a specific block:
<?php
namespace App\Controller;
use Pimcore\Bundle... | [
0.026293404400348663,
0.5750751495361328,
-0.13334473967552185,
0.0916227251291275,
-0.31039124727249146,
-0.0330205038189888,
0.06201208010315895,
-0.2872653305530548,
0.7222036719322205,
0.009454503655433655,
0.2374543845653534,
0.4916660189628601,
0.18864013254642487,
0.0762737020850181... |
Influencing generated code through the CODE_TRACKING_DATA event | https://pimcore.com/docs/platform//Google_Marketing/Analytics#influencing-generated-code-through-the-code_tracking_data-event | Influencing generated code through the CODE_TRACKING_DATA event
Before the tracking code is generated, the GoogleAnalyticsEvents::CODE_TRACKING_DATA event is dispatched which gives
you full control over the generated code:
<?php
namespace App\EventListener;
use Pimcore\Bundle\GoogleMarketingBundle\Model\Event\Trac... | [
-0.18598362803459167,
0.32237058877944946,
-0.23034054040908813,
0.20220620930194855,
-0.28891482949256897,
-0.4444830119609833,
-0.07179046422243118,
0.0869327187538147,
0.4990757703781128,
0.052791111171245575,
0.14896807074546814,
0.7187532186508179,
0.2920689582824707,
-0.3358990848064... |
Overriding the rendered template | https://pimcore.com/docs/platform//Google_Marketing/Analytics#overriding-the-rendered-template | Overriding the rendered template
As you can see in the sample event listener above, you can change the template which will be used for the tracking code.
If you set a custom template, you can extend the core one and just override the blocks you want:
{# templates/Analytics/Tracking/Google/Analytics/universalTrackingCod... | [
-0.7011367082595825,
-0.3993645906448364,
-0.2299097627401352,
-0.05866466462612152,
-0.4658375382423401,
-0.22188502550125122,
-0.17210714519023895,
0.011261812411248684,
0.6713178157806396,
0.0653214380145073,
0.24056148529052734,
0.6724661588668823,
0.32274773716926575,
-0.0110922604799... |
Google Services Integration | https://pimcore.com/docs/platform//Google_Marketing/Google_Services_Integration#google-services-integration | Google Services Integration
Menus and buttons may vary depending on the current GUI version | [
-0.19757813215255737,
-0.16944412887096405,
-0.1424339860677719,
1.0058673620224,
-0.9620509743690491,
-0.34565794467926025,
0.33052194118499756,
-0.1080966517329216,
1.060004472732544,
0.15432141721248627,
-0.19939473271369934,
0.7213422060012817,
-0.062447577714920044,
-0.359412401914596... |
Console - APIs | https://pimcore.com/docs/platform//Google_Marketing/Google_Services_Integration#console---apis | Console - APIs
https://console.developers.google.com/project
Menu: [+ Create project]
Project name: project-sk
Menu: Select project
Menu: IAM & admin / Service accounts
[+ Create service account]
Service account name: api_id (email)
Role: App Engine / App Engine Viewer
[Done]
[+ Create service a... | [
0.3012280762195587,
-0.01012276578694582,
-0.5361146926879883,
-0.1218646690249443,
-0.656055212020874,
0.020426109433174133,
-0.27904829382896423,
0.5709863305091858,
0.3042324483394623,
0.807687520980835,
-0.33677878975868225,
-0.48366597294807434,
0.5512491464614868,
-0.4722206890583038... |
Analytics | https://pimcore.com/docs/platform//Google_Marketing/Google_Services_Integration#analytics | Analytics
https://analytics.google.com/
Menu: Administrator
[Create new account]
Account name: project
Web
Website name: project.sk
Website URL: https://www.project.sk/
Industry category:
Reporting Time Zone:
Get Tracking ID: track_id
Menu: All website data
View settings
Search tracking: ON
query p... | [
0.28513163328170776,
0.32951706647872925,
-0.8928865194320679,
-0.19379998743534088,
-0.5732541680335999,
-0.17165794968605042,
0.35607659816741943,
0.4048687815666199,
0.4011804461479187,
0.3519183397293091,
-0.22618360817432404,
0.1981603503227234,
0.20926469564437866,
-0.656953275203704... |
Configuring Google Services in Pimcore | https://pimcore.com/docs/platform//Google_Marketing/Google_Services_Integration#configuring-google-services-in-pimcore | Configuring Google Services in Pimcore
APIs
copy JSON to /config/pimcore/google-api-private-key.json
edit /config/config.yaml or use System Settings in admin interface
services/google/client_id = api_id
services/google/email = api_email
services/google/simple_api_key = s_api_key
services/google/browser_api_key = ... | [
0.2735498547554016,
0.22830745577812195,
-0.466047078371048,
0.13790102303028107,
-1.0179380178451538,
0.18310414254665375,
0.07207336276769638,
-0.1544351577758789,
0.995112419128418,
0.8428064584732056,
-0.042028579860925674,
0.3365302085876465,
0.5171287059783936,
-0.2752395570278168,
... |
Google Marketing Bundle | https://pimcore.com/docs/platform//Google_Marketing#google-marketing-bundle | Google Marketing Bundle
The Marketing Settings gives you the possibility to configure marketing-specific settings, which are:
Google Analytics
Google Search Console
Google Tag Manager
| [
0.1519201695919037,
0.43638959527015686,
-0.34816253185272217,
0.513043224811554,
-0.444926917552948,
-0.17257370054721832,
0.1493520736694336,
0.4078626334667206,
0.012413575313985348,
-0.1534622311592102,
-0.34921345114707947,
0.9050199389457703,
0.012039026245474815,
-0.1409962177276611... |
Google Analytics | https://pimcore.com/docs/platform//Google_Marketing#google-analytics | Google Analytics
Google Analytics code is automatically injected during the rendering of the page. See Google Analytics for
details. | [
-0.77530437707901,
0.1513216495513916,
-1.0115445852279663,
-0.08555465936660767,
-0.39375829696655273,
-0.012822547927498817,
0.4045736491680145,
0.4977366626262665,
0.8847094178199768,
0.6096275448799133,
-0.36957788467407227,
0.7549038529396057,
-0.0004805447533726692,
0.182447388768196... |
Google Tag Manager | https://pimcore.com/docs/platform//Google_Marketing#google-tag-manager | Google Tag Manager
The Google Tag Manager code is built and injected in a similar way as the Google Analytics one and exposes the same customization
possibilities through:
the GoogleTagManagerEvents::CODE_HEAD and GoogleTagManagerEvents::CODE_BODY events, each defining a set of customizable
blocks
a dedicated template... | [
0.27645257115364075,
0.16776788234710693,
-0.7040636539459229,
-0.21143515408039093,
0.1933554857969284,
-0.23308032751083374,
-0.10559612512588501,
0.06705721467733383,
0.44346949458122253,
0.09151425212621689,
-0.02463286928832531,
0.6195902824401855,
0.016464244574308395,
-0.39643812179... |
Google Service Integrations | https://pimcore.com/docs/platform//Google_Marketing#google-service-integrations | Google Service Integrations
For a more detailed description, see Google Service Integration | [
0.3714441955089569,
-0.3097381293773651,
-0.7067244052886963,
0.912690281867981,
-0.38537511229515076,
-0.4675363600254059,
-0.49279582500457764,
-0.10228758305311203,
1.13947331905365,
0.8546738028526306,
0.4412318170070648,
0.9311236143112183,
0.0236036516726017,
-0.653864860534668,
-0... |
Installation | https://pimcore.com/docs/platform//Web_To_Print/Installation#installation | Installation | [
0.008305035531520844,
0.060598794370889664,
-0.21498022973537445,
-0.4450346529483795,
-0.5080509781837463,
-0.09725302457809448,
-0.12314953655004501,
0.12177811563014984,
0.4541318118572235,
0.4160004258155823,
0.23847107589244843,
0.06712134182453156,
0.12488314509391785,
-0.12956567108... |
Installing processor dependencies | https://pimcore.com/docs/platform//Web_To_Print/Installation#installing-processor-dependencies | Installing processor dependencies
If you want to use Gotenberg or Chromium as processor, you need to install additional dependencies. For more information and installation informations have a look at Document Types and Available PDF Processors | [
-0.07272788137197495,
-0.31136441230773926,
-0.18739649653434753,
-0.4375498592853546,
-0.47763699293136597,
0.3950548768043518,
-0.24093571305274963,
-0.3775261342525482,
-0.12071157991886139,
0.3950200378894806,
-0.7921377420425415,
-0.13796283304691315,
1.019317626953125,
-0.71760964393... |
Installation Process | https://pimcore.com/docs/platform//Web_To_Print/Installation#installation-process | Installation Process
After installing the bundle and the required dependencies of the processor you wish to use, you need to configure the settings under Settings > Web-to-Print.
There you will find detailed notes about the options and settings available. depending on which processor you will use. | [
-0.2771989405155182,
-0.12290182709693909,
-0.23259004950523376,
-0.021006735041737556,
-0.003965400159358978,
0.17680348455905914,
-0.2680511474609375,
-0.2988714575767517,
-0.03367521986365318,
0.4117937386035919,
-0.874711275100708,
0.3141455054283142,
0.5284086465835571,
-0.34736743569... |
Uninstallation | https://pimcore.com/docs/platform//Web_To_Print/Installation#uninstallation | Uninstallation
Uninstalling the bundle does not clean up printpages or printcontainers. Before uninstalling make sure to remove or archive all dependent documents.
You can also use the following command to clean up you database. Create a backup before executing the command. All data will be lost.
bin/console pimcore:d... | [
-0.47970327734947205,
-0.4218244254589081,
0.4591054916381836,
0.3224201798439026,
-0.10961263626813889,
-0.527016282081604,
-0.2252029925584793,
-0.687349259853363,
0.5435915589332581,
0.10334975272417068,
0.2898530662059784,
0.938286304473877,
0.5459325909614563,
-0.37609681487083435,
... |
Document Types and Available PDF Processors | https://pimcore.com/docs/platform//Web_To_Print/Doc_Types_and_Available_Processors#document-types-and-available-pdf-processors | Document Types and Available PDF Processors | [
0.39719727635383606,
-0.5490663647651672,
0.6287991404533386,
-0.38162940740585327,
-0.1917356550693512,
0.11334267258644104,
-0.2787560522556305,
-0.2932853698730469,
0.33254531025886536,
0.6814970970153809,
-0.4847341477870941,
0.2808802127838135,
0.6732642650604248,
0.19377395510673523,... |
Document Types | https://pimcore.com/docs/platform//Web_To_Print/Doc_Types_and_Available_Processors#document-types | Document Types
This bundle introduces 2 new document types:
Type
Description
PrintPage
Like pages, but specialized for print (PDF preview, rendering options, ...)
PrintContainer
Organizing print pages in chapters and render them all together.
| [
0.19682587683200836,
-0.576087474822998,
0.6212045550346375,
-0.27459046244621277,
0.4426547884941101,
-0.14112208783626556,
-0.2807336449623108,
-0.11155060678720474,
0.40992897748947144,
0.7434219121932983,
0.19028498232364655,
0.31038302183151245,
1.2150084972381592,
0.45308899879455566... |
Available PDF Processors | https://pimcore.com/docs/platform//Web_To_Print/Doc_Types_and_Available_Processors#available-pdf-processors | Available PDF Processors
Name
Description
Chromium
Convert to PDF by installing the Chromium binary or by using a dockerized chromium (via websocket)
Gotenberg
A Docker service with Chromium and LibreOffice support
PDF Reactor
A REST/SOAP solution, please visit the official website for further information
... | [
0.06924205273389816,
-0.16202762722969055,
-0.22062543034553528,
-0.361858993768692,
-0.34112420678138733,
0.17967888712882996,
-0.18706730008125305,
-0.6502792835235596,
0.32050397992134094,
0.4679197371006012,
-0.6592691540718079,
0.09073926508426666,
0.8888057470321655,
0.10132246464490... |
Print Documents | https://pimcore.com/docs/platform//Web_To_Print/Print_Documents#print-documents | Print Documents
Print documents are the way to create print-ready PDFs directly within Pimcore.
They are based on the normal Pimcore documents and therefore support everything as pages do - starting from MVC pattern
and template creation to document composing within Pimcore backend with areas, drag&drop etc.
Web to... | [
0.07736039906740189,
-0.5268293023109436,
-0.10725638270378113,
-0.45350131392478943,
0.5813030004501343,
0.11620258539915085,
-0.37717416882514954,
-0.8614459037780762,
0.8669162392616272,
1.2086000442504883,
0.2121759057044983,
0.37657469511032104,
1.1764326095581055,
0.16705678403377533... |
Web-To-Print Document Types | https://pimcore.com/docs/platform//Web_To_Print/Print_Documents#web-to-print-document-types | Web-To-Print Document Types | [
0.051376499235630035,
-0.4724515974521637,
0.4577939808368683,
-0.3687657117843628,
0.14231917262077332,
-0.14344345033168793,
-0.18851624429225922,
-0.25985684990882874,
0.5059710741043091,
0.8371965885162354,
-0.23954425752162933,
0.4048171937465668,
0.5117172002792358,
0.154670193791389... |
PrintPage | https://pimcore.com/docs/platform//Web_To_Print/Print_Documents#printpage | PrintPage
PrintPages are the documents that contain the actual content - with all the areas, editables, images, and so on.
They are based on the normal Pimcore documents and to content editing should be quite self explaining.
| [
0.179454505443573,
-0.8221307396888733,
0.2917662262916565,
0.21729086339473724,
0.42400848865509033,
-0.3844599723815918,
-0.452560156583786,
-1.173965573310852,
0.7053022384643555,
0.4307960867881775,
0.3486715853214264,
0.685694694519043,
1.0363318920135498,
-0.04845740273594856,
-0.7... |
PrintContainer | https://pimcore.com/docs/platform//Web_To_Print/Print_Documents#printcontainer | PrintContainer
PrintContainers are a special document type to represent containers of PrintPages. They do not have content for their own,
they just combine all sub pages to one single output PDF. By doing so they allow to structure big print documents like catalogs,
pricelists, books, etc.
Of course, PrintContainers ca... | [
-0.034537605941295624,
-0.432528018951416,
0.24355298280715942,
-0.45604005455970764,
0.34544575214385986,
-0.23298443853855133,
-0.017831072211265564,
-0.7940428853034973,
0.6848876476287842,
0.5133755207061768,
0.3415919542312622,
0.34197625517845154,
0.9259056448936462,
-0.3607650995254... |
PDF Rendering | https://pimcore.com/docs/platform//Web_To_Print/Print_Documents#pdf-rendering | PDF Rendering
Both web-to-print documents have an additional tab that is the place for rendering documents to print-ready PDFs.
When rendering, the print is first rendererd to HTML, then rendered as a Twig template (yes, you can use Twig expressions in the document) and then rendered to an PDF. PDF rendering itself is ... | [
-0.48024940490722656,
-0.7546867728233337,
-0.1841086894273758,
-0.17233116924762726,
0.3284938335418701,
0.08373907953500748,
-0.3239002227783203,
-0.4662216603755951,
0.7827903628349304,
0.7613924741744995,
-1.057300090789795,
-0.08885204046964645,
1.1621137857437134,
0.5723509192466736,... |
Sandbox Restrictions | https://pimcore.com/docs/platform//Web_To_Print/Print_Documents#sandbox-restrictions | Sandbox Restrictions
Print document renders user controlled twig templates in a sandbox with restrictive
security policies for tags, filters & functions. Please use following configuration to allow more in template rendering:
pimcore:
templating_engine:
twig:
sandbox_secu... | [
-0.1427011340856552,
-0.16431425511837006,
0.2967150807380676,
-0.020292315632104874,
0.36109769344329834,
0.07129865139722824,
-0.6928481459617615,
-0.05449424311518669,
0.2684675455093384,
0.6035023331642151,
0.1204921081662178,
0.33258992433547974,
0.9061799049377441,
0.2784920334815979... |
Special PDFreactor Settings | https://pimcore.com/docs/platform//Web_To_Print/Print_Documents#special-pdfreactor-settings | Special PDFreactor Settings
Printermarks: With PDFreactor there comes a out-of-the-box feature to add printermarks to the PDF.
They can be activated by the printermarks rendering setting. Technically they are implemented by an additional CSS-file which needs to be included.
For Details, check links below:
view-script... | [
-0.08933358639478683,
-0.5175026059150696,
0.1895330399274826,
0.05194903537631035,
-0.013392414897680283,
-0.09192405641078949,
-0.10548312962055206,
-0.32699742913246155,
-0.16394375264644623,
0.5842785239219666,
-0.5807230472564697,
-0.020864129066467285,
1.0278908014297485,
0.433255672... |
Settings | https://pimcore.com/docs/platform//Web_To_Print/Print_Documents#settings | Settings
In the web-to-print settings, the used PDF renderer is specified. Depending on the renderer, there are additional settings to be made.
Additional explanation can be found directly in the settings form.
These settings have to be set properly before starting PDF rendering. | [
-0.3564762771129608,
-0.5252090096473694,
-0.3342909514904022,
-0.12523213028907776,
0.0012974180281162262,
-0.12672856450080872,
-0.47305551171302795,
-0.27215924859046936,
0.13667060434818268,
0.5393433570861816,
-0.2830830216407776,
0.013935036025941372,
1.0329656600952148,
0.5501906871... |
Relevant Log Files | https://pimcore.com/docs/platform//Web_To_Print/Print_Documents#relevant-log-files | Relevant Log Files
If PDF rendering doesn't work properly, following log files should give you a hit for the reason.
var/log/dev.log or var/log/prod.log - contains general logging information for rendering process at INFO level
var/log/web2print-output.log - contains output of rendering PHP process (if any). It is r... | [
-0.09150688350200653,
0.02295525372028351,
0.38575509190559387,
0.13939708471298218,
-0.04374738782644272,
-0.8324418663978577,
-0.2650688886642456,
-0.3450917601585388,
0.5230029821395874,
1.5909439325332642,
-0.1864689439535141,
0.4059741497039795,
0.946215808391571,
0.368863046169281,
... |
Color management and images | https://pimcore.com/docs/platform//Web_To_Print/Print_Documents#color-management-and-images | Color management and images
If you are using the PDFReactor renderer, use CMYK CSS color specifications (see PDFReactor documentation on details).
There are two possible workflows for images:
Use print-ready source images (for example TIFF files with the correct ICC Profiles) in your documents with "Print (...)&... | [
0.20231981575489044,
-0.5942546725273132,
0.6364111304283142,
-0.20221351087093353,
-0.2665828466415405,
-0.2650897800922394,
-0.10431400686502457,
-0.3539978861808777,
0.2956143617630005,
1.0075201988220215,
-0.5760993361473083,
-0.39556071162223816,
0.8768969178199768,
0.6958890557289124... |
Extending PDF Creation Config for PDF/X Conformance | https://pimcore.com/docs/platform//Web_To_Print/Web2Print_Extending_Config_for_PDFX_conformance#extending-pdf-creation-config-for-pdfx-conformance | Extending PDF Creation Config for PDF/X Conformance
Sometimes it is necessary to add additional configuration options to the PDF processing configuration in the Pimcore backend UI -
for example when creating PDF/X conform PDFs with PDF Reactor.
But also for other use cases, it might be necessary to hook into the PDF c... | [
0.3365345597267151,
-0.49452492594718933,
-0.2695527970790863,
-0.530651330947876,
-0.048997119069099426,
-0.0316670760512352,
-0.34182488918304443,
-0.6307281851768494,
0.30631813406944275,
0.9435082077980042,
0.09126339852809906,
0.36540088057518005,
1.1264476776123047,
-0.10924006253480... |
Example for adding Additional Config | https://pimcore.com/docs/platform//Web_To_Print/Web2Print_Extending_Config_for_PDFX_conformance#example-for-adding-additional-config | Example for adding Additional Config
Services in Container:
app.event_listener.test:
class: App\EventListener\PDFConfigListener
tags:
- { name: kernel.event_listener, event: pimcore.document.print.processor.modifyProcessingOptions, method: modifyProcessingOptions }
- { name: ker... | [
0.3875865638256073,
0.14365512132644653,
-0.046533435583114624,
-0.3646722137928009,
-0.08856702595949173,
-0.42490845918655396,
-0.6144781708717346,
-0.4336749315261841,
0.48760706186294556,
0.6778414845466614,
0.4567551910877228,
0.0926532968878746,
1.1662123203277588,
0.1587346792221069... |
Example for adding PDF/X Conformance | https://pimcore.com/docs/platform//Web_To_Print/Web2Print_Extending_Config_for_PDFX_conformance#example-for-adding-pdfx-conformance | Example for adding PDF/X Conformance
Services in Container see above.
Implementation of Listener
<?php
namespace App\EventListener;
class PDFConfigListener
{
public function modifyProcessingOptions(\Pimcore\Bundle\WebToPrintBundle\Event\Model\PrintConfigEvent $event): void
{
//optionally add some c... | [
0.18238145112991333,
0.09441215544939041,
0.022503292188048363,
-0.15115921199321747,
0.07077732682228088,
-0.36984145641326904,
-0.6775758266448975,
-0.4399127960205078,
0.09133249521255493,
0.8329718708992004,
0.22396500408649445,
0.3855209946632385,
1.2731841802597046,
0.502586781978607... |
Gotenberg PDF Engines | https://pimcore.com/docs/platform//Web_To_Print/Web2Print_Extending_Config_for_PDFX_conformance#gotenberg-pdf-engines | Gotenberg PDF Engines
When using Gotenberg, please also take in consideration https://github.com/gotenberg/gotenberg-php#pdf-format | [
0.12959034740924835,
0.1176518052816391,
-0.19659453630447388,
0.1483222097158432,
-0.6304625272750854,
0.11328503489494324,
0.04127257317304611,
-0.4731784462928772,
0.17433176934719086,
0.7067543864250183,
-0.15395204722881317,
0.3267335891723633,
1.11310613155365,
0.04566201940178871,
... |
Web_To_Print | https://pimcore.com/docs/platform//Web_To_Print#web_to_print | Web_To_Print
| [
-0.10650663822889328,
-0.3547579050064087,
-0.1793665736913681,
-0.2476472705602646,
0.6312927007675171,
-0.5154262185096741,
-0.010926077142357826,
-0.20663857460021973,
0.17100012302398682,
0.5341110229492188,
-0.12283772230148315,
-0.5303242802619934,
0.022616315633058548,
0.22939161956... |
title: Web to Print Module | https://pimcore.com/docs/platform//Web_To_Print#title:-web-to-print-module | title: Web to Print Module | [
0.2867288589477539,
-0.28482621908187866,
-0.32831647992134094,
-0.17979830503463745,
0.21482858061790466,
0.04621247574687004,
-0.22943063080310822,
-0.7926186323165894,
0.1418336033821106,
0.7030960917472839,
-0.23640286922454834,
-0.09159480780363083,
0.16556517779827118,
0.269219130277... |
Pimcore Web to Print Module | https://pimcore.com/docs/platform//Web_To_Print#pimcore-web-to-print-module | Pimcore Web to Print Module
Adds the ability to create web-to-print documents in Pimcore and to convert them into a PDF. | [
0.08653181046247482,
-0.4374501407146454,
-0.2847502827644348,
-0.4493790566921234,
0.06604316085577011,
0.09050311148166656,
-0.5668069124221802,
-1.0136998891830444,
1.080512523651123,
0.8176014423370361,
-0.05391911789774895,
-0.13810545206069946,
0.9446313381195068,
0.15580637753009796... |
Features in a Nutshell | https://pimcore.com/docs/platform//Web_To_Print#features-in-a-nutshell | Features in a Nutshell
Add web2print support for generating PDFs to Pimcore.
Add new Pimcore-specific Document types to create print documents with Pimcore Documents (and all related concepts and features).
Allow creating single pages and whole catalogs with chapters, subchapters and table of contents.
Integrate diffe... | [
0.32770246267318726,
-0.20558689534664154,
-0.03908136114478111,
-0.7905060648918152,
-0.02178851142525673,
0.41416966915130615,
-0.305658221244812,
-0.45739156007766724,
0.992458164691925,
0.7730823159217834,
-0.54233318567276,
-0.09669976681470871,
1.1753021478652954,
-0.0583702810108661... |
Documentation Overview | https://pimcore.com/docs/platform//Web_To_Print#documentation-overview | Documentation Overview
Installation
Document Types and Available PDF Processors
Print Documents
Extending PDF Creation Config for PDF/X Conformance
| [
0.09130249917507172,
-0.4517883360385895,
0.6347568035125732,
-0.32443198561668396,
0.13803322613239288,
-0.1118040382862091,
-0.4403667151927948,
-0.1630854308605194,
0.26753559708595276,
0.988574743270874,
-0.22726237773895264,
0.2883088290691376,
0.9469178915023804,
-0.13185706734657288... |
Contributing and Development | https://pimcore.com/docs/platform//Web_To_Print#contributing-and-development | Contributing and Development
For details see our Contributing guide. | [
-0.14750996232032776,
-0.1187196895480156,
-0.753412663936615,
-0.3397100567817688,
-0.18838918209075928,
0.049867626279592514,
-0.3469782769680023,
0.2761552929878235,
0.4391913115978241,
0.3911707401275635,
-0.52118980884552,
0.02983568049967289,
0.6890997886657715,
-0.06138625741004944,... |
Installation | https://pimcore.com/docs/platform//Advanced_Object_Search/Installation#installation | Installation | [
0.008305035531520844,
0.060598794370889664,
-0.21498022973537445,
-0.4450346529483795,
-0.5080509781837463,
-0.09725302457809448,
-0.12314953655004501,
0.12177811563014984,
0.4541318118572235,
0.4160004258155823,
0.23847107589244843,
0.06712134182453156,
0.12488314509391785,
-0.12956567108... |
Installation Process | https://pimcore.com/docs/platform//Advanced_Object_Search/Installation#installation-process | Installation Process | [
-0.20254547894001007,
0.2934083640575409,
-0.5684934854507446,
-0.15376776456832886,
-0.46003133058547974,
-0.16791191697120667,
-0.15330982208251953,
0.04020388051867485,
0.49200063943862915,
0.9063884019851685,
0.2507457733154297,
0.2077140212059021,
0.0724649652838707,
-0.29972586035728... |
For Pimcore >= 10.5 | https://pimcore.com/docs/platform//Advanced_Object_Search/Installation#for-pimcore->=-10.5 | For Pimcore >= 10.5
To install Advanced Object Search Bundle for Pimcore 10.5 or higher, follow the three steps below:
Install the required dependencies:
composer require pimcore/advanced-object-search
Make sure the bundle is enabled in the config/bundles.php file. The following lines should be added:
return [... | [
0.43822476267814636,
0.19826321303844452,
-0.29902902245521545,
-0.5753613114356995,
-0.20838411152362823,
0.11929549276828766,
-0.09098950773477554,
-0.15370117127895355,
1.0456774234771729,
0.637663722038269,
0.7632896304130554,
-0.32889819145202637,
0.20999065041542053,
-0.3330792784690... |
For Older Versions | https://pimcore.com/docs/platform//Advanced_Object_Search/Installation#for-older-versions | For Older Versions
To install the Advanced Object Search Bundle for older versions of Pimcore, please run the following commands instead:
composer require pimcore/advanced-object-search
bin/console pimcore:bundle:enable AdvancedObjectSearchBundle
bin/console pimcore:bundle:install AdvancedObjectSearchBundle
| [
0.22006331384181976,
-0.39745765924453735,
-0.49605050683021545,
-0.5085873603820801,
-0.1752847582101822,
0.016581567004323006,
-0.06825335323810577,
-0.4106980562210083,
1.2521501779556274,
0.5487880110740662,
0.7418717741966248,
-0.8207886219024658,
-0.05732598528265953,
-0.452456980943... |
Required Backend User Permission | https://pimcore.com/docs/platform//Advanced_Object_Search/Installation#required-backend-user-permission | Required Backend User Permission
To access the Advanced Object Search feature, a user needs to meet at least one of the following criteria:
Be an admin user.
Have bundle_advancedsearch_search permission.
| [
0.3773820698261261,
-0.4734669625759125,
-0.22442951798439026,
-0.35190173983573914,
0.37274613976478577,
0.5469182133674622,
-0.41624629497528076,
-0.17530058324337006,
0.6062234044075012,
0.9217461943626404,
0.16053834557533264,
-0.2955132722854614,
0.06773556768894196,
-0.51850652694702... |
Extending Filters | https://pimcore.com/docs/platform//Advanced_Object_Search/Extending_Filters#extending-filters | Extending Filters
The advanced object search enables the definition of custom search filters that can be used to filter the result. This
gives the possibility to filter lists of products by article numbers, types or colors e.g. without having to create
a complete custom advanced object search for it.
In order to create... | [
-0.08700207620859146,
-0.12212835997343063,
0.08684810250997543,
-0.6680360436439514,
-0.26261642575263977,
0.038578521460294724,
0.06161152571439743,
0.0195970069617033,
0.9089202284812927,
0.9345163702964783,
0.7632452249526978,
0.17734353244304657,
0.03246006369590759,
-0.21620348095893... |
Event Listeners | https://pimcore.com/docs/platform//Advanced_Object_Search/Extending_Filters#event-listeners | Event Listeners
To add your custom condition(s) to the search, you have two possibilities
add the condition(s) to the elastic search directly
add the condition(s) to the pimcore listing which will load all objects the elastic search found
For convenience reasons you can extend the AdvancedObjectSearchBundle\Event\Abs... | [
-0.05034849792718887,
0.3011746108531952,
-0.19300195574760437,
-0.6352552771568298,
0.07040063291788101,
0.29503923654556274,
-0.058109767735004425,
-0.14241205155849457,
0.8093259334564209,
0.8536096811294556,
0.8208540678024292,
-0.14878158271312714,
1.0569038391113281,
-0.2808184325695... |
Elastic Search Conditions | https://pimcore.com/docs/platform//Advanced_Object_Search/Extending_Filters#elastic-search-conditions | Elastic Search Conditions
Condition(s) can be added to the elastic search directly by creating an event listener that listens to the
advanced_object_search.elastic_filter event (AdvancedObjectSearchBundle\Event::ELASITIC_FILTER). As mentioned
before the AbstractFilterListener already takes care of that for you, if you ... | [
0.005719996988773346,
0.43310320377349854,
-0.1713675707578659,
-0.1903918981552124,
0.13418585062026978,
0.21554316580295563,
0.22801639139652252,
0.08139300346374512,
0.5138701796531677,
1.2829132080078125,
0.8554412126541138,
-0.03665049746632576,
0.7657408118247986,
-0.0464441068470478... |
Listing Conditions | https://pimcore.com/docs/platform//Advanced_Object_Search/Extending_Filters#listing-conditions | Listing Conditions
In some cases you might have to join your result with another table before you can actually achieve the filter that you
want. For that you can use the listing filter. The elastic search only returns the object ids which were found. These
will be loaded using a basic pimcore listing of that class whic... | [
0.05721462890505791,
0.16327744722366333,
-0.15703782439231873,
-0.23956963419914246,
-0.23872420191764832,
0.11798779666423798,
-0.009701861999928951,
0.14305226504802704,
0.6608957648277283,
1.1245156526565552,
0.9578666687011719,
-0.015598931349813938,
0.5023478269577026,
0.182753458619... |
Javascript Filter | https://pimcore.com/docs/platform//Advanced_Object_Search/Extending_Filters#javascript-filter | Javascript Filter
Now that the result can be filtered by an article number, you have to create an input with javascript to be able to type
in an article number.
For that you have to create a javascript class that extends pimcore.bundle.advancedObjectSearch.searchConfig.ResultExtension
and register it in the extension b... | [
0.3475363552570343,
-0.014459843747317791,
0.12621378898620605,
-0.3888351321220398,
-0.2659197449684143,
0.2833634912967682,
0.04378371685743332,
-0.2812003791332245,
0.996428370475769,
0.8193705677986145,
0.7063859105110168,
0.0589897483587265,
-0.044339023530483246,
0.16933070123195648,... |
Exclude Fields | https://pimcore.com/docs/platform//Advanced_Object_Search/Exclude_Fields#exclude-fields | Exclude Fields
It is possible to exclude specified fields from the elasticsearch index by extending the services.yaml:
advanced_object_search:
index_configuration:
exclude_classes:
- CustomerSegment
- CustomerSegmentGroup
exclude_fields:
OfferToolOffer:
... | [
-0.4821251928806305,
0.3196011483669281,
-0.6797961592674255,
-0.3684733808040619,
0.6996434926986694,
0.19912634789943695,
0.4359249174594879,
-0.18568997085094452,
0.3589023947715759,
1.6266310214996338,
0.43750789761543274,
-0.010736831463873386,
1.0421689748764038,
-0.7333967089653015,... |
Upgrade Notes | https://pimcore.com/docs/platform//Advanced_Object_Search/Upgrade_Notes#upgrade-notes | Upgrade Notes | [
0.052410516887903214,
-0.2534591257572174,
-0.6424592137336731,
0.062447063624858856,
-0.8232324719429016,
-0.5481067299842834,
0.4483388662338257,
-0.18305133283138275,
1.0413897037506104,
0.6215392351150513,
0.17863427102565765,
0.7704036235809326,
0.7889806032180786,
-0.5586071014404297... |
Upgrade to v3.0.0 | https://pimcore.com/docs/platform//Advanced_Object_Search/Upgrade_Notes#upgrade-to-v3.0.0 | Upgrade to v3.0.0
Reinstall of Bundle might be necessary - due to switch to MigrationInstaller.
Update ES mapping and reindex is necessary - run commands advanced-object-search:update-mapping and advanced-object-search:re-index.
| [
0.009025652892887592,
-0.01991509646177292,
-0.6535394787788391,
-0.01864692009985447,
-0.37537717819213867,
-0.263308048248291,
0.015250752680003643,
0.062296878546476364,
0.5336586236953735,
0.6877009272575378,
0.4758552312850952,
0.023723198100924492,
0.5272771716117859,
-0.474396377801... |
Upgrade to v4.0.0 | https://pimcore.com/docs/platform//Advanced_Object_Search/Upgrade_Notes#upgrade-to-v4.0.0 | Upgrade to v4.0.0
Removed BC Layer for old configuration file. Configuration now only in symfony configuration tree.
Removed deprecated IFieldDefinitionAdapter, use FieldDefinitionAdapterInterface instead.
Data in Elasticsearch might be different, so recheck if you are depending directly on the data in Elasticsearch.
... | [
0.009420114569365978,
0.007674011401832104,
-0.1672230362892151,
0.457760751247406,
-0.06802628934383392,
0.550281286239624,
0.007905312813818455,
-0.2048826366662979,
0.6072252988815308,
0.6357364058494568,
1.0859084129333496,
-0.15025682747364044,
0.781708300113678,
-0.6774739623069763,
... |
Upgrade to Pimcore X | https://pimcore.com/docs/platform//Advanced_Object_Search/Upgrade_Notes#upgrade-to-pimcore-x | Upgrade to Pimcore X
Update to latest (allowed) bundle version in Pimcore 6.9 and execute all migrations.
Make sure you are using ElasticSearch 7.
Then update to Pimcore X.
| [
0.38699257373809814,
0.19510506093502045,
-1.0748764276504517,
-0.35061198472976685,
0.2957853376865387,
0.7491869926452637,
-0.023447396233677864,
-0.5880686640739441,
1.293653964996338,
1.0533336400985718,
0.45457446575164795,
0.42984312772750854,
0.6967138051986694,
-0.4778163433074951,... |
Upgrade to v5.0.0 | https://pimcore.com/docs/platform//Advanced_Object_Search/Upgrade_Notes#upgrade-to-v5.0.0 | Upgrade to v5.0.0
Removed Elasticsearch v6 and v7 support
Changed elasticsearch client configuration
| [
-0.7043344378471375,
-0.028758840635418892,
-0.46924060583114624,
0.3049159646034241,
-0.6022915244102478,
-0.23263022303581238,
-0.18910104036331177,
-0.3419792652130127,
0.17865212261676788,
1.196898341178894,
0.24384276568889618,
-0.5038601160049438,
0.9140799641609192,
-0.8361698985099... |
Advanced_Object_Search | https://pimcore.com/docs/platform//Advanced_Object_Search#advanced_object_search | Advanced_Object_Search
| [
0.14042724668979645,
0.03674225136637688,
-0.03819737583398819,
-0.23102131485939026,
-0.4519185423851013,
-0.5498096942901611,
0.04933081194758415,
0.21108366549015045,
0.9700453281402588,
0.9454746842384338,
0.9237431287765503,
-0.6613118648529053,
-0.5874915719032288,
-0.230617344379425... |
title: Advanced Object Search | https://pimcore.com/docs/platform//Advanced_Object_Search#title:-advanced-object-search | title: Advanced Object Search | [
0.3331453204154968,
0.06508802622556686,
0.12141567468643188,
-0.5885002017021179,
-0.1569485366344452,
-0.18114006519317627,
-0.3124372363090515,
0.06643974035978317,
0.6768645644187927,
0.5352534055709839,
0.5410597324371338,
-0.34683874249458313,
-0.3268130123615265,
-0.344800740480423,... |
Pimcore Advanced Object Search via Elasticsearch | https://pimcore.com/docs/platform//Advanced_Object_Search#pimcore-advanced-object-search-via-elasticsearch | Pimcore Advanced Object Search via Elasticsearch
Advanced Object Search bundle provides advanced object search in
Pimcore backend powered by Elasticsearch v8. | [
-0.37155675888061523,
-0.5076688528060913,
-0.6219053864479065,
-1.2801991701126099,
-0.15013602375984192,
0.5754124522209167,
-0.44482922554016113,
-0.8505442142486572,
1.1403491497039795,
0.7924932241439819,
0.6314738988876343,
-0.3752095103263855,
0.126713827252388,
-0.38242974877357483... |
Integration into Pimcore | https://pimcore.com/docs/platform//Advanced_Object_Search#integration-into-pimcore | Integration into Pimcore | [
0.0777408555150032,
-0.21974453330039978,
-0.37853580713272095,
-0.35927391052246094,
-0.41020482778549194,
0.32161375880241394,
0.08855541795492172,
-0.6858205795288086,
1.0489051342010498,
0.6160088777542114,
0.40769729018211365,
0.31877872347831726,
0.38396310806274414,
-0.1991430670022... |
Installation and Configuration | https://pimcore.com/docs/platform//Advanced_Object_Search#installation-and-configuration | Installation and Configuration
Follow Installation instructions. | [
-0.533915638923645,
0.32821619510650635,
-0.2708313465118408,
-0.2303449511528015,
-0.5518434643745422,
0.6083106994628906,
-0.08916259557008743,
-0.014687447808682919,
0.6943854093551636,
0.9485394954681396,
-0.06481141597032547,
0.5749618411064148,
-0.22943106293678284,
-0.30389207601547... |
Configure Elasticsearch Client | https://pimcore.com/docs/platform//Advanced_Object_Search#configure-elasticsearch-client | Configure Elasticsearch Client
Elasticsearch client configuration takes place via Pimcore Elasticsearch Client Bundle and has two parts.
Configuring an elasticsearch client.
Define the client to be used by advanced object search.
# Configure an elasticsearch client
pimcore_elasticsearch_client:
es_clients:
... | [
-0.37790507078170776,
0.6290532350540161,
-0.591833770275116,
-1.0294537544250488,
-0.4778019189834595,
0.339717835187912,
-0.34664496779441833,
-0.5506158471107483,
0.36532989144325256,
0.7829914689064026,
0.5939386487007141,
-0.10549823194742203,
0.9880791306495667,
-0.38333407044410706,... |
Configure Advanced Object Search | https://pimcore.com/docs/platform//Advanced_Object_Search#configure-advanced-object-search | Configure Advanced Object Search
Before starting, setup at least following configuration in symfony configuration tree:
advanced_object_search:
# Prefix for index names
index_name_prefix: 'advanced_object_search_'
For further configuration options follow the docs and the inline description of the configuration... | [
-0.17257358133792877,
0.17766110599040985,
-0.05519294738769531,
-0.5477258563041687,
-0.08590639382600784,
0.1475866287946701,
-0.30017852783203125,
0.1698540598154068,
0.8769787549972534,
0.6227692365646362,
1.0707064867019653,
-0.3377135396003723,
0.05378406494855881,
-0.038602083921432... |
Initial Indexing | https://pimcore.com/docs/platform//Advanced_Object_Search#initial-indexing | Initial Indexing
Call Pimcore command advanced-object-search:update-mapping for creating mappings and advanced-object-search:re-index
for indexing data for the first time. | [
-0.09541226178407669,
0.21290278434753418,
-0.3870067894458771,
-0.7912817597389221,
-0.7926846146583557,
-0.4976668953895569,
-0.26632556319236755,
-0.7181500792503357,
0.9747863411903381,
0.8670814633369446,
0.8992703557014465,
-0.10264547914266586,
0.16746029257774353,
-0.59937459230422... |
GUI | https://pimcore.com/docs/platform//Advanced_Object_Search#gui | GUI
GUI for creating searches against ES index with
saving functionality
sharing functionality
| [
-0.2772277593612671,
0.015165510587394238,
-0.03921520709991455,
-0.21344448626041412,
-0.906643271446228,
-0.007757676765322685,
-0.7197166681289673,
-0.09887807071208954,
0.41611552238464355,
1.0909444093704224,
-0.38964197039604187,
0.05468093603849411,
0.005966727156192064,
-0.29064661... |
Plugin Hooks | https://pimcore.com/docs/platform//Advanced_Object_Search#plugin-hooks | Plugin Hooks
Following event listeners are called automatically
pimcore.dataobject.postUpdate - data object is updated in ES index, all child objects are added to update queue.
pimcore.dataobject.preDelete - data object is deleted from ES index.
pimcore.class.postUpdate - ES index mapping is updated or index recr... | [
-0.7185255885124207,
0.1328219324350357,
-0.5954012870788574,
-0.4882374107837677,
-0.38240304589271545,
-0.34912917017936707,
-0.4497048854827881,
-0.23017938435077667,
0.8618012070655823,
1.1238822937011719,
0.32152998447418213,
-0.12585465610027313,
0.25459375977516174,
-0.3144494891166... |
Pimcore Console | https://pimcore.com/docs/platform//Advanced_Object_Search#pimcore-console | Pimcore Console
Functions in Pimcore console.
advanced-object-search:process-update-queue --> processes whole update queue of es search index.
advanced-object-search:re-index --> Reindex all data objects of given class. Does not delete index first or resets update queue.
advanced-object-search:update-mapping ... | [
-0.2797583043575287,
0.02720261551439762,
-0.5210844874382019,
-0.02073105238378048,
-0.7628946304321289,
-0.2018289566040039,
-0.39962586760520935,
-0.6934157013893127,
0.4985578954219818,
1.502245545387268,
0.4916188418865204,
-0.029607733711600304,
-0.017928428947925568,
-0.421497434377... |
Pimcore Maintenance & Symfony Messenger | https://pimcore.com/docs/platform//Advanced_Object_Search#pimcore-maintenance-&-symfony-messenger | Pimcore Maintenance & Symfony Messenger
By default, with every Pimcore maintenance call, 500 entries of update queue are processed.
As an alternative, you also can activate symfony messenger to process the update queue. For that,
just activate it as follows.
advanced_object_search:
messenger_queue_processing:
... | [
0.4365885555744171,
0.7819066047668457,
-0.8391827344894409,
1.1444660425186157,
-0.11784935742616653,
0.21919158101081848,
-0.44635188579559326,
-0.5545108318328857,
0.6196687817573547,
0.6909368634223938,
0.7191944122314453,
0.24906155467033386,
-0.011389208026230335,
0.3042137622833252,... |
API Methods | https://pimcore.com/docs/platform//Advanced_Object_Search#api-methods | API Methods | [
0.13869640231132507,
0.39252105355262756,
-0.6061285138130188,
-0.30843350291252136,
-0.13727185130119324,
-0.18744836747646332,
0.017771849408745766,
0.3212345242500305,
0.8330899477005005,
1.0370513200759888,
-0.04892740771174431,
0.13664977252483368,
-0.24013511836528778,
0.239350363612... |
Create Mapping for data object classes | https://pimcore.com/docs/platform//Advanced_Object_Search#create-mapping-for-data-object-classes | Create Mapping for data object classes
Per data object class one index with one document type is created.
<?php
/**
* @var \AdvancedObjectSearchBundle\Service $service
*/
$service = $this->get("AdvancedObjectSearchBundle\Service");
$service->updateMapping(ClassDefinition::getByName("Product&quo... | [
-0.39781245589256287,
0.6630898714065552,
-0.07953338325023651,
-0.1660441756248474,
-0.3326142430305481,
-0.01666121371090412,
-0.10678020864725113,
0.2971794903278351,
0.49241188168525696,
1.012416124343872,
0.6028689742088318,
0.2130865901708603,
0.3037441074848175,
0.2953759729862213,
... |
Update index data | https://pimcore.com/docs/platform//Advanced_Object_Search#update-index-data | Update index data
On data object save or via script:
<?php
/**
* @var \AdvancedObjectSearchBundle\Service $service
*/
$service = $this->get("AdvancedObjectSearchBundle\Service");
$objects = Product::getList();
foreach($objects as $object) {
$service->doUpdateIndexData($object);
}
| [
-0.47379663586616516,
0.42923879623413086,
-0.608451247215271,
-0.06008279323577881,
-0.09546538442373276,
-0.6180221438407898,
-0.18060354888439178,
-0.02595175988972187,
1.6616172790527344,
1.0196048021316528,
0.49102482199668884,
0.09010571986436844,
-0.13704080879688263,
0.083203934133... |
Search/Filter for data | https://pimcore.com/docs/platform//Advanced_Object_Search#searchfilter-for-data | Search/Filter for data
<?php
/**
* @var \AdvancedObjectSearchBundle\Service $service
*/
$service = $this->get("AdvancedObjectSearchBundle\Service");
//filter for relations via ID
$results = $service->doFilter(3,
[
new FilterEntry(
"objects",
[
... | [
-0.3697189688682556,
0.30431798100471497,
0.12939701974391937,
0.190300852060318,
-0.15754590928554535,
-0.3508880138397217,
-0.32498762011528015,
-0.06118962913751602,
0.5679565668106079,
0.7465209364891052,
0.053307272493839264,
0.35540488362312317,
-0.10648766160011292,
0.38450223207473... |
Not Supported Data Types | https://pimcore.com/docs/platform//Advanced_Object_Search#not-supported-data-types | Not Supported Data Types
Currently following data types are not supported - but can be added if needed in future versions:
ClassificationStore
Slider
Password
Block
Table
StructuredTable
Geographic data types
Image data types
| [
0.10083325207233429,
-0.4797956049442291,
0.21734105050563812,
-0.19942781329154968,
-0.17145228385925293,
0.3408893346786499,
0.8551573157310486,
0.4045242667198181,
-0.07966471463441849,
1.239715337753296,
-0.1141820028424263,
0.2513057291507721,
0.1947750300168991,
0.08203155547380447,
... |
Integrate new Data Type | https://pimcore.com/docs/platform//Advanced_Object_Search#integrate-new-data-type | Integrate new Data Type
Implement Field Definition Adapter by implementing the IFieldDefinitionAdapter interface.
Register new Field Definition Adapter as service
Add mapping in configuration like
advanced_object_search:
field_definition_adapters:
newDataTypeName: SERVICE_ID_OF_FIELD_DEFINITION_ADAPTER
| [
-0.39235419034957886,
-0.39127206802368164,
0.1436491310596466,
-0.09285169094800949,
0.002013757824897766,
0.44575828313827515,
0.6185234785079956,
-0.2881162762641907,
0.410098671913147,
1.020622730255127,
0.7394081950187683,
0.0841110497713089,
0.6223613619804382,
-0.4995574951171875,
... |
Extend Filters in the Result Tab | https://pimcore.com/docs/platform//Advanced_Object_Search#extend-filters-in-the-result-tab | Extend Filters in the Result Tab
If you want custom filters in the result tab directly without having to create a new advanced object search every time
read here on how to extend the result tab with custom filters.. | [
-0.20457890629768372,
-0.47947272658348083,
0.02614418789744377,
-0.6966574192047119,
-0.10213393718004227,
0.4776739776134491,
0.15320807695388794,
0.12150513380765915,
1.1351640224456787,
0.9700339436531067,
0.3808536231517792,
0.5087763667106628,
-0.0788053572177887,
0.00873202458024025... |
Supported Elasticsearch Versions | https://pimcore.com/docs/platform//Advanced_Object_Search#supported-elasticsearch-versions | Supported Elasticsearch Versions
ElasticSearch 8
| [
-0.33378690481185913,
0.24529878795146942,
-0.24780893325805664,
-0.5511456727981567,
-0.31698092818260193,
0.7556150555610657,
0.27332597970962524,
-0.3105024993419647,
0.2737964987754822,
1.253541350364685,
-0.5594660043716431,
0.23267674446105957,
0.7636587619781494,
-0.4797715842723846... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.