aboutsummaryrefslogtreecommitdiffstats
path: root/include/text.php
Commit message (Collapse)AuthorAgeFilesLines
* fix double encoding of homepage in profile activity - not as ↵friendica2014-12-211-0/+1
| | | | straight-forward as it looked
* Access list of smilies over JSONStefan Parviainen2014-12-201-31/+38
|
* allow a variety of latitude/longitude delimiters since nobody can agree on them.friendica2014-12-171-1/+3
|
* ability to generate arbitrary map with [ map=lat/lon] and also free form ↵friendica2014-12-171-0/+6
| | | | location using [ map]somewhere[/map] but the second one currently has no plugins available to generate it.
* Add [ map ] element to bbcode, no closing tag. Requires a map generator ↵friendica2014-12-161-0/+14
| | | | plugin (like openstreetmap which was just updated) and also requires that the author has browser location enabled.
* Add security logger to RedDAV.Klaus Weidenbach2014-12-141-216/+193
| | | | Some smaller clean ups whitepsaces and tabs, use PHP_EOL, Doxygen, etc.
* Show tags in other channels profile field to make it easier to navigate to ↵Stefan Parviainen2014-12-071-0/+256
| | | | the channels
* new system config reserved_channelsHabeas Codice2014-11-211-1/+6
| | | | prevents members from creating channels in a reserved list
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-131-2/+20
|\ | | | | | | | | | | | | | | | | | | | | | | 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
| * cleanupfriendica2014-11-111-0/+3
| |
| * slow progress on sys publishing, making sure all the data we need is in the ↵friendica2014-11-111-1/+1
| | | | | | | | places we need it but validate it anyway
| * a couple of places where we need to look for a sys channel euid.friendica2014-11-111-0/+7
| |
| * and urlencode that.friendica2014-11-111-2/+2
| |
| * Most directory searches are POST. get_query_args() only handles GET so that ↵friendica2014-11-111-1/+9
| | | | | | | | had to be fixed or page 2 of directory search results wouldn't match the search.
* | PostgreSQL support initial commitHabeas Codice2014-11-131-7/+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)
* Don't recognise hashtags starting with #, e.g. ###friendica2014-10-151-2/+2
|
* template for searchbox and some more work on saved searchesmarijus2014-10-081-19/+17
|
* trying to call mod/magic on rss resources - which have no hubfriendica2014-09-221-1/+5
|
* better way to deal with effective_uidfriendica2014-09-221-1/+9
|
* prevent red#matrix smilie replacements from tripping over each other.friendica2014-09-081-2/+3
|
* extra_query_args() restricted to $_GET only. $_REQUEST was adding cookies ↵friendica2014-09-061-4/+5
| | | | and this is undesired and potentially a security issue.
* ajax workfriendica2014-09-061-0/+14
|
* improved logging if you're using php54 or laterfriendica2014-09-041-2/+8
|
* various rss fixesfriendica2014-08-311-0/+5
|
* Revert - see comments.Thomas Willingham2014-08-261-3/+3
|
* HTML doesn't work without ACCOUNT_ROLE_ALLOWCODE, so don't offer itThomas Willingham2014-08-261-2/+3
| | | | as an option.
* profile edit - missing visibility and drop link on non-default profiles, ↵friendica2014-08-211-4/+4
| | | | re-arrange order of replacing red#matrix smilie so it works correctly, accept a post with body content of '0' which was interpreted by x() as nothing (was treated as integer).
* provide an overt indication that a post/comment was edited.friendica2014-08-181-2/+4
|
* don't subdue archived connections in viewconnectionsfriendica2014-07-161-2/+3
|
* subdue archived connections in group editor and don't show at all in ↵friendica2014-07-161-2/+2
| | | | contact_block()
* rename friendica_smartyfriendica2014-07-131-1/+1
|
* added A NAME/ID to whitelist in HTMLpurifier. That means we can now make ↵jeroenpraat2014-07-111-0/+1
| | | | vintage indexes in web pages.
* for non-post items (e.g. photos, events, whatever) add mention tags ↵friendica2014-06-301-0/+25
| | | | explicitly to the output rendering since they may not be present in the post body.
* use consistent capitalisation in the item actions menufriendica2014-05-291-1/+1
|
* fix search to use in appfriendica2014-05-221-2/+2
|
* show hidden connections in contact block if and only if the observer is the ↵friendica2014-05-081-4/+14
| | | | profile owner
* Unfortunate omissionfriendica2014-04-261-3/+1
|
* better mapping of visible connectionsfriendica2014-04-141-8/+6
|
* remove extra tag loggingfriendica2014-04-121-1/+1
|
* don't match quote remnantsfriendica2014-04-121-1/+5
|
* let normal hashtags be quoted strings alsofriendica2014-04-121-1/+12
|
* convert /network saved search to bootstrap buttonsfriendica2014-04-071-2/+2
|
* check_webbie (webbie validator) returning bad webbiesfriendica2014-04-061-2/+4
|
* community tags don't show up in the tagged posts because we removed the ↵friendica2014-03-311-0/+30
| | | | displayed list of hashtags at the bottom (which are usually redundant since hashtags are usually present in the message text). This brings them back, but only for tags which aren't currently present in the message body (e.g. community tags)
* issue #378, failure to correctly link tags where one tag contains a ↵friendica2014-03-301-1/+17
| | | | substring of the other (depends on the order they are discovered).
* little fixes of hopefully nil significancefriendica2014-03-161-0/+5
|
* contact_block() not being shown to unauthenticated visitors - even if perms ↵friendica2014-03-131-0/+6
| | | | allow. Also separate the permissions logic for this function so that we can have a mini-profile widget and a separate contact_block widget instead of always lumping them together. We probably also should move contact_block() outside of include/text.php as it doesn't really belong there. Just not sure where it belongs - perhaps contact_widgets wouold be a good place.
* some anomolies found when viewing connections in various cases.friendica2014-03-021-3/+9
|
* fix zrl bookmarks which broke with this checkin: c9192991c95a5145friendica2014-02-181-27/+6
| | | | | | It was documented that: Issues: Currently the order of HTML parameters in the text is somewhat rigid and inflexible. but as that was in a different function it was easy to overlook.
* operation snakebite continued. openid now works for local accounts using the ↵friendica2014-02-171-0/+4
| | | | rmagic module and after storing your openid in pconfig. This is just an interesting but trivial (in the bigger scheme of things) side effect of snakebite. The snake hasn't even waken up yet.
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-21 11:24:21 +0000