I've just put up a new beta version of phpFlickr. I've implemented a rather large fix to the XML problems that were plauging it before. If you were having troubles with the XML parser puking when it got to non-english or unusual characters, this is the release for you! Try it out and see if you have any problems with it. Feel free to leave a comment here about whether it works or if you find tons of bugs. You could also use the contact form on this site. All you should need to do is drop it into your phpFlickr folder and watch the magic happen. *crosses fingers*
I've also implemented the new photo replacement API. That should prove to be pretty useful.
Hopefully, I can put out a non-beta release soon if I get positive feedback about this beta.
That's what I need !!! I will be testing it as soon as I arrive home !!!
Thank you Dan !!!
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.
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!
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…
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.
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"
}
}
my xml wasn't escaped in the above comment, so it looks weird
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.
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.
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.