Just noticed an odd sub-feature of the original 'cached pages' problem (which is still here).

Using IE7 on Windows (both Vista SP1 and XP SP2), if I save up a reference from a forum page, by right-clicking a link and choosing 'Open in New Tab', and then go back to the page I originally arrived from, the page refreshes and the yellow pages are cleared. Just an observation.

But it reminds me of an aggravation with the recent design changes on these boards. "Send message" (as in PM) is wrong. It doesn't send a message, it's a link to a message composition page. What I want to be able to do is to open the message form in a new tab by right-clicking, so I can keep my place on the forum page and refer back to it while I'm composing the private message. You can't do that with a button in IE7. (Workround - right-click to the user's account page, and PM from there - but I don't like unnecessary two-step workrounds).

But it reminds me of an aggravation with the recent design changes on these boards. "Send message" (as in PM) is wrong. It doesn't send a message, it's a link to a message composition page. What I want to be able to do is to open the message form in a new tab by right-clicking, so I can keep my place on the forum page and refer back to it while I'm composing the private message. You can't do that with a button in IE7. (Workround - right-click to the user's account page, and PM from there - but I don't like unnecessary two-step workrounds).

I agree. The buttons are used in all the wrong places...

I used to read big threads and middle-click (or ctrl-click) the Reply links to posts I planned to reply, and continued reading the rest of the posts. Then replied on the tabs I had accumulated. I can't do that anymore.

And yet many things that are actually actions and where buttons should be used (like logout) are still links! BOINC going backwards, how surprising.

---

"Send message" (as in PM) is wrong. It doesn't send a message, it's a link to a message composition page. What I want to be able to do is to open the message form in a new tab by right-clicking, so I can keep my place on the forum page and refer back to it while I'm composing the private message. You can't do that with a button in IE7.

I agree. The buttons are used in all the wrong places...

I used to read big threads and middle-click (or ctrl-click) the Reply links to posts I planned to reply, and continued reading the rest of the posts. Then replied on the tabs I had accumulated. I can't do that anymore.

And yet many things that are actually actions and where buttons should be used (like logout) are still links! BOINC going backwards, how surprising.

Do the buttons look nicer (especially the over-wide PM button on IE7) or are they supposed to be more straightforward to use for novices???

We could make a Boinc-wide poll to ged rid of the buttons and get links back. But whether it'd impress anyone in charge?

Peter

My most important reason for having anything done with the caching:

I'm subscribed to a thread. After getting a email notification on a new message here, I follow the link and reading the new message(s) (in IE7), possibly reply there... Afterwards I'll go somewhere else.

Later when another notification email comes, I'll grab the link and throw it to the same browser window. My thread gets opened, the message(s) I've already read are (still) marked as unread - and nothing else. I can think "Am I dumb? I've already read this!", delete the notification email and read other threads again. The thread gets forgot, no new notification will ever come (because someone might await my response on his post).

If I would get the idea, I'd manually refresh the thread page I was notified about, and - BINGO, there are really some new messages!

Try it out yourself. Drives me nuts sometimes.

Peter

CPDN Beta has:

<!-- SVN VERSIONS -->
<!-- $Id: translation.inc 14562 2008-01-15 22:22:08Z davea $ -->
<!-- $Id: pm.inc 14019 2007-11-01 23:04:39Z davea $ -->
<!-- $Id: team.inc 14394 2007-12-18 20:28:08Z davea $ -->
<!-- $Id: text_transform.inc 14264 2007-11-20 00:55:35Z davea $ -->
<!-- $Id: stats_sites.inc 14562 2008-01-15 22:22:08Z davea $ -->
<!-- $Id: user.inc 14546 2008-01-14 16:32:34Z davea $ -->
<!-- $Id: profile.inc 14562 2008-01-15 22:22:08Z davea $ -->
<!-- $Id: util.inc 14474 2008-01-06 18:09:23Z boincadm $ -->

CPDN Beta now has

<!-- $Id: translation.inc 14916 2008-03-14 21:40:18Z davea $ -->
<!-- $Id: pm.inc 14019 2007-11-01 23:04:39Z davea $ -->
<!-- $Id: team.inc 14394 2007-12-18 20:28:08Z davea $ -->
<!-- $Id: text_transform.inc 14866 2008-03-07 04:38:06Z boincadm $ -->
<!-- $Id: stats_sites.inc 15020 2008-04-06 03:15:36Z davea $ -->
<!-- $Id: user.inc 14626 2008-01-28 16:12:28Z boincadm $ -->
<!-- $Id: profile.inc 14866 2008-03-07 04:38:06Z boincadm $ -->
<!-- $Id: util.inc 14854 2008-03-06 00:40:48Z davea $ -->

and it's become as bad as the others. Any chance we could move forwards, instead of backwards?

And why do threads become 'unread' after ?31 days?

And why do threads become 'unread' after ?31 days?

It's then not necessary to notify you on any updates to these threads :-D

(Well, not really, if you omit the "On my Account page (no email)" notification type and choose any of the two "by email" options, you will be possibly spammed by notifications anyway... Where is the fourth (formerly only) option, getting notified just on the first unread post?)

Peter

...someone should open a Trac ticket suggesting that pages which should not be cached be given the appropriate HTTP headers directing that this be so?

Ticket [trac]ticket:626[/trac]

I'll leave the suggestions on someone more HTTP/PHP versed ;-)

Peter

The PHP session functions sent no-cache headers;
the fix was to send them ourselves.

Reminder: BOINC is an open-source project.
It's pretty easy to download the code and debug
problems like this, rather than complain that
"BOINC is going backwards" when a bug is found.

---

Reminder: BOINC is an open-source project.
It's pretty easy to download the code and debug
problems like this, rather than complain [...] when a bug is found.

Sure. I'd really try if I'd understand the functionality deep behind HTTP/PHP. (I do try if it concerns C/C++.)
Thus I'm at least trying to point out the problems to let those more versed to find and fix the reasons (testing part of debugging process).

So, anyway, thanks for the fix.

Peter