aboutsummaryrefslogtreecommitdiffstats
path: root/include/photos.php
Commit message (Collapse)AuthorAgeFilesLines
* more message restrict conversionsfriendica2015-01-291-17/+16
|
* Merge branch 'master' into tres and add some work on the item_deleted flag ↵friendica2015-01-261-3/+17
|\ | | | | | | | | | | | | | | | | | | refactor Conflicts: include/attach.php include/onedirsync.php include/zot.php mod/locs.php
| * turn "large photo thumbnails" into a feature.friendica2015-01-251-6/+11
| |
| * provide pref to set default photo resolution for posts to something other ↵friendica2015-01-231-0/+9
| | | | | | | | than 2. The only acceptable option is 1. (640)
* | slow progress removing bitfields on item tablefriendica2015-01-211-37/+39
|/
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-131-2/+2
|\ | | | | | | | | | | | | | | | | | | | | | | 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
| * visible flag reversedfriendica2014-11-061-1/+1
| |
| * add some more safety checks before turning the conversation request messages ↵friendica2014-11-021-1/+1
| | | | | | | | back on
* | PostgreSQL support initial commitHabeas Codice2014-11-131-3/+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)
* just mark dead hubloc deleted - don't remove them. This could cause ↵friendica2014-09-161-0/+1
| | | | problems. Also clean up fetch_url/post_url header option
* support title and description (and dates which were done earlier) for ↵friendica2014-08-131-0/+4
| | | | friendica photo import
* provide a way to preserve photo timestamps when importing (rather than ↵friendica2014-08-121-0/+5
| | | | uploading)
* Friendica photo import tool. This will bring in all your photos from the ↵friendica2014-08-121-5/+5
| | | | chosen Friendica account and import them into Red. Note that profile photos will also be imported, but will not be scaled for profiles, nor will they be attached to any profiles. They will appear however in your Profile Photos album. Photos that had any access restrictions in Friendica will be made private to only you. Comments and likes, captions, and tags are not transferred, only the actual photos. You will only be able to do this once. If something goes wrong but any photos were imported, a pconfig called frphotos.complete will be set and you'll have to remove it to start over. If you should remove this to start over, we also check each photo and will not over-write a photo you already brought over.
* nothing going on here. nothing to see. move along.friendica2014-08-101-31/+48
|
* oh this is nice... http://kmkeen.com/jshon - this is what we need to make ↵friendica2014-06-181-3/+4
| | | | shred -- well "shred". I also had to change the photos album list API a bit to fix any imagined and/or real parsing issues and also fixed shred so it can find its auxiliary files.
* add photo count to photo album listfriendica2014-06-171-2/+3
|
* Merge https://github.com/friendica/red into zpullfriendica2014-03-251-1/+5
|\
| * Fix wall photo uploads.Thomas Willingham2014-03-251-1/+5
| |
* | missed onefriendica2014-03-251-1/+0
| |
* | ensure wall_upload always has width and height if the image is validfriendica2014-03-251-1/+5
|/
* add width and height to uploaded photo bodymarijus2014-03-221-1/+3
|
* use border-box for everythingmarijus2014-03-221-1/+1
|
* missing filename in uploaded photos (we don't really use this, but we will ↵friendica2014-01-221-0/+1
| | | | need to have a filename to export via DAV or API and the original filename would be the most likely choice).
* API: provide a link to photo albums in api/red/albumsfriendica2014-01-221-1/+5
|
* some minor cleanup on plinks for some very subtle permissions issuesfriendica2014-01-091-0/+5
|
* make storage limit service classes apply to accounts, not channels. Also ↵friendica2014-01-071-4/+2
| | | | include a css file that was missing from work yesterday.
* 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.
* add 'src' parameter to api photo listfriendica2013-12-191-1/+4
|
* prepare for Comanchification of mod_photosfriendica2013-12-131-2/+10
|
* missing verb on items linked to photosfriendica2013-09-171-1/+1
|
* provide detailed error to remote site for the myriad of things that can go ↵friendica2013-09-101-2/+4
| | | | wrong inside item_store(), !! this changes the return of item_store !!
* big changes to photo->store() which is now photo->save() and takes an array ↵friendica2013-08-071-4/+12
| | | | 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.
* start using profile_flags in photo queries so we can start creating ↵friendica2013-07-181-4/+9
| | | | PHOTO_THING's
* add photos and albums enumeration to Red API (will allow us to export either ↵friendica2013-05-291-3/+36
| | | | all our photos or individual albums using a script)
* convert most red photos to zmgfriendica2013-05-281-2/+2
|
* photo driver abstractionfriendica2013-04-251-1/+3
|
* turn all Red links into zrls (not the old zrls, the new bbcode zrl which ↵friendica2013-04-151-4/+4
| | | | means we can zidify them)
* rename 'uri' (and parent_uri) to 'mid' (and parent_mid) since these no ↵friendica2013-03-211-7/+7
| | | | longer remotely resemble uri's and are actually message_id's. This change is potentially destabilising because it touches a lot of code and structure. But it has to get done and there's no better time than the present.
* update for js_uploadfriendica2013-03-211-3/+3
|
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* partial cleanup of mod/profile_photo - needs a LOT morefriendica2013-02-051-0/+1
|
* convert wall_upload to use the photo apifriendica2013-02-051-1/+3
|
* debugging the photo apifriendica2013-02-021-4/+4
|
* more progress on photos apifriendica2013-02-021-1/+37
|
* photos cont.friendica2013-01-261-1/+45
|
* more photo backend stufffriendica2013-01-261-1/+28
|
* further baby steps on the photos APIfriendica2013-01-251-1/+25
|
* start on photos reworkfriendica2013-01-251-0/+226