photo / frontend Goto Github PK

Ideally the script would be interactive and ask for directory locations.

https://github.com/openphoto/frontend/blob/master/documentation/guides/InstallationUbuntu.markdown

There's already a branch created for this. Need to complete the work.

Ideally the script would be interactive and ask for directory locations.

https://github.com/openphoto/frontend/blob/master/documentation/guides/InstallationOSXMacports.markdown

There needs to be a framework to (in a sane manner) extend functionality via plugins.

From a Kickstarter comment:

Hey,
Just forked the latest source and got it working, everything seems very nice and smooth.
I try not to comment on anything functionality related as it's a very alpha stage - but I'd like to ask something that came to me from a comment made around albums.

I understand that people like to categorize photos differently.

• You Jaisen and others by tags.
• Other users by albums that they manage manually.
• I like my pics automatically added to albums by their "date taken" and these albums named according to the date and "gps location".
• Random dude might want to have instant albums based on tags, date and person on photo.

By no means I expect that everyone's crazy idea should be even considered - but - what if we could allow users to help each other?

• Plugins...
  Photo viewer plugins for example.
• Tags
• Albums
• Datetime
• Some random EXIF or meta tag.
• All of the above

Photo uploader plugins.

• Automatically organize uploaded pic according to something?
• Reverse GPS location and add street name to description?
• Face recognition?
• Automatically crop/resize/add-yellow-dots-to-image...

Anything goes.

The reason why I'm suggesting such an approach is that people WILL hack the source (I have already started) to add functionality they want for themselves.
Why not allow them to do it in a orderly fashion and help other non-developers to benefit from it?

Thanks for a great app and sorry for ranting. xD
George aka geoah.

Would exist at /tags and /tags.json

Same as issue 49.

I have a patch too

Ifyou upload a photo without date (a screenshot for instance) the following message is displayed instead of the date
Warning: date() expects parameter 2 to be long, string given in /srv/www/photosstore/src/libraries/models/Utility.php on line 6

How do you plan to execute PHP files on a static file storage system?

I think it should return

Content-Type: application/json;charset=utf-8

when asking for .json.

Here is how it looks now:

curl -v http://current.openphoto.me/photos.json
* About to connect() to current.openphoto.me port 80 (#0)
*   Trying 173.255.221.13... connected
* Connected to current.openphoto.me (173.255.221.13) port 80 (#0)
> GET /photos.json HTTP/1.1
> User-Agent: curl/7.21.2 (x86_64-apple-darwin10.5.0) libcurl/7.21.2 OpenSSL/1.0.0d zlib/1.2.5 libidn/1.19
> Host: current.openphoto.me
> Accept: */*
> 
< HTTP/1.1 200 OK
< Date: Mon, 08 Aug 2011 04:28:12 GMT
< Server: Apache/2.2.17 (Ubuntu)
< Set-Cookie: sessid=r2p8ogm8tmu5d18vnaanv2ot35; path=/
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< Pragma: no-cache
< Vary: Accept-Encoding
< Transfer-Encoding: chunked
< Content-Type: text/html
< 
{"message":"Successfully retrieved user's photos","code":200,"result":[{"tags":[],
...

DatabaseInterface::getUser() is missing, which mean that an eventual adapter will miss it until a runtime error.

I have a patch.

I'm getting the following warning:

PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given in /var/www/openphoto/src/libraries/external/epi/EpiRoute.php on line 107, referer: http://[site_name]/?m=welcome

This leads to a broken "image" on the photos screen that when clicked throws the following:

An error occurred and you have exceptions disabled so we're displaying the information. To turn exceptions on you should call: Epi::setSetting('exceptions', true);.
File: /var/www/openphoto/src/libraries/external/epi/EpiRoute.php
Line: 159
Message: Could not find route /photo/ from /photo/
Stack trace: #0 /var/www/openphoto/src/libraries/external/epi/EpiRoute.php(105): EpiRoute->getRoute('/photo/', 'GET')
#1 /var/www/openphoto/src/html/index.php(28): EpiRoute->run()
#2 {main}

Any help would be appreciated...getting excited about this!

Exif should be imported better.

Title and description should be imported for IPTC or XMP.
Tags should be imported as well

SetupController doesn't show correct errors.
SetupController confuses Imagick missing with folder permission error and doesn't warn that Imagick doesn't exist.

Will submit a pull request for this fix if I may. :)

In src/views/setup.php the input fields for key/secret should have autocomplete="off".

Determine the feasibility of running OpenPhoto on PHPFog and provide documentation on setting it up.

That way you could literally provision new EC2 instance using chef and have a fully functioning openphoto install

Update the docs and the code.

Without photo an error is displayed because we pass an empty array to foreach() ApiPhotoController.php around line 151.

I have a fix for that.

Photo updates include the entire tagset including existing tags and may remove some. There needs to be a way to increment the tag counts by diff'ing the existing set of tags against the new set.

Does not sound fun.

Option (or plugin) to check the md5/sha1 sum of the photo being uploaded with the photos db table to verify that the photo has not been uploaded again.

Similar to https://github.com/jmathai/twitter-async/blob/master/EpiTwitter.php#L152

Photos are not properly displaying a dateTaken field. It's defaulting the uploadDate. Reproducible on photos from an iPhone.

A table or database needs to be added to support tagclouds.

DatabaseInterface and all implementations need to support this.

FAQ page for documentation

Tag::sanitize() remove the spaces from the tags, turning multi-word tags to one word.

I don't know if it is a mistake or by design, but this is wrong IMHO.

Also I'm sure this might break in non latin scripts (or worse, non-ASCII)

Need to fill in the details of this.

The first step in authentication is to support public/private photos.

Private photos are only accessible by the owner of the photo.

I have the following message displayed on top of the page /tags
Warning: Division by zero in /srv/www/photosstore/src/libraries/models/Tag.php on line 63 Warning: Division by zero in /srv/www/photosstore/src/libraries/models/Tag.php on line 63 Warning: Division by zero in /srv/www/photosstore/src/libraries/models/Tag.php on line 63 Warning: Division by zero in /srv/www/photosstore/src/libraries/models/Tag.php on line 63 Warning: Division by zero in /srv/www/photosstore/src/libraries/models/Tag.php on line 63
It seems the number of warning is dependant of the number of tags (I have 5 tags).
Revision: git snapshot of today
webserver: cherokee 1.2.98
php: mode fpm, version 5.3.5

Should include at minimum the last photo id.

A config file that's consumed and includes the proper assets.

1. Viewed the current state at http://current.openphoto.me/

2. Tried "Search" for "cat" (since I could see that one of the photos on the home page was a cat

3. result was at http://current.openphoto.me/photos/tags-cat with the text:

An error occurred and you have exceptions disabled so we're displaying the information. To turn exceptions on you should call: Epi::setSetting('exceptions', true);.
File: /www/openphoto.me/current/src/libraries/external/epi/EpiRoute.php
Line: 159
Message: Could not find route /photo/ from /photo/
Stack trace: #0 /www/openphoto.me/current/src/libraries/external/epi/EpiRoute.php(105): EpiRoute->getRoute('/photo/', 'GET')
#1 /www/openphoto.me/current/src/html/index.php(28): EpiRoute->run()
#2 {main}

When a user clicks on a thumbnail the next/previous photos should reflect their previous page. If it was a tag search, for example, the next/previous should retain that context so the user can browse through photos in that "set".

The meta data needs to be normalized inside of the database adapter using a shared Photo class. The photo class exists but is not defined or used.

Primarily a problem when you first begin and don't have any photos.

These endpoints should accept a parameter and return a url to that resource. Similar to how returnOptions work for uploading a photo.

Report of the upload form crashing Chrome 13.0.782.99 on OSX 10.7

Reported via Twitter: http://twitter.com/#!/tehdik/status/95633836670590976

Determine the feasibility of running OpenPhoto on Pagodabox and provide documentation on setting it up.