phpFlickr

11 Comments for 'phpFlickr 1.6 fixes major XML problems (hopefully!)'

1.  
   Bernardo Achirica
   June 20, 2006 | 12:03 am
    
   That's what I need !!! I will be testing it as soon as I arrive home !!! Thank you Dan !!! :-D
2.  
   Bernardo Achirica
   June 20, 2006 | 8:09 am
    
   And aparently it does great !! I have been testing the scripts that we discussed some time ago in the forum and they all work great !! The only thing... I had to incrase the max_execution_time parameter in the php.ini file because I was getting some timeouts that with the previous version I dindn't had... but that's all.
3.  
   Ed
   June 21, 2006 | 11:03 am
    
   The update fixed the problem I was having, where in some cases instead of a thumbnail photo I was getting the text description. Keep up the great work!
4.  
   Bernardo Achirica
   June 22, 2006 | 12:26 pm
    
   I think I'm detecting some memory problems with the new parser... I have explained them in the forums... http://www.phpflickr.com/forums/comments.php?DiscussionID=89 Tell me if there's anything I can do to help you locate the problem... ;-)
5.  
   Jesse Warden - Flash, Flex, and Component Developer
   July 7, 2006 | 5:45 pm
    
   FlickrMobile: A Flash Lite 2 Application... *** Update 4.25.2006: Provided a Flash Player 6 version for PSP. *** Update: Yes, I used FAME (Flashout + ASDT + MTASC + Eclipse) to build this. Preface As has been reported by Scott F. and Scott J., the Flash......
6.  
   China Doll
   July 22, 2006 | 6:32 am
    
   Thanks for the codes. Simply brilliant. I tried it both in my localhost IIS and my apache web host. Working perfectly without any problems in both cases.
7.  
   Brenda
   August 12, 2006 | 6:02 pm
    
   1.6beta is still behaving funny for me... here's an example (one of many with this problem) for this photo here http://flickr.com/photos/36251685@N00/199469720/ the xml response from the api contains the 3 comments, including that funny apostrophe in the first comment whats´s that? This looks so cool. Can it work with a standard keyboard? Also does it suffer from a slow Windows startup? yes, just plug in a USB keyboard as for windows, no idea. The first thing we did after opening the box was installing linux. but the array from ->photos_comments_getList() only contains one empty comment var_dump: array(1) { [0]=> array(8) { ["_name"]=> string(7) "comment" ["_attributes"]=> array(5) { ["id"]=> string(34) "126545-199469720-72157594216934715" ["author"]=> string(12) "69225861@N00" ["authorname"]=> string(6) "pmarin" ["datecreate"]=> string(10) "1154250441" ["permalink"]=> string(72) "http://www.flickr.com/photos/taniwha/199469720/#comment72157594216934715" } ["_value"]=> NULL ["id"]=> string(34) "126545-199469720-72157594216934715" ["author"]=> string(12) "69225861@N00" ["authorname"]=> string(6) "pmarin" ["datecreate"]=> string(10) "1154250441" ["permalink"]=> string(72) "http://www.flickr.com/photos/taniwha/199469720/#comment72157594216934715" } }
8.  
   Brenda
   August 12, 2006 | 6:03 pm
    
   my xml wasn't escaped in the above comment, so it looks weird
9.  
   Brenda
   August 12, 2006 | 6:20 pm
    
   xml.php, line 52 xml_parse_into_struct($this->_parser, $xml, $this->_struct, $this->_index); good $xml with 3 comments goes in only one comment comes out in the struct.
10.  
    Eliot
    August 17, 2006 | 10:55 am
     
    Also finding an order of magnitude greater memory usage with the 1.6 parser. A script that ran on 1.5 with a 32MB limit now chokes about 10% through.
11.  
    Dan
    August 17, 2006 | 11:39 am
     
    Thanks for all of the great feedback. It's not terribly surprising that the SAXY parser uses more memory because it's not offloading its processing to pre-compiled libraries. The solution that I'm using in 1.6-final is to use the old parser by default and allow the developer to enable SAXY if he is having trouble with weird characters. I'll put a warning in that it can use more memory, of course.

Leave a comment