aboutsummaryrefslogtreecommitdiffstats
path: root/mod/network.php
Commit message (Collapse)AuthorAgeFilesLines
* don't included any deleted posts in the self queryfriendica2015-03-301-1/+1
|
* $simple_update isn't so simple any more. Make sure we don't re-itnroduce the ↵friendica2015-03-221-12/+10
| | | | 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-2/+3
|
* Merge https://github.com/friendica/red into pending_mergefriendica2015-03-211-2/+15
|\
| * fix acl for if we have an cid in /network and make $bang better visibleMario Vavti2015-03-211-2/+15
| |
* | add loadtime search to channel and fix it for home. display and search need ↵friendica2015-03-211-3/+2
|/ | | | further investigation
* some tabs title statuseditor restructuringMario Vavti2015-03-211-10/+23
|
* ok it has to be owner.friendica2015-03-171-3/+3
|
* revert the revert - that is working. My test was bad.friendica2015-03-141-3/+3
|
* revert and rethinkfriendica2015-03-141-3/+3
|
* create terms for Diaspora mention tags - which in Diaspora are handled ↵friendica2015-03-131-6/+6
| | | | differently than other tag links and have to be done separately; they aren't processed by linkify_tags which handles all of our other tag processing. Also move the abook_channel clause in mod_network to the join statement. This works fine in mysql and achievies the desired result. I hope postgres can handle an expression as a join clause.
* fix posts not showing up in network if author is not in connectionszottel2015-03-141-3/+3
|
* use local_channel() connnections to match the abook against when joining the ↵friendica2015-03-131-2/+2
| | | | abook on the discover tab.
* more JS=1 weirdnessfriendica2015-03-121-1/+1
|
* sql optimisation for affinity searches. A new index was added which wasn't ↵friendica2015-03-101-3/+5
| | | | added retro-actively to existing DBs as an update. It isn't clear if this helps sites any more than just restricting the abook table to certain channel_id's is (and this field is already indexed).
* make network page default options work more or less universally instead of ↵friendica2015-03-091-1/+10
| | | | just from the navbar, and fix some saved-search weirdness related to the delete-term icon
* typofriendica2015-02-121-1/+1
|
* provide relief to sites that are severely impacted by the slow ITEM_UNSEEN ↵friendica2015-02-121-5/+2
| | | | 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.
* local_user => local_channelfriendica2015-01-281-17/+17
|
* now that's useful...friendica2015-01-131-2/+8
|
* hide friends broken, add parameter for item search by verbfriendica2015-01-131-0/+1
|
* wall tagsfriendica2014-12-151-15/+25
|
* allow members to set the per-item "show more" height (separately for network ↵friendica2014-11-171-1/+8
| | | | and matrix, display and search are system pages and therefore set at 400)
* add unseen count and way to mark unseen to list mode. Also fix automatic ↵friendica2014-11-171-6/+23
| | | | mark of unseen so as to work with list mode.
* module cleanupfriendica2014-11-161-106/+109
|
* "list mode" (forum and blog mode, no comments or comment boxes displayed on ↵friendica2014-11-161-1/+6
| | | | the summary page)
* PostgreSQL support initial commitHabeas Codice2014-11-131-11/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* better way to deal with effective_uidfriendica2014-09-221-2/+2
|
* make discover items interactivefriendica2014-09-221-1/+1
|
* sql string unquotedfriendica2014-07-221-1/+1
|
* the "page 2 shows up on top of page 1 when you wake up in the morning" bug. ↵friendica2014-07-211-0/+17
| | | | See the comments.
* get rid of some old crapfriendica2014-06-171-57/+4
|
* change the way jot tools are displayed/hiddenmarijus2014-04-081-1/+1
|
* Missed oneThomas Willingham2014-03-301-1/+1
|
* Default discover to on.Thomas Willingham2014-03-301-1/+1
|
* Let the site admin choose whether to display the Discover tab.Alexandre Hannud Abdo2014-03-301-1/+1
|
* firehose fixes and optimisations. In particular get rid of the unresponsive ↵friendica2014-03-271-14/+16
| | | | script warning when trying to load updates (sine they aren't our posts, we can't check for unseen, hence we can't really load updates). Also make the url selection pluggable.
* superfluous commafriendica2014-03-271-2/+1
|
* catch the "new" view as wellfriendica2014-03-261-3/+3
|
* firehose testing (network?f=&fh=1) - some possible security bugs so testing ↵friendica2014-03-261-9/+19
| | | | purposes only
* 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.
* remove a couple of mysql reserved words from being used as table or row ↵friendica2013-12-221-1/+1
| | | | names. For this round we're getting 'group' and 'desc'. Warning: potentially destabilising as this touches a lot of code.
* check that every invocation of htmlspecialchars has the right arg listfriendica2013-12-121-1/+1
|
* The affinity tool is not a "traditional" widget. But it is nevertheless a ↵friendica2013-12-111-25/+0
| | | | 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.
* mod_network is now running under Comanche. Yay.friendica2013-12-101-9/+0
|
* we're almost ready to turn on comanche for mod_network. All the widgets are ↵friendica2013-12-101-107/+24
| | | | done.
* comanchify the savedsearch widgetfriendica2013-12-091-3/+3
|
* notes widgetfriendica2013-12-091-1/+1
|
* suggestion widget tweaked to make it comanche capable. Remove old versions ↵friendica2013-12-081-2/+2
| | | | 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.
* transition to $a->set_widget in /network on the short term - long term this ↵friendica2013-12-081-5/+5
| | | | will be in view/pdl files
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-08 11:47:03 +0000