wpsnoop: fix Lock a blog plugin conflicts, errors & issues

When the plugin Lock a blog conflicts or throws a PHP error we hope wpsnoop can help you to fix the issue quickly.


Discover which shortcodes wp-options PHP functions database tables and files are created by Lock a blog, plus learn which plugins and/or themes could be in conflict with Lock a blog.


Troubleshooting theme and plugin conflicts is easier when you know what Lock a blog leaves behind after uninstalling it from a WordPress installation, there is a list down below for your convenience.

Expert advice is recommended if you are not technically proficient with PHP, MySQL etc. View support options for Lock a blog

Get professional support for Lock a blog here

When you need professional help with WordPress: get help here


What does Lock a blog version 1.0 add to WordPress? Answers Here.

This is an automatically generated report - it is possible for Lock a blog to perform differently in your installation, previous versions before 1.0 may have created a different set of shortcodes, used different function names or could have created entirely different database tables to store settings and operate. This is not an exhaustive list but shows how version 1.0 of Lock a blog behaves when installed and removed on a clean installation of WordPress.

We have not tested individual shortcodes, features or settings of this plugin but instead have concentrated on the potential for obvious errors and conflicts which can occur, if you need help with the plugin in your local installation you can get WordPress help and support for Lock a blog by clicking here.

Our testing covered the free version of this plugin there may or may not be a paid version or premium version available for purchase that unlocks additional features and could behave in a slightly or very different manner.

Which new files does Lock a blog add to WordPress?

This section will populate with a table showing an icon, size and filepath.

Type & Path Size Conflicts
wp-content/plugins/lockablog/ 65.43kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/changelog.txt 31.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/includes/ 4.60kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/includes/_notes/ 58.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/includes/_notes/dwsync.xml 58.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/includes/lockablog_css.php 219.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/includes/lockablog_filters.php 1.14kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/includes/lockablog_metadata.php 2.72kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/includes/lockablog_templatetags.php 473.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/index.php 2.15kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/pages/ 1.04kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/pages/_notes/ 58.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/pages/_notes/dwsync.xml 58.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/pages/form.php 0.98kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/readme.txt 1.33kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/style/ 5.48kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/style/images/ 5.11kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/style/images/bl.gif 124.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/style/images/br.gif 122.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/style/images/lock-icon.jpg 1.66kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/style/images/lock.png 2.87kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/style/images/nt.gif 55.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/style/images/rounded.php 55.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/style/images/tl.gif 116.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/style/images/tr.gif 116.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/style/style.css 380.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/translation/ 50.81kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/translation/twitme-nl_NL.mo 11.02kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/translation/twitme-nl_NL.po 21.88kB No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/translation/twitme.mo 556.00B No known conflicts with other themes or plugins.
wp-content/plugins/lockablog/translation/twitme.po 17.36kB No known conflicts with other themes or plugins.

Which new shortcodes does Lock a blog add to WordPress?

Which new database tables are created by the WordPress plugin Lock a blog?

Which new options are added to the wp-options table by Lock a blog?

Using Lock a blog from the command line with WP-CLI

The following commands are provided for convenience and should only be used if you understand how WP-CLI works. These commands refer to a single WordPress instance and may need to be modified if you are working with a Multisite installation.


How to install Lock a blog from the command line with WP-CLI

Navigate to the root of your WordPress installation and type the following command:

wp plugin install lockablog


How to activate Lock a blog from the command line with WP-CLI

To immediately activate Lock a blog after WP-CLI downloads the latest version you can use the following command:

wp plugin install lockablog --activate


How to reinstall Lock a blog from the command line with WP-CLI

To force a reinstallation of Lock a blog which overwrites the current plugin without asking for confirmation you can use the following command:

wp plugin install lockablog --force


How to update Lock a blog to the latest version from the command line with WP-CLI

wp plugin update lockablog


How to delete Lock a blog from the command line with WP-CLI

wp plugin delete lockablog

Where can you download earlier versions of Lock a blog?

Whenever possible you should use the latest version of plugins and themes, however if you have recently updated and discovered that you need to install an earlier version you may be able to download other versions of Lock a blog from the WordPress repository by visiting this link.

Please note that installing earlier versions of a theme or plugin is not generally a recommended course of action for most users and could re-introduce security, stability or other issues in Lock a blog

About our testing enviroment

Tests were conducted using Apache 2.4.29, PHP 7.2 on Ubuntu 18.04, MySQL 5.7.33 and WordPress 5.9

It is very possible that different versions of PHP such as PHP 8.0, PHP 7.4, or PHP 7.3 could behave differently with Lock a blog. Different versions of WordPress could implement the features of this plugin in slightly different ways as well.