Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | some initial work on uploading and cropping cover photos | redmatrix | 2016-01-13 | 1 | -2/+2 |
| | |||||
* | add v4 project roadmap, partial fix for cloning of profile photos on ↵ | redmatrix | 2015-11-20 | 1 | -0/+3 |
| | | | | alternate profiles | ||||
* | profile photo change activities | redmatrix | 2015-09-13 | 1 | -5/+67 |
| | |||||
* | profile photo issues #36 | redmatrix | 2015-09-09 | 1 | -1/+4 |
| | |||||
* | issues with "use this photo for profile photo" #36 | redmatrix | 2015-09-08 | 1 | -5/+27 |
| | |||||
* | Merge branch 'master' of https://github.com/redmatrix/redmatrix | redmatrix | 2015-07-10 | 1 | -2/+2 |
|\ | | | | | | | | | | | | | | | Conflicts: mod/editpost.php util/messages.po view/nl/messages.po view/nl/strings.php | ||||
| * | increase width of the aside area and make default profile image size 300x300 | Mario Vavti | 2015-07-09 | 1 | -2/+2 |
| | | |||||
* | | move profile photos to new methods | redmatrix | 2015-06-15 | 1 | -47/+36 |
| | | |||||
* | | Merge branch 'master' of https://github.com/redmatrix/redmatrix | redmatrix | 2015-05-31 | 1 | -1/+1 |
|\| | |||||
| * | fix unable to crop profile pic on postgres | Habeas Codice | 2015-05-30 | 1 | -1/+1 |
| | | |||||
* | | bring the new photo schema into play | redmatrix | 2015-05-18 | 1 | -18/+6 |
|/ | |||||
* | local_user => local_channel | friendica | 2015-01-28 | 1 | -22/+22 |
| | |||||
* | Fix unescaped image data | Habeas Codice | 2015-01-10 | 1 | -0/+1 |
| | |||||
* | implicit type conversion | Habeas Codice | 2014-11-21 | 1 | -1/+1 |
| | |||||
* | PostgreSQL support initial commit | Habeas Codice | 2014-11-13 | 1 | -5/+5 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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) | ||||
* | Allows extra content to be inserted at end of profile_photo page. Needed for ↵ | habeascodice | 2014-09-28 | 1 | -1/+3 |
| | | | | openclipatar addon. | ||||
* | Now we also refresh permissions after the user posted connedit. | sirius | 2014-04-20 | 1 | -1/+29 |
| | |||||
* | Added permission handling of profile-photos | sirius | 2014-04-20 | 1 | -15/+29 |
| | | | | Now we automatically set the appropiate viewing-permissions on profile edit and revert photos chosen as default profile picture bacl to public access. | ||||
* | Merging in conflict | sirius | 2014-04-16 | 1 | -9/+19 |
|\ | |||||
* | | Added hackish support for permissions-sync between profile and profile-pictures | sirius | 2014-04-14 | 1 | -0/+33 |
|/ | |||||
* | comanchify all the simple cases - those that only load a profile. Rework ↵ | friendica | 2013-12-11 | 1 | -10/+0 |
| | | | | permission checks for the profile sidebar so that it is all done internally. Remove crepair which we aren't using. | ||||
* | couple of errant SQL queries | friendica | 2013-12-05 | 1 | -2/+2 |
| | |||||
* | issue #225 | friendica | 2013-12-05 | 1 | -1/+1 |
| | |||||
* | big changes to photo->store() which is now photo->save() and takes an array ↵ | friendica | 2013-08-07 | 1 | -9/+35 |
| | | | | instead of a list of args. Also the beginning of the migration to using photo_flags to indicate special purpose photos such as profile photos and contact photos and "thing" photos. | ||||
* | photo driver abstraction | friendica | 2013-04-25 | 1 | -4/+4 |
| | |||||
* | we don't need to quote or rename 'default' in mySQL if we just use the ↵ | friendica | 2013-02-15 | 1 | -1/+1 |
| | | | | original column name 'is_default' | ||||
* | Whinging whining stupid fucks. | friendica | 2013-02-12 | 1 | -8/+6 |
| | |||||
* | fix profile selector on profile_photo page (unquoted mysql reserved word ↵ | friendica | 2013-02-10 | 1 | -3/+3 |
| | | | | 'default') | ||||
* | partial cleanup of mod/profile_photo - needs a LOT more | friendica | 2013-02-05 | 1 | -52/+65 |
| | |||||
* | clean up the photo storage backend, revamp mod/wall_upload | friendica | 2013-01-22 | 1 | -5/+6 |
| | |||||
* | more work on notification system, fix a couple of minor issues from smarty ↵ | friendica | 2013-01-07 | 1 | -2/+2 |
| | | | | conversion | ||||
* | implement Smarty3 | Zach Prezkuta | 2013-01-06 | 1 | -1/+11 |
| | |||||
* | "profile url" e.g. the wall/stream is now "channel url". "Profile URL" goes ↵ | friendica | 2012-10-29 | 1 | -1/+1 |
| | | | | to the profile details. | ||||
* | restore profile_photo functionality after structural changes | friendica | 2012-10-24 | 1 | -11/+18 |
| | |||||
* | here's where the heavy lifting begins - everything is likely to be broken ↵ | friendica | 2012-10-01 | 1 | -10/+10 |
| | | | | 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. | ||||
* | moving a lot of structure around. 'entity' is now 'channel' | friendica | 2012-09-25 | 1 | -1/+2 |
| | |||||
* | unbreak some more stuff | friendica | 2012-09-04 | 1 | -2/+2 |
| | |||||
* | more DB cleanup | friendica | 2012-08-30 | 1 | -2/+2 |
| | |||||
* | start on contacts/profiles | friendica | 2012-08-30 | 1 | -3/+3 |
| | |||||
* | stuff | friendica | 2012-08-27 | 1 | -1/+1 |
| | |||||
* | Removing connectors we won't be needing - this is probably going to break ↵ | friendica | 2012-07-18 | 1 | -2/+0 |
| | | | | some shit. | ||||
* | front end for alternate profile photos | friendica | 2012-07-17 | 1 | -1/+9 |
| | |||||
* | backend support for alternate profile photos for private profiles | friendica | 2012-07-17 | 1 | -9/+36 |
| | |||||
* | upstream fixes and a lot of taxonomy stuff | friendica | 2012-07-10 | 1 | -1/+7 |
| | |||||
* | png support: update database.sql, fix some typos, fix tinymce image browser | Fabio Comuni | 2012-06-07 | 1 | -1/+2 |
| | |||||
* | Add support for PNG images with alpha | Fabio Comuni | 2012-06-07 | 1 | -4/+6 |
| | |||||
* | Merge branch 'master' of https://github.com/friendica/friendica | Alexander Kampmann | 2012-04-05 | 1 | -1/+1 |
|\ | | | | | | | | | | | Conflicts: include/config.php update.php | ||||
| * | form security error when using existing photo | friendica | 2012-03-27 | 1 | -1/+1 |
|/ | |||||
* | Some security against XSRF-attacks | Tobias Hößl | 2012-03-12 | 1 | -6/+12 |
| | |||||
* | add remove_user hook (it looks like dreamhost changed all my file ↵ | friendica | 2012-01-18 | 1 | -0/+0 |
| | | | | permissions, this will make a nasty commit) |