With #983260: Refactor chessboard_process_attached() in, we can get rid of the hardcoded options in chessboard_process_attached().
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | chessboard-options-in-render-element-983284-1.patch | 3.53 KB | eric_a |
With #983260: Refactor chessboard_process_attached() in, we can get rid of the hardcoded options in chessboard_process_attached().
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | chessboard-options-in-render-element-983284-1.patch | 3.53 KB | eric_a |
Comments
Comment #1
eric_a commentedComment #2
eric_a commentedWhen updating from earlier versions this code will be dealing with old data, effectively setting preprocess to TRUE, instead of the desired FALSE. As a result a new set of aggregrates may be created.
If we think this is bad, we need an update function.
Comment #3
eric_a commentedI'm not to keen on throwing database update routines for patch level updates.
This old data will live for 25 hours. Only sites that aggregrate css and update from a previous version of Chessboard Renderer will see the number of aggregates grow. Administrators may stop this by flushing their filter cache after updating.
Reported installs: 7 sites currently report using this module.
After some debating I decided to commit this and prepare for a new release.
Comment #4
eric_a commented