Two useful parameters you can edit from the config page in Firefox (type about:config in the address bar to access this page):
- Don’t highlight the domain name of the website: browser.urlbar.formatting.enabled = false (new in Fx 6)
- Always display the protocol of the page (including http://): browser.urlbar.trimURLs = false (new in Fx 7)
Now, does someone know a way for a sysadmin to easily stop notifications about new releases for all users on Mac OS X? At work, users do not have admin privs and so cannot do the updates themselves. As we get a lot of comments from our users that Firefox asks them to update, we need a way to force Firefox to shup up. Asking each user to edit their preferences to disable notifications is out of question. And it’s also out of question to update Firefox on 70 computers every 6 weeks (yes, a sysadmin’s weekly job is not to update Firefox all the time, especially when he works part-time!). Updates are usually only acceptable when everybody is on vacation, i.e. Easter, summer and Christmas mostly (which means every 4 months). But in 4 months, Mozilla releases 3 new versions of Firefox!! Hum…. too frequent updates, this reminds me another story about Firefox last year.
If you are like me and want to compile DBD::Oracle to use with Bugzilla and your installation of Oracle 10g XE, simply type the following command from the bugzilla/ root directory:
Of course, you must have installed oracle-xe-univ-10.2.0.1-1.0.i386.rpm already. This should save you a few headaches to make it work. :)
More than 3 months after our last releases, we finally released Bugzilla 4.1.3, 4.0.2, 3.6.6 and 3.4.12 last night. Bugzilla 3.6.6 and 3.4.12 are security releases for our old supported branches. Bugzilla 4.0.2 contains security fixes and several useful bug fixes, including:
- The Bug.create() WebService method now throws an error if you pass a group name which doesn’t exist. In Bugzilla 4.0 and 4.0.1, this group name was silently ignored, leaving your bug unsecure if no other group applied.
- Moving several bugs at once into another product works again. In Bugzilla 4.0 and 4.0.1, it displayed the same confirmation page again and again, and changes were never committed.
- Marking a bug as a duplicate now works in Internet Explorer 9.
- The XML-RPC interface now works with SOAP::Lite 0.711 and 0.712 under mod_perl.
- and much more!
I strongly recommend to upgrade to 4.0.2, which is much more stable and usable than 4.0 or 4.0.1!
And for those who love to live dangerously, we also released Bugzilla 4.1.3, our lastest development snapshot. It contains all the security and bug fixes mentioned above. As we don’t accept any new features for Bugzilla 4.2 since we released 4.1.2, we focused on fixing regressions and other nasty bugs. Bugzilla 4.1.3 should be much more usable than 4.1.2, even if it’s not production-quality yet. Depending on how things go and the feedback we get, this could be the last development snapshot before 4.2rc1. Note that once Bugzilla 4.2 is released (probably near the end of this year), Bugzilla 3.4 will reach End Of Life and we won’t support this branch anymore.