aboutsummaryrefslogtreecommitdiffstats
path: root/mod/photos.php
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'master' into tresfriendica2015-01-291-11/+11
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/group.php include/text.php mod/acl.php mod/channel.php mod/connections.php mod/display.php mod/group.php mod/item.php mod/locs.php mod/network.php mod/photos.php mod/ping.php mod/starred.php mod/viewsrc.php
| * remote_user => remote_channelfriendica2015-01-281-4/+4
| |
| * local_user => local_channelfriendica2015-01-281-10/+10
| |
* | start on item_restrict conversionfriendica2015-01-221-12/+1
| |
* | heavy lifting converting item flag bitsfriendica2015-01-221-4/+2
|/
* Merge branch 'moretagging' of git://github.com/pafcu/red into pafcu-moretaggingfriendica2015-01-131-1/+1
|\ | | | | | | | | Conflicts: mod/profiles.php
| * Allow tags in mail, many profile fields, and admin infoStefan Parviainen2015-01-131-1/+1
| |
* | change deletion behaviour of linked photo items. Previously deleting the ↵friendica2015-01-121-1/+1
|/ | | | visible item in the conversation deleted the photo as well. Now photos must be deleted in the photos module. Deleting the linked item removes any attached conversation elements (likes, etc.) and sets the conversation item to hidden. This may create an issue in the future if we move the photo tags, title, or other photo elements to the linked item rather than the photo. Noting here so this can potentially be discovered and remembered at that time.
* Refactor mention code to make it more reusableStefan Parviainen2015-01-121-48/+19
|
* Fix wrong requireStefan Parviainen2015-01-041-1/+1
|
* Cruft left over from stuff we don't have anymore.Thomas Willingham2014-12-261-3/+0
|
* minor photo flag issue - and some more whitespace editsfriendica2014-11-191-1/+1
|
* turn the "adult photo flagging" (which prevents a particularly flagged photo ↵friendica2014-11-181-0/+1
| | | | from showing up in your top level albums) into a feature so it doesn't clutter the normal photo edit form. This feature was a quick hack and needs more work; but it could be important to somebody.
* another oneHabeas Codice2014-11-171-1/+1
|
* Merge branch 'master' of https://github.com/habeascodice/redHabeas Codice2014-11-171-1/+1
|\
| * fix lost $sql_extra in recent sql query changesmarijus2014-11-151-1/+1
| |
* | fix booleanHabeas Codice2014-11-171-1/+1
|/
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-131-55/+64
|\ | | | | | | | | | | | | | | | | | | | | | | 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
| * Merge https://github.com/friendica/red into pending_mergefriendica2014-11-071-5/+6
| |\
| | * provide lockstate for photo editmarijus2014-11-071-5/+6
| | |
| * | fix broken photo edits when adult flag is changedfriendica2014-11-071-8/+7
| |/
| * Provide a way to mark photos as adult and hide them from the default album ↵friendica2014-11-061-27/+31
| | | | | | | | view. Still need a button or setting to enable "unsafe viewing". This has no effect anywhere but in the album views. They can still be viewed by flipping through the individual photos with 'prev' and 'next'. We probably need a comprehensive strategy for how to deal with n-s-f-w photos in albums so consider this a band-aid which requires additional work and integration with other facilities which access these photos. It is entirely optional.
| * provide a lockstate for photo uploadsmarijus2014-11-061-1/+4
| |
| * if uploading a photo go away to albummarijus2014-11-031-2/+7
| |
| * if deleting a photo go away to albummarijus2014-11-031-1/+3
| |
| * even more photos workmarijus2014-11-011-11/+9
| |
* | PostgreSQL support initial commitHabeas Codice2014-11-131-20/+27
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* do not reload page for photo uploadmarijus2014-10-311-12/+8
|
* more work on photo uploadmarijus2014-10-311-7/+5
|
* some work on photo uploadmarijus2014-10-301-36/+13
|
* Merge https://github.com/friendica/red into pending_mergefriendica2014-10-281-1/+1
|\
| * change the way tagrm works to allow tag removal on the flymarijus2014-10-281-1/+1
| |
* | change photo tag bubble tipfriendica2014-10-281-1/+1
|/
* do not reload page for edit album and some minor cleanupmarijus2014-10-271-27/+21
|
* a couple of photo tag issuesfriendica2014-10-261-5/+11
|
* some work on photos like/dislikemarijus2014-10-251-3/+37
|
* more work on photosmarijus2014-10-201-10/+10
|
* merge madnessfriendica2014-10-191-2/+2
|
* $comments > $commentboxmarijus2014-10-151-1/+1
|
* some work on single photo view commentsmarijus2014-10-151-1/+2
|
* one more item_id > idmarijus2014-10-151-1/+1
|
* it seems we do not have an key called item_id here so must be id onlymarijus2014-10-151-1/+1
|
* it seems this is needed also to not allow editing profile photo albummarijus2014-10-031-2/+2
|
* more work on photosmarijus2014-10-021-65/+49
|
* some more work on photosmarijus2014-09-281-2/+2
|
* some more work on photos - work in progressmarijus2014-09-261-9/+12
|
* update jg to latest preview release and try once more to really justify the ↵marijus2014-09-201-11/+4
| | | | whole gallery
* set items/page back to 60marijus2014-09-111-2/+2
|
* content-complete must not be in photo-album-contentsmarijus2014-09-111-1/+4
|
* typomarijus2014-09-111-1/+1
|