** Description changed: Binary package hint: wordpress I let ubuntu manage my wordpress install and I want to continue doing that. Thus, I don't think the built-in function from wordpress to inform about a new upstream release makes any sense and can easily be counterproductive. Somebody who is not so well-versed with the whole FOSS-process of upstream->debian->ubuntu might well be irritated that the software keeps telling about the available upgrade when "sudo aptitude" disagrees. executive summary (as per SRU wiki page, subheading "Procedure"): 2.1 impact: blog admin users are instructed to update which runs counter to the idea of a distribution to manage packages - 2.2 upstream dev branch: - this is not applicable upstream, the aim is to disable a feature which has a purpose but not in the context of a managed distribution + 2.2 dev branch: + fixed since version 2.5.1-5ubuntu1 in Intrepid, but there is a more elegant solution put forth here and suggested for the next Jaunty merge in bug 301340. The fix currently in Intrepid and Jaunty is only partial. 2.3 minimal patch see attached debdiffs. I worked together with james_w to iron out a few minor kinks still present in even the latest versions. To keep the bug-spam low, I did not attach them here. 2.4 TEST CASE: install and configure wordpress in hardy (I think the same thing should already be observable in Intrepid, too). log in as a blog admin. You are presented with a message that your installation of wordpress is out of date and you should update. 2.5 regression potential low. The patch disables certain portions of a page only visible to wiki admins. I guess the worst case would be that something becomes unbalanced and the page would not validate as HTML (I assume this indeed happened with the patch as it is now applied in Intrepid) for those users on administrative pages. Browsers are usually quite tolerant of incorrect HTML. pages served to regular visitors are completely unchanged.
** Description changed: Binary package hint: wordpress I let ubuntu manage my wordpress install and I want to continue doing that. Thus, I don't think the built-in function from wordpress to inform about a new upstream release makes any sense and can easily be counterproductive. Somebody who is not so well-versed with the whole FOSS-process of upstream->debian->ubuntu might well be irritated that the software keeps telling about the available upgrade when "sudo aptitude" disagrees. - executive summary (as per SRU wiki page, subheading "Procedure"): + + *** executive summary *** (as per SRU wiki page, subheading + "Procedure"): + 2.1 impact: blog admin users are instructed to update which runs counter to the idea of a distribution to manage packages 2.2 dev branch: fixed since version 2.5.1-5ubuntu1 in Intrepid, but there is a more elegant solution put forth here and suggested for the next Jaunty merge in bug 301340. The fix currently in Intrepid and Jaunty is only partial. 2.3 minimal patch see attached debdiffs. I worked together with james_w to iron out a few minor kinks still present in even the latest versions. To keep the bug-spam low, I did not attach them here. 2.4 TEST CASE: install and configure wordpress in hardy (I think the same thing should already be observable in Intrepid, too). log in as a blog admin. You are presented with a message that your installation of wordpress is out of date and you should update. 2.5 regression potential - low. The patch disables certain portions of a page only visible to wiki + low. The patch disables certain portions of a page only visible to blog admins. I guess the worst case would be that something becomes unbalanced and the page would not validate as HTML (I assume this indeed happened with the patch as it is now applied in Intrepid) for those users on administrative pages. Browsers are usually quite tolerant of incorrect HTML. pages served to regular visitors are completely unchanged. -- ubuntu wordpress should suppress the "please update" warning https://bugs.launchpad.net/bugs/227547 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
