aboutsummaryrefslogtreecommitdiffstats
path: root/mod/admin.php
Commit message (Collapse)AuthorAgeFilesLines
* put mirror_frontpage setting into admin/siteredmatrix2015-06-091-0/+3
|
* more frontpage tweaksredmatrix2015-06-071-2/+2
|
* reverse logic of homepage login settingredmatrix2015-06-071-3/+6
|
* frontpage tweaksredmatrix2015-06-071-0/+3
|
* add toggle for ALLOWCODE to admin/channel and also fix the ability to toggle ↵redmatrix2015-05-251-5/+37
| | | | the censor flag from that page.
* more work isolating the projectname from core.redmatrix2015-05-171-1/+1
|
* Correcting reported Doxygen syntax warnings.Klaus Weidenbach2015-03-291-37/+37
| | | | | | | Fixed wrong Doxygen syntax and add some of the available FIXME to Doxygen documentation. Updated Doxygen configuration to add also all capital letter tags. Adding some more Doxygen documentation.
* improve description of that settingfriendica2015-03-251-1/+1
|
* admin config for default expirationfriendica2015-03-251-9/+12
|
* cleanup of old delegation stufffriendica2015-03-101-2/+2
|
* channel delegationfriendica2015-03-101-2/+3
|
* more work on queue optimisationsfriendica2015-03-091-1/+2
|
* Whoops... should've actually checked the pg manual before merging #920 :-)Habeas Codice2015-03-091-2/+2
| | | | | replace if(cond,val,val) with case when cond then val else val end, works on both DBs
* Fixing (un)blocking accounts in /admin/users.Klaus Weidenbach2015-03-081-34/+61
| | | | | | When I look at the instructions in sql_conventions about setting bit flags I don't understand how this could have worked before. Changed the behavior for (un)blocking so that it should work now.
* Add alert to admin page about old PHP version.Klaus Weidenbach2015-03-081-296/+282
| | | | | | | | | | | | Add an alert message to admin summary page when a PHP version < 5.4 was detected as this has reached EOL and will not be supported with the new SabreDAV library. Some styleguide optimisation. Add NULL_DATE example to doc/sql_conventions.bb. Display a "0" when no plugins active in summary page. Added some more numbers to summary admin page, expired accounts, channels. Hope I interpreted them right. I have no idea how to get blocked accounts.
* make destructive queue management functions an expert optionfriendica2015-03-051-1/+4
|
* remove broken sql query from early queue manager.friendica2015-03-041-3/+0
|
* queue management actions. Still needs further work such as indication of ↵friendica2015-03-011-8/+31
| | | | last successful connection or indication that the hub was marked offline, but these are potentially expensive queries.
* don't report already delivered queue items in admin queue summaryfriendica2015-02-261-1/+1
|
* high level queue inspector - needs a lot more, like the ability to dump ↵friendica2015-02-261-1/+25
| | | | certain destinations and indicating known dead sites, but this is a start
* solve some (hopefully most) missing delivery issuesfriendica2015-02-251-1/+1
|
* admin/dbsync not reporting failed updatesfriendica2015-02-011-1/+1
|
* Add allowed and not allowed emails to the UI in theChristian Vogeley2015-01-291-0/+3
| | | | admin menu
* local_user => local_channelfriendica2015-01-281-1/+1
|
* Allow tags in mail, many profile fields, and admin infoStefan Parviainen2015-01-131-0/+2
|
* don't allow admin to delete the sys channel from the channel manage pagefriendica2015-01-061-2/+2
|
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-131-28/+25
|\ | | | | | | | | | | | | | | | | | | | | | | Conflicts: boot.php include/dba/dba_driver.php include/diaspora.php include/follow.php include/session.php include/zot.php mod/photos.php mod/ping.php
| * Add a new theme flag - library. Not directly available to be used itself butThomas Willingham2014-11-101-28/+25
| | | | | | | | | | | | | | | | | | | | | | | | installed as a lib for other themes. Like SDL, or GTK. Get rid of mobility - it's better done with Comanche and schemas. Describe themes instead of restricting them. Mobile themes can be used as the desktop theme and vice-versa. This deals with the problem of "but my device is something inbetween". Presently not exposed to members.
* | PostgreSQL support initial commitHabeas Codice2014-11-131-18/+19
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* Allow ordering by createdChristian Vogeley2014-09-201-1/+3
|
* push individual block to directoryfriendica2014-09-151-0/+1
|
* fat finger - must have been here a whilefriendica2014-09-151-1/+1
|
* Deprecate site channel. The sys channel should be doing this. Will fixThomas Willingham2014-09-151-3/+3
| | | | shortly.
* make verify_email the default for new installs (at least English installs), ↵friendica2014-09-101-1/+3
| | | | and provide a setting on the admin page for it.
* implement service class for feed polling frequenecy, fixed a service class ↵friendica2014-09-031-2/+0
| | | | bug, moved service class stuff from plugin to account.php where it belongs and load that by default instead of on demand
* consistency: the diaspora post plugin uses "diaspora_enable". The protocol ↵friendica2014-08-281-3/+3
| | | | driver uses "diaspora_enabled" with a 'd'. They got mixed up in a couple of places.
* begin embeddable/shareable design elements (blocks, webpages, layouts, ↵friendica2014-08-271-1/+1
| | | | menus, etc.)
* ability to create/edit/delete custom profile field definitions - read the ↵friendica2014-08-271-0/+63
| | | | source. Currently the created entries aren't added to the allowed fields arrays, but this can be done by hand until that bit is made available. Only choice for input type at the moment is 'text' or a text input, not a textarea. Multiple choice will be added later.
* Admin setting for Diaspora Protocol enable. We may want to have this also at ↵friendica2014-08-271-0/+3
| | | | a channel level since there are privacy issues and quirks and trade-offs.
* provide admin option for allowing rss/atom feed connections. Need to do this ↵friendica2014-08-201-45/+5
| | | | now before the feature is complete so that public sites don't get borked. We also will need a service class for this.
* Account deletionChristian Vogeley2014-08-151-1/+1
| | | | fix multi user deletion, add confirmation message
* Merge pull request #561 from cvogeley/masterRedMatrix2014-08-151-1/+1
|\ | | | | Some work on account deletion
| * Some work on account deletionChristian Vogeley2014-08-141-1/+1
| |
* | some work on extended profile fieldsfriendica2014-08-131-0/+23
|/
* when an admin censors a channel, we only need to notify the directory and ↵friendica2014-06-221-0/+1
| | | | not all the connections.
* make maximum load average setting work againmarijus2014-06-161-0/+1
|
* Attempt to reduce the support burden of access and register policy.Thomas Willingham2014-04-211-9/+9
|
* Hope I have repaired the channel admin page.sasiflo2014-04-061-47/+34
| | | | | | | | | | Channel blocking and deleting was copied from user actions. This was not done to an end. Hope what I do is enough to enable channel blocking and deleting the correct way. On deletion all entities that belong to the channel are deleted. But the channel itself is just marked as deleted. Do not really understand why it is done this way.
* removed default maximagesize - it can be set in the admin pages.friendica2014-04-021-1/+1
|
* Default discover to on.Thomas Willingham2014-03-301-3/+3
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 09:34:12 +0000