Bugzilla – Bug 13391
Need a page explaining 7.4 upgrade to users
Last modified: 2009-10-05 16:42:23 UTC
After users upgrade to 7.4, they will be instructed to visit www.squeezenetwork.com. www.squeezenetwork.com needs to redirect to a new page, www.mysqueezebox.com/upgrade. This new page will have a special design (very basic and stripped down); it might make sense to do this as a static HTML page? We need: - copy and (simple) artwork from product marketing and myself explaining new features to users - the page itself to be eventually implemented
assigning to Seth for copy.. reference screen (which will be updated) is attached to bug 13392
Assigning to Angela, who already has a draft of the initial portion of the copy for this page.
Copying Matthew. I believe he has added the copy for this to the CMS, but I don't know what page/"position" it has been set as. Matthew? Assigning to Michael to complete any necessary work related to Matt's design (see below). Michael, do you need the copy attached to this bug as well for any reason?
We don't need anything on www.squeezenetwork.com except for the automatic redirection, right? Is /upgrade a good choice? Shouldn't we make it something like /goodbyesqueezenetwork? I'd prefer some unique url which doesn't risk to be re-used at a later stage. /upgrade seems to geneeric and too similar to /update (which we already have). But that's a detail :-).
Matthew - what's the CMS key here?
(In reply to comment #5) > Matthew - what's the CMS key here? cms key: WHATS-NEW I agree with your point about a perma-link for this long-term since what's new could get used in the future. I'll put this in a unique position name for long-term use and append info to this bug.
http://localhost:3000/whatsnew CMS isn't ready yet?
== Auto-comment from SVN commit #7233 to the network repo by michael == == https://svn.slimdevices.com/network?view=revision&revision=7233 == Bug: 13391 +0.5 Description: add /whatsnew page. Still needs content defined.
The CMS has had this content for a while, but looks like there was a cache issue which gummed it up. Anyway, it's working now so SN should be pulling new content: http://cms.mysqueezebox.com/backend.php/content/get/?position=WHATS-NEW
assigning to QA for verification
This bug has been fixed in the latest release of MySqueezebox.com (formally known as SqueezeNetwork)! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.