[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 370: 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/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 • Heads up: Dojo 1.12 has landed in trunk
Page 1 of 2

Heads up: Dojo 1.12 has landed in trunk

Posted: 21 Jan 2017, 22:13
by fox
Thanks to efforts of Anders Kaseorg, Dojo (and a bunch of other third party libraries) has been upgraded to the latest version.

Everything seems to mostly work fine. However, there are a few minor (mostly cosmetic) issues. Also, other stuff might be broken. Who knows!

If you don't want to deal with this, don't pull latest trunk yet. Stay on c606bd or w/e instead for a few days while we iron stuff out.

If you did pull and are having problems please report in this thread. Thanks.

Known stuff:

(nothing right now)



Q: UI issues, missing icons
A: Refresh with Ctrl-Shift-R and/or clear browser cache:

Firefox: https://fakecake.org/uploads/2017/016wnhxo.png
Chrome: https://fakecake.org/uploads/2017/013xaWLf.png

Q: Clearing the cache doesn't help!
A: Check for obsolete custom CSS in preferences and/or custom themes. Don't be who wasted a lot of my time for nothing.

Q: My feed tree gone fucked up
A: Try deleting cookies from your tt-rss domain, the tree persists in a cookie which may get corrupted or incompatible with the new version

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 22 Jan 2017, 01:01
by AngryChris
The favicons are missing for me in the feed list on the left. I've cleared all my cookies for the domain of my server to no effect. Here's a small screenshot:

Capture.PNG
Capture.PNG (16.22 KiB) Viewed 5130 times

The favicons that would be to the left of the text 9to5Google, Ars Technica, etc, are now missing. The icons themselves are still where they're expected to be (feed-icons) and still owned appropriately (www-data:www-data).

I don't know how to confirm if I'm running the new dojo version or not but this issue started right after a pull.

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 22 Jan 2017, 01:20
by dariottolo


obviously clearing the cookies did solve the (non existing) issue.

Sorry

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 22 Jan 2017, 02:30
by Zottelchen

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 22 Jan 2017, 09:50
by fox

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 22 Jan 2017, 09:56
by udzguru

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 22 Jan 2017, 09:59
by fox

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 22 Jan 2017, 09:59
by fox

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 22 Jan 2017, 10:10
by udzguru
Quick update: I tried if the Android app worked. It worked out fine and I marked all unread articles read. Now the browser works again.

I am using PHP 7.0.13.

Will try to apply your suggested fix later and report back if any further problems occur.

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 22 Jan 2017, 10:15
by fox
yeah okay looks like it's the author of the gettext library being a retard and using is_int() for some unknown reason and thus not allowing php to automatically typecast the argument. i guess this check was added in the newer gettext library.

e: workaround for this should be in trunk, no need to manually edit anything

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 24 Jan 2017, 00:10
by pcause
Minor thing: When I right click on a category in the tree I get the two item pop-up, but the first item (mark read) isn't selected.

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 24 Jan 2017, 00:54
by martywd

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 24 Jan 2017, 07:45
by fox
there wasn't any special handling to select first menu item on open so i guess this is something Dojo has changed or maybe it's a bug with implementation of menus in tt-rss (although idk what it could be)

if you check http://archive.dojotoolkit.org/nightly/ ... ester.html the popup menus also don't have first item selected on open so maybe this is how it should work?

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 24 Jan 2017, 18:39
by nameless
Is it just me or does ttrss feel a little more responsive after upgrading to dojo 1.12?

Re: Heads up: Dojo 1.12 has landed in trunk

Posted: 24 Jan 2017, 18:43
by martywd