Mime types broke my feeds

[Kourai]

I just update to the latest release, and since then, several of my feeds seems to be broken.

I Can't access them using firefox (it just download a text file).
Chrome seems to display the text file directly.

All of text files have something in comon and begin with 👍
<br /> <b>Warning</b>: is_file(): open_basedir restriction in effect. File(/etc/mime.types) is not within the allowed path(s): (/home/users3/j/[my_id]:/home/temporaire/upload:/tmp:/usr/local/lib/php:/usr/local/lib/ZFramework:/dev/urandom) in <b>/home/users3/j/[my_id]/www/kourai/rss-bridge/lib/contents.php</b> on line <b>172</b><br />

(Then, it's the regular
<?xml version="1.0" encoding="UTF-8"?> that I expected)

Most of the broken one are using the wordpress bridge, or the Instagram bridge.

I'm on a shared host, so there's no way I can modify my open_basedir configuration...

Any idea ?
(Other wise, I'll just rollback to the previous version!)

[ORelio]

Didn't know is_file could pose an issue on some shared hosts, that mean we need additional checks before calling that fonction. I'll look into this.

Meanwhile, please put error_reporting(0); on top of index.php to mute the warning, that should restore your feeds

[Kourai]

Works perfectly ! :)

Thanks!

[ORelio]

According to this thread (https://stackoverflow.com/questions/21427211/) there is no proper way of checking if a file can be accessed, other than manually parsing the open_basedir whitelist or muting errors on the is_readable function. Given that constraint, do you think it is reasonable to do this:

if(@is_readble('/etc/mime.types')) {
   //...

I know using @ is a bad practice but it seems like that's the only straightforward way...
Any thought on this, @logmanoriginal @teromene?

[teromene]

Would a try/catch block be able to silence this ? If not, I am OK with using @

[ORelio]

After some research, I managed to enable open_basedir restriction on my server to start investigating. A try/catch does not seems to do anything. According to this thread (https://stackoverflow.com/questions/1241728/) it is possible catch it by messing with error handlers, but that seems even more hacky than just using a single @. I'll fix it that way and leave a comment.

[logmanoriginal]

@Kourai Can you confirm the bug is fixed in master?

[Kourai]

Hey! Sorry for the delay, I wasn't home this weekend!
I just updated to master, and actualize all my bridged-feeds, and everything is fine! :)

Thanks again for fixing things so quickly! ❤️