<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Core Functionality &#8211; Debug Log Viewer</title>
	<atom:link href="https://www.lysyiweb.net/docs-category/core-functionality/feed" rel="self" type="application/rss+xml" />
	<link>https://www.lysyiweb.net</link>
	<description></description>
	<lastBuildDate>Sat, 14 Mar 2026 14:19:13 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>

<image>
	<url>https://www.lysyiweb.net/wp-content/uploads/2026/02/cropped-logo-1-2-32x32.png</url>
	<title>Core Functionality &#8211; Debug Log Viewer</title>
	<link>https://www.lysyiweb.net</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Log View Tab</title>
		<link>https://www.lysyiweb.net/docs/core-features-log-view-tab</link>
					<comments>https://www.lysyiweb.net/docs/core-features-log-view-tab#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Thu, 19 Feb 2026 15:55:51 +0000</pubDate>
				<guid isPermaLink="false">https://www.lysyiweb.net/?post_type=docs&#038;p=1284</guid>

					<description><![CDATA[Monitor and analyze WordPress debug logs with the Log View tab in Debug Log Viewer. Search, filter, track errors, and manage debug settings in real time.]]></description>
										<content:encoded><![CDATA[<!-- content style : start --><style type="text/css" data-name="kubio-style"></style><!-- content style : end -->
<p class="wp-block-paragraph">The Log View tab is the primary interface for monitoring and analyzing debug logs.</p>



<h2 class="wp-block-heading">Viewing Debug Logs</h2>



<h3 class="wp-block-heading">Understanding the Log Table Structure</h3>



<p class="wp-block-paragraph">The log table displays entries with these columns:</p>



<ul class="wp-block-list">
<li><strong>Timestamp</strong>: When the error occurred</li>



<li><strong>Type</strong>: Error level (Notice, Warning, Fatal Error, etc.)</li>



<li><strong>Datetime</strong>: Full date and time</li>



<li><strong>Description</strong>: Error message details with callstack (if presented)</li>



<li><strong>File</strong>: Source file path</li>



<li><strong>Line</strong>: Line number in the file</li>
</ul>



<h3 class="wp-block-heading">Table Interface Features</h3>



<p class="wp-block-paragraph">The interface includes pagination controls for large log files and row display options (10, 25, 50, or 100 entries per page). The responsive design adapts to different screen sizes.</p>



<h2 class="wp-block-heading">Debug Constants Control</h2>



<h3 class="wp-block-heading">Toggling WP_DEBUG</h3>



<ul class="wp-block-list">
<li>Enable or disable debug mode directly from the interface</li>



<li>Changes are reflected in real-time</li>
</ul>



<h3 class="wp-block-heading">Managing Other Constants</h3>



<ul class="wp-block-list">
<li><strong><code>SCRIPT_DEBUG</code></strong>: Controls script version loading</li>



<li><strong><code>WP_DEBUG_LOG</code></strong>: Logs errors to debug.log file</li>



<li><strong><code>WP_DEBUG_DISPLAY</code></strong>: Shows errors on screen (use with caution)</li>
</ul>



<h3 class="wp-block-heading">Security Warning for WP_DEBUG_DISPLAY</h3>



<p class="wp-block-paragraph">On production sites, this should usually be disabled to prevent sensitive data exposure.</p>



<h2 class="wp-block-heading">Search &amp; Filtering</h2>



<h3 class="wp-block-heading">Basic Search Functionality</h3>



<ul class="wp-block-list">
<li>Use the search bar to filter logs by keyword</li>



<li>Searches across all columns simultaneously</li>
</ul>



<h3 class="wp-block-heading">Understanding Log Entry Types</h3>



<p class="wp-block-paragraph">Common error types include:</p>



<ul class="wp-block-list">
<li><strong>Notice</strong>: Non-critical issues that do not stop script execution. Notices typically indicate minor problems such as undefined variables, deprecated behavior usage, or small inconsistencies in the code. While they do not break functionality, they may signal areas that should be cleaned up to ensure stability and future compatibility.</li>



<li><strong>Warning</strong>: More serious issues that still allow the script to continue running. Warnings often occur when a file cannot be included, an argument is invalid, or an operation fails but does not completely halt execution. These should be investigated, as they may lead to unstable behavior.</li>



<li><strong>Fatal Error</strong>: Critical errors that immediately stop script execution. Fatal errors occur when PHP encounters a problem it cannot recover from, such as calling an undefined function, exceeding memory limits, or failing to load a required class. These errors typically result in a white screen or a visible error message.</li>



<li><strong>Database Error</strong>: Errors related to database operations. These occur when a query fails, a table does not exist, credentials are incorrect, or the database server is unreachable. Database errors can break site functionality, especially when retrieving or saving content.</li>



<li><strong>Deprecated Error:</strong> ndicates that a function, method, parameter, or feature is outdated and should no longer be used. Deprecated elements still work but are scheduled for removal in future versions. These notices help developers update their code before compatibility breaks.</li>



<li><strong>Custom:</strong> Log entries intentionally created by developers or plugins for debugging or monitoring purposes. Custom logs are not native PHP error types but are manually written using logging functions. They help track specific events, variable values, API responses, or execution flow during development and troubleshooting.</li>
</ul>



<h3 class="wp-block-heading">Column Visibility Controls</h3>



<p class="wp-block-paragraph">Show or hide columns based on your needs:</p>



<ul class="wp-block-list">
<li>Toggle visibility using the column selector dropdown</li>
</ul>



<h2 class="wp-block-heading">Advanced Filtering &#8211; SearchBuilder</h2>



<p class="wp-block-paragraph">For complex filtering, use the SearchBuilder:</p>



<ul class="wp-block-list">
<li>Create multiple filter conditions</li>



<li>Combine criteria using AND/OR logic</li>
</ul>



<h2 class="wp-block-heading">Real-Time Updates</h2>



<h3 class="wp-block-heading">Live Updates Mode</h3>



<ul class="wp-block-list">
<li>Auto mode: Polls the log file every 10 seconds</li>



<li>Manual mode: Updates only when refreshed by clicking to the button</li>
</ul>



<h3 class="wp-block-heading">Performance Considerations</h3>



<ul class="wp-block-list">
<li>Auto mode provides real-time monitoring but uses more resources</li>



<li>Manual mode is suitable for large log files or low-resource environments</li>
</ul>



<h2 class="wp-block-heading">Log Actions</h2>



<h3 class="wp-block-heading">Viewing Stack Traces</h3>



<ul class="wp-block-list">
<li>Click on an entry to expand the stack trace</li>



<li>See the full call hierarchy leading to the error</li>
</ul>



<h3 class="wp-block-heading">Copying Stack Traces</h3>



<ul class="wp-block-list">
<li>One-click copy functionality for easy sharing</li>



<li>Copies formatted text to clipboard</li>
</ul>



<h3 class="wp-block-heading">Reading Detailed Error Descriptions</h3>



<ul class="wp-block-list">
<li>Full error messages with context</li>



<li>File and line references for quick navigation</li>
</ul>



<h2 class="wp-block-heading">Log File Information</h2>



<ul class="wp-block-list">
<li>View the current log file path</li>



<li>Check file size with warnings for large files (&gt;10MB)</li>



<li>Verify file accessibility and security</li>
</ul>



<p class="wp-block-paragraph">For more advanced features, see the <a href="https://www.lysyiweb.net/docs/settings-tab" data-type="docs" data-id="1321">Settings Tab</a> guide.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.lysyiweb.net/docs/core-features-log-view-tab/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Settings Tab</title>
		<link>https://www.lysyiweb.net/docs/settings-tab</link>
					<comments>https://www.lysyiweb.net/docs/settings-tab#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Fri, 20 Feb 2026 16:05:58 +0000</pubDate>
				<guid isPermaLink="false">https://www.lysyiweb.net/?post_type=docs&#038;p=1321</guid>

					<description><![CDATA[Configure Debug Log Viewer settings: update modes, datetime formats, and timezone options for efficient WordPress debug log monitoring and analysis.]]></description>
										<content:encoded><![CDATA[<!-- content style : start --><style type="text/css" data-name="kubio-style"></style><!-- content style : end -->
<p class="wp-block-paragraph">The Settings tab allows you to configure how the plugin behaves and displays information.</p>



<h2 class="wp-block-heading">Log Update Mode Configuration</h2>



<h3 class="wp-block-heading"><strong>Manual Update Mode</strong></h3>



<ul class="wp-block-list">
<li>Logs update only when you refresh the page</li>



<li>Lower resource usage, ideal for large log files</li>
</ul>



<h3 class="wp-block-heading"><strong>Auto Update Mode</strong></h3>



<ul class="wp-block-list">
<li>Logs update automatically every 10 seconds</li>



<li>Provides real-time monitoring but uses more resources</li>
</ul>



<h3 class="wp-block-heading"><strong>Performance Considerations</strong></h3>



<ul class="wp-block-list">
<li>Auto mode is best for active debugging sessions</li>



<li>Manual mode is suitable for routine checks or large logs</li>
</ul>



<h2 class="wp-block-heading"><strong>Datetime Display Options</strong></h2>



<h3 class="wp-block-heading"><strong>Absolute Time Format</strong></h3>



<ul class="wp-block-list">
<li>Shows full date and time (e.g., &#8220;2026-05-15 14:30:22&#8221;). The output format depends on the website&#8217;s datetime setting in Settings -&gt; General -&gt; Date Format</li>



<li>Useful for precise timestamp comparisons</li>
</ul>



<h3 class="wp-block-heading"><strong>Relative Time Format</strong></h3>



<ul class="wp-block-list">
<li>Displays time relative to now (e.g., &#8220;2 hours ago&#8221;)</li>



<li>Easier to understand at a glance</li>
</ul>



<h3 class="wp-block-heading"><strong>Switching Between Formats</strong></h3>



<ul class="wp-block-list">
<li>Toggle between formats using the datetime format switcher</li>



<li>Your preference is saved for future sessions</li>
</ul>



<h2 class="wp-block-heading">Timezone Settings</h2>



<h3 class="wp-block-heading"><strong>Setting Custom Timezone</strong></h3>



<ol class="wp-block-list">
<li>Click the timezone selector dropdown</li>



<li>Search for your desired timezone</li>
</ol>



<h3 class="wp-block-heading"><strong>Using WordPress Default Timezone</strong></h3>



<ul class="wp-block-list">
<li>Automatically inherits WordPress site timezone</li>



<li>Ensures consistency with other WordPress features</li>
</ul>



<h3 class="wp-block-heading"><strong>Why Timezone Matters</strong></h3>



<ul class="wp-block-list">
<li>Ensures log timestamps match your local time</li>



<li>Helps correlate errors with specific events</li>
</ul>



<h3 class="wp-block-heading"><strong>Impact on Log Entry Timestamps</strong></h3>



<ul class="wp-block-list">
<li>Affects how timestamps are displayed in the log table</li>



<li>Does not change the actual log file contents</li>
</ul>



<p class="wp-block-paragraph">For email notification setup, see the <a href="https://www.lysyiweb.net/docs/alerts-email-notifications" data-type="docs" data-id="1326">Alerts Tab</a> guide.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.lysyiweb.net/docs/settings-tab/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Alerts (Email Notifications)</title>
		<link>https://www.lysyiweb.net/docs/alerts-email-notifications</link>
					<comments>https://www.lysyiweb.net/docs/alerts-email-notifications#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Fri, 20 Feb 2026 17:01:57 +0000</pubDate>
				<guid isPermaLink="false">https://www.lysyiweb.net/?post_type=docs&#038;p=1326</guid>

					<description><![CDATA[The Alerts tab allows you to configure email notifications for critical errors. Setting Up Email Alerts Enabling/Disabling Notifications Configuring Notification Recipient (Free) Adding Multiple Recipients (Pro) Alert Frequency Options Hourly Notifications Twice Daily Notifications Daily Notifications Weekly Notifications Understanding Cron Schedules Error Level Selection (Pro Feature) Understanding Different Error Levels Default Monitoring Levels Additional Selectable [&#8230;]]]></description>
										<content:encoded><![CDATA[<!-- content style : start --><style type="text/css" data-name="kubio-style"></style><!-- content style : end -->
<p class="wp-block-paragraph">The Alerts tab allows you to configure email notifications for critical errors.</p>



<h2 class="wp-block-heading"><strong>Setting Up Email Alerts</strong></h2>



<h3 class="wp-block-heading">Enabling/Disabling Notifications</h3>



<ul class="wp-block-list">
<li>Toggle the main switch to enable or disable alerts</li>



<li>Disabled by default for new installations</li>
</ul>



<h3 class="wp-block-heading"><strong>Configuring Notification Recipient (Free)</strong></h3>



<ul class="wp-block-list">
<li>Enter a single email address in the recipient field</li>



<li>Supports standard email formats</li>
</ul>



<h3 class="wp-block-heading"><strong>Adding Multiple Recipients (Pro)</strong></h3>



<ul class="wp-block-list">
<li>Up to 3 recipients can be added in the Pro version</li>



<li>Use a separate input field for each recipient; do not separate Emails by comma</li>
</ul>



<h2 class="wp-block-heading"><strong>Alert Frequency Options</strong></h2>



<h3 class="wp-block-heading"><strong>Hourly Notifications</strong></h3>



<ul class="wp-block-list">
<li>Receives alerts every hour with accumulated errors</li>



<li>Good for active development or high-traffic sites</li>
</ul>



<h3 class="wp-block-heading">Twice Daily Notifications</h3>



<ul class="wp-block-list">
<li>Alerts sent at 12-hour intervals</li>



<li>Balances frequency and email volume</li>
</ul>



<h3 class="wp-block-heading">Daily Notifications</h3>



<ul class="wp-block-list">
<li>Single daily digest of all errors</li>



<li>Suitable for routine monitoring</li>
</ul>



<h3 class="wp-block-heading">Weekly Notifications</h3>



<ul class="wp-block-list">
<li>Summary sent once per week</li>



<li>Ideal for long-term tracking without clutter</li>
</ul>



<h3 class="wp-block-heading">Understanding Cron Schedules</h3>



<ul class="wp-block-list">
<li>Alerts are triggered by WordPress cron jobs. The notification may be delayed if the site has low traffic.</li>



<li>Next scheduled time is displayed in the interface</li>
</ul>



<h2 class="wp-block-heading">Error Level Selection (Pro Feature)</h2>



<h3 class="wp-block-heading"><strong>Understanding Different Error Levels</strong></h3>



<ul class="wp-block-list">
<li><strong>Database Errors</strong>: Issues with database queries</li>



<li><strong>Fatal Errors</strong>: Crashes that stop script execution</li>



<li><strong>Parse Errors</strong>: Syntax issues in PHP code</li>
</ul>



<h3 class="wp-block-heading"><strong>Default Monitoring Levels</strong></h3>



<ul class="wp-block-list">
<li>Database Errors</li>



<li>Fatal Errors</li>



<li>Parse Errors</li>



<li>Deprecated function usage</li>
</ul>



<h3 class="wp-block-heading"><strong>Additional Selectable Levels (Pro)</strong></h3>



<ul class="wp-block-list">
<li>Warnings: Non-critical issues that may become problems</li>



<li>Notices: Informational messages about potential issues</li>



<li>Custom: User-defined error types</li>
</ul>



<h3 class="wp-block-heading"><strong>Reducing Notification Noise</strong></h3>



<ul class="wp-block-list">
<li>Select only the most critical error levels</li>



<li>Use another notification interval</li>
</ul>



<h2 class="wp-block-heading">Testing &amp; Management</h2>



<h3 class="wp-block-heading"><strong>Sending Test Emails</strong></h3>



<ul class="wp-block-list">
<li>Click the &#8220;Send Test Email&#8221; button to verify the setup immediately after enabling notifications</li>
</ul>



<h3 class="wp-block-heading">Verifying Email Delivery</h3>



<ul class="wp-block-list">
<li>Check your inbox for the test email</li>



<li>Ensure emails aren&#8217;t being marked as spam</li>
</ul>



<h3 class="wp-block-heading">Viewing Next Scheduled Notification Time</h3>



<ul class="wp-block-list">
<li>Displayed in the alert summary section</li>



<li>Helps plan for expected email arrivals</li>
</ul>



<figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" width="1024" height="134" src="https://www.lysyiweb.net/wp-content/uploads/2026/02/debug-log-viewer-next-notification-time-1024x134.png" alt="" class="wp-image-1328" srcset="https://www.lysyiweb.net/wp-content/uploads/2026/02/debug-log-viewer-next-notification-time-1024x134.png 1024w, https://www.lysyiweb.net/wp-content/uploads/2026/02/debug-log-viewer-next-notification-time-300x39.png 300w, https://www.lysyiweb.net/wp-content/uploads/2026/02/debug-log-viewer-next-notification-time-768x101.png 768w, https://www.lysyiweb.net/wp-content/uploads/2026/02/debug-log-viewer-next-notification-time.png 1340w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading">Example of incoming Email</h3>


<div class="wp-block-image">
<figure class="aligncenter size-large is-resized"><img decoding="async" width="826" height="1024" src="https://www.lysyiweb.net/wp-content/uploads/2026/02/Example-of-alerts-Email-826x1024.png" alt="" class="wp-image-1329" style="width:650px;height:auto" srcset="https://www.lysyiweb.net/wp-content/uploads/2026/02/Example-of-alerts-Email-826x1024.png 826w, https://www.lysyiweb.net/wp-content/uploads/2026/02/Example-of-alerts-Email-242x300.png 242w, https://www.lysyiweb.net/wp-content/uploads/2026/02/Example-of-alerts-Email-768x953.png 768w, https://www.lysyiweb.net/wp-content/uploads/2026/02/Example-of-alerts-Email-871x1080.png 871w, https://www.lysyiweb.net/wp-content/uploads/2026/02/Example-of-alerts-Email.png 1082w" sizes="(max-width: 826px) 100vw, 826px" /></figure>
</div>


<p class="wp-block-paragraph">For log file management, see the <a href="https://www.lysyiweb.net/docs/cleanup-tab-pro-feature" data-type="docs" data-id="1332">Cleanup Tab</a> guide.</p>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.lysyiweb.net/docs/alerts-email-notifications/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Cleanup Tab (Pro Feature)</title>
		<link>https://www.lysyiweb.net/docs/cleanup-tab-pro-feature</link>
					<comments>https://www.lysyiweb.net/docs/cleanup-tab-pro-feature#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sat, 21 Feb 2026 11:46:04 +0000</pubDate>
				<guid isPermaLink="false">https://www.lysyiweb.net/?post_type=docs&#038;p=1332</guid>

					<description><![CDATA[The Cleanup tab provides tools to manage your log files and prevent them from growing too large. Automatic Log File Management Importance of Log Cleanup Disk Space Considerations Cleanup Safety and Backups Original logs are preserved before cleanup (the option available for Pro users) Cleanup Configuration Setting Maximum Log Size (MB) Cleanup Methods Truncate (Keep [&#8230;]]]></description>
										<content:encoded><![CDATA[<!-- content style : start --><style type="text/css" data-name="kubio-style"></style><!-- content style : end -->
<p class="wp-block-paragraph">The Cleanup tab provides tools to manage your log files and prevent them from growing too large.</p>



<h2 class="wp-block-heading">Automatic Log File Management</h2>



<h3 class="wp-block-heading"><strong>Importance of Log Cleanup</strong></h3>



<ul class="wp-block-list">
<li>Prevents log files from consuming excessive disk space</li>



<li>Helps maintain a manageable number of log entries</li>
</ul>



<h3 class="wp-block-heading"><strong>Disk Space Considerations</strong></h3>



<ul class="wp-block-list">
<li>Large log files can impact server performance</li>



<li>Especially important on shared hosting environments</li>
</ul>



<h3 class="wp-block-heading">Cleanup Safety and Backups</h3>



<p class="wp-block-paragraph">Original logs are preserved before cleanup (the option available for Pro users)</p>



<h2 class="wp-block-heading">Cleanup Configuration</h2>



<h3 class="wp-block-heading"><strong>Setting Maximum Log Size (MB)</strong></h3>



<ul class="wp-block-list">
<li>Define the maximum allowed log file size</li>



<li>Recommended: 10MB or less for optimal performance</li>
</ul>



<h3 class="wp-block-heading"><strong>Cleanup Methods</strong></h3>



<h4 class="wp-block-heading">Truncate (Keep Last X%)</h4>



<ul class="wp-block-list">
<li>Removes older entries while preserving recent logs</li>



<li>Configurable percentage to retain (e.g., keep last 20%)</li>
</ul>



<h4 class="wp-block-heading">Empty File Completely</h4>



<ul class="wp-block-list">
<li>Clears the entire log file</li>



<li>Useful for starting fresh after resolving issues</li>
</ul>



<h4 class="wp-block-heading">Archive with Backup (Pro)</h4>



<ul class="wp-block-list">
<li>Creates a backup before cleanup</li>



<li>Archived logs can be restored if needed</li>
</ul>



<h3 class="wp-block-heading"><strong>Choosing the Right Method</strong></h3>



<ul class="wp-block-list">
<li><strong>Truncate</strong>: Best for ongoing monitoring</li>



<li><strong>Empty File</strong>: Useful after resolving all issues</li>



<li><strong>Archive</strong>: Recommended before major site changes</li>
</ul>



<h2 class="wp-block-heading">Scheduled Cleanup</h2>



<h3 class="wp-block-heading"><strong>Available Cleanup Frequencies</strong></h3>



<ul class="wp-block-list">
<li><strong>Every 6 hours</strong>: Aggressive cleanup for high-traffic sites</li>



<li><strong>Every 12 hours</strong>: Balanced approach for active sites</li>



<li><strong>Twice Daily</strong>: Standard cleanup schedule</li>



<li><strong>Once Daily</strong>: Suitable for most monitoring needs</li>
</ul>



<h3 class="wp-block-heading"><strong>Viewing Next Scheduled Cleanup Time</strong></h3>



<ul class="wp-block-list">
<li>Displayed in the cleanup summary section</li>



<li>Helps plan for expected maintenance windows</li>
</ul>



<h3 class="wp-block-heading"><strong>WP-Cron Integration</strong></h3>



<ul class="wp-block-list">
<li>Uses WordPress built-in cron system</li>



<li>No additional server cron jobs required</li>
</ul>



<h2 class="wp-block-heading">Manual Cleanup</h2>



<h3 class="wp-block-heading"><strong>Running Cleanup On Demand</strong></h3>



<ul class="wp-block-list">
<li>Click the &#8220;Run Now&#8221; button to initiate immediate cleanup</li>



<li>Useful before troubleshooting or maintenance</li>
</ul>



<h3 class="wp-block-heading"><strong>Understanding Cleanup Results</strong></h3>



<ul class="wp-block-list">
<li>View statistics after cleanup completion</li>



<li>See file size before and after</li>



<li>Percentage of space freed</li>



<li>Number of entries removed</li>



<li>New file size</li>
</ul>



<h3 class="wp-block-heading"><strong>Cleanup Notifications</strong></h3>



<ul class="wp-block-list">
<li>Receive email alerts after cleanup tasks</li>



<li>Includes summary of actions performed</li>
</ul>



<p class="wp-block-paragraph">For advanced features, see the <a href="https://www.lysyiweb.net/docs/advanced-features" data-type="docs" data-id="1298">Advanced Features</a> guide.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.lysyiweb.net/docs/cleanup-tab-pro-feature/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
