CHILIconnector for Magento2.x
The \"CHILIconnector\" for Magento connects the world leading eCommerce platform \"Magento 2.x\" with the hottest online-document-editor \"CHILIpublisher\".
\nUse CHILIconnector from enobis as a “plug-and-play”-extension for your existing B2C- or B2B-shop and enable your customers to edit documents online easily.
\nOr use the connector as a “starter kit” for your individual eCommerce publishing solution.
\nThe whole range of functions from both systems allows you to create solutions for a wide variety of scenarios such as: Web2Print webshops, marketing solutions, dealer- and partner portals or brand management platforms.
\nMany “out-of-the-box” features allow you to get your platform up and running quickly.
","device_type":"all","background_type":"image","background_style":"auto","background_position":"center-top","parallax_speed":0.5,"mouse_parallax_size":30,"mouse_parallax_speed":10000,"lg_background_type":"image","lg_background_style":"auto","lg_background_position":"center-top","md_background_type":"image","md_background_style":"auto","md_background_position":"center-top","sm_background_type":"image","sm_background_style":"auto","sm_background_position":"center-top","xs_background_type":"image","xs_background_style":"auto","xs_background_position":"center-top","type":"text","id":"e851jfq","history":false}]}]}],"pid":"uyv4palh63cj"}[/mgz_pagebuilder]
The \"CHILIconnector\" for Magento connects the world leading eCommerce platform \"Magento 2.x\" with the hottest online-document-editor \"CHILIpublisher\".
\nUse CHILIconnector from enobis as a “plug-and-play”-extension for your existing B2C- or B2B-shop and enable your customers to edit documents online easily.
\nOr use the connector as a “starter kit” for your individual eCommerce publishing solution.
\nThe whole range of functions from both systems allows you to create solutions for a wide variety of scenarios such as: Web2Print webshops, marketing solutions, dealer- and partner portals or brand management platforms.
\nMany “out-of-the-box” features allow you to get your platform up and running quickly.
","device_type":"all","background_type":"image","background_style":"auto","background_position":"center-top","parallax_speed":0.5,"mouse_parallax_size":30,"mouse_parallax_speed":10000,"lg_background_type":"image","lg_background_style":"auto","lg_background_position":"center-top","md_background_type":"image","md_background_style":"auto","md_background_position":"center-top","sm_background_type":"image","sm_background_style":"auto","sm_background_position":"center-top","xs_background_type":"image","xs_background_style":"auto","xs_background_position":"center-top","type":"text","id":"mli6d4a","history":false},{"text":"What can the CHILIconnector do for you?","heading_type":"h2","device_type":"all","background_type":"image","background_style":"auto","background_position":"center-top","parallax_speed":0.5,"mouse_parallax_size":30,"mouse_parallax_speed":10000,"lg_background_type":"image","lg_background_style":"auto","lg_background_position":"center-top","md_background_type":"image","md_background_style":"auto","md_background_position":"center-top","sm_background_type":"image","sm_background_style":"auto","sm_background_position":"center-top","xs_background_type":"image","xs_background_style":"auto","xs_background_position":"center-top","type":"heading","id":"x16or16"}]}]},{"row_type":"full_width_row","content_position":"top","gap_type":"padding","content_align":"center","device_type":"all","background_type":"image","background_style":"auto","background_position":"center-top","parallax_speed":0.5,"mouse_parallax_size":30,"mouse_parallax_speed":10000,"lg_background_type":"image","lg_background_style":"auto","lg_background_position":"center-top","md_background_type":"image","md_background_style":"auto","md_background_position":"center-top","sm_background_type":"image","sm_background_style":"auto","sm_background_position":"center-top","xs_background_type":"image","xs_background_style":"auto","xs_background_position":"center-top","type":"row","id":"kbus142","elements":[{"device_type":"all","background_type":"image","background_style":"auto","background_position":"center-top","parallax_speed":0.5,"mouse_parallax_size":30,"mouse_parallax_speed":10000,"lg_background_type":"image","lg_background_style":"auto","lg_background_position":"center-top","md_background_type":"image","md_background_style":"auto","md_background_position":"center-top","sm_background_type":"image","sm_background_style":"auto","sm_background_position":"center-top","xs_background_type":"image","xs_background_style":"auto","xs_background_position":"center-top","xl_offset_size":"","xl_size":"","lg_offset_size":"","lg_size":"","md_offset_size":"","sm_offset_size":"","sm_size":"","xs_size":"","type":"column","id":"ux558e9","elements":[{"active_tab":1,"no_fill_content_area":false,"device_type":"all","background_type":"image","background_style":"auto","background_position":"center-top","parallax_speed":0.5,"mouse_parallax_size":30,"mouse_parallax_speed":10000,"lg_background_type":"image","lg_background_style":"auto","lg_background_position":"center-top","md_background_type":"image","md_background_style":"auto","md_background_position":"center-top","sm_background_type":"image","sm_background_style":"auto","sm_background_position":"center-top","xs_background_type":"image","xs_background_style":"auto","xs_background_position":"center-top","tab_align":"left","tab_position":"top","type":"tabs","id":"lsviy1h","elements":[{"icon_position":"left","device_type":"all","background_type":"image","background_style":"auto","background_position":"center-top","parallax_speed":0.5,"mouse_parallax_size":30,"mouse_parallax_speed":10000,"lg_background_type":"image","lg_background_style":"auto","lg_background_position":"center-top","md_background_type":"image","md_background_style":"auto","md_background_position":"center-top","sm_background_type":"image","sm_background_style":"auto","sm_background_position":"center-top","xs_background_type":"image","xs_background_style":"auto","xs_background_position":"center-top","title":"Key-Features","padding_left":14,"padding_right":14,"padding_top":20,"padding_bottom":20,"type":"tab","id":"k3gmpwd","elements":[{"content":"KEY-FEATURES
\n- \n
- Use the full functionality of Magento and CHILIpublisher \n
- Simply make Web2Print products available in a Magento webshop. \n
- Sell \"web2print\"- and \"standard\"-products in one store \n
- Support for simple, virtual and configurable Products (bundled products optional) \n
- Web2Print articles are added to the shopping cart like \"standard\" products \n
- Automatic preview image generation (cart, wishlist) \n
- User-friendly, seamless integration of ChiliPublisher in separate editor page \n
- most compatible integration (separte editor page) approach to reduce incompatibilities with other extensions and different themes \n
- Extensive data integration between Magento and ChiliPublisher (pre-population of data from Magento such as customer, address, product and custom option data) \n
- Simple \"Plug-and-Play\" installation and extensive range of functions \"Out-of-the-Box\" \n
- Support of different configuration scopes (global, website, storeview, product, customer) for complex multi-store environments \n
- Extensive possibilities for (optical) adaptation by using own templates \n
- Easy licensing with support for multi-store environments \n
- Optional add-ons: Extensibility of functions through optional add-ons such as workflow functionalities (Document Workflow), \"My-Documents\" area with naming and copying functions or support for bundle product configurations \n
- Easy and cost-efficient installation to your existing webshop \n
- continous development \n
| Chili Webservice Url | \nString | \n\n URL to Chili-Webservice (E.g. but depends on CHILIserver-Configuration https://yourdomain.com/CHILI/main.asmx?WSDL \n | \n\n Storeview \n | \n
| Chili Baseurl | \nString | \n\n\n | \n\n Storeview \n | \n
| Chili Environment | \nString | \n\n Name of Chili environment \n | \n\n Storeview \n | \n
| Chili Api User | \nString | \n\n Name of API-User \n | \n\n Storeview \n | \n
| Chili Api Key | \nString | \n\n Password of API-User \n | \n\n Storeview \n | \n
| Chili Workspace | \nDropdown | \n\n List of workspaces \n | \n\n Storeview \n | \n
| Chili View Preference | \nDropdown | \n\n List of view preferences \n | \n\n Storeview \n | \n
| Chili Editor Engine | \nDropdown | \n\n HTML5, Flash (Deprecated) \n | \n\n Storeview \n | \n
| Chili Editor Anonymous User | \nYes, No | \n\n Ability to use the chili-editor for anonymous users \n | \n\n Storeview \n | \n
| Chili Editor Workspace Admin | \nYes, No | \nActivation of the chili-editor-workspace-admin (e.g. for debugging reasons) | \n\n Storeview \n | \n
| Chili Editor Viewer Only | \nYes, No | \nActivation of viewer-only-mode (Workspace for viewer-only-mode below!) | \nStoreview | \n
| Chili Editor Viewer Workspace | \nDropdown | \nList of workspaces (So it depends on the configuration, if the \"viewer-only-mode\" is really a locked-down-workspace or not!) | \nStoreview | \n
| Chili Editor Same Origin Domain | \nString | \n\n Domain (e.g. yourdomain.com) in which your editor runs. In most cases will run the editor as a subdomain of the shop-environment. E.g. \nshop.yourdomain.com -->Shop-URL \neditor.yourdomain.com -->Editor-Url \nSame-Origin-domain -->yourdomain.com \nImportant: In order to avoid CORS problematics it is a best-practise to run the editor in a subdomain. Alternatively it could run as a subfolder of the shop! But this needs an advanced reverse-proxy-configuration-setup of your servers! \n | \nStoreview | \n
| Chili Language | \nDropdown | \n\n List of Languages (Standard-Language) \n | \nStoreview | \n
| Chili Folder Document Order | \nString | \n\n Save-location of the chili-documents, when a order is created (moved from tmp-folder) \nDefault: orders/{{date}}/{{order_id}}/{{item_id}} \nE.g. The document will be saved to Documents/orders/2020-02-01/100000001/34 \nafter the order is created. \n | \nStoreview | \n
| Chili Folder Document Tmp | \nString | \n\n Save-location of the chili-documents, when a temporary document will be created (Click on Edit) \ntmp/{{date}} \nE.g. The document will be saved to Documents/tmp/2020-02-01/ \nafter the user openes the document to edit it. \n | \nStoreview | \n
| Chili Folder Document Tmp Relative | \nYes, No | \n\n Should the document be saved relatively to the document template folder. \n | \nStoreview | \n
| Document Naming Type | \nDropdown | \n\n - DocumentName_Timestamp (Default) | \nStoreview | \n
General configuration settings
\n| Enabled | \nYes, No (Default) | \n\n Enable the Chili-Editor \n | \n\n Storeview \n | \n
| Custom Editor Template | \nString | \n\n Location of the custom editor template \n | \n\n Storeview \n | \n
| Document Copy Method | \nDropdown | \n\n - Before_edit (Default) - Document will be first copied to a user document | \n\n Storeview \n | \n
| Allow Guest Editor | \nYes, No (Default) | \n\n Chili-Editor can be used by guests (without to log in first). Yes: No need to be logged in to open the editor \n | \n\n Storeview \n | \n
| Show Preview In Cart | \nYes (Default), No | \n\n Show a document preview in the cart? The document preview will be created as an image, that will be shown in the cart-item. \n | \n\n Storeview \n | \n
| Show Edit Document Link In Cart | \nYes (Default), No | \n\n enables direct document editing from the cart \n | \n\n Storeview \n | \n
| Show Edit Document Link In Wishlist | \nYes (Default), No | \n\n enables direct document editing from the wishlist \n | \n\n Storeview \n | \n
| Show Preview pages on Frontpage | \nString | \n\n * for all pages, empty for Page 1 or comma-separated list \n | \n\n Storeview \n | \n
| Enabled Modal Box | \nYes, No (Default) | \n\n Enabling modal boxes for several actions \n | \n\n Storeview \n | \n
| Preflight Check enabled | \nYes, No (Default) | \n\n When this feature is enabled, a chili preflight check is done before you can add the document to the cart. \nIf there are Preflight erros an Alert Box is prompted. Actions like \"add to cart\" or \"finish digital output\" are not possible. \n | \n\n Storeview \n | \n
Configuration of server-side processing of chili-documents
\n| Automatic Variable Assignment after Order Creation Enabled | \nYes, No (Default) | \n\n Option to enable variable-assignments to documents after ther order is created. The configured document variables (see below) will be overwritten by the values of the configured Magento-Properties. Important: The document will be reopened again \n | \n\n Storeview \n | \n
| Automatic Variable Assignment Mapping | \nTable-configuration | \n\n Magento-Property: order.increment_id \nChili-Variable-Name: orderid \n | \n\n Website \n | \n
| Allow server side rendering | \nYes (Default), No | \n\n
If you set this switch to \"No\" chili processes the server side calculation via the flash engine, if you set it to \"Yes\" chili uses the new server side html rendering engine to do this! \nImportant: Please choose \"Yes\" on newer CHILIServer-configurations, since the Flash-version is deprecated! \n | \n\n Website \n | \n
Configuration of editor-url specific details.
\n| Add Customer Id to Editor Url | \nYes (Default), No | \n\n Adds the customer-Id (userId) to the editor-url, while opening the chili-editor-page \n | \n\n Storeview \n | \n
| \n | Yes, No (Default) | \n\n Adds the relation-Id (relationId) to the editor-url, while opening the chili-editor-page \n | \n\n Storeview \n | \n
| \n | Yes, No (Default) | \n\n Adds the product-Id (productId) to the editor-url, while opening the chili-editor-page \n | \n\n Storeview \n | \n
| \n | Yes, No (Default) | \n\n Adds the storeview code (storeView) to the editor-url, while opening the chili-editor-page \n | \n\n Storeview \n | \n
| \n | Yes, No (Default) | \n\n Advanced security signature parameter in chili-url. This can be used for e.g. to call external datasources in a more secure way. \nBuilds an hash of all parameters+values (included signature prefix) to give the possibility to verify the given parameters and values against the hash in order to avoid the manipulation of parameters and parameter values. (security mechanismen) | \n\n Storeview \n | \n
| \n | Yes, No (Default) | \n\n Prefix for URL-Param Signature \n | \n\n Storeview \n | \n
Additional configuration settings
\n| Richtext Editor Default Bold Font | \nString | \n\n Fontname for Lightweight-Wysiwyg in Customer-Account \n | \n\n Storeview \n | \n
| Richtext Editor Default Italic Font | \nString | \n\n Fontname for Lightweight-Wysiwyg in Customer-Account \n | \n\n Storeview \n | \n
| Direct Add To Cart Enabled | \nYes, No(Default) | \n\n Possibility to add chili documents without editing to the cart (experimental) \n | \n\n Storeview \n | \n
| Enabled Modal Box | \n\n | \n\n | \n\n\n | \n
Defaults
\n| Chili Pdf Export Settings (Order (Backend), Order (Frontend) E-Mails, Checkout) | \nList of available Render Setting of CHILIserver | \n\n Select the default PDF-Export-Setting for your CHILI-documents. Important! Please uncheck use System Value and define a PDF export setting. If not set, it could create an error! \n | \n\n Storeview, Product \n | \n
| \n | Yes, No (Default) | \n\n Enables you to generate PDF-Exports on Checkout (Order Creation) automatically. \nIf set to \"Yes\", please configure the corresponding \"order status\" on which the PDF-Export should start automatically. \n | \n\n Storeview \n | \n
| Automatic Pdf Generation Order Status (Checkout) | \nMultiple Select | \n\n Selection of available \"Order Status\" on which the PDF-Exports should start automatically. \n | \n\n website \n | \n
| PDF-Generation Behavior on Order Creation (Checkout) | \nSync, Async | \n\n | \n Storeview \n | \n
Frontend
\n| Allow Pdf Download Links | \nYes, No (Default) | \n\n If enabled, a download link will be shown at the order detail. \nImportant! Caution, the user will be able to create and download a PDF with the corresponding PDF-Settings. In most B2C-cases this feature is disabled, because the user is maybe able to download HIGHres/PRintready PDF-Files. \n | \n\n Storeview \n | \n
| PDF download in editor | \nYes, No (Default) | \n\n Enables the PDF-Download-Feature inside the CHILI-editor page. \n | \n\n Storeview, Product \n | \n
| \n | List of available Render Setting of CHILIserver | \n\n List of possible render-settings. \nImportant: In most cases this feature is enabled to give the user the possiblity to download a \"preview\"-pdf of the document. But this depends on the assigned \"PDF-Export-Settings\". \n | \n\n Website \n | \n
| User Specific Asset Directories Enabled | \nYes, No (Default) | \n\n Enable/ Disable support for user- / user-group specific asset directories \n | \n\n Storeview \n | \n
| User Asset Directory | \nString | \n\n Enables support for customer specific asset directories in the chili dam system. \n{{customer_id}} You can use {{customer_id}} or {customer_email}} to use the values in chili directories with %user% \n | \n\n Storeview \n | \n
| User Group Asset Directory | \nString | \n\n Enables support for customergroup specific asset directories in the chili dam system. \nYou can use {{customer_group_id}} or {{customer_group_name}} to use the values in chili directories with %userGroup% \n{{customer_group_id}} \n{{customer_group_name}} \n | \n\n Storeview \n | \n
| Anonymous Specific Asset Directories Enabled | \nYes, No (Default) | \n\n Enable/ Disable support for anonymous specific asset directories \n | \n\n Storeview \n | \n
| Anonymous Asset Directory | \nString | \n\n Use the following variables to create directories for anonymous user assets. \n{{random}} | \n\n Storeview \n | \n
| Anonymous Group Asset Directory | \nString | \n\n Use the following variables to create directories for anonymous usergroup assets. \n{{random}} | \n\n Storeview \n | \n
The \"singleusage\"-feature enables you to restrict the usage of documents. If enabled you can configure which type of document can be created only once.
\n| Mode | \nCustomer/ Relation | \n\n Mode for the single usage functionality (defines the context of the single usage mode) \nCustomer: default mode - every configuration regards to the customer context. \nRelation: advanced mode (account_relation-extension needed) - every configuration regards to the relation context. \n | \n\n System-> Storeview \n | \n
| Allow only one Wishlist / Drafts item per product | \nYes, No (Default) | \nOnly one wishlist-/draft item per product allowed | \n\n System-> Storeview, Product->Storeview \n | \n
| Allow only one Digital Output Item per product | \nYes, No (Default) | \nOnly one digital output item per product allowed | \n\n System-> Storeview, Product->Storeview \n | \n
| \n | Yes, No (Default) | \nOnly one document workflow item per product allowed | \n\n System-> Storeview, Product->Storeview \n | \n
| Allow only one item in Cart/Order per product | \nYes, No (Default) | \nOnly one cart/ order item per product allowed | \n\n System-> Storeview, Product->Storeview \n | \n
| \n | Yes, No (Default) | \nIf this feature is turned on, your customers will automatically be shown a modal popup with existing Document items of the above configured types and the customer can choose to continue with that items. If this feature is turned off only a button is shown where the user can choose to continue with existing items of the below configured types. | \n\n System->Storeview \n | \n
| Single Usage - Current Period Startdate | \nDate | \nStartdate of single usage (current period) | \n\n Product ->Storeview \n | \n
| Single Usage - Current Period Enddate | \nDate | \nEnddate of single usage (current period) | \n\n Product ->Storeview \n | \n
| Single Usage - Next Period Startdate | \nDate | \nStartdate of single usage (next period) | \n\n Product ->Storeview \n | \n
| Single Usage - Next Period Enddate | \nDate | \nEnddate of single usage (next period) | \n\n Product ->Storeview \n | \n
| Reload Datasource On Completion | \nYes, No (Default) | \n\n If you enable this feature the datasource will be reloaded on completing the document. \"Completing\" means either ordering the document or finishing the document for the digital output. \n | \n\n Storeview \n | \n
| \n | Yes, No (Default) | \nIf you enable this feature a download link is shown in the Magento Backend on order items that have a chili document with datasource data | \n\n Storeview \n | \n
| \n | None (Default), Datasource num. rows | \n\n - None (Default): A document with datasource will be ordered as any other document. The cart quantity can be adjusted from the amount of datasource rows independently. \n- Datasource num rows: The cart quantity will be adjusted automatically according the amount of datasource rows. The qty-field is disabled for these documents! \n | \n\n Storeview, Product \n | \n
| Enable Logging | \nYes, No (Default) | \n\n Enable to log each Soap Call to a file var/log/chili_soap.log. Attention this reduces performance and should be only used for debugging purposes \n | \n\n Storeview \n | \n
| \n | Yes, No (Default) | \nAttention although Automatic Preview Generation is the Chili standard, it is recommended to leave this feature disabled, because Chili internally generates a pdf for each preview and that consumes some cpu power. | \n\n Storeview \n | \n
In addition to the default render settings (Renderer Settings->Default) it is possible to make a more detailed renderer configuration.
\nThe CHILIconnector supports either PDF-, Image- and HTML render features of the CHILIpublisher. There is a separate configuration for each renderer.
\n| \n | Yes, No (Default) | \n\n Enabling the expert settings disables the default renderer settings. \n | \n\n Storeview, Product \n | \n
| \n | \n \n \nDynamic configuration grid \n | \n\n Label: Display Label, which will be shown in the display area \nChili Renderer: PDF-Exportsettings \nDisplay Area: Order-Backend, Order-Frontend, Digital Output \n | \n\n Storeview, Product \n | \n
| HTML Renderer Settings | \n\n \n \nDynamic configuration grid \n | \n\n Label: Display Label, which will be shown in the display area \nChili Renderer: PDF-Exportsettings \nDisplay Area: Order-Backend, Order-Frontend, Di \nThe Block Id column is optional. If not filled, a standard HTML export archive is generated. Alternatively, if a Magento BlockId is specified as base template, the Magento Block Template can be populated with the variables from the Chili Document and with rendered Html Layer fragments from the Chili Html export. \nThe syntax for these block placeholders is #chili_variable_VARNAME#, #chili_layer_LAYERNAME# and #base_url#. \nIf the BlockID is specified, the images, fonts, and css files of the HTML export are published in a dedicated public folder below the Magento Pub/Media directory. \nThe url of this directory is available in the #base_url# variable. \n | \n\n Storeview, Product \n | \n
| Image Renderer Settings | \n\n \n \nDynamic configuration grid \n | \n\n Label: Display Label, which will be shown in the display area \nChili Renderer: PDF-Exportsettings \nDisplay Area: Order-Backend, Order-Frontend, Di \n | \n\n Storeview, Product \n | \n
CHANGELOG
\n| 1.0.0 | \nInitial Relase | \n\n Basic integration of chili-editor in magento incl. alternative panel layout \n– read-out-function of chili-variables for custom options | \n
| 1.0.1 - 1.1.1 | \nbugfixes | \n- qty-bug with magento 2.1.9 | \n
| 1.2.0 | \ncompatibility | \ncompatibility with magento 2.2 | \n
| 1.2.1 | \nbugfix | \nbugfix for some static-product-attributes bugfix for passing static-product-attributes to the chilieditor-api | \n
| 1.3.0 | \nfeatures | \nautomatic order attribute value assignment possibility to assign order attribute values to a chili document automatically. | \n
| 1.3.1 - 1.3.5 | \ncompatibility | \n- advanced compatibility with older magento2-versions - optimized compatibility with configurable products | \n
| 1.4.0 | \nfeatures | \n- support for user- and usergroup asset directories - direct document-edit-link in wishlist and cart - optimized start of pdf-export via link, optional asynchronous pdf-export with checkout [until 1.4.0 the rendering process is started with opening the order in the backend or storefront of magento. Now the rendering process is started via a pdf-rendering link in the backend and frontend. In addtion to the pdf-export-link there is now an option to start the pdf-export at the end of the checkout automatically. Please note: This task runs asyncronous – there will be no response to the end user!] | \n
| 1.4.1 - 1.4.8 | \nbugfixes / compatibility | \n\n - minor bugfix for rendering in multi-website-environments | \n
| 1.5.0 | \nfeatures | \n- features– added 3rd (top)menu panel (beta – not ready for production!) as alternative chili editor panel (in addition to left sidebar and gear-menu; – order status related automatic pdf generation; – support for direct customer attribute value assignment to the chili document (similar to direct product attribute value assignment) - chili sync quantity mode – ability to use number of datasource-rows for the cart quantity - support for virtual products | \n
| 1.5.1 - 1.5.4 | \nbugfix / optimisation | \n- hidden custom options are also hidden in cart by default; including additional css-class to disable this feature - start pdf-rendering process from backend depending on order status, reordering bug, minor bugfixes | \n
| 1.6.0 | \nfeatures | \n- support for preflight checks - possibility for PDF-download in editor (e.g. for preview-lowres-version) - possibility to generate automatic previews in cart - possibility to download datasource from backend - possibility to add userId, relationId, productId and storeview-code to chili-editor-url (to use them in e.g. datasource-, asset or snippet-urls) - support for document-consent and document-info - support for html and image-rendering - single-usage functionality (preview) | \n
| 1.6.1 - 1.6.31 | \nbugfixes / improvements / compatability | \n- several bugfixes - configurable logging and image generation feature - simplifying module dependencies - compatibility with chili bundle extension - compatibility with order workflow extension - show view document link in sales order view too - add \"chili_editor_viewer_workspace\" system config parameter, improve view document in editor from orders - improve view document in editor from orders - improvments backend configuration - improvments panel menu - csp-support for Magento2.3.5-p1 - improvments for download and rendering statistics - MariaDB magento 2.4.0 row too long - Avoid Check of Chili Environment | \n
| 1.7.0 | \nfeatures | \n- Magento 2.4.0 and php 7.4 compatibility - Default Value for Zoom Level should be empty - Simplify Initial Configuration | \n
| 1.7.1 | \nfeatures | \n- single usage feature (beta) | \n
| 1.8.0 | \nfeatures | \n- single usage feature (final) \n Possibilty to configure scenarios where customers are only allowed to create only one documentversion Possibility to define date periods in that only one documentversion per customer can be created Add Info to product detail page that explains why its currently not possible to configure a documentversion \nshow 2 Buttons on Product Detail Page \"Start Configuration\" and \"Continue Configuration\". Configure if open reminder dialogue automatically popups on entering of the product detail page \n | \n
| 1.8.1 - 1.8.3 | \noptimisation | \n- Datasource Sync Qty Mode - Now the datasource qty is also synchronized after document initialisation - datasource qty field should be readonly when syncqty mode is on - new minor helper functions for later use and min chili-lib requirement raised getDatasourceId changeDocumentDatasourceValuesFromCsvFileContent | \n
| 1.8.4 - 1.8.5 | \nbugfixes | \n- fix for loader in combination with chili-bundle | \n
ROADMAP
\n| 1.9.0 | \nfeatures | \n\n - enhancement of singleusage-feature: Possibility to (re-)use old values of existing chili document for new document drafts \n | \n\n Oct. 2020 \n | \n
| 1.10.0 | \noptimization | \n\n - possibility to change location of save location of tmp-documents (cart-items, wishlist-items) \n | \n\n Q4 2020 \n | \n
| 2.0 | \nfeatures | \n\n - inline mode (for simple, virtual products): loads the chili-editor inside the product detail page (hidden iframe) and shows it when clicking on \"EDIT\". Pro: \"openening the editor\" seems to be faster for the user Con: a tmp-document will be created on entering the product detail page. Actually it will be created, when the user clicks \"EDIT\" and opens the chili editor. \n | \n\n Q4 2020 \n | \n
| 2.1 | \ncompatibility | \n\n compatibility with B2B-Modul of Magento2.x-Commerce Edition (Preassignment of values from a Company- and Company-Address Attribute) \n | \n\n Q1 2021 \n | \n
| 2.2 | \ncompatibility | \n\n compatibility with B2B-Modul of Ecoplan for Magento2.x-Community Edition (Preassignment of values from a Company- and Company-Address Attribute) \n | \n\n Q1 2021 \n | \n
| 3.0 | \nfeatures | \n\n - support of rest api (CHILI-Server) \n | \n\n Q1 2021 \n | \n
| 3.1 | \ncompatibility | \n\n compatibility with SAAS-version of CHILIServer \n | \n\n Q1 2021 \n | \n
INSTALLATION & ADDONS
\n- \n
- The extension can be installed via a (private) satis repository. Please note: The extension is not available via the magento-marketplace or packagist.org! \n
- To install the extension we recommend to use “composer”. Please use the following commands within your ssh-commandline to install the extension.
composer require enobis/module-chili-editor
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento cache:clean
php bin/magento indexer:reindex \n - Access to the latest version of the extension by automatically updating the repository (valid maintenance agreement required) \n