aboutsummaryrefslogtreecommitdiffstats
path: root/mod/display.php
Commit message (Collapse)AuthorAgeFilesLines
* revertMario Vavti2015-07-091-2/+2
| | | | do not show status editor in /display - we most probably want to read the thread or comment.
* do not show status editor in /display - we most probably want to read the ↵Mario Vavti2015-07-091-1/+2
| | | | thread or comment.
* add loadtime search to channel and fix it for home. display and search need ↵friendica2015-03-211-0/+13
| | | | further investigation
* correct indentzottel2015-02-201-2/+2
|
* show item title in channel/mid and display pageszottel2015-02-201-0/+3
|
* provide relief to sites that are severely impacted by the slow ITEM_UNSEEN ↵friendica2015-02-121-4/+1
| | | | searches. This does not incorporate any other flag optimisations as that will require a major DB update and possibly involve significant downtime. This is just to bite off a little chunk now and provide some much needed relief.
* remote_user => remote_channelfriendica2015-01-281-1/+1
|
* local_user => local_channelfriendica2015-01-281-7/+7
|
* hide friends broken, add parameter for item search by verbfriendica2015-01-131-0/+1
|
* incorrect check for sys ownershipfriendica2014-12-191-4/+5
|
* wall tagsfriendica2014-12-151-0/+1
|
* PostgreSQL support initial commitHabeas Codice2014-11-131-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* repeated content collapse on update from display page under rare conditions ↵friendica2014-09-181-0/+2
| | | | (when the conversation hasn't changed)
* honour sys channel permissions for who can view the sys owned contentfriendica2014-07-261-2/+11
|
* cleanupfriendica2014-06-191-1/+1
|
* only show jotnets when posting conversation itemsfriendica2014-06-141-1/+1
|
* issue #433friendica2014-06-101-0/+1
|
* add sys channel (discover) posts to "anonymous" search. They will by default ↵friendica2014-06-031-2/+7
| | | | be public.
* mod_display: match "message_id begins with xxxx" as well as "message_id = xxxx"friendica2014-05-221-3/+3
|
* change the way jot tools are displayed/hiddenmarijus2014-04-081-1/+1
|
* add fh to other page templatesfriendica2014-03-271-0/+1
|
* preparatory work for supporting a "list view" mode for conversations. This ↵friendica2014-01-081-0/+1
| | | | would be useful for forum-like channels and/or block-oriented themes.
* JS-less displayzottel2013-12-171-4/+7
|
* quite a bit of work on default acl permissions and various acl quirksfriendica2013-11-291-1/+9
|
* mod_display - if we are given the mid of a webpage, redirect to that ↵friendica2013-10-281-1/+19
| | | | webpage. This lets us include webpages in searches and 'view in context' will do the right thing.
* doc - complete hook list, still need detailed functional descriptions with ↵friendica2013-10-181-1/+1
| | | | parameters and examples for each
* Put a status editor on the display page if you're logged in. This fixes ↵friendica2013-10-181-0/+23
| | | | issue #113 and also provides the ability to reshare from that page.
* turn off endless scroll if we have no more content to load - currently for ↵friendica2013-10-131-0/+2
| | | | mod_display, need to add to other content modules
* one more edge case in the public perms - don't match perms = 0 which is ↵friendica2013-09-221-3/+3
| | | | private, this and prior checkin are for issue #114
* fixes for display and search privacy enforcementfriendica2013-09-221-1/+3
|
* remove old debugging cruftfriendica2013-09-101-1/+1
|
* encode and decode channel names containing HTML special characters and ↵friendica2013-09-061-3/+3
| | | | quotes so they will survive a reshare without mangling
* fix mod-display when not logged in.friendica2013-06-181-2/+2
|
* odds and ends in prepearation for photo abstraction, plus red-to-friendica addonfriendica2013-04-251-0/+15
|
* Updated build_query for midThomas Willingham2013-03-251-5/+3
|
* fix mod_display breakage.friendica2013-03-241-2/+9
|
* rename 'uri' (and parent_uri) to 'mid' (and parent_mid) since these no ↵friendica2013-03-211-9/+9
| | | | longer remotely resemble uri's and are actually message_id's. This change is potentially destabilising because it touches a lot of code and structure. But it has to get done and there's no better time than the present.
* improve mod/display for local users - use their own copy if possiblefriendica2013-03-021-11/+23
|
* progress on tag deliveryfriendica2013-02-111-1/+1
|
* taming the wild mod_displayfriendica2013-02-101-7/+4
|
* progress on mod/display - slow but any progress is goodfriendica2013-02-101-24/+9
|
* mod_display - no fun. Not working at all. But a bit of progress.friendica2013-02-101-100/+96
|
* bring back selective "mark unseen" on network page now that we can mark all ↵friendica2013-02-031-2/+0
| | | | unseen
* implement Smarty3Zach Prezkuta2013-01-061-1/+2
|
* mod_display - now barely functional but that's a lot better than being ↵friendica2012-12-201-43/+51
| | | | totally buggered.
* there are now 2 permalinks - one is the remote original post (plink) and the ↵friendica2012-12-161-0/+2
| | | | other is a pointer to a local copy (llink). mod_display is not longer tied to a particular id or channel so if a message is publicly viewable it will appear without any ownership info.
* that was certainly some fun debugging (not)friendica2012-11-041-1/+1
|
* this one is going to be hardfriendica2012-10-231-43/+69
|
* wall posts now display - address book structure revamp startedfriendica2012-10-101-5/+1
|
* updatesfriendica2012-09-091-2/+12
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-11 14:44:41 +0000