gnu-social

History

Alexei Sorokin 9a515b9234 [SCHEMA] Improve timestamp storage Avoid the use of deprecated MariaDB "zero dates" globally. If they're present as attribute defaults somewhere, they will be replaced with NULL implicitly. The existing "zero dates" in MariaDB storage will be left intact and this should not present any issues. The "timestamp" type in table definitions now corresponds to DATETIME in MariaDB with "DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP", which should be close enough to the original behaviour for compatibility purposes. It is now the recommended type for "modified" attributes, because of the update trigger on MariaDB. But there is no such trigger implemented on PostgreSQL as of this moment.		2020-06-29 01:41:46 +03:00
..
actions	[DATABASE] Replace NOW() with CURRENT_TIMESTAMP	2020-06-09 20:26:06 +03:00
classes	[SCHEMA] Improve timestamp storage	2020-06-29 01:41:46 +03:00
forms	[LIB_REFACTOR] Fix requires	2019-09-03 03:33:13 +01:00
locale	[PLUGINS] Removed GeoURL as the service doesn't exist anymore	2019-08-24 01:59:36 +01:00
README	Add plugin READMEs	2016-02-08 17:48:37 +00:00
UserFlagPlugin.php	[CORE] Add GNUSOCIAL_ENGINE_REPO_URL and increase usage of GNUSOCIAL_ENGINE_URL	2019-11-21 00:21:22 +00:00

README

The UserFlag plugin allows flagging of profiles for review and reviewing
flagged profiles.

Installation
============
add "addPlugin('UserFlag');"
to the bottom of your config.php

Settings
========
flagOnBlock: Whether to automatically flag a profile when a user blocks it.

Example
=======
addPlugin('UserFlag', array(
    'flagOnBlock' => true
));