It will tell you if a plugin is installed or not and any errors that are present.

This is needed too when new addons are added to the new plugin version.

Normally addon list is generated during installation, but with the update is safer to use this tool. You can find your plugin in the list and check if all the needed addons are there.

Running the scan generates a list:

It says to you:

- if the plugin is installed

- if the plugin uses an outdated addon 

- if there is an error (there is help: If an addon shows an error, check for characters outside the PHP opening/closing tags.)

Old shortcodes (.sc) and old bbcodes (.bb) are not checked.

How to allow a plugin page to bypass maintenance mode?

Place this before class2.php in your plugin script: $_E107['no_maintenance'] = true;

Warnings:

- don't export core prefs for theme demo data without checking - sensitive data there

- if you check the option Convert paths, you will override install.xml in your theme folder and all images will be moved there. It would be nice option if you could set at least file name (if not destination)

The log system serves several critical functions, including error tracking, auditing user activities, and monitoring system performance. By maintaining detailed logs, administrators can swiftly identify issues, understand user interactions, and ensure compliance with various standards.

The e107 CMS provides a structured logging system that categorizes logs into distinct types, each designed for specific monitoring and auditing purposes. Here’s a detailed look at the different types of logs you mentioned, along with their descriptions and functionalities:

Log Levels:

The logging system utilizes various log levels, including DEBUG, INFO, NOTICE, WARNING, ERROR, and CRITICAL. This hierarchy allows users to filter logs based on severity, making it easier to focus on the most critical issues first.

Log Levels:

DEBUG: Detailed information, typically for developers.

INFO: General information about system operations.

NOTICE: Indications of minor issues or noteworthy events.

WARNING: Indications of potential problems that may require attention.

ERROR: Errors that occur during execution that need immediate attention.

CRITICAL: Critical errors that may cause the system to fail.

Integration with Events:

e107 can automatically generate log entries based on specific events within the CMS. For example, logging can occur when a user logs in or when content is created or modified, providing a comprehensive audit trail.

Configuration:

• Settings: Admins can configure which types of logs to enable or disable through the settings. This allows customization based on the needs of the website.
• Log Levels: Some configurations may allow setting different logging levels, such as debug, info, warning, or error, enabling finer control over what gets logged.

Using Logs for Troubleshooting:

• Debugging: When issues arise, logs can be the first place to check for error messages or warnings that provide clues about the root cause.
• Performance Tuning: Analyzing logs can help identify slow queries or processes that may be impacting website performance.

The e107 CMS logging system

The e107 CMS logging system is a robust feature designed to help developers and administrators monitor, troubleshoot, and maintain their websites effectively. 

System logs is only one part of e107 CMS logging system, it is the admin panel, user interface that provides an interface to view logs, often with filtering options to narrow down the logs based on date, severity, or type.

Access and Security:

Access to log files is typically restricted to authorized personnel to protect sensitive information. The logging system is designed to ensure that critical data remains confidential and secure from unauthorized access. 

Only main admins have access by default.  Then only admins with access to System Logs functionality can see this part of admin area.

Search Functionality: Logs can typically be searched for specific entries or keywords to quickly find relevant information.

 Admin Log

• Description: The Admin Log specifically tracks actions performed by system administrators within the CMS.
• Purpose: This log is essential for auditing administrative activities, providing accountability for changes made by users with elevated permissions. It helps in understanding who made specific changes, when they occurred, and what actions were taken.

User Audit Log

• Description: This log records user-related events, capturing activities such as signups, setting changes, logins, and logouts.
• Purpose: The User Audit Log provides insights into user behavior and interactions with the system. It is crucial for tracking user activities, enhancing security by identifying unusual patterns, and ensuring compliance with user management policies.

 Rolling Log

• Description: The Rolling Log is intended for recording transient events that may not require permanent storage.
• Purpose: This log captures temporary events that occur during normal operations, such as notifications or temporary alerts. It helps in monitoring real-time activities without cluttering the main log files with less significant entries.

Preferences

For rolling logs:

Options

If offers way how to clean logs from admin area.

Best Practices:

• Regular Monitoring: Regularly check logs to catch issues before they escalate.
• Backup Logs: Maintain backups of logs if they contain critical information for compliance or auditing.
• Security Considerations: Ensure that access to logs is restricted to authorized personnel to prevent exposure of sensitive information.

Notes:

• there is also Access logs option, where every site access is logged as small txt file. It will be covered in Preferences. 
• this topic is very well covered in official documentation here: https://userguide.e107.org/administration/tools/system-logs
• advice:  before exporting/backuping database, clean log table