GitLab

Merge commit 'refs/merge-requests/39' of https://gitorious.org/social/mainline into merge-requests/39

Fixes: ErrorException: [2] array_merge(): Argument #2 is not an array

Empty timelines are no longer warnings, but debug information

Reported on https://bugz.foocorp.net/T79
Fix by MrB: https://gist.github.com/mrvdb/0f5d84c9b56c0a390c4a

Merge commit 'refs/merge-requests/37' of https://gitorious.org/social/mainline into merge-requests/37

Merge commit 'refs/merge-requests/30' of https://gitorious.org/social/mainline into merge-requests/30

Merge commit 'refs/merge-requests/31' of https://gitorious.org/social/mainline into merge-requests/31

Merge commit 'refs/merge-requests/36' of https://gitorious.org/social/mainline into merge-requests/36

The 'created' column in attention SQL table has NOT NULL
restriction.

The 'created' column in ostatus_source SQL table has NOT NULL restriction.
INSERTs fail when running MySQL/MariaDB in strict mode if this is not
populated.

Also made sure we only match local group IDs in recognizedFeed for PushhubAction

Merge commit 'refs/merge-requests/33' of https://gitorious.org/social/mainline into merge-requests/33

Merge commit 'refs/merge-requests/34' of https://gitorious.org/social/mainline into merge-requests/34

Merge commit 'refs/merge-requests/35' of https://gitorious.org/social/mainline into merge-requests/35

There were problems with queries that were executed but didn't seem to
be committed. Trying to patch that up by calling a ROLLBACK on transactions
where the loading of the page isn't stopped after the BEGIN statement's
intended function fails (like with the rememberme cookie in this commit).

Fixes an issue where INSERTs fail if MySQL/MariaDB runs in "strict
mode".

This fixes an issue where INSERTs in HubSub fail if MySQL/MariaDB is
running in "strict mode" since the default lease time in
PushHubAction::subunsub is null.

Permanent subscriptions have been removed in PuSH v0.4, but they are
being kept here for backward-compatibility with previous GS/SN versions.

Apparently True isn't true in javascript. They fiddle around like crazy with
loose typing (causing all kinds of problems) but vars are case sensitive?!

From statusnet to gnusocial.

This goes for both users and groups, since they share nickname namespace.

If you want to enable nickname changes, just add this to your config:

   $config['profile']['changenick'] = true;

This commit should cover all changes in our usual web forms as well as through
the API.

Garbage collecting should also allow to clean up leftover database entries.

singleuser instances shouldn't be too special and have too many
alternative methods of doing stuff.

We should get rid of PEAR::DB and reenable these logs. Upstream
doesn't seem to update.