| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
friendica photo import
|
|
|
|
| |
uploading)
|
|
|
|
| |
out but their profile photo will remain rainbow man (or the site default). However the photo_date has been updated so we won't try again. This checkin looks for such a failure and leaves the photo_date alone if the photo import failed.
|
| |
|
|
|
|
| |
need to have a filename to export via DAV or API and the original filename would be the most likely choice).
|
| |
|
|
|
|
| |
images but may result in cropping important parts of the picture. Still this will work well for 95 out of 100 cases. If the width exceeds the height by greater than 1.2 we will remove an equal margin from either side of the photo leaving the center intact. If the height exceeds the width we will chop off the bottom to make it square. This is good for most single person photographs, unless the object of interest is off-center horizontally in a wide photo - or one is trying to emphasize aspects of human anatomy which may be at the bottom of a tall photo.
|
|
|
|
| |
issues with duplicate notifications and contact photos not getting an album name (it was crossed with filename). The last one doesn't matter as neither is used, but it was wrong so it has been corrected. Oh and thing photos weren't working at all because the form element name was different than what the module was looking for. But that had never been tested as I was waiting to get the import/resize finished. Next up for that module is display and deletion of things; but the priority is pretty low.
|
|
|
|
| |
admin ui
|
|
|
|
| |
selectable. Also red != friendica so we don't need all these friendica logos taking up space
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
instead of photo_factory()
|
| |
|
|
|