aboutsummaryrefslogtreecommitdiffstats
path: root/mod/manage.php
Commit message (Collapse)AuthorAgeFilesLines
* working through the xchan table to remove bitfields, mostly complete except ↵friendica2015-01-201-3/+2
| | | | for updating the updater
* Merge remote-tracking branch 'upstream/master'Christian Vogeley2015-01-111-7/+11
|\ | | | | | | | | | | Conflicts: doc/html/classRedmatrix_1_1Import_1_1Import-members.html doc/html/classRedmatrix_1_1Import_1_1Import.js
| * Don't show current channel separately in channel manager, highlight it insteadStefan Parviainen2014-12-291-5/+2
| |
| * Allow quick access to mail and connections from Channel ManagerStefan Parviainen2014-12-271-2/+7
| |
| * Fix #771, add tooltips to mail and intros count in channel manager, always ↵Stefan Parviainen2014-12-271-1/+3
| | | | | | | | show counts (even when 0, makes it easier to understand what the icons are)
* | Fix for issue #763 Error creating new channel within the limits of theChristian Vogeley2015-01-111-1/+1
|/ | | | subscription plan
* PostgreSQL support initial commitHabeas Codice2014-11-131-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There were 11 main types of changes: - UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just copied from Friendica. All of these instances, the LIMIT 1 was simply removed. - Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice to boot). Proper explicit boolean conversions were added. New queries should use proper conventions. - MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_ func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There were no true toggles (XOR). New queries should refrain from using XOR when not necessary. - There are several fields which the schema has marked as NOT NULL, but the inserts don't specify them. The reason this works is because mysql totally ignores the constraint and adds an empty text default automatically. Again, non-compliant, obviously. In these cases a default of empty text was added. - Several statements rely on a non-standard MySQL feature (http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run a zillion times faster, even on MySQL. - A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG, UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_ - INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes around the value -- assist functions added in the dba_ - NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are handled in Zot/item packets automagically by quoting all dates with dbescdate(). - char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype for all text fields in the postgres schema. varchar was used in a couple of places where it actually seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code actually validates data, new bugs might come out from under the rug. - postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted. bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function was added to handle this transparently. - postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax. Statements were updated to be standard. These changes require corresponding changes in the coding standards. Please review those before adding any code going forward. Still on my TODO list: - remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting - Rewrite search queries for better results (both MySQL and Postgres)
* add some notification counts to the structure passed to the "channel select" ↵friendica2014-08-031-1/+72
| | | | template (mod/manage). All it takes is to create an appropriate template to turn this page into a list with tallies of various notifications attached to each channel.
* don't include deleted channels in number of channels service class checksfriendica2014-02-161-2/+3
|
* removeme sort of works for a single channel - lots of loose ends to deal ↵friendica2013-11-121-2/+3
| | | | with but it's a start
* usage message showed wrong number of channelsChristian Vogeley2013-09-091-1/+1
|
* Service classChristian Vogeley2013-09-081-0/+12
| | | | identity, follow, photo upload, att upload
* fix default channelfriendica2012-11-021-8/+13
|
* settings page channel permissions front-end (needs back-end still)friendica2012-11-011-1/+1
|
* add current selection to channel managerfriendica2012-11-011-2/+10
|
* cleanup channel managementfriendica2012-11-011-4/+17
|
* fix channel creation and management after last changesfriendica2012-10-301-2/+1
|
* zchannel rename to new_channelfriendica2012-10-291-1/+1
|
* Can't see any posts currently - after the big shakeup, but we can now post ↵friendica2012-10-031-2/+2
| | | | top level activities and store them.
* use hash for channel idfriendica2012-10-011-12/+6
|
* moving a lot of structure around. 'entity' is now 'channel'friendica2012-09-251-11/+11
|
* fix the navfriendica2012-09-021-84/+7
|
* channel/identity selection manage pagefriendica2012-09-021-7/+31
|
* begin channel management (was "manage") page, use term "channel" instead of ↵friendica2012-08-301-17/+14
| | | | the vague and hard to explain "identity"
* one-click change for manage modulefriendica2012-06-121-2/+3
|
* Merge branch 'master' of https://github.com/friendica/friendicaAlexander Kampmann2012-04-051-0/+0
| | | | | | Conflicts: include/config.php update.php
* basic ssl_policy for important modulesfriendica2012-03-141-1/+1
|
* backend for delegating forumsfriendica2012-01-261-18/+52
|
* add remove_user hook (it looks like dreamhost changed all my file ↵friendica2012-01-181-0/+0
| | | | permissions, this will make a nasty commit)
* manage also needs the new authenticate_success functionfriendica2012-01-121-34/+3
|
* add info() function. Works like notice() but show messages in a div with ↵Fabio Comuni2011-05-231-2/+2
| | | | | | | class info-message. update code to use info() instead of notice() when appropriate (non-error message) add info-message class style in themes
* Fix spaces around t() and tt()fabrixxm2011-03-131-1/+1
|
* update source stringsfabrixxm2011-03-111-1/+1
|
* add manage fileFriendika2011-03-011-0/+110
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-24 23:25:20 +0000