[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 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/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 • Mark as read Button
Page 1 of 2

Mark as read Button

Posted: 03 Apr 2013, 16:54
by Bobjespat
After manualy upgrading from 1.7.5 to 1.7.6 i must notice that the "Mark as read" Button is disappeared. Instead of this, there is now a third Dropdown Box. If i choose the first entry "Mark as read" -> Nothing happens in the article View. Is there a way to get the Button back?

Additionaly, is there a way to have a "Get new feeds" Button, to load new feeds manually?

Re: Mark as read Button

Posted: 03 Apr 2013, 16:55
by fox
Mark as read -> All articles. First entry is a caption, this is a limitation of how dropdowns work I'm afraid.

Re: Mark as read Button

Posted: 03 Apr 2013, 17:05
by Bobjespat
Ahh Ok. I understand.

Re: Mark as read Button

Posted: 03 Apr 2013, 17:37
by justauser

Re: Mark as read Button

Posted: 03 Apr 2013, 17:49
by idoxlr8
or... you could see this post about a plugin that has this and more

Re: Mark as read Button

Posted: 03 Apr 2013, 18:04
by linuxdaemon
Thank you for the button with date code. My preference is for that to be a single action, where the drop-down introduced a 2-step process. If the button and dropdown could be combined into one object, I think that would be the best UI for this type of interaction. Unfortunately I'm not sure how to accomplish that.

The interface I'm thinking of is like the "Font color" selection in Word (or Libre/Openoffice). You have a button that does the action, and a drop-down that selects the behaviour of that button.

Re: Mark as read Button

Posted: 03 Apr 2013, 18:06
by fox
Actually I think there's a control like that in Dojo, so this could be changed to perform like that.

Edit: fixed

See this is why trunk testing is important, if someone pushed for this earlier, it would've been done before 1.7.6...

Re: Mark as read Button

Posted: 03 Apr 2013, 18:51
by jakob42

Re: Mark as read Button

Posted: 03 Apr 2013, 19:34
by xtaz

Re: Mark as read Button

Posted: 03 Apr 2013, 20:56
by fox
jakob42,

>About that: I don't mind testing trunk before a release, but I prefer to run the stable build generally. 

If you pay any attention whatsoever you'll quickly notice that it's all meaningless anyway. The release is nothing more than a trunk snapshot with a tag attached.

I think i have recently explained why trunk stays usable minor issues notwithstanding.

xtaz,

>To be honest it sounds like that might actually be a lot easier than running individual releases.

That's what I keep telling people. Somehow they still prefer to fuck around with tarballs and whatnot.

Re: Mark as read Button

Posted: 03 Apr 2013, 21:55
by craywolf

Re: Mark as read Button

Posted: 03 Apr 2013, 22:11
by fox
>If (like me) you know your way around a linux system but aren't a developer and have never used a version control system, a tarball is far less intimidating.

To be fair it's really easy to learn all two basic commands: git clone and git pull. Branching is not much harder.

Re: Mark as read Button

Posted: 03 Apr 2013, 22:18
by craywolf

Re: Mark as read Button

Posted: 03 Apr 2013, 22:47
by xtaz
Been playing and so far worked out clone, pull, log -n2 <file>, status, and diff. The one thing I've been trying to work out and so far haven't is if you make a commit which I find breaks something and I want to locally revert it how do I go about doing that. On subversion I usually do svn log --limit=2 <file> to get the last couple of commits to that file including the revision numbers and then svn update -r <rev_number> to update the file back to that number. Anyone know what would be the git equivalent of that? It looks like I can do revert <commit_number> but that appears to do a commit to my local repository with the changes. Not sure if that's the correct way to do it or not.

*edit* Running trunk via git now for both tt-rss itself and the ttrss-mobile client. Which I know I can now keep up to date just by typing git pull in the appropriate directory. Still curious about my final question though. I know technically if there's any issue I should just report it on here and then pull the latest fix that fox makes, but if I want to get it working straight away what's the best way to revert the latest pull and go back to what I was using before, and then after fox fixes it go back to the master trunk copy again?

Re: Mark as read Button

Posted: 03 Apr 2013, 23:47
by Bobjespat
thx for both, the Codechange and the Plugin. Tryed both things, like the idea of the plugin, but the buttons are to big for my feelings. So i keep the Codechange. Maybe i create smaller buttons tomorrow and post them here.