aboutsummaryrefslogtreecommitdiffstats
path: root/mod/channel.php
Commit message (Collapse)AuthorAgeFilesLines
* $simple_update isn't so simple any more. Make sure we don't re-itnroduce the ↵friendica2015-03-221-1/+1
| | | | bug that session['loadtime'] was created to fix. It's questionable whether we still need to even look for item_unseen but I won't make that call today. We can also eliminate the restriction on not doing live updates from the discover tab since we aren't relying completely on item_unseen (which can only be set by the owner and won't work on a page with virtual owners).
* provide visual feedback when deleting a like by liking it again.friendica2015-03-221-3/+2
|
* add loadtime search to channel and fix it for home. display and search need ↵friendica2015-03-211-2/+19
| | | | further investigation
* make the channel item query match recent changes to network item query (and ↵friendica2015-03-181-3/+5
| | | | some slightly older changes in display item query), and allow '@' in linkified urls.
* openid cleanupfriendica2015-03-161-1/+1
|
* mod_id: load profile so the sidebar profile will workfriendica2015-03-151-0/+5
|
* show item title in channel/mid and display pageszottel2015-02-201-1/+4
|
* provide relief to sites that are severely impacted by the slow ITEM_UNSEEN ↵friendica2015-02-121-9/+5
| | | | 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-6/+6
|
* hide friends broken, add parameter for item search by verbfriendica2015-01-131-0/+1
|
* add Thomas's Diaspora repair script as include/fixd.php - altered so it can ↵friendica2014-12-161-5/+4
| | | | | | be re-run if necessary with a count of remaining hublocs to be fixed. Some sites are down so it probably can't ever get to zero. The check for a null join is quite an expensive query. It could block your DB for a couple minutes while it runs. Also some preliminary work on a means to take the channel module out of list/forum mode if a specific mid is requested.
* wall tagsfriendica2014-12-151-0/+5
|
* allow members to set the per-item "show more" height (separately for network ↵friendica2014-11-171-1/+6
| | | | and matrix, display and search are system pages and therefore set at 400)
* fix the update_unseen stuff on the channel page alsofriendica2014-11-171-8/+26
|
* "list mode" (forum and blog mode, no comments or comment boxes displayed on ↵friendica2014-11-161-1/+7
| | | | the summary page)
* PostgreSQL support initial commitHabeas Codice2014-11-131-9/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* wrong template loaded issuefriendica2014-10-201-1/+1
|
* via Mario: default channel permissions not working on channel pagefriendica2014-04-111-6/+11
|
* change the way jot tools are displayed/hiddenmarijus2014-04-081-1/+1
|
* add fh to other page templatesfriendica2014-03-271-0/+1
|
* remove debuggingfriendica2014-01-211-1/+0
|
* fix location of string file in Translations.md, fix some permissions and ↵friendica2014-01-211-0/+1
| | | | owner vagueness (potential bugs) in profile_tabs()
* when loading a single thread on the channel page, tell JS that there isn't ↵friendica2014-01-201-2/+6
| | | | any more content to load.
* and don't send duplicate notices <sigh>zottel2014-01-101-3/+0
|
* add security fix to load case, toozottel2014-01-101-3/+9
|
* security fix for channel?mid= per zottelfriendica2014-01-101-2/+4
|
* some minor cleanup on plinks for some very subtle permissions issuesfriendica2014-01-091-20/+4
|
* fix noticeszottel2014-01-091-7/+12
|
* took out some left-overs from the debugging phasezottel2014-01-091-12/+0
|
* fix a bug that made it possible for everyone to access any message from otherzottel2014-01-091-0/+26
| | | | channels using channel/<channel>/?mid=...
* Merge pull request #258 from zzottel/masterfriendica2014-01-081-28/+48
|\ | | | | Add display of a thread to channel module
| * Add display of a thread to channel module using channel/<channel>/?mid=<mid>zottel2014-01-081-28/+48
| |
* | 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.
* mod channel is now Comanchifiedfriendica2013-12-101-24/+0
|
* enable JS-less display of channelzottel2013-12-091-3/+7
|
* include re-organisation and more doco, post_to_red fix ampersands in categoriesfriendica2013-12-041-22/+9
|
* quite a bit of work on default acl permissions and various acl quirksfriendica2013-11-291-1/+8
|
* If an observer doesn't have view_stream perms, try for view_profile beforeThomas Willingham2013-10-041-0/+5
| | | | giving up.
* Upstream mergeChristian Vogeley2013-09-151-3/+2
|\
| * make /channel respect "Maximum number of conversations to load at any time" ↵marijus2013-09-101-3/+2
| | | | | | | | setting like /network does.
* | Search by dateChristian Vogeley2013-09-151-11/+12
|/ | | | Search by date (archive) works a bit now
* filter by category fixesMichael Johnston2013-09-061-1/+4
|
* $yoursite/~foo has taken you to foo's channel page for ages. If you're ↵friendica2013-08-041-3/+10
| | | | logged in locally, $yoursite/~ will now take you to *your* channel page. If you aren't logged in, it won't.
* tag cloud tweaking - allow your own comments, disallow all private postsfriendica2013-07-031-1/+1
|
* This probably needs some configurable options, but let's only show tags from ↵friendica2013-07-021-1/+1
| | | | your top-level posts in your personal tag cloud to prevent your commenters from tag spamming you and featuring their tags on your wall. It would be bad if somebody was able to make #penis_enlargement *your* personal top tag. We can do something different for the matrix, as it can't be seen by outsiders.
* oops - returned too many itemsfriendica2013-07-021-1/+1
|
* tag cloud feature (enable the feature, then it will show up on your channel ↵friendica2013-07-021-0/+3
| | | | page)
* fix location setting stufffriendica2013-05-281-3/+2
|
* Updated build_query for midThomas Willingham2013-03-251-1/+1
|