23/10/2023 1:01:49
|
---|
|
Re: Standup Reportsworks for me. I'll get a first beta version ready for inclusion by the end of the week. |
_________________
|
18/11/2023 10:19:30
|
---|
|
Re: Standup ReportsPR waiting approval - Password reset: https://github.com/ImpressCMS/impresscms/pull/1527 Issue - Remove banner components from the db: https://github.com/ImpressCMS/impresscms/issues/1528 Issue - CKeditor customizations: https://github.com/ImpressCMS/impresscms/issues/1529 There are a few other improvements to work on. With these and the new theme from @fiammybe, I think we're ready for a release (RC) |
22/12/2023 9:13:46
|
---|
|
Re: Standup Reportscurrent score : 2 down, 1 to go (the new theme is a bit too ambitious before the end of the year). I'm looking in the CKEditor stuff now, might even just go for an update to CKEditor 5 if I can get that to run in a reasonable timeframe (next 2 days) |
_________________
|
23/12/2023 13:15:13
|
---|
|
Re: Standup ReportsFor CKeditor - config.js is part of the standard package from the developers (we've run into this with things we've done with Smarty, too). What's in there could be moved to formCkeditor.php |
1/1/2024 9:49:18
|
---|
|
Re: Standup ReportsThe editor integration is a bit messy, with in my view lots of times whee configuration is rebuilt and overwritten later in the loop. It's not as easy as I had hoped, so please bear with me as I try to make sense of it all ... I first tried to update the CKEditor version to v5, which is the current, supported, one. That version is not backward compatible with previous versions, which means that the entire integration would need to be rewritten. The javascript functions in the CKEDITOR object that replace a textarea on the page no longer exist, so I am now greeted with a nice, empty editor space That's something for later, after I get the v4 integration correct again. |
_________________
|
10/11/2024 20:10:53
|
---|
|
Re: Standup ReportsWe had scheduled to do another release this weekend, and during testing for some of the things we targeted for this release (2.0.0 beta 2), we discovered some other things we need to address. They're pretty straightforward issues, so we should have them sorted out by next weekend. Here's the list of issues we're working on. |