Billy Wilcosky

Wiki Blocks lets you add collaborative wiki content with full version control. Users can suggest changes, review version history, and merge updates with proper permission controls.
<h4>Key Features</h4>
<ul>
<li>Gutenberg Block Integration: Seamlessly adds the wiki block type</li>
<li>Version Control: Complete history of all changes with user attribution</li>
<li>Collaborative Editing: Users can suggest changes that are reviewed before acceptance</li>
<li>Permission System: Granular control over who can suggest, browse, and merge changes</li>
<li>Modern UI: Clean, responsive interface with modal dialogs</li>
<li>Accessibility: Full accessibility support with keyboard navigation and screen reader compatibility</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Add a Wiki Block: Insert the Wiki Block into any post or page</li>
<li>Initial Content: Set the initial content that becomes the first version</li>
<li>User Suggestions: Logged-in users can suggest changes with summaries</li>
<li>Version History: Browse all versions with excerpts and full content views</li>
<li>Review & Merge: Administrators or authorized users can merge suggestions into the live version</li>
</ol>
<h4>Permission Levels</h4>
<ul>
<li>Suggest Changes: Control which user roles can submit suggestions</li>
<li>Browse History: Manage who can view version history</li>
<li>Merge Versions: Restrict who can accept changes as the new live version</li>
<li>Login Requirements: Optionally require login to browse versions</li>
</ul>
<h4>Use Cases</h4>
<ul>
<li>Documentation Sites: Collaborative documentation with version tracking</li>
<li>Knowledge Bases: Community-driven content with review process</li>
<li>Policy Pages: Controlled content updates with approval workflow</li>
<li>Educational Content: Student contributions with teacher oversight</li>
<li>Team Wikis: Internal knowledge sharing with permission controls</li>
</ul>
<h3>Translation</h3>
This plugin is translation-ready and includes a POT file for internationalization. To contribute translations:
<ol>
<li>Download the POT file from <code>/languages/wiki-blocks.pot</code></li>
<li>Translate using a tool like Poedit</li>
<li>Save as <code>wiki-blocks-{locale}.po</code> and <code>wiki-blocks-{locale}.mo</code></li>
<li>Submit translations to the plugin repository</li>
</ol>
<h3>Support</h3>
For support, feature requests, or bug reports, please visit the <a href="https://wilcosky.com/contact" rel="nofollow ugc">plugin support page</a>.
<h3>Credits</h3>
Developed by <a href="https://wilcosky.com" rel="nofollow ugc">Billy Wilcosky</a>
Built with WordPress best practices and modern web standards.
<h3>License</h3>
This plugin is licensed under the GPL v2 or later.
<h3>Privacy</h3>
Wiki Blocks stores version history and user contributions in your WordPress database. This data includes:
<ul>
<li>Content versions and change summaries</li>
<li>User attribution for changes</li>
<li>Block-specific settings and permissions</li>
</ul>
No data is sent to external servers. All information remains within your WordPress installation.
<h3>Security</h3>
Wiki Blocks follows WordPress security best practices:
<ul>
<li>All user inputs are sanitized and validated</li>
<li>Nonces are used for all AJAX requests</li>
<li>SQL queries use prepared statements</li>
<li>Output is properly escaped</li>
<li>Permission checks are performed on all actions</li>
</ul>
<h3>Performance</h3>
<ul>
<li>Optimized database queries with proper indexing</li>
<li>Efficient asset loading with cache busting</li>
<li>Minimal impact on page load times</li>
<li>Responsive design for all devices</li>
</ul>
<h3>Accessibility</h3>
<ul>
<li>Full keyboard navigation support</li>
<li>Screen reader compatible</li>
<li>High contrast mode support</li>
<li>Reduced motion preferences respected</li>
<li>Semantic HTML structure</li>
<li>ARIA labels and descriptions</li>
</ul>
<h3>Development</h3>
Wiki Blocks is built with:
<ul>
<li>PHP 8.0+ compatibility</li>
<li>WordPress coding standards</li>
<li>Modern JavaScript (ES6+)</li>
<li>Responsive CSS with Flexbox/Grid</li>
<li>Accessibility-first design principles</li>
</ul>
<h3>Roadmap</h3>
Future versions may include:
<ul>
<li>What you suggest</li>
</ul>
<h3>Contributing</h3>
Contributions are welcome! Please:
<ol>
<li>Follow WordPress coding standards</li>
<li>Include proper documentation</li>
<li>Test thoroughly before submitting</li>
<li>Use meaningful commit messages</li>
<li>Respect accessibility guidelines</li>
</ol>
<h3>Donate</h3>
If you find this plugin useful, consider supporting its development:
<ul>
<li><a href="https://buymeacoffee.com/billyw" rel="nofollow ugc">Donate</a></li>
</ul>
Thank you for using Wiki Blocks!

Wiki Blocks

Add wiki Gutenberg blocks to any page/post with version control and user collaboration features.

Adeel

eLearning evolve

Dedicated Support 
For quick support and assistance, please contact us here 
<a href="https://elearningevolve.com/contact/" rel="nofollow ugc">https://elearningevolve.com/contact/</a>
UpdateGuard – Safe Auto Updates, Semantic Version Control and Update Manager provides intelligent automatic updates for WordPress plugins, themes, and core using semantic versioning principles. Unlike WordPress’s default auto-update system that updates to any available version, this plugin gives you granular control over update types.
Perfect for: 
* WordPress site administrators who want automatic security updates without breaking changes 
* Developers managing multiple WordPress sites 
* Businesses requiring stable, secure WordPress installations 
* Agencies maintaining dozens of client websites 
* Anyone who wants to prevent major version updates from breaking their site
Why Use UpdateGuard – Safe Auto Updates, Semantic Version Control and Update Manager? 
WordPress’s built-in auto-update feature applies ALL updates automatically, including major version changes that can break your site. UpdateGuard – Safe Auto Updates, Semantic Version Control and Update Manager lets you: 
* Automatically install security patches and minor updates 
* Block major version updates that might break compatibility 
* Configure update policies per plugin or globally 
* Get email notifications about updates 
* Track all update activity with comprehensive logs 
* Manually test and trigger updates on demand 
* Block both auto and manual updates that violate your policy
Key Features:
<ul>
<li>Semantic Versioning Support – Automatically detects major.minor.patch version numbers and categorizes every pending update</li>
<li>Selective Update Control – Choose to allow only minor and patch updates while blocking major version changes</li>
<li>4-Level Update Policy – Set each plugin to Major, Minor, Patch, or Hold (block all updates entirely)</li>
<li>Per-Plugin Configuration – Set individual update levels for each plugin in a compact, sortable table, or use a global default</li>
<li>Safe Update Strategy – Prevents breaking changes from major version updates</li>
<li>Manual & Auto Update Blocking – UpdateGuard blocks not only auto-updates but also manual/bulk updates from the Plugins page that violate your policy</li>
<li>Test Update Workflow – One-click “Check and Update Plugins Now” button lets you immediately trigger bulk updates using a separate test update level, independent from your global policy</li>
<li>Comprehensive Logging – Track all completed plugin updates with plugin names, version changes, and timestamps. Log retention is configurable</li>
<li>Email Notifications – Get notified about applied automatic updates, blocked/manual-only updates, and new pending updates. Emails include changelog links for each plugin</li>
<li>Pending Updates Dashboard – View all pending updates at a glance, color-coded: green for updates that will be applied automatically and red for updates blocked by your policy</li>
<li>Full Multisite / Network Support – Network-wide settings, network admin menu, and proper permission checks</li>
<li>Theme Auto-Updates – Enable or disable automatic updates for all installed themes with a single checkbox</li>
<li>Translation Auto-Updates – Enable or disable automatic updates for all translation files with a single checkbox</li>
<li>Lock Settings – Administrators can lock the settings page to prevent other users from changing the update policy</li>
<li>Custom Admin Email – Send update notifications to any email address, not just the default admin email</li>
<li>Clean Uninstall – All plugin options are cleanly removed from the database on uninstall</li>
<li>Lightweight & Fast – No external API calls, no bloat, fast batch processing</li>
</ul>
How It Works:
The plugin uses semantic versioning (semver) to categorize updates: 
* Major updates (e.g., 3.0.0 → 4.0.0) – Breaking changes, blocked by default 
* Minor updates (e.g., 3.1.0 → 3.2.0) – New features, backwards compatible 
* Patch updates (e.g., 3.1.1 → 3.1.2) – Bug fixes and security patches 
* Hold – Block all updates for a specific plugin
You can configure the plugin to automatically apply only minor and patch updates while requiring manual review for major version changes, ensuring your site stays updated with security fixes while avoiding potentially breaking changes.
How UpdateGuard Protects Your Site:
<ol>
<li>When WordPress checks for updates (every 12 hours), UpdateGuard intercepts the update check.</li>
<li>It compares the installed version with the available version and determines the update level (major, minor, or patch).</li>
<li>If the update level exceeds your configured policy, the update is blocked — both for automatic updates AND for manual/bulk updates from the Plugins page.</li>
<li>Allowed updates proceed normally, and the plugin logs the update with timestamp and version details.</li>
<li>Email notifications are sent to your configured address with a summary of applied, blocked, and pending updates.</li>
</ol>

UpdateGuard – Safe Auto Updates, Semantic Version Control and Update Manager

Control WordPress auto-updates with semantic versioning. Allow minor and patch updates automatically while blocking major releases for safety.

Wiki Blocks vs UpdateGuard – Safe Auto Updates, Semantic Version Control and Update Manager