aboutsummaryrefslogtreecommitdiffstats
path: root/include/photos.php
Commit message (Collapse)AuthorAgeFilesLines
* add obj_type and object againMario Vavti2015-10-201-1/+3
|
* fix jot photo uploadMario Vavti2015-10-201-10/+6
|
* create photo object if feature large photos is enabled and display those ↵Mario Vavti2015-10-201-18/+52
| | | | slightly different
* we now provide images for all suffixes (0-3) -> simplify photo item body ↵Mario Vavti2015-10-161-36/+25
| | | | creation and provide width x height for any size
* generate all (non-square) photo scales - even if the original photo is ↵redmatrix2015-10-151-21/+21
| | | | smaller than the scale target sizes.
* (re)add default image-size 320px - it is good for gallery preview. this size ↵Mario Vavti2015-10-151-0/+9
| | | | has the suffix -3 now
* double up default photo sizes - even the mos simple camera can now do images ↵Mario Vavti2015-10-151-4/+4
| | | | > 1024px
* allow photo-items to appear full width if large photos feature is enabled. ↵Mario Vavti2015-10-141-1/+1
| | | | in prepare_body() split off mentions, tags, categories folders and attachments from body for easier theming. some other little fixes.
* consolidate import_items/sync_itemsredmatrix2015-09-071-3/+0
|
* make js_upload work with hubzilla. It still needs a rewrite.redmatrix2015-09-051-2/+2
|
* more AccessList stuff - this time it's mod-item, which is a biggieredmatrix2015-08-281-1/+1
|
* now we get to the heavy lifting with AccessList stuffredmatrix2015-08-271-57/+29
|
* redphotos updatesredmatrix2015-08-261-1/+8
|
* change attach_store to allow a predefined item to accompany a photoredmatrix2015-08-261-44/+80
|
* lots of stuff that was needed for successful photo import from redredmatrix2015-08-241-6/+15
|
* fix photo locationredmatrix2015-08-191-1/+11
|
* photo permission inheritance. We want to use the folder permissions unless ↵redmatrix2015-08-061-14/+26
| | | | specific permissions have been set to over-ride them. If nothing is set, use the channel default. We may have to mess with his further in the case of somebody trying to create a public photo directory when their normal permissions are set to private. Kind of a chicken/egg problem because the folder permissions will be empty.
* don't throw errors or do the wrong thing if photos have no album (placed on ↵redmatrix2015-08-051-1/+1
| | | | your dav rootdir)
* photo album is decided in dav or attach modules now - don't set it in ↵redmatrix2015-08-051-8/+8
| | | | photos_upload
* incorrect photo permissions when uploaded via /cloud; issue #21redmatrix2015-07-301-0/+11
|
* the view_photos and post_photos permissions are redundant and are now mapped ↵redmatrix2015-07-191-5/+5
| | | | to view_storage and write_storage
* more work on photos, including os_storage for the size '0' photo and ↵redmatrix2015-06-231-2/+18
| | | | numbering duplicate filenames
* Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-06-161-2/+2
|\ | | | | | | | | | | Conflicts: mod/photos.php mod/siteinfo.php
| * fix deleting of album for remote channelMario Vavti2015-06-161-2/+2
| |
* | bring the new photo schema into playredmatrix2015-05-181-3/+3
| |
* | Merge branch 'master' into tresredmatrix2015-05-141-1/+0
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/Import/refimport.php include/activities.php include/attach.php include/event.php include/externals.php include/identity.php include/items.php include/notifier.php include/photos.php include/taxonomy.php include/zot.php mod/channel.php mod/connedit.php mod/events.php mod/item.php mod/like.php mod/manage.php mod/mood.php mod/ping.php mod/poke.php mod/subthread.php mod/tagger.php mod/thing.php
| * | convert ITEM_WALL from bitfield to standaloneredmatrix2015-05-061-2/+4
| |/
* | Merge branch 'master' into tresfriendica2015-04-231-86/+158
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/Contact.php include/ItemObject.php include/api.php include/attach.php include/diaspora.php include/dir_fns.php include/enotify.php include/event.php include/expire.php include/items.php include/notifier.php include/notify.php include/photos.php include/taxonomy.php include/text.php include/widgets.php include/zot.php mod/admin.php mod/channel.php mod/dirsearch.php mod/display.php mod/editwebpage.php mod/events.php mod/home.php mod/item.php mod/manage.php mod/mood.php mod/network.php mod/page.php mod/photos.php mod/ping.php mod/post.php mod/thing.php mod/viewsrc.php view/css/mod_events.css
| * Correcting reported Doxygen syntax warnings.Klaus Weidenbach2015-03-291-46/+71
| | | | | | | | | | | | | | Fixed wrong Doxygen syntax and add some of the available FIXME to Doxygen documentation. Updated Doxygen configuration to add also all capital letter tags. Adding some more Doxygen documentation.
| * get the correct hemisphere for geotagged photosfriendica2015-03-171-2/+2
| |
| * turn photo location mapping into a featurefriendica2015-03-171-1/+1
| |
| * display a map for photos if allowed. Note: there is a bug in that if the map ↵friendica2015-03-161-0/+41
| | | | | | | | div starts with display:none one needs to reload the frame or zoom in or they end up at minimum resolution. Still trying to sort this out.
| * started to add the ability to geotag photos (default will be disabled) but ↵friendica2015-03-161-1/+3
| | | | | | | | my phone isn't outputting the GPS tags even after being explicitly enabled so I'll have to wait until I've got a device that I can reliably test against.
| * skip trying to come up with an intelligent way to decide what photos should ↵friendica2015-03-111-19/+1
| | | | | | | | get a status post - leave it manual.
| * Change logic of "don't create a status post for this photo upload" and turn ↵friendica2015-03-101-2/+2
| | | | | | | | it into a bona-fide on/off toggle. This takes up one more vertical line, but we have it to spare, and the single button (while concise visually) provided no feedback of the current state, or indicate whether a second click toggled it. Some addons use this setting so addons will need to be pulled when this is pulled in order to remain in sync.
| * Deprecate the "wall uploads" photo album. Photo uploads (from any source) ↵friendica2015-03-041-1/+1
| | | | | | | | with no album specified will go now into an album based on YYYY-MM.
| * Some cleanups and documentation.Klaus Weidenbach2015-03-041-29/+46
| | | | | | | | | | | | | | Fixed some wrong variable names. Initialized some variables before using them. Removed some checks for STATUSNET_PRIVACY_COMPATIBILITY in include/security.php as it does not seem to be defined anywhere.
* | 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.