digg - Project Hosting on Google Code

Earlier this year Sep 01, 2009 issue 5 (oEmbed discovery -- support entities and whitespace) commented on by candr...@integralblue.com - Whitespace is valid before and after = in HTML. I believe the proper solution is to subtly modify the regex's. I've done this in the laconica/statusnet bundled copy of Services_oEmbed. http://gitorious.org/laconica/mainline/commit/29d0dd740c329c2674de58bec172419148a1b495 : Allow whitespace before and after the = and require space before the href in <link href="url"> html Whitespace is valid before and after = in HTML. I believe the proper solution is to subtly modify the regex's. I've done this in the laconica/statusnet bundled copy of Services_oEmbed. http://gitorious.org/laconica/mainline/commit/29d0dd740c329c2674de58bec172419148a1b495 : Allow whitespace before and after the = and require space before the href in <link href="url"> html Sep 01, 2009 issue 5 (oEmbed discovery -- support entities and whitespace) reported by ohnobinki - I have an oEmbed disovery URL listed in http://ohnopub.net/pix/?id=6215 . All of http://ohnopub.net/pix/ is reformatted by tidy for readability and slight insurance of conformance. This causes the <link /> elements to be split across multiple lines: `` <link rel="alternate" type="text/xml+oembed" href= "http://ohnopub.net/pix/oembed.php?url=http%3A%2F%2Fohnopub.net%2Fpix%2F%3Fid%3D6215&format=xml" title="phppix" /> '' The regex of Services_oEmbed does not support whitespace between attribute names and values. I am not sure where it is valid to have whitespace: maybe whitespace is allowed between ``href'' and ``=''? But I do know that whitespace is allowed after the equal sign and before the value because of Tidy's output and http://validator.w3.org/'s approval of my content. Also, it seems that Services_oEmbed cannot handle the ``&'' XML/HTML entity in the href= attribute. Use of this entity is necessary for the page to be loaded as XML/XHTML. I have fixed both at http://git.ohnopub.net/services_oembed.git . I have some PHP code that tests my modifications attached. I'm not sure how to properly use services_oembed -- I can't really easily test the whole chunk of code, but I extracted the parts which I modified into the attached file. I have an oEmbed disovery URL listed in http://ohnopub.net/pix/?id=6215 . All of http://ohnopub.net/pix/ is reformatted by tidy for readability and slight insurance of conformance. This causes the <link /> elements to be split across multiple lines: `` <link rel="alternate" type="text/xml+oembed" href= "http://ohnopub.net/pix/oembed.php?url=http%3A%2F%2Fohnopub.net%2Fpix%2F%3Fid%3D6215&format=xml" title="phppix" /> '' The regex of Services_oEmbed does not support whitespace between attribute names and values. I am not sure where it is valid to have whitespace: maybe whitespace is allowed between ``href'' and ``=''? But I do know that whitespace is allowed after the equal sign and before the value because of Tidy's output and http://validator.w3.org/'s approval of my content. Also, it seems that Services_oEmbed cannot handle the ``&'' XML/HTML entity in the href= attribute. Use of this entity is necessary for the page to be loaded as XML/XHTML. I have fixed both at http://git.ohnopub.net/services_oembed.git . I have some PHP code that tests my modifications attached. I'm not sure how to properly use services_oembed -- I can't really easily test the whole chunk of code, but I extracted the parts which I modified into the attached file. Jul 09, 2009 Services_Digg-0.4.7.tgz (Services_Digg-0.4.7) file uploaded by bshupp Jul 09, 2009 Services_Digg-0.4.6.tgz (Services_Digg-0.4.6) file uploaded by matt.erkkila May 28, 2009 issue 4 (Class.js Internet Explorer problem with indexOf) commented on by martin.saulis - You need to add this JavaScript code to add indexOf functionality to IE6 (extending Array class): if(!Array.indexOf){ Array.prototype.indexOf = function(obj){ for(var i=0; i<this.length; i++){ if(this[i]==obj){ return i; } } return -1; } } You need to add this JavaScript code to add indexOf functionality to IE6 (extending Array class): if(!Array.indexOf){ Array.prototype.indexOf = function(obj){ for(var i=0; i<this.length; i++){ if(this[i]==obj){ return i; } } return -1; } } May 28, 2009 issue 4 (Class.js Internet Explorer problem with indexOf) reported by patxi1980 - I use the class.js to create OO Classes in jQuery. I have a problem with Internet Explorer. When i see the code, i see that there is a call that uses indexOf to search inside an array. IndexOf is not supported by InternetExplorer. This must by fixed in order to make the class cross-browsers. I use the class.js to create OO Classes in jQuery. I have a problem with Internet Explorer. When i see the code, i see that there is a call that uses indexOf to search inside an array. IndexOf is not supported by InternetExplorer. This must by fixed in order to make the class cross-browsers. May 21, 2009 Pattern-1.3.0RC4.tgz (Pattern-1.3.0RC4) file uploaded by ian.eure - Labels: Featured Type-Package OpSys-All Labels: Featured Type-Package OpSys-All May 21, 2009 Muuttaa-0.0.10.tgz (Muuttaa-0.0.10) file uploaded by ian.eure - Labels: Featured Type-Package OpSys-All Labels: Featured Type-Package OpSys-All Apr 16, 2009 PDB-0.5.0RC3.tgz (PDB -.5.0RC3) file uploaded by ian.eure - Labels: Featured Type-Package OpSys-All Labels: Featured Type-Package OpSys-All Apr 02, 2009 Services_Digg-0.4.5.tgz (Services_Digg-0.4.5) file uploaded by matt.erkkila - Labels: digg services_digg diggapi Labels: digg services_digg diggapi Mar 30, 2009 Muuttaa-0.0.9.tgz (Muuttaa-0.0.9) file uploaded by ian.eure - Labels: Featured Type-Package Labels: Featured Type-Package Mar 24, 2009 PDB-0.5.0RC2.tgz (PDB 0.5.0RC2) file uploaded by ian.eure - Labels: Type-Package Featured OpSys-All Labels: Type-Package Featured OpSys-All Mar 24, 2009 Pattern-1.3.0RC3.tgz (Pattern 1.3.0RC3) file uploaded by ian.eure - Labels: Type-Package Featured OpSys-All Labels: Type-Package Featured OpSys-All Feb 06, 2009 Muuttaa-0.0.7.tgz (Muuttaa-0.0.7) file uploaded by ian.eure - Labels: Type-Package Featured OpSys-All Labels: Type-Package Featured OpSys-All Feb 06, 2009 r117 (Move to pear.php.net, bump version. ) committed by ian.eure - Move to pear.php.net, bump version. Move to pear.php.net, bump version. Jan 12, 2009 r116 (Tag Muuttaa-0.0.4) committed by ian.eure - Tag Muuttaa-0.0.4 Tag Muuttaa-0.0.4 Jan 09, 2009 r115 (Require Muuttaa/Common.php ) committed by ian.eure - Require Muuttaa/Common.php Require Muuttaa/Common.php Jan 09, 2009 Muuttaa-0.0.6.tgz (Muuttaa-0.0.6) file uploaded by ian.eure - Labels: Type-Package Featured OpSys-All Labels: Type-Package Featured OpSys-All Jan 09, 2009 r114 (Tag Muuttaa-0.0.6) committed by ian.eure - Tag Muuttaa-0.0.6 Tag Muuttaa-0.0.6 Jan 09, 2009 r113 (Prep Muuttaa-0.0.6) committed by ian.eure - Prep Muuttaa-0.0.6 Prep Muuttaa-0.0.6 Jan 09, 2009 r112 (Fix query in `destroy()`. ) committed by ian.eure - Fix query in `destroy()`. Fix query in `destroy()`. Jan 08, 2009 Muuttaa-0.0.5.tgz (Muuttaa-0.0.5) file uploaded by ian.eure - Labels: Featured Type-Package OpSys-All Labels: Featured Type-Package OpSys-All Jan 08, 2009 r111 (Tag Muuttaa-0.0.5) committed by ian.eure - Tag Muuttaa-0.0.5 Tag Muuttaa-0.0.5 Jan 08, 2009 r110 (Prep Muuttaa-0.0.5) committed by ian.eure - Prep Muuttaa-0.0.5 Prep Muuttaa-0.0.5 Jan 08, 2009 r109 (Move the queue pruning out-of-band, otherwise the queue will...) committed by ian.eure - Move the queue pruning out-of-band, otherwise the queue will never reach empty. Fix a SQL error in the prune, the `WHERE` for the `errors` table was using `id`, rather than `statementid`. Prime the output of `getQueueStats()` so there's always a key for each status, negating the need to messy `isset()` tests. Add `Muuttaa_Common::destroy()` to nuke a whole queue. Move the queue pruning out-of-band, otherwise the queue will never reach empty. Fix a SQL error in the prune, the `WHERE` for the `errors` table was using `id`, rather than `statementid`. Prime the output of `getQueueStats()` so there's always a key for each status, negating the need to messy `isset()` tests. Add `Muuttaa_Common::destroy()` to nuke a whole queue. Jan 07, 2009 issue 2 (PDB_Common::setFetchMode() fatals) Status changed by ian.eure - Status: Fixed Status: Fixed Jan 07, 2009 issue 3 (db or db() in Muuttaa_Process) Status changed by ian.eure - This is a bug (typo?), and I've fixed it in r108. It doesn’t cause problems in this case; the `$this->db()` method sets the `$this->db` member, so it doesn’t trigger a function call on non-object fatal error like it would if `db()` kept the DB instance in a function-local static variable. Nevertheless, it’s incorrect and should be fixed. Status: Fixed This is a bug (typo?), and I've fixed it in r108. It doesn’t cause problems in this case; the `$this->db()` method sets the `$this->db` member, so it doesn’t trigger a function call on non-object fatal error like it would if `db()` kept the DB instance in a function-local static variable. Nevertheless, it’s incorrect and should be fixed. Status: Fixed Jan 07, 2009 r108 (Use `$this->db()`, rather than `$this->db`, fixes issue #3. ) committed by ian.eure - Use `$this->db()`, rather than `$this->db`, fixes issue #3 . Use `$this->db()`, rather than `$this->db`, fixes issue #3 . Jan 07, 2009 Muuttaa-0.0.4.tgz (Muuttaa-0.0.4) file uploaded by ian.eure - Labels: Type-Package Featured OpSys-All Labels: Type-Package Featured OpSys-All Jan 07, 2009 r107 (Tag Muuttaa-0.0.4) committed by ian.eure - Tag Muuttaa-0.0.4 Tag Muuttaa-0.0.4 Jan 07, 2009 r106 (Prep Muuttaa-0.0.4) committed by ian.eure - Prep Muuttaa-0.0.4 Prep Muuttaa-0.0.4 Jan 07, 2009 PDB.php (SDFDSf) file uploaded by ian.eure Jan 07, 2009 PDB-0.0.7.tgz (PDB-0.0.7) file uploaded by matt.erkkila Jan 07, 2009 r105 (Tag PDB-0.0.7) committed by ian.eure - Tag PDB-0.0.7 Tag PDB-0.0.7 Jan 07, 2009 r104 (Prep PDB-0.0.7) committed by ian.eure - Prep PDB-0.0.7 Prep PDB-0.0.7 Jan 07, 2009 r103 (The test for "2006 MySQL server has gone away" is bogus; we ...) committed by ian.eure - The test for "2006 MySQL server has gone away" is bogus; we re-throw any PDOException exception in PDB_Common::query(), so the PDB_Exception we catch won't have $info set. Check the error string instead. The test for "2006 MySQL server has gone away" is bogus; we re-throw any PDOException exception in PDB_Common::query(), so the PDB_Exception we catch won't have $info set. Check the error string instead. Jan 07, 2009 r102 (Add queue-handling functions to Muuttaa_Common: getQueue(), ...) committed by ian.eure - Add queue-handling functions to Muuttaa_Common: getQueue(), getQueueSize() and getQueueStats(). Call getQueue() in Muuttaa_Process::process() instead of rolling SQL. Refactor Muuttaa::commit(): - Instead of returning true, return an array of STATEMENT_ID -> STATEMENT, where STATEMENT_ID is the DB ID of the statement after it was inserted. - Wrap the whole commit in a transaction instead of each statement, which allows us to fail the whole thing if a statement can't be added. Also, once you commit, lastInsertId() doesn't work. - Use a prepared statement. Add queue-handling functions to Muuttaa_Common: getQueue(), getQueueSize() and getQueueStats(). Call getQueue() in Muuttaa_Process::process() instead of rolling SQL. Refactor Muuttaa::commit(): - Instead of returning true, return an array of STATEMENT_ID -> STATEMENT, where STATEMENT_ID is the DB ID of the statement after it was inserted. - Wrap the whole commit in a transaction instead of each statement, which allows us to fail the whole thing if a statement can't be added. Also, once you commit, lastInsertId() doesn't work. - Use a prepared statement. Older Dec 30, 2008 issue 3 (db or db() in Muuttaa_Process) reported by jplock - On line 202 in Muuttaa_Process, it reads: $errors = $this->db->getCol($sql, 0, array( looking through the rest of the code, it seems to use $this->db() instead. I'm not sure if this was intended or not. Thanks for releasing this code from digg, it's very insightful! On line 202 in Muuttaa_Process, it reads: $errors = $this->db->getCol($sql, 0, array( looking through the rest of the code, it seems to use $this->db() instead. I'm not sure if this was intended or not. Thanks for releasing this code from digg, it's very insightful! Dec 26, 2008 r101 (Move the `$limit` var out of the args array and into the que...) committed by ian.eure - Move the `$limit` var out of the args array and into the query body, since PDO seems to escape it with quotes even though it's an int, and this breaks the query. Bad PDO, no treat. Move the `$limit` var out of the args array and into the query body, since PDO seems to escape it with quotes even though it's an int, and this breaks the query. Bad PDO, no treat. Dec 23, 2008 PDB-0.0.6.tgz (PDB 0.0.6) file uploaded by phatduckk Dec 23, 2008 r100 (Prep PDB-0.0.6. ) committed by ian.eure - Prep PDB-0.0.6. Prep PDB-0.0.6. Dec 23, 2008 r99 (It's InvalidArgumentException, not UnexpectedArgumentExcepti...) committed by ian.eure - It's InvalidArgumentException, not UnexpectedArgumentException. It's InvalidArgumentException, not UnexpectedArgumentException. Dec 23, 2008 PDB-0.0.5.tgz (PDB 0.0.5) file uploaded by phatduckk Dec 23, 2008 r98 (Tag PDB-0.0.5) committed by ian.eure - Tag PDB-0.0.5 Tag PDB-0.0.5 Dec 23, 2008 r97 (It's `throw new Export`, not `throw Exception`, fixes #2. ) committed by ian.eure - It's `throw new Export`, not `throw Exception`, fixes #2. It's `throw new Export`, not `throw Exception`, fixes #2. Dec 23, 2008 r96 (create tag for 0.0.4 from trunk r94) committed by phatduckk - create tag for 0.0.4 from trunk r94 create tag for 0.0.4 from trunk r94 Dec 23, 2008 r95 (back out c93) committed by phatduckk - back out c93 back out c93 Dec 23, 2008 r94 (change version in package.xml) committed by phatduckk - change version in package.xml change version in package.xml Dec 23, 2008 r93 (Fix `setFetchMode()`, fixes #2. ) committed by ian.eure - Fix `setFetchMode()`, fixes #2. Fix `setFetchMode()`, fixes #2. Dec 23, 2008 issue 2 (PDB_Common::setFetchMode() fatals) reported by ian.eure - What steps will reproduce the problem? 1. Execute the following code: {{{ $db = PDB::connect($dsn, $user, $pass); $db->setFetchMode(PDO::FETCH_CLASS, 'stdClass'); }}} What is the expected output? What do you see instead? Dies with: {{{ Fatal error: Call to undefined function UnexpectedArgumentException() in PDB/Common.php on line 509 }}} This is because line 590 has `throw UnexpectedArgumentException` rather than `throw new UnexpectedArgumentException`. What steps will reproduce the problem? 1. Execute the following code: {{{ $db = PDB::connect($dsn, $user, $pass); $db->setFetchMode(PDO::FETCH_CLASS, 'stdClass'); }}} What is the expected output? What do you see instead? Dies with: {{{ Fatal error: Call to undefined function UnexpectedArgumentException() in PDB/Common.php on line 509 }}} This is because line 590 has `throw UnexpectedArgumentException` rather than `throw new UnexpectedArgumentException`.

issue 5 (oEmbed discovery -- support entities and whitespace) reported by ohnobinki - I have an oEmbed disovery URL listed in http://ohnopub.net/pix/?id=6215 . All of http://ohnopub.net/pix/ is reformatted by tidy for readability and slight insurance of conformance. This causes the <link /> elements to be split across multiple lines: `` <link rel="alternate" type="text/xml+oembed" href= "http://ohnopub.net/pix/oembed.php?url=http%3A%2F%2Fohnopub.net%2Fpix%2F%3Fid%3D6215&format=xml" title="phppix" /> '' The regex of Services_oEmbed does not support whitespace between attribute names and values. I am not sure where it is valid to have whitespace: maybe whitespace is allowed between ``href'' and ``=''? But I do know that whitespace is allowed after the equal sign and before the value because of Tidy's output and http://validator.w3.org/'s approval of my content. Also, it seems that Services_oEmbed cannot handle the ``&'' XML/HTML entity in the href= attribute. Use of this entity is necessary for the page to be loaded as XML/XHTML. I have fixed both at http://git.ohnopub.net/services_oembed.git . I have some PHP code that tests my modifications attached. I'm not sure how to properly use services_oembed -- I can't really easily test the whole chunk of code, but I extracted the parts which I modified into the attached file.

I have an oEmbed disovery URL listed in http://ohnopub.net/pix/?id=6215 . All of http://ohnopub.net/pix/ is reformatted by tidy for readability and slight insurance of conformance. This causes the <link /> elements to be split across multiple lines: `` <link rel="alternate" type="text/xml+oembed" href= "http://ohnopub.net/pix/oembed.php?url=http%3A%2F%2Fohnopub.net%2Fpix%2F%3Fid%3D6215&format=xml" title="phppix" /> '' The regex of Services_oEmbed does not support whitespace between attribute names and values. I am not sure where it is valid to have whitespace: maybe whitespace is allowed between ``href'' and ``=''? But I do know that whitespace is allowed after the equal sign and before the value because of Tidy's output and http://validator.w3.org/'s approval of my content. Also, it seems that Services_oEmbed cannot handle the ``&'' XML/HTML entity in the href= attribute. Use of this entity is necessary for the page to be loaded as XML/XHTML. I have fixed both at http://git.ohnopub.net/services_oembed.git . I have some PHP code that tests my modifications attached. I'm not sure how to properly use services_oembed -- I can't really easily test the whole chunk of code, but I extracted the parts which I modified into the attached file.

Earlier this year

Older