aboutsummaryrefslogtreecommitdiffstats
path: root/mod/profiles.php
Commit message (Collapse)AuthorAgeFilesLines
* Checkboxify yesno-fields, but use CSS to show them as switches in RedbasicStefan Parviainen2015-01-011-7/+6
|
* Redirect /profiles to default profile when multi_profiles is off. Fixes #768Stefan Parviainen2014-12-271-4/+14
|
* fix double encoding of homepage in profile activity - not as ↵friendica2014-12-211-1/+1
| | | | straight-forward as it looked
* Issue #739Thomas Willingham2014-12-131-1/+1
|
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-131-0/+18
|\ | | | | | | | | | | | | | | | | | | | | | | 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
| * the code is a bit crufty, but this should fix issue #687friendica2014-11-111-0/+16
| |
| * issue #683 - don't linkify homepage field without validatingfriendica2014-11-101-0/+2
| |
* | 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)
* merge madnessfriendica2014-10-191-30/+2
|
* This is a fix to not interfere the ongoing adding of ↵marijus2014-10-101-2/+0
| | | | | | | .generic-content-wrapper with the ongoing styling of redbasic theme. adding of .generic-content-wrapper is needed and useful for derivative themes but it should not contain any styling information for redbasic theme. therefor i added .generic-content-wrapper-styled as a quickfix for spots where redbasic is not finished yet. Sidenote: please avoid opening a div in one *.tpl and close it in another or (even worse) open a div in a *.tpl and close it in an already templatified mod/*.php. This will really make the code and templates very, very confusing.
* Added and changed on some places div class generic-content-wrapper. And ↵Jeroen2014-10-091-0/+3
| | | | added to redbasic. Other thems can now also theme backgrounds of a lot of pages. I'm not completely done, but till now - this is it.
* This is long overdue - use a symblic constant NULL_DATE instead of the ↵friendica2014-09-081-2/+2
| | | | easily mis-typed sequence '0000-00-00 00:00:00'
* except for a typofriendica2014-08-281-3/+1
|
* fix saving of extended profile attributesfriendica2014-08-281-0/+38
|
* extensible profiles - add the input form elements. Still needs styling and ↵friendica2014-08-201-0/+19
| | | | we're not yet storing the results. And right now we're ignoring the type and only doing type=string. Oh yeah - and I split off starting the second delivery chain into its own function in tag_deliver since it was largely duplicate code.
* more editing of visibility displaysfriendica2014-08-071-1/+1
|
* cleanup some text where we said "public" or "visible to anybody on the ↵friendica2014-08-071-1/+3
| | | | internet" when that isn't necessarily true.
* issue #551 provide import/export of profiles (if this feature is enabled)friendica2014-08-041-0/+36
|
* backend for profile exportfriendica2014-08-041-0/+27
|
* Let site admin choose what profile fields to support.friendica2014-08-021-1/+13
|
* Update nl. Added a link from the edit profile page to the edit visibility page.Jeroen2014-08-011-0/+1
|
* make the profile minimal by default. Use features to enable the advanced form.friendica2014-08-011-0/+5
|
* always provide a profile edit entry in the nav usermenufriendica2014-07-241-2/+2
|
* rule of snakes #1, kill the snake.friendica2014-06-281-2/+2
| | | | | | tinymce is gone. if you want a visual editor, figure out what you want and make it happen. If you don't want a visual editor, do nothing. This is in the community's hands. I don't need a visual editor.
* sync profiles to nomadic clonesfriendica2014-06-171-1/+10
|
* allow birthdays with just a year (no month or day).friendica2014-05-011-3/+3
|
* fix vcard truncation and escapingfriendica2014-04-201-18/+18
|
* fix marital partner linkingfriendica2014-01-231-26/+14
|
* expose profile things in the UIfriendica2013-12-301-0/+2
|
* comanchify all the simple cases - those that only load a profile. Rework ↵friendica2013-12-111-11/+0
| | | | permission checks for the profile sidebar so that it is all done internally. Remove crepair which we aren't using.
* birthday error checking - if year is present but no month or day, set to 1 ↵friendica2013-07-031-0/+5
| | | | January. Otherwise the date will be set to 30 November the prior year due to how the PHP strtotime() function works.
* multi-profiles workfriendica2013-07-031-1/+2
|
* TypoThomas Willingham2013-05-181-1/+1
|
* otherwise add profile wont workMichael Meer2013-03-211-1/+1
|
* Make the channels profile tab actually do something.Thomas Willingham2013-03-201-1/+6
|
* hidden directory entriesfriendica2013-01-221-1/+1
|
* more work on notification system, fix a couple of minor issues from smarty ↵friendica2013-01-071-1/+1
| | | | conversion
* implement Smarty3Zach Prezkuta2013-01-061-122/+156
|
* remove the private keywords stuff to reduce directory and search complexityfriendica2012-12-261-12/+6
|
* send stuff to zothub as a fallback directory master for nowfriendica2012-12-181-4/+1
|
* upstream fixes, revision updated, and mail autocomplete was lost after a ↵friendica2012-12-081-0/+1
| | | | recent change I made
* plaintext default - richtext is a featurefriendica2012-11-051-3/+3
|
* upstream fixesfriendica2012-10-211-177/+106
|
* this might post a profile change activity now - it just won't broadcast anywherefriendica2012-10-191-36/+22
|
* cleanup abook structurefriendica2012-10-191-2/+2
|
* more work on profile changes - the notify activity is still stuffed as we ↵friendica2012-10-191-29/+35
| | | | finalise the json structure for activitystream meta-data
* get profile edits workingfriendica2012-10-181-25/+19
|
* Can't see any posts currently - after the big shakeup, but we can now post ↵friendica2012-10-031-1/+1
| | | | top level activities and store them.
* here's where the heavy lifting begins - everything is likely to be broken ↵friendica2012-10-011-1/+12
| | | | for quite some time as we add location and db independence to items and conversations and work through the rest of the permissions and how to federate the buggers.
* States/Countries now free formfriendica2012-09-091-5/+0
|