aboutsummaryrefslogtreecommitdiffstats
path: root/include/nav.php
Commit message (Collapse)AuthorAgeFilesLines
* uno stuffredmatrix2016-02-051-8/+11
|
* some heavy private mail restructuring - work in progressMario Vavti2015-09-241-4/+4
|
* looks like chat has been neglected a bit recentlyredmatrix2015-09-201-3/+2
|
* change matrix to grid, begin webfinger optimisationredmatrix2015-09-161-2/+2
|
* more work on db storage of docoredmatrix2015-07-051-2/+2
|
* DB changes for some channel flagsredmatrix2015-06-151-7/+2
|
* adjust icon sizeMario Vavti2015-05-071-1/+1
|
* whitespacefriendica2015-03-091-2/+1
|
* make network page default options work more or less universally instead of ↵friendica2015-03-091-2/+1
| | | | just from the navbar, and fix some saved-search weirdness related to the delete-term icon
* remote_user => remote_channelfriendica2015-01-281-2/+2
|
* local_user => local_channelfriendica2015-01-281-11/+11
|
* Make nav search use textcompleteStefan Parviainen2015-01-071-9/+1
|
* Add hint on how to use search boxStefan Parviainen2014-12-141-0/+1
|
* Add some ids to nav elementsStefan Parviainen2014-12-121-27/+27
|
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-131-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | 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
| * Use consistent terminology for channel directoryStefan Parviainen2014-11-091-1/+1
| |
* | PostgreSQL support initial commitHabeas Codice2014-11-131-1/+1
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* merge madnessfriendica2014-10-191-1/+1
|
* Login menuStefan Parviainen2014-10-161-6/+5
|
* fix userinfo icon sizemarijus2014-10-091-1/+1
|
* network page default optionfriendica2014-10-041-1/+4
|
* implement a "powered-by" but leave it turned off until somebody with a good ↵friendica2014-09-291-0/+7
| | | | eye for layout can figure out where best to put it.
* Navbar notifications: don't show "nothing new here" unless we've checked and ↵friendica2014-09-201-1/+1
| | | | there's nothing. Until we know for sure, display "Loading...".
* aalso change the way we check for number of chatroomsmarijus2014-09-201-2/+2
|
* show bookmarks menu only if we have any bookmarks alreadymarijus2014-09-201-2/+7
|
* nav channel selectionfriendica2014-08-181-1/+14
|
* always provide a profile edit entry in the nav usermenufriendica2014-07-241-0/+7
|
* whitespacemarijus2014-06-141-2/+0
|
* unclutter menues a littlemarijus2014-06-141-3/+9
|
* change app dropdown to point to apps module (changes nav template). ↵friendica2014-05-211-3/+2
| | | | Important: Plugins using the app-menu hook will no longer be accessible from there and may require re-writing to plug into the system apps page. Also filter apps in items from the language detector to avoid false triggers from the base64 content.
* finish "ifpending" connectionsfriendica2014-04-041-1/+1
|
* introduce a connection type called 'ifpending' for number 6 of issue #395 - ↵friendica2014-04-041-1/+1
| | | | so that we can still have an unconditional 'pending' link. Needs testing before integrating with the nav menu
* move language selector to a modulefriendica2014-03-051-1/+0
|
* revert the temporary fix for the missing hdr.tpl and add the ability to ↵friendica2014-03-031-1/+1
| | | | provide context sensitive help/documentation by passing the current URL path to the help module as $_REQUEST['cmd']. So we could create a special help page for settings/display or whatever. The only issue is whether this should be presented first with a link to the main help page, or if we put a line at the top of the main help page that says "I need help for settings/display". Also edited the help target window name, as "friendika-help" is a bit dated.
* add choklet template with several defined flavours, two and three column ↵friendica2014-03-021-17/+22
| | | | fluid layouts with optional side margins and a region for a blog-style header photo
* use the medium size photo on the nav bar if that photo stays larger, as the ↵friendica2014-02-201-1/+1
| | | | small one usually looks awful when you scale it up.
* extend the usermenu so we don't have to keep going back to channel homepage ↵friendica2014-02-061-3/+7
| | | | to get to the other channel links
* 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.
* use sitename for the banner if nothing else has been setfriendica2013-12-141-1/+1
|
* yeah - that's what I'm going to do. we'll just keep system notifications. If ↵friendica2013-12-061-3/+0
| | | | somebody wants web pages for the others we'll start fresh. It's easier than starting with curfty friendica code that doesn't work anymore and will never work without starting over.
* some code cleanup - gad I forgot what a mess the "other" notifications tabs ↵friendica2013-12-061-1/+1
| | | | (everything but system) were in. Maybe I'll just remove them so we can start over.
* allow themes to mess with the navbar contents without a custom template. ↵friendica2013-11-281-2/+5
| | | | | | | | | | | | It's done as a callback using a transient plugin hook. For instance to get rid of the notifications link: insert_hook('nav','strip_notify'); function strip_notify($a,&$b) { unset($b['nav']['notifications']); }
* make autocomplete better themable by adding an idmarijus2013-11-141-0/+1
|
* more redbasic icon workfriendica2013-10-091-4/+8
|
* nav iconsfriendica2013-10-091-2/+2
|
* Changed CSS class "selected" to "active" in navbar, according to ↵Olivier Migeot2013-09-181-1/+1
| | | | https://abcentric.net/display/f17b319c6d4b616a0d0a639e177969c6ae084248f1ee2bec9d8147c9291bf495@abcentric.net
* make displaying the language selector configurablefriendica2013-09-031-1/+1
|
* make home link on remote sites work againmarijus2013-07-181-2/+4
|
* more cleanupfriendica2013-04-141-1/+0
|
* just tinkering and trying a few things - don't get upset. It can all be ↵friendica2013-03-051-8/+8
| | | | reverted it it sucks. Freedom's just another word for "nothin' left to lose" and I'm not sure it's possible to create a UI that's hated more than Friendica. So that gives us plenty of artististic license to explore some different directions and see if they lead to anything interesting.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 03:47:15 +0000