SoylentNews is people
SoylentNews
We just deployed a new point upgrade to rehash today to fix a bunch of small bugs that have been with us since the rehash upgrade and a few that were around longer than that. Here are the highlights:
- Fixes for various XSS isues by adding strip_title where appropriate in output templates.
- Fix PollBooth for Nexus support (found the bugs when cleaning up XSS issues).
- Fix broken daily mails by removing a utf decode that was unneeded since mod_perl 2 is better with utf8.
- Comment links now link to the the commentwrap div just above the comment.
- Commentwrap div's 'Reply' button now has verbage based on if we are on the story or on a specific comment.
- Add cert store location to Subscribe code to get rid of LWP errors and allow PayPal subscriptions to complete.
- Fix missing hit counts by adding accesslog back in (for editors and admins).
- Fix for unordered singoffs in story edit page (for editors and admins).
- Fix broken block save in admin.pl by setting defaults for not null table update (for admins).
We were able to kill off about 10 high priority bugs with this mini release. Current issues and feature requests can be found on GitHub and you can submit new issues or feature requests here if you have a GitHub account. We also welcome bugs and requests sent via email to admin@soylentnews.org or left in the comments below.
Our goals for the next major update is more of the same bug hunting and killing with a few features added here and there. Again I would like to thank you for your patience with the growing pains we have had with the 15_05 rehash upgrade. This update should bring us mostly back to where we were before in terms of broken features.
(Score: 2) by goodie on Wednesday June 17 2015, @01:55PM
RE: differences between dev and prod dbs: How did this happen? Didn't you test by taking a backup of prod and putting it in dev running only those scripts that were for the new version? Anyway, a good diff tool for database might come in handy for the future to check whether differences exist before doing the upgrade. My old company had SQL Compare for MSSQL, which could even generate a convert script one way or the other. For MySQL, looks like there is some stuff built-in too: http://dev.mysql.com/doc/mysql-utilities/1.3/en/mysqldbcompare.html [mysql.com] (not sure about the version). Or a simple script that compares two databases' catalogs could do that for you if you have basic objects only.
(Score: 3, Interesting) by paulej72 on Wednesday June 17 2015, @05:15PM
The current dev database is a copy of the production db from around last year at this time. Since then we have added vars and made schema changes as needed to provide for new features and bug fixes. These changes are supposed to be written to the sql/mysql/upgrades file to then be applied to production at the next deploy of the code. The problem arises when someone makes a change to the db but fails to add the change into the upgrades file. So we have both schema differences and some vars in the configuration table that are slightly different.
What we will probably do soonish is take another dump of the prod db and put it on dev to give us the same db again. Or we might just dump the schemas on both and do a diff.
Team Leader for SN Development
(Score: 2) by goodie on Thursday June 18 2015, @01:22PM
Thanks for the info! Maybe running a diff before upgrades could help if you have a code freeze period where you can validate those things. Because I imagine that it's the same type of issue that can arise with server configs etc. since none of that stuff is "built" and therefore fails to compile etc.