edward_plainview

<p>Activity Monitor tracks all user activity on your blog or network. The activities can be viewed in global table showing activities on the whole network, or locally for just the blog you are currently viewing. The activites can be filtered so that only specific blogs / hooks / IPs / users are displayed.</p>
<p>Monitored actions include (not exhaustive):</p>
<ul>
<li>Comments: approve, held, spam, delete</li>
<li>Custom Post Types:  draft, publish, update, trash, delete</li>
<li>Logins: login, login failed, logout</li>
<li>Pageviews: admin, front-end</li>
<li>Passwords: reset, retrieve</li>
<li>Plugins: activate, deactivate</li>
<li>Pages: draft, publish, update, trash, delete</li>
<li>Posts: draft, publish, update, trash, delete, password</li>
<li>Taxonomies: create, edit, delete</li>
<li>Themes: switched</li>
<li>Updates: WordPress core, plugins, themes</li>
<li>Users: register, delete, profile changes</li>
<li>And more….</li>
</ul>
<p>The logged information consists of:</p>
<ul>
<li>A description of what was logged</li>
<li>Blog</li>
<li>Timestamp</li>
<li>Hook that was triggered</li>
<li>User ID</li>
</ul>
<h4>git</h4>
<p>The <a href="https://bitbucket.org/edward_electric/activity-monitor" rel="nofollow ugc">Activity Monitor has a git repository</a>.</p>
<h4>Security tips</h4>
<p>There are several ways for people to break in to your WordPress installation, or cause trouble by DDOS. Here are some tips on how to use the Activity Monitor and its plugins to help detect problems:</p>
<ul>
<li>Get a DDOS protection service with an API. There is a plugin to ban IPs via CloudFlare (<em>Send To CloudFlare</em>). Other APIs could be supported as the need arises.</li>
<li>If you have another DDOS service, write a script that can ban visitors by IP. Use this script with the <em>Send To Exec</em> plugin.</li>
<li>If you can’t ban users using a script, at least set up the <em>Send To E-mail</em> plugin to inform you of suspicious activity.</li>
<li>Use the Bruteforce Detect plugin to detect when an IP or IPs are trying to guess the admin’s password. Ban the IPs automatically using <em>Send To Exec</em>.</li>
<li>Do not use admin as the username for your administrator account. Instead, use some else and add the admin username to the list of banned usernames in the <em>Login Failed Username</em> plugin. Ban the IPs that cause the plugin to react.</li>
</ul>
<h4>Custom hooks</h4>
<p>See the <a href="https://pvactivitymonitor.com/doc/dev/" rel="nofollow ugc">developer documentation</a> for relevant info on how to create custom hooks.</p>


Plainview Activity Monitor

Real-time monitoring of users, content, functionality, appearance, security, and updates.

D Cartwright

<p>NOTE: THIS PLUGIN REQUIRES WPMU!</p>
<p>This plugin provides simple group wiki functionality within BuddyPress.</p>
<p>A group admin can create a group wiki and corresponding group wiki pages.  Each page has settings (which can override the group privacy settings) to control access to the page both in terms of view access and edit access.  The group also has a shared document library for uploading files.  Page revisions are fully supported, as are revision compares and restores.  Activity stream updates for wiki edits are also created, based on an excerpt of the changed text.</p>
<p>The wiki pages are edited with tinymce for lots of wysiwyg loveliness.  We chose not to implement any kind of edit-lock, but users are warned if other people are editing the page at the same time.  They also receive a more noticable alert should someone else save a page whilst they are editing it.  Finally, after 30 minutes of viewing the wiki edit page, the page is automatically saved and the user is returned to the view screen (given a warning 5 minutes beforehand).</p>
<p>This plugin is licensed under the GNU AGPL.  Use it however you like.  Modify it however you like.  Provide any improvements to the code to the wordpress community for free.</p>
<p>http://www.fsf.org/licensing/licenses/agpl-3.0.html</p>
<p>Technical stuff you might want to know:</p>
<ol>
<li>Each group wiki is actually a wordpress blog in the database.  This was done to take advantage of all the prebuilt WP functions for revisions, file uploads/media libraries/etc.</li>
</ol>
<p>Where to get support:</p>
<p>http://namoo.co.uk</p>
<p>Possible future updates:</p>
<ol>
<li>Global Wiki Directory</li>
<li>Site-wide wiki pages (not tied to a particular group)</li>
<li>Nested pages to allow for better categorisation/namespace type stuff</li>
<li>Improved navigation.  Substitution of top menu nav in groupwiki pages with breadcrumb nav</li>
<li>i18n support</li>
</ol>
<p>Known bugs:</p>
<ol>
<li>Slowness of tinymce to load.  Partially due to use of dev code and bloated plugins and partially due to dodgy implementation</li>
<li>On group deletion, wiki (blog) database tables + files are not deleted</li>
<li>Page edit save warnings (see above) are sometimes troublesome after multiple warnings</li>
</ol>
<h3>Changelog === 1.8 =* Fixed incorrect domain set during blog creation</h3>
<p>= 1.7 =* Fixed some missing js files.= 1.6 =* Fixed a bug with frotend page creation.* Fixed a bug with group wikis being shown in the site blog lists.* Fixed a bug with group wiki creation in wordpress 3.0.= 1.5 =* Fixed a bug which was preventing saving of comments and wiki pages.</p>
<h4>1.4</h4>
<ul>
<li>Massive cleanup of code and comments.</li>
</ul>
<h4>1.3</h4>
<ul>
<li>Some cleanup</li>
</ul>
<h4>1.2</h4>
<ul>
<li>Fixed issue with blog domain/path on wikis.  </li>
</ul>
<h4>1.1</h4>
<ul>
<li>Frontend page creation fixed.</li>
<li>CSS, JS issues fixed.</li>
<li>Some other stuff fixed.</li>
</ul>
<h4>1.0</h4>
<ul>
<li>Initial release.  </li>
<li>Not recommended for production sites.</li>
<li>Please test and provide feedback.</li>
</ul>


BuddyPress Group Wiki

This plugin provides simple group wiki functionality within BuddyPress.  REQUIRES WPMU!

Plainview Activity Monitor vs BuddyPress Group Wiki