<?xml version="1.0"?>
<?xml-stylesheet
href="http://www.w3.org/2000/08/w3c-synd/style.css" type="text/css"
?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel rdf:about="http://pear.php.net/bugs/search.php">
    <title>PEAR Bug Search Results</title>
    <link>http://pear.php.net/bugs/search.php?cmd=display&amp;package_name%5B0%5D=Services_Twitter</link>
    <description>Search Results</description>
    <dc:language>en-us</dc:language>
    <dc:creator>pear-webmaster@lists.php.net</dc:creator>
    <dc:publisher>pear-webmaster@lists.php.net</dc:publisher>
    <admin:generatorAgent rdf:resource="http://pear.php.net/bugs"/>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
    <items>
     <rdf:Seq>
      <rdf:li rdf:resource="http://pear.php.net/bug/19360" />
      <rdf:li rdf:resource="http://pear.php.net/bug/18061" />
      <rdf:li rdf:resource="http://pear.php.net/bug/18023" />
      <rdf:li rdf:resource="http://pear.php.net/bug/17979" />
      <rdf:li rdf:resource="http://pear.php.net/bug/17872" />

     </rdf:Seq>
    </items>
  </channel>

  <image rdf:about="http://pear.php.net/gifs/pearsmall.gif">
    <title>PEAR Bugs</title>
    <url>http://pear.php.net/gifs/pearsmall.gif</url>
    <link>http://pear.php.net/bugs</link>
  </image>

    <item rdf:about="http://pear.php.net/bug/19360">
      <title>Services_Twitter: Bug 19360 [Open] Missing parameter on API XML Map</title>
      <link>http://pear.php.net/bugs/19360</link>
      <content:encoded><![CDATA[<pre>Services_Twitter Bug
Reported by flavioheleno
2012-03-29T23:50:48+00:00
PHP: 5.3.10 OS: Ubuntu 12.04 x86_64 Package Version: 0.6.3

Description:
------------
The search endpoint can receive &quot;include_entities&quot; as a  boolean 
parameter, and it's definition is missing in api.xml, so the 
parameter is droped from request.

Test script:
---------------
require_once 'Services/Twitter.php';
$options = array(
	'q' =&gt; 'php',
	'include_entities' =&gt; true
);
$twitter = new Services_Twitter();
print_r($twitter-&gt;search($options));

Expected result:
----------------
The returned statuses should have entities defined.

Actual result:
--------------
The returned statuses doesn't have entities defined.</pre>]]></content:encoded>
      <description><![CDATA[<pre>Services_Twitter Bug
Reported by flavioheleno
2012-03-29T23:50:48+00:00
PHP: 5.3.10 OS: Ubuntu 12.04 x86_64 Package Version: 0.6.3

Description:
------------
The search endpoint can receive &quot;include_entities&quot; as a  boolean 
parameter, and it's definition is missing in api.xml, so the 
parameter is droped from request.

Test script:
---------------
require_once 'Services/Twitter.php';
$options = array(
	'q' =&gt; 'php',
	'include_entities' =&gt; true
);
$twitter = new Services_Twitter();
print_r($twitter-&gt;search($options));

Expected result:
----------------
The returned statuses should have entities defined.

Actual result:
--------------
The returned statuses doesn't have entities defined.</pre>]]></description>
      <dc:date>2012-03-29T23:55:13+00:00</dc:date>
      <dc:creator>flaviohbatista &amp;#x61;&amp;#116; gmail &amp;#x64;&amp;#111;&amp;#x74; com</dc:creator>
      <dc:subject>Services_Twitter Bug</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/18061">
      <title>Services_Twitter: Feature/Change Request 18061 [Analyzed] Solving SSL issues (ssl_verify_peer and ssl_verify_host)</title>
      <link>http://pear.php.net/bugs/18061</link>
      <content:encoded><![CDATA[<pre>Services_Twitter Feature/Change Request
Reported by brutuscat
2010-11-16T15:11:51+00:00
PHP: 5.2.9 OS: Ubuntu Package Version: 0.6.3

Description:
------------
Instead of disable the security provided by SSL setting 
ssl_verify_peer' = false, you should take a look at 
http://curl.haxx.se/docs/sslcerts.html

I have built my bundle cert using this 
http://curl.haxx.se/docs/caextract.html,  and appended the 
https://twitter.com cert (follow point 3 of the page) to the 
bundle.

I have tested all this and works great! The code at the test 
section 
will show it.

I am attaching the full cert also.

Regards, 
Mauro



Test script:
---------------
          $twitter = new Services_Twitter(null, null, array('use_ssl' =&gt; true));
          //$twitter-&gt;getRequest()-&gt;setAdapter('HTTP_Request2_Adapter_Curl');
          $twitter-&gt;getRequest()-&gt;setConfig('ssl_verify_peer', true);
          $twitter-&gt;getRequest()-&gt;setConfig('ssl_verify_host', true);
          $twitter-&gt;getRequest()-&gt;setConfig('ssl_cafile', dirname(__FILE__). '/twitter/cacert.pem');</pre>]]></content:encoded>
      <description><![CDATA[<pre>Services_Twitter Feature/Change Request
Reported by brutuscat
2010-11-16T15:11:51+00:00
PHP: 5.2.9 OS: Ubuntu Package Version: 0.6.3

Description:
------------
Instead of disable the security provided by SSL setting 
ssl_verify_peer' = false, you should take a look at 
http://curl.haxx.se/docs/sslcerts.html

I have built my bundle cert using this 
http://curl.haxx.se/docs/caextract.html,  and appended the 
https://twitter.com cert (follow point 3 of the page) to the 
bundle.

I have tested all this and works great! The code at the test 
section 
will show it.

I am attaching the full cert also.

Regards, 
Mauro



Test script:
---------------
          $twitter = new Services_Twitter(null, null, array('use_ssl' =&gt; true));
          //$twitter-&gt;getRequest()-&gt;setAdapter('HTTP_Request2_Adapter_Curl');
          $twitter-&gt;getRequest()-&gt;setConfig('ssl_verify_peer', true);
          $twitter-&gt;getRequest()-&gt;setConfig('ssl_verify_host', true);
          $twitter-&gt;getRequest()-&gt;setConfig('ssl_cafile', dirname(__FILE__). '/twitter/cacert.pem');</pre>]]></description>
      <dc:date>2011-03-27T20:36:13+00:00</dc:date>
      <dc:creator>mauroasprea &amp;#x61;&amp;#116; gmail &amp;#x64;&amp;#111;&amp;#x74; com</dc:creator>
      <dc:subject>Services_Twitter Feature/Change Request</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/18023">
      <title>Services_Twitter: Feature/Change Request 18023 [Open] Output of assoc array instead of stdClass for JSON</title>
      <link>http://pear.php.net/bugs/18023</link>
      <content:encoded><![CDATA[<pre>Services_Twitter Feature/Change Request
Reported by jeremiahlee
2010-11-02T03:06:39+00:00
PHP: 5.2.10 OS: Not Relevant Package Version: 0.6.3

Description:
------------
$twitter-&gt;statuses-&gt;update() is returning a stdClass instead of 
an associative array when set to OUTPUT_JSON, so responses 
cannot be converted to strings for logging or database 
storage. To fix: json_decode($body, TRUE) will provide an 
associative 
array.

I understand that I can get the raw response and do this 
manually. It would be preferable to have an associative array 
of 
the JSON as a configurable option.</pre>]]></content:encoded>
      <description><![CDATA[<pre>Services_Twitter Feature/Change Request
Reported by jeremiahlee
2010-11-02T03:06:39+00:00
PHP: 5.2.10 OS: Not Relevant Package Version: 0.6.3

Description:
------------
$twitter-&gt;statuses-&gt;update() is returning a stdClass instead of 
an associative array when set to OUTPUT_JSON, so responses 
cannot be converted to strings for logging or database 
storage. To fix: json_decode($body, TRUE) will provide an 
associative 
array.

I understand that I can get the raw response and do this 
manually. It would be preferable to have an associative array 
of 
the JSON as a configurable option.</pre>]]></description>
      <dc:date>2010-11-02T03:07:11+00:00</dc:date>
      <dc:creator>mass &amp;#x61;&amp;#116; jeremiahlee &amp;#x64;&amp;#111;&amp;#x74; com</dc:creator>
      <dc:subject>Services_Twitter Feature/Change Request</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/17979">
      <title>Services_Twitter: Feature/Change Request 17979 [Open] Support for new 64-bit IDs</title>
      <link>http://pear.php.net/bugs/17979</link>
      <content:encoded><![CDATA[<pre>Services_Twitter Feature/Change Request
Reported by steve_twitpic
2010-10-19T23:03:24+00:00
PHP: 5.3.3 OS: Not Relevant Package Version: 0.6.3

Description:
------------
Twitter is switching to a new ID scheme for Tweets that will 
use unsigned 64-bit integers. PHP (and many other 
languages) do not have support for unsigned 64-bit integers. 
In order to circumvent this issue, Twitter is going to 
start providing both an &quot;id&quot; and &quot;id_str&quot; in their JSON/XML 
responses.

Info:
http://groups.google.com/group/twitter-development-
talk/browse_thread/thread/6a16efa375532182

Example:
{&quot;id&quot;: 10765432100123456789, &quot;id_str&quot;: 
&quot;10765432100123456789&quot;} 

In PHP, we're going to have to use id_str, because the id 
integer overflows. Personally, I'd prefer if this change 
was handled seamlessly within Services_Twitter. In other 
words, if I access $tweet-&gt;id, it should really return 
id_str, since $tweet-&gt;id will always be invalid when accessed 
within PHP.

Additionally, any API functions that take a tweet id as a 
parameter will have to be updated to accept a string for 
the tweet id.

I can help with a patch but I wanted to post here first. 
Thoughts?</pre>]]></content:encoded>
      <description><![CDATA[<pre>Services_Twitter Feature/Change Request
Reported by steve_twitpic
2010-10-19T23:03:24+00:00
PHP: 5.3.3 OS: Not Relevant Package Version: 0.6.3

Description:
------------
Twitter is switching to a new ID scheme for Tweets that will 
use unsigned 64-bit integers. PHP (and many other 
languages) do not have support for unsigned 64-bit integers. 
In order to circumvent this issue, Twitter is going to 
start providing both an &quot;id&quot; and &quot;id_str&quot; in their JSON/XML 
responses.

Info:
http://groups.google.com/group/twitter-development-
talk/browse_thread/thread/6a16efa375532182

Example:
{&quot;id&quot;: 10765432100123456789, &quot;id_str&quot;: 
&quot;10765432100123456789&quot;} 

In PHP, we're going to have to use id_str, because the id 
integer overflows. Personally, I'd prefer if this change 
was handled seamlessly within Services_Twitter. In other 
words, if I access $tweet-&gt;id, it should really return 
id_str, since $tweet-&gt;id will always be invalid when accessed 
within PHP.

Additionally, any API functions that take a tweet id as a 
parameter will have to be updated to accept a string for 
the tweet id.

I can help with a patch but I wanted to post here first. 
Thoughts?</pre>]]></description>
      <dc:date>2010-10-19T23:03:24+00:00</dc:date>
      <dc:creator>steve &amp;#x61;&amp;#116; twitpic &amp;#x64;&amp;#111;&amp;#x74; com</dc:creator>
      <dc:subject>Services_Twitter Feature/Change Request</dc:subject>
    </item>
    <item rdf:about="http://pear.php.net/bug/17872">
      <title>Services_Twitter: Documentation Problem 17872 [Open] Search only returns status ids</title>
      <link>http://pear.php.net/bugs/17872</link>
      <content:encoded><![CDATA[<pre>Services_Twitter Documentation Problem
Reported by arnom
2010-09-17T15:14:38+00:00
PHP: 5.3.0 OS: Ubuntu Server 10.04 Package Version: 0.6.3

Description:
------------
When I perform a search using Services_Twitter (with oAuth 
details supplied), it only returns an array of ids and a field called 
created_in.
How can I extract the actually tweets and the users who send 
them?

Test script:
---------------
&lt;?php
//$oAuth = new HTTP_OAuth_Consumer( /** Supply oAuth details here **/ );
$Twitter = new Services_Twitter();
//$Twitter-&gt;setOAuth($oAuth);
try {
    $Response = $Twitter-&gt;search(array(
      &quot;q&quot;	=&gt; &quot;#FF -RT OR #FollowFriday -RT&quot;,
      &quot;rpp&quot;	=&gt; 10,
      &quot;since_id&quot;  =&gt; 23982086000,
      &quot;result_type&quot;	=&gt; &quot;recent&quot;
    ));
    var_dump($Response);
  } catch (Exception $e) {
    fwrite(STDERR, $e-&gt;getMessage());
  }
?&gt;

Expected result:
----------------
I would like to access the fields shown in this example response 
in the Twitter API documentation:
http://dev.twitter.com/doc/get/search#example-requests

Actual result:
--------------
object(stdClass)#88 (2) {
  [&quot;statuses&quot;]=&gt;
  array(11) {
    [0]=&gt;
    int(49497593539)
    [1]=&gt;
    int(49497593851)
    [2]=&gt;
    int(49497598001)
    [3]=&gt;
    int(49497599055)
    [4]=&gt;
    int(49497599597)
    [5]=&gt;
    int(49497600733)
    [6]=&gt;
    int(49497602607)
    [7]=&gt;
    int(49497607031)
    [8]=&gt;
    int(49497607453)
    [9]=&gt;
    int(49497609577)
    [10]=&gt;
    int(49497610605)
  }
  [&quot;created_in&quot;]=&gt;
  float(0.008847)
}</pre>]]></content:encoded>
      <description><![CDATA[<pre>Services_Twitter Documentation Problem
Reported by arnom
2010-09-17T15:14:38+00:00
PHP: 5.3.0 OS: Ubuntu Server 10.04 Package Version: 0.6.3

Description:
------------
When I perform a search using Services_Twitter (with oAuth 
details supplied), it only returns an array of ids and a field called 
created_in.
How can I extract the actually tweets and the users who send 
them?

Test script:
---------------
&lt;?php
//$oAuth = new HTTP_OAuth_Consumer( /** Supply oAuth details here **/ );
$Twitter = new Services_Twitter();
//$Twitter-&gt;setOAuth($oAuth);
try {
    $Response = $Twitter-&gt;search(array(
      &quot;q&quot;	=&gt; &quot;#FF -RT OR #FollowFriday -RT&quot;,
      &quot;rpp&quot;	=&gt; 10,
      &quot;since_id&quot;  =&gt; 23982086000,
      &quot;result_type&quot;	=&gt; &quot;recent&quot;
    ));
    var_dump($Response);
  } catch (Exception $e) {
    fwrite(STDERR, $e-&gt;getMessage());
  }
?&gt;

Expected result:
----------------
I would like to access the fields shown in this example response 
in the Twitter API documentation:
http://dev.twitter.com/doc/get/search#example-requests

Actual result:
--------------
object(stdClass)#88 (2) {
  [&quot;statuses&quot;]=&gt;
  array(11) {
    [0]=&gt;
    int(49497593539)
    [1]=&gt;
    int(49497593851)
    [2]=&gt;
    int(49497598001)
    [3]=&gt;
    int(49497599055)
    [4]=&gt;
    int(49497599597)
    [5]=&gt;
    int(49497600733)
    [6]=&gt;
    int(49497602607)
    [7]=&gt;
    int(49497607031)
    [8]=&gt;
    int(49497607453)
    [9]=&gt;
    int(49497609577)
    [10]=&gt;
    int(49497610605)
  }
  [&quot;created_in&quot;]=&gt;
  float(0.008847)
}</pre>]]></description>
      <dc:date>2010-09-17T19:27:13+00:00</dc:date>
      <dc:creator>am &amp;#x61;&amp;#116; vanda &amp;#x64;&amp;#111;&amp;#x74; ag</dc:creator>
      <dc:subject>Services_Twitter Documentation Problem</dc:subject>
    </item>
</rdf:RDF>
