dbAdmin is a database table administration tool that shows corresponding MODX object classes for system tables.

**Base features:**

- browse tables
- truncate, remove and rename tables
- export entire database or selected tables to text file
- filter by table name or class name
- execute sql queries

**Permissions**

To work with dbadmin you need the following permissions (except sudo users):

- **tables_list** — Allow to view a list of tables.
- **table_view** — Table view permission.
- **table_save** — Table save permission.
- **table_truncate** — Truncate permission (truncate table).
- **table_remove** — Remove permission (drop table).
- **table_export** — Allow to export a table.
- **sql_query_execute** — Allow to execute sql queries.

Short [video](https://youtu.be/Qnm2a8vsqiU).

dbAdmin allows to manage your MySql tables - export, rename, truncate and drop them. Also you can execute native sql queries.

dbAdmin

This component offers an alternative concept of content templating without the MODX template engine. 
It also supports the RESTful API based on the FastRoute library.

ZoomX offers an alternative way to handling a request and preparing a response. The main goal is not to use elements from the database (as far as it's possible) and use your favorite IDE and versioning support for full development.

**Important!**
This Extra requires PHP >= 7.0.

ZoomX

Library of the helpfull functions for MODX. Available more than 70 functions.It requires PHP 5.5+.# Send an emailemail('darling@mail.com', 'Subject', 'Email content');email_user('admin', $subject, $content);  // To user# Check the user existenceif (user_exists(['email'=>'admin@mail.com']) { // Exists }# Verify the emailif (!is_email($_POST['email']) { // Validation error }# Get the data from the cache$value = cache('key', 'my_data');# Get lexicon record$name = lang('language_key');# Redirect to the page with the id = 5redirect(5);# Remove resources of the category with the id = 10resources()->where(['parent'=>10])->remove();# Get users from the group "Managers" $usersArray = users()->members('Managers')->toArray();Use is_auth() instead of $modx->user->isAuthenticated($modx->context->key)# Make a list of faked news (using a snippet) return collection(10)->each(function($item, $idx, $modx){return '' . faker()->date() . img(faker()->imageUrl(100,100),['class'=>'img-news']) . ' ' . faker()->text(700) . '';});See details on <a href="https://github.com/sergant210/modHelpers">GitHub.</a>

Library of helpfull functions for MODX developers.

modHelpers

It's a middleware emulator based on classes for MODx Revolution. But
 not only. In addition you can use class-based listeners instead of 
usual plugins.See <a href="https://github.com/sergant210/Middlewares">documentation</a>.

It's a middlewares emulator and plugins substitute based on classes.

Middlewares

MySQL

Now you will not miss any errors. If the log is too large you will see a certain number of the last lines you have specified in the system setting "Last lines" (thanks Bob Ray for the idea). By default, 15.

### Error log on the frontend
It's very useful in development mode. It's available only for users with the "error_log_view" permission.

### System settings
* **admin_email** - Admin email to notify about changes in the error log. If empty the notification would not work. 
* **allow_copy_deletion** - Allow to delete copies of the error log instead of clearing them. 
* **auto_refresh** - Check the state of the error log with the specified frequency. 
* **control_frontend** - If true the error log will be shown on the frontend. 
* **date_format** - Date format in the strftime function style. 
* **format_output** - Displays error log in formatted form. 
* **last_lines** - Displays the specified number of last lines when the error log is too large to display. 
* **refresh_freq** - Error log refresh frequency in seconds. By default, set to 60 seconds. 
* **tpl** - Smarty template for displaying messages from the error log. 
* **css_file** - URL of a css file for the frontend. 
* **js_file** - URL of a javascript file for the frontend.

### Cron task
Use the script _core/components/controlerrorlog/cron/checkerrorlog.php_ to check the error log for new errors.

Important! The error indicator in the manager interface is displayed only for administrators (sudo) and users with permission "error_log_view".

See details on <a href="https://github.com/sergant210/controlErrorLog">Github</a>.

Now you will not miss any errors. If the log is too large you will see a certain number of the last lines you have specified in the system setting "Last lines" (thanks Bob Ray for the idea). By default, 15.
### System settings
- last_lines - display the specified number of last lines when the error log is too large to display. 
- auto_refresh - check the state of the error log with the specified frequency. 
- refresh_freq - error log refresh frequency in seconds. By default, 60 seconds.
- control_frontend - if true the error log will be checked on every site request. If it's changed, the admin will get an email notification. Must be specified the admin email. Not recommended for use on a production site. Use cron task instead. 
- admin_email - admin email to notify about changes in the error log. If empty the notification would not work.

### Cron task
Use the script _core/components/controlerrorlog/cron/checkerrorlog.php_ to check the error log for new errors.

Important! The error indicator in the manager interface is displayed only for administrators (sudo) and users with permission "error_log_view".

See details on <a href="https://github.com/sergant210/controlErrorLog">Github</a>.

Now you will not miss any errors. If the log is too large you will see a certain number of the last lines you have specified in the system setting "Last lines" (thanks Bob Ray for the idea). By default, 15.System settingslast_lines - Displays the specified number of last lines when the error log is too large to display. auto_refresh - Check the state of the error log with the specified frequency. refresh_freq - Error log refresh frequency in seconds. By default, set to 60 seconds.control_frontend - If true the email notification is activated. Must be specified the admin email.admin_email - Admin email to notify about changes in the error log. If empty the notification would not work.Cron taskUse the script core/components/controlerrorlog/cron/checkerrorlog.php to check the error log for new errors.Important! The error indicator in the manager interface is displayed only for administrators (sudo) and users with permission "error_log_view".See details on <a href="https://github.com/sergant210/controlErrorLog">Github</a>.

Now you will not miss any errors. If the log is too large you will see a certain number of the last lines you have specified in the system setting "Last lines" (thanks Bob Ray for the idea). By default, 15.System settingslast_lines - Displays the specified number of last lines when the error log is too large to display. auto_refresh - Check the state of the error log with the specified frequency. refresh_freq - Error log refresh frequency in seconds. By default, set to 60 seconds.control_frontend - If true the email notification is activated. Must be specified the admin email.admin_email - Admin email to notify about changes in the error log. If empty the notification would not work.Important! The error indicator in the manager interface is displayed only for administrators (sudo) and users with permission "error_log_view".See details on <a href="https://github.com/sergant210/controlErrorLog">Github</a>.

Now you will not miss any errors. If the log is too large you will see a certain number of the last lines you have specified in the system setting "Last lines" (thanks Bob Ray for the idea). By default, 15.System settingslast_lines - Displays the specified number of last lines when the error log is too large to display. auto_refresh - Check the state of the error log with the specified frequency. refresh_freq - Error log refresh frequency in seconds. By default, set to 60 seconds.control_frontend - If true the error log will be monitored on each site page loading.admin_email - Admin email to notify about errors.Important! The error indicator is displayed only for administrators (sudo) and users with permission "error_log_view".See details on <a href="https://github.com/sergant210/controlErrorLog">Github</a>.

Now you will not miss any errors. If the log is too large you will see a certain number of the last lines you have specified in the system setting "Last lines" (thanks Bob Ray for the idea). By default, 15.System settingslast_lines - Displays the specified number of last lines when the error log is too large to display. auto_refresh - Check the state of the error log with the specified frequency. refresh_freq - Error log refresh frequency in seconds. By default, set to 60 seconds.Important! The error indicator is displayed only for administrators (sudo) and users with permission "error_log_view".See details on <a href="https://github.com/sergant210/controlErrorLog">Github</a>.

Now you will not miss any mistakes. If the log is too large you can see any number of lines you have specified in the plugin controlErrorLog (thanks Bob Ray for the idea). By default, 10.See details on <a href="https://github.com/sergant210/controlErrorLog">Github</a>.

This Extra adds new features:
- ability to control the error log and to view it in a popup window.
- email notification about changes in the error log. 
- displaying error log on the frontend.

controlErrorLog

About controlErrorLog

Information

Instructions

New in 1.4.6-pl

Current releases

Related Extras

More by Sergei Shlokov

dbAdmin

ZoomX

modHelpers

Middlewares

Browse Category

Administration