aboutsummaryrefslogtreecommitdiffstats
path: root/include/widgets.php
Commit message (Collapse)AuthorAgeFilesLines
* PostgreSQL support initial commitHabeas Codice2014-11-131-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* put privacy role selector in settings page. Change visibility of various ↵friendica2014-10-261-5/+8
| | | | permissions items accordingly.
* porting more widgets to bs nav-pillsmarijus2014-10-071-0/+2
|
* channel export with itemsfriendica2014-09-151-5/+5
|
* add collections widget to connections page - and some more work on realmsfriendica2014-08-171-0/+7
|
* don't add a birthday event if the birthday channel doesn't have permission ↵friendica2014-06-031-1/+1
| | | | to send you posts.
* don't provide a second (actually third counting the navbar) search box on ↵friendica2014-06-031-1/+1
| | | | the search page if you've got saved searches turned on. This should solve some problems with duplicate html id's (and save wasn't working anyway). If you don't have saved search ability (which will provide a saved search widget in the sidebar), provide a simple search box in the main content region but without save ability.
* don't show app editing options to non-authenticated folksfriendica2014-06-011-0/+1
|
* more app workfriendica2014-05-211-4/+4
|
* most of the remaining apps basic infrastructure except a form to create the ↵friendica2014-05-201-3/+3
| | | | things. Don't let this fool you - there is still a lot of work, but there isn't a whole lot of work to create a demo; in fact you can demo it now.
* some sidebar content (doesn't yet do anything)friendica2014-05-151-0/+12
|
* xss preventionfriendica2014-05-141-0/+5
|
* add photo widgetfriendica2014-05-131-1/+43
|
* bring the posted-date selector widget up to date. There are no longer two ↵friendica2014-05-011-1/+1
| | | | different styles.
* Better handling of restricted /channel and /profile permissions. We will ↵friendica2014-04-141-0/+12
| | | | show the name, profile photo and a 'connect' button if appropriate on these pages regardless of permissions. A blank page makes it difficult for folks to figure out how to connect and if it is their real life friend 'x' or not. It also matches our overall policy (adopted from Facebook's lessons learned) that the channel name and default profile photo are always visible and can't really be blocked without messing up the usability of the entire network. This also makes sure that a connect button can be found somewhere besides the directory - where the entry could be blocked; and avoid somebody having to figure out the webbie and find the link to "follow" (another related issue).
* provide 'style' option to archive widget to choose between 'select' and ↵friendica2014-03-231-0/+2
| | | | 'list' format
* add clock widget and correct some docofriendica2014-03-051-0/+56
|
* item widget - displays one (webpage) item by mid. This is how you could put ↵friendica2014-03-031-0/+27
| | | | multiple content blobs on a page without turning them all into blocks.
* put schemas in Comanche (this requires theme support (!))friendica2014-02-271-1/+1
|
* minor fixes to suggested chatroomsfriendica2014-02-271-3/+1
|
* chatroom suggestionsfriendica2014-02-271-0/+36
|
* small changes to a couple of lookup functions which we need to use a bit morefriendica2014-02-201-1/+1
|
* whitespacemarijus2014-02-121-3/+0
|
* make chatrooms in /chat/channel visible to observers aswellmarijus2014-02-121-3/+6
|
* chatroom management front-end stufffriendica2014-01-291-1/+2
|
* more testing of chatroom interfaces, also corrected a function call that ↵friendica2014-01-291-0/+3
| | | | should have been a class instantiation in reddav
* chatroom list widget backendfriendica2014-01-291-0/+9
|
* vcard widget needs to include Contact if it's not included from the module ↵Thomas Willingham2014-01-181-0/+1
| | | | that calls it.
* appears that I missed a few files for Comanchification. so here's mitem.friendica2013-12-221-1/+8
|
* split private messages into two modules - "message" is just for message ↵friendica2013-12-211-1/+1
| | | | lists, "mail" is for reading and writing conversations. This is so we can Comanchify it cleanly.
* comanchify mod_directory. Two modules remaining. Actually three because ↵friendica2013-12-201-0/+19
| | | | message needs to be split.
* comanchify connedit, groupfriendica2013-12-191-3/+32
|
* comanchificate mod_photosfriendica2013-12-191-14/+19
|
* more comanchefriendica2013-12-191-0/+4
|
* more comanche migrationfriendica2013-12-191-0/+16
|
* split off mod_connections into mod_connections & mod_connedit - lots of ↵friendica2013-12-181-1/+1
| | | | links to fix
* a couple more comanche conversionsfriendica2013-12-141-0/+132
|
* more htmlspecialchars sanitisationfriendica2013-12-121-2/+2
|
* cmax wasn't defaulting correctlyfriendica2013-12-111-1/+4
|
* The affinity tool is not a "traditional" widget. But it is nevertheless a ↵friendica2013-12-111-0/+26
| | | | widget. It just makes fewer page layout decisions which are hard-coded. If you want to shrink it down and put it on the sidebar in your theme, go for it.
* this makes quotes appear as quotes in notes once page is reloaded. i guess ↵marijus2013-12-111-1/+1
| | | | thats fine since we use escape_tags() in notes.php
* make suggest channels a featuremarijus2013-12-111-1/+4
|
* mod channel is now Comanchifiedfriendica2013-12-101-0/+31
|
* we're almost ready to turn on comanche for mod_network. All the widgets are ↵friendica2013-12-101-1/+66
| | | | done.
* comanchify the savedsearch widgetfriendica2013-12-091-0/+83
|
* turn private notes into a featurefriendica2013-12-091-0/+3
|
* notes widgetfriendica2013-12-091-0/+14
|
* more comanchisation (I declare this to be a word)friendica2013-12-091-0/+13
|
* migrate follow widget to comanche and remove obsolete mod/intro.phpfriendica2013-12-091-1/+30
|
* suggestion widget tweaked to make it comanche capable. Remove old versions ↵friendica2013-12-081-0/+53
| | | | of specs that are so obsolete it isn't funny. Zot protocol reference is in red's github wiki, and in the code. We should move the github copy to /doc once it is updated to match the code. There's no point in documenting dfrn in the red code base.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-20 08:18:09 +0000