A Magento Open Source extension that enhances the admin panel experience with additional tools, tweaks and customization options.
This module:
✅ Enhances the admin interface with additional configuration tools.
✅ Improves menu management for better navigation within Acid Unit extensions.
✅ Acts as a dependency for all Acid Unit extensions, ensuring consistent admin functionality.
To install the module, run:
composer require acid-unit/module-adminEnabling this option allows users to edit content visually instead of dealing with raw HTML, reducing errors and improving content management efficiency.
Since the HTML Code element is powerful yet complex, this configuration
lets admin users toggle the WYSIWYG editor inside the element for quicker editing.
Stores > Settings > Configuration > General > Content Management > WYSIWYG Options
Provides HTML editing directly within the admin field, providing a lightweight alternative to PageBuilder for small-to-medium content sections.
This feature allows admins to manage structured data efficiently, making it easier to configure settings like custom redirects, tracking events, and more.
The toggle button should be defined as a new <field> element with the following structure:
<!-- VendorName/VendorModule/etc/adminhtml/system.xml -->
<section id="page">
<group id="form">
<field id="editable_field" type="textarea" sortOrder="10">...</field>
<field id="editable_field_toggle_editor" sortOrder="15">
<attribute type="target_field">page_form_editable_field</attribute>
<frontend_model>AcidUnit\Admin\Block\Adminhtml\System\Config\Form\Field\ToggleEditorButton</frontend_model>
</field>
</group>
</section>📌 Ensure the sortOrder value for the toggle button is higher than the target field
so that it appears directly beneath it.
The Table Field is useful for storing structured data in the admin panel, like custom redirects,
event tracking mappings, or configurable lists.
Below is how to define it in system.xml.
To render a table field, define the <frontend_model> and <backend_model>
classes in your <field> element:
<!-- VendorName/VendorModule/etc/adminhtml/system.xml -->
<section id="...">
<group id="...">
<field id="...">
<label>...</label>
<frontend_model>VendorName\VendorModule\Block\Adminhtml\Form\Field\YourCustomTableField</frontend_model>
<backend_model>VendorName\VendorModule\Model\System\Config\Backend\YourCustomTableField</backend_model>
</field>
</group>
</section>Backend & Frontend Virtual Models
Define virtual classes for backend, frontend, and helper models:
<!-- VendorName/VendorModule/etc/adminhtml/di.xml -->
<!-- Backend Model Helper -->
<virtualType name="VendorName\VendorModule\Helper\YourCustomTableField"
type="AcidUnit\Admin\Helper\AdminTableField">
<arguments>
<argument name="tableFields" xsi:type="array">
<!-- items for 'tableFields' argument represent column IDs of your table -->
<item name="enabled" xsi:type="string">enabled</item>
<item name="url" xsi:type="string">url</item>
<item name="event" xsi:type="string">event</item>
</argument>
</arguments>
</virtualType>
<!-- Backend Model defined in system.xml -->
<virtualType name="VendorName\VendorModule\Model\System\Config\Backend\YourCustomTableField"
type="AcidUnit\Admin\Model\System\Config\Backend\AdminTableField">
<arguments>
<!-- backend model helper virtual class
should be passed as an argument with 'helper' name -->
<argument name="helper" xsi:type="object">VendorName\VendorModule\Helper\YourCustomTableField</argument>
</arguments>
</virtualType>
<!-- Frontend Model defined in system.xml -->
<virtualType name="VendorName\VendorModule\Block\Adminhtml\Form\Field\YourCustomTableField"
type="AcidUnit\Admin\Block\Adminhtml\Form\Field\AdminTableField">
<arguments>
<argument name="tableFields" xsi:type="array">
<!-- items for 'tableFields' argument here
represents columns of your table -->
<!-- for item names use id's defined in backend model helper -->
<item name="enabled" xsi:type="array">
<!-- 'label' item should have the column label -->
<item name="label" xsi:type="string">Enabled</item>
<!-- for the dropdown field you should define 'renderer' item
and pass dropdown renderer class which will be implemented below -->
<item name="renderer" xsi:type="object">VendorName\VendorModule\Block\Adminhtml\Form\Field\Yesno</item>
</item>
<item name="url" xsi:type="array">
<item name="label" xsi:type="string">Page URL</item>
<!-- for the text input field you should define 'class'
item with HTML class list -->
<!-- 'admin__control-text' is a required class;
use 'required-entry' class if the field should be required -->
<item name="class" xsi:type="string">admin__control-text required-entry</item>
</item>
<item name="event" xsi:type="array">
<item name="label" xsi:type="string">Event Name</item>
<item name="class" xsi:type="string">admin__control-text required-entry</item>
</item>
</argument>
<!-- 'buttonLabel' argument is used to set a text
for the button to create a new row -->
<argument name="buttonLabel" xsi:type="string">Add Custom Page</argument>
</arguments>
</virtualType>📌 Note: Ensure all virtual classes are compiled before deployment.
Dropdown Renderer for Table Fields
<?php
/** VendorName\VendorModule\Block\Adminhtml\Form\Field\Yesno.php */
namespace VendorName\VendorModule\Block\Adminhtml\Form\Field;
use Magento\Framework\View\Element\Html\Select;
class Yesno extends Select
{
/**
* @param string $value
* @return mixed
*/
public function setInputName(string $value): mixed
{
return $this->setName($value);
}
/**
* Dropdown options are set in this method
* First addOption() parameter is an option value, second parameter is an option label
* @return string
*/
public function _toHtml(): string
{
if (!$this->getOptions()) {
$this->addOption('1', __('Yes'));
$this->addOption('0', __('No'));
}
return parent::_toHtml();
}
}📌 Compile & Deploy:
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f
bin/magento cache:flush
The Table Field value is stored as a stringified object and can be handled like any regular admin text field.
- On the frontend, use
JSON.parse. - On the backend, use
\Magento\Framework\Serialize\Serializer\Json::serialize.
to parse and manipulate the data.
If you're using another Acid Unit extension, this module is installed automatically as a dependency.
However, if you want to use these Admin Features separately, install the module manually.
composer require acid-unit/module-adminAfter installation, enable the module and run setup:upgrade:
bin/magento module:enable AcidUnit_Admin
bin/magento setup:upgrade✅ Compatible with: Magento Open Source & Adobe Commerce >=2.4.4
✅ Requires PHP 8.1+
🛠 Tested on Magento Open Source 2.4.7-p3 with PHP 8.3