[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5312: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3925)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5312: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3925)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5312: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3925)
Tiny Tiny RSS • Reeder (iOS) integration with TT-RSS (via Fever API) - Page 5
Page 5 of 15

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 25 May 2013, 03:16
by ZeGuigui

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 25 May 2013, 03:48
by morsedl
(Odd, I posted this already, but it didn't show up, so trying again...)

@ZeGuigui:

My tt-rss installation is at https://xxxxx.xxxxxxx.com/reader/

I didn't have SSLCertificateChainFile configured in Apache 2, but I downloaded CAcert_chain.pem from cacert.org and added:

SSLCertificateChainFile /etc/ssl/certs/CAcert_chain.pem

to the right place in my Apache mod_ssl config (i.e., /etc/apache2/sites-enables/ikrg-ssl), but still no joy (same login failed error).

Thanks again so much for your assistance! And thank you VERY much for confirming that this CAN work.

I wondering what I'm doing wrong or what I am I missing?

Doug

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 25 May 2013, 04:24
by LifeWOutMilk
Considering the guys at cacert.org can't even get it right, I'm not surprised.



Edit: Why not go to StartSSL.com and get a cert that will actually work in current browsers instead of this broken cacert.org nonsense?

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 25 May 2013, 07:05
by morsedl

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 26 May 2013, 18:09
by whatiris
Hullo! I have figured out the problem with the fever plugin and postgresql, I think. The PHP postgres handler returns "t" and "f" instead of 1 and 0 for boolean fields.

This means getUnreadItemIds() needs to be edited to handle the case of "t" instead of 1

if ($line["unread"] == "t")
$unreadItemIdsCSV .= $line["ref_id"] . ",";

and getItems() needs to handle the case of "f" when checking unread status

"is_read" => ($line["unread"] == "f" ? 1 : 0),

I am not much of a developer so I don't know how to submit a patch but as far as I can see those two changes are the only thing required to support postgres. The setItem type functions specify the boolean true in the query so they should work I think. I haven't tested this much beyond basic sanity checking.

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 26 May 2013, 18:19
by fox
functions.php, sql_bool_to_bool()

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 26 May 2013, 18:30
by whatiris
Ah cool, can wrap in that function instead.

And yes, obviously I'm talking about the functions in fever_api.php I forgot to mention that.

Anyway, hope this helps, DigitalDJ.

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 26 May 2013, 23:34
by IvanRaide
Seeing the above working for morsedl I decided to try it as well (but am much less qualified I believe to actually accomplish it).

I got an express cert from StartSLL, which was a p12 file. I noticed that all the apache2 ssl settings required pem files in the examples above, so I ran the following...
openssl pkcs12 -in StartSSL.p12 -out StartSSL.pem -nodes

I then ran:

a2enmod ssl
a2ensite default-ssl
service apache2 restart


Now when I go to the tt-rss website it came up with untrusted cert (which makes sense, I believe its using that snake-oil cert).
I copied over the StartSSL.pem file to /etc/ssl/certs and changed the following 3 lines in default-ssl to:

SSLCertificateFile /etc/ssl/cert/StartSSL.pem
SSLCertificateKeyFile/etc/ssl/cert/StartSSL.pem
SSLCertificateChainFile /etc/ssl/cert/StartSSL.pem

but when trying to restart apache it fails. My assumption was that pem are a concatenation of all the info required, but honestly, I don't know very much about openssl,ssl etc, so I'm sure that assumption is wrong.
if that assumption is wrong, how do you get the necessary files from StartSSL ? I guess, "am I close, or am I so far off the mark that I should just give up"

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 26 May 2013, 23:35
by fox
Last I checked you were posting on a tt-rss forum, not "plz halp I can't apache".

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 27 May 2013, 00:34
by morsedl

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 27 May 2013, 03:04
by DigitalDJ

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 27 May 2013, 05:19
by whatiris
Yep, I did make the changes myself and have been using it in Reeder successfully since yesterday. I'll give your 1.2 a go later today.

Edit: I have updated to 1.2 now and was able to successfully refresh in Reeder, and mark an item read which updated correctly in the web interface.

Looking at the changes you've made, they're pretty much exactly what I did which has been fine so should be all good.

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 02 Jun 2013, 06:34
by vasechka
Absolutely great plugin.
I tried to get it working with ReadKit on OS X. And didn't go - ReadKit will crash after requesting groups list. Just FYI.
Oh, btw, got it working on https - had to install my own CA certificate onto iOS device.

Re: Reeder (iOS) integration with TT-RSS (via Fever API)

Posted: 02 Jun 2013, 09:10
by morsedl

Chill Pill support?

Posted: 18 Jun 2013, 19:44
by pendor