Michael Ott

In early 2018, the ability to delete logs from the database was <a href="https://wordpress.org/support/topic/latest-update-missing-a-button-to-clear-logs/" rel="ugc">removed</a>. This plugin gives you that control back.
<h3>Support</h3>
<a href="https://wordpress.org/support/plugin/log-cleaner-for-ithemes-security" rel="ugc">Log cleaner for Solid Security Support</a> at the official WordPress repository.
<h3>How to use</h3>
<ul>
<li>Go to Tools -> Solid Security Log Cleaner</li>
<li>Select which logs to delete (or select ‘All’)</li>
<li>Hit the Clear logs button</li>
<li>Get on with the rest of your day (optional)</li>
</ul>
Note: This plugin comes with no warranty of any kind.
<h3>Uninstall</h3>
Deactivate the plugin, delete if desired.

Log cleaner for Solid Security

This plugin does what it says - removes all the old database log entries which are useless when things are running smoothly with a site. Switching to file-only logging also has performance benefits. Use this before you switch to file-only logging. Great job, mate.

my database thanks you

Time saver!


It does what it says and does it very well.


Great!

Restores the ability to manually delete Solid Security logs from the database.

aveltens

The plugin publishes Linked Data about your blog contents and helps you hosting or connecting your WebID.
<h4>Linked Data</h4>
Turtle and RDF/XML documents can be retrieved performing a HTTP GET request with an appropriate HTTP-Accept-Header set. Blog posts and pages are identified by their original document URI appended by the fragment identifier #it.
E.g. if a blog post ist available at http://example.org/2013/04/my-first-blog-post, the post itself (as an “abstract thing”) is identified by http://example.org/2013/04/my-first-blog-post#it
You may use curl to retrieve Linked Data, e.g.:
curl -H ‘Accept: text/turtle’ http://example.org/2013/04/my-first-blog-post#it
An author, as a person, is per default identified by the author page URI appended by the fragment identifier #me.
E.g. if the authors page is http://example.org/author/alice, the person Alice is identified by http://example.org/author/alice#me
You may try curl again, to retrieve a FOAF-Profile:
curl -H ‘Accept: text/turtle’ http://example.org/author/alice#me
Instead of using WordPress to host the FOAF-Profile, you are able to link your existing WebID to your WordPress account. (See next section)
<h4>WebID</h4>
The Plugin adds a WebID section to the user profile screen in the admin backend. (Note: The section is only available, when editing your own profile).
WebID Location
You can choose, where your WebID is hosted:
<ol>
<li>Locally hosted WebID: The WebID is hosted within your wordpress blog at http://[your-domain]/author/[your-username]#me</li>
<li>Custom WebID: You may enter whatever your WebID URI is and your WordPress account will be linked to it.</li>
</ol>
Whatever option you choose, your wordpress account will always be identified as “http://[your-domain]>/author/[your-username]>#account”. The option only affects, how you, as a person, will be identified.
If you do not have a WebID yet, choose the first option, or get a WebID at https://solidcommunity.net. More Information about WebID: http://webid.info/
RSA Public Key
You may enter the exponent and modulus of the public key of your WebID certificate. This will allow you to use your WordPress WebID for authentication elsewhere on the web. The wp-linked-data plugin is not yet capable of creating WebID certificates, so you will have to create the certificate with another tool (e.g. openssl) and enter the data into this section afterwards.
Additional RDF
You may enter any RDF triples as RDF/XML, Turtle or N3. The triples will occur in the RDF representation of your WordPress profile document at at http://[your-domain]/author/[your-username]

wp-linked-data

Publishes blog post & author data as Linked Data.

Log cleaner for Solid Security vs wp-linked-data