Dotclear NewsBlog management made easy2024-03-05T17:28:40+01:00Olivier Meunierurn:md5:970398d9af9827ce0594e9f36689ec4fDotclearDotclear 2.29urn:md5:496539fccfc6ba2b1501204cae9633cf2024-02-13T10:14:00+01:002024-02-13T10:14:00+01:00FranckNews <p>After several complicated versions for plugins and themes, this version 2.29 does not break compatibility for everything that was adapted for 2.28.</p>
<p>There are quite a few new features, but they are lighter than in previous versions. Of particular note is a new dashboard dedicated entirely to managing updates, which will help to better separate update-related processes from the rest of the code and avoid a complete multi-blog crash. You'll see it in action in the next version.</p>
<p>New features :</p>
<ul>
<li>Dashboard dedicated to update management.</li>
<li>Switch from JQuery to Vanilla for various javascript functions,</li>
<li>Ability to modify theme .php files,</li>
<li>Addition of behaviors (adminPostAfterButtons, adminPageAfterButtons),</li>
<li>Overhaul of image attributes (accessibility) inserted via editors,</li>
<li>Changes to styles on the admin side (particularly the buttons),</li>
<li>Numerous UI/UX/a11y tweaks (see <a href="https://git.dotclear.org/dev/dotclear/src/branch/master/CHANGELOG">CHANGELOG</a>)</li>
</ul>
Dotclear 2.28.1urn:md5:16a8523aa286d646c273531117aa14062023-11-19T08:46:00+01:002023-11-19T09:16:18+01:00FranckNews <p>Inevitably, we look everywhere, test a thousand times, and then a small typing error creeps into the well-oiled cogs and so this morning a small maintenance version with some light visible effect.</p>
<p>Yes, again :-)</p>
<p>PS: You should use safe-mode (as described <a href="https://dotclear.org/blog/post/2023/11/15/Dotclear-2.28">in previous post</a>) if you upgrade from 2.27.3 or lower version.</p>
Dotclear 2.28urn:md5:6fa22ea291a70c6788a1d3ae43e177f52023-11-15T10:24:00+01:002023-11-15T10:35:09+01:00FranckNews <p>The new version for the festive season.</p>
<h3>Be careful before updating!!!</h3>
<p>We strongly recommend that you perform the update <a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24">in rescue mode</a>, which will then allow you to update the plugins that need updating.</p>
<p>If some plugins have no updates available, we advise you to temporarily deactivate them (in rescue mode) and then check their operation one by one (one re-activation at a time) in normal mode.</p>
<p>If you have trouble logging in after the update, delete the associated cookies before refreshing the login page.</p>
<h3>What's changed</h3>
<p>It's essentially the internal code (the engine) that has been modernized, something we had already started with the latest Dotclear 2.27 and which is now complete, at least for the PHP code. We'll now be able to concentrate on new functionalities; more on that when the time comes.</p>
<p>On the visible side, we've added full support for the Avif format for images, alongside the already-supported JPEG, WebP, PNG and Gif, and we've fixed a number of small, more or less annoying bugs.</p>
<p>Don't forget the forum if you have any difficulties (comments are not for that), and in the case of more technical problems we may advise you to open <a href="https://git.dotclear.org/dev/dotclear/issues/new">a ticket</a>.</p>
Dotclear 2.27.3urn:md5:3772c5e7b8659a056b1376bc9246ce382023-08-31T16:34:00+02:002023-08-31T16:34:00+02:00FranckNews <p>A new version that corrects a few problems encountered with installation, plugin and theme dependency management, the password recovery procedure, flat export and when certain widget settings were incorrect.</p>
Dotclear 2.27.2urn:md5:728d5be15d0812fc494abebd637ea66b2023-08-22T11:06:00+02:002023-08-22T11:06:00+02:00FranckNews <p>A new maintenance release that includes a few fixes for errors encountered with previous versions <a href="https://dotclear.org/blog/post/2023/08/13/Dotclear-2.27">2.27</a> and <a href="https://dotclear.org/blog/post/2023/08/14/Dotclear-2.27.1">2.27.1</a>.</p>
Dotclear 2.27.1urn:md5:deb89fbf0a5f58b09b9c280ab7374ec52023-08-14T09:44:00+02:002023-08-14T09:44:00+02:00FranckNews <p>Inevitably, we look everywhere, test a thousand times, and then a small typing error creeps into the well-oiled cogs and so this morning a small maintenance version with no visible effect.</p>
Dotclear 2.27urn:md5:0efa53fceade10cc4893ae5a80225f0b2023-08-13T08:46:00+02:002023-08-13T08:46:00+02:00FranckNews <p>As is often the case, we'd planned for the best, but along the way we've become reasonable again, given our respective availabilities, with a few visible improvements and, above all, a lot of invisible work to modernize the code and get rid of old stuff.</p>
<p>This quarter, <strong>version 2.27</strong> introduces theme previews with the blog's current content, which can be useful for a visual check before activating a theme, and we've added and completed (with the help of translation engines) a few languages; but above all, this version <strong>is the last to support PHP 7.4 and PHP 8.0</strong>.</p>
<p>We therefore advise you to switch to <strong>PHP 8.1 or PHP 8.2</strong> if you wish to continue upgrading in the future. Note that not doing so will not prevent you from using 2.27 for a long time to come - it's up to you.</p>
<p>Finally, we'd like to wish DotClear a happy <strong>20th birthday</strong> with a capital C, as Olivier wrote in <a href="https://fr.dotclear.org/blog/post/2003/08/13/1-ouverture-du-site-dotclear">his announcement post</a> (in French)!</p>
Dotclear 2.26.1urn:md5:661c0499188527d815c8c29cfc11fa042023-06-04T09:15:00+02:002023-06-04T09:15:00+02:00Franck <p>A small maintenance release, as is customary after a major release, to resolve a few problems encountered since then.</p>
<p>The next major release (2.27) is scheduled for mid-August, which will also be the occasion to celebrate Dotclear's 20th anniversary, and you should know that this version will be <strong>the last</strong> to still support PHP 7.4.</p>
<p>Starting with 2.28, which will be released at the end of the year (mid-November a priori), you'll need at least <strong>PHP 8.1</strong> to run.</p>
<p>You can already prepare for this by switching to this version, or even better to 8.2, as Dotclear has been supporting it well for several versions now!</p>
Dotclear 2.26urn:md5:24cc0d7f77df39f5327e9d7bb8c715402023-05-13T06:26:00+02:002023-05-13T08:49:01+02:00FranckNews <p>A new version which update should pass without major problem for most of you.</p>
<p>Nothing extraordinary this time, mostly small improvements here and there, and it is especially on the side of the code that the main thing has been done because for the first time since the first version of Dotclear 2, the Clearbricks library is no longer part of it, or rather has been integrated directly into the code of Dotclear.</p>
<p>It was also the occasion to reinforce the unit tests and the static analysis of the code (with PHPStan, PSalm and Rector) which will continue to be progressively modernized (there is quite a lot left).</p>
<p>A new theme is under development and it should, if possible, be part of the next major release — which will also mark Dotclear's 20th anniversary —, but as we've often said here: "It will be when it is ready!".</p>
<p>Moreover, the redesign of the administration architecture is under study, in particular to benefit from the latest HTML and CSS possibilities. There might be some breakage, but we'll try to limit the damage, as usual.</p>
<p>Have a good update!</p>
Dotclear 2.25.3urn:md5:eaa097d7d8d30c569e94fc97e67472552023-02-25T09:16:00+01:002023-02-25T09:21:59+01:00FranckNews <p>An update that fixes some bugs encountered with the last 2.25.2.</p>
Dotclear 2.25.2urn:md5:1323fb525381c289187399f60472eb892023-02-19T09:14:00+01:002023-02-19T09:17:25+01:00FranckNews <p>An update that fixes some bugs encountered with the last 2.25.1.</p>
Dotclear 2.25.1urn:md5:7db99c2918b89df47980fee6da0458232023-02-18T13:09:00+01:002023-02-18T13:14:08+01:00FranckNews <p>An update that fixes some bugs encountered with the last 2.25.</p>
Dotclear 2.25urn:md5:dd6c43367f2b0f1ef0aa237723e5b5d12023-02-13T09:37:00+01:002023-02-13T17:54:38+01:00FranckNews <p>A new version of Dotclear for which you should encounter fewer problems, if any, than at the time of the update to 2.24.</p>
<p>This version essentially incorporates a code modernization - a modernization that should continue for a few more quarters.</p>
<p>It is possible that in the near future the required PHP version will change, especially to allow us to focus on code modernization. For now it is still PHP 7.4, but the 2.25 administration interface will tell you, if you are still using this version, that it is time to consider switching to PHP 8.0 or PHP 8.1, or even PHP 8.2 for which we have worked hard to ensure compatibility.</p>
<p>A small note to plugin developers: It was optional until now to define the module type in the <code>_define.php</code> file; it is likely that the future 2.26 will require it, so add this line in the properties:</p>
<pre class="brush: php">
'type' => 'plugin',
</pre>
<p>Take example on one of the plugins distributed with Dotclear if necessary.</p>
<p>The changelog of the 2.25:</p>
<ul>
<li>🐘 PHP 7.4+ is required, PHP 8.0/8.1 compliance (and as far as we know PHP 8.2)</li>
<li>Core: New plugin/theme code structure (using a brand new autoloader), old plugins/themes remain compatibles</li>
<li>Core: Clearbricks is now included in Dotclear code, not more as a git sub-module</li>
<li>Core: Update last step will not redirect to the safe-mode login page</li>
<li>Core: No more need to add namespace (blog-settings) / workspace (user-preferences) before using them</li>
<li>Core: Add possible using of external db driver (Experimental)</li>
<li>Core: Add support of .mjs ECMAScript module files</li>
<li>Core: Remove unnecessary and weak protection code</li>
<li>Core: Move some legacy and proxy code in dcProxyV2 plugin</li>
<li>a11y: Some aria attributes have been set in backend</li>
<li>Theme: Merge default smilies and blog's smilies (the blog's smilies have a higher priority)</li>
<li>Theme: Merge plugin blowupConfig into theme Blowup</li>
<li>Admin: Some jQuery javascript scripts have been rewritten in pure ECMAScript</li>
<li>Admin: Add Atkinson Hyperlegible font (used by default in admin, may be disabled in user pref)</li>
<li>Admin: Add some shortcuts (CTRL+letter) to dcLegacyEditor toolbar</li>
<li>Admin: Add a specific warning message on update page if necessary (breaking changes)</li>
<li>Admin: Cope with no user TZ defined (use UTC in this case)</li>
<li>Admin: Fix admin permission management for blogroll and pages plugins</li>
<li>Admin: Cope with float/double values in about:config and user:pref</li>
<li>🐛 → Various bugs, a11y concerns and typos fixed</li>
<li>🌼 → Some locales and cosmetic adjustments</li>
<li>📣 Warning: Next major release (2.26) may require PHP 8.0 (announced in backend) or PHP 8.1</li>
</ul>
Dotclear 2.24.1urn:md5:ed5f251201a4f023ae61e9775bfdb0ca2023-01-18T12:13:00+01:002023-01-18T12:21:15+01:00FranckNews <p>An update that fixes some bugs encountered with the 2.24 of last Christmas.</p>
Dotclear 2.24urn:md5:2d768fb5c1a1c568d6c5236937cb17c42022-12-24T10:00:00+01:002022-12-24T10:00:00+01:00FranckNews <p>The new version for the holidays. It is <strong>strongly</strong> recommended that you do <a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24">the update in safe mode</a>, which will then allow you to update the plugins that need to be updated.</p>
<p>If you have trouble logging in after the update, delete the associated cookies before refreshing the login page.</p>
<p>The 2.24 CHANGELOG:</p>
<ul>
<li>🐘 PHP 7.4+ is required, PHP 8.0/8.1 compliance</li>
<li>🗑 Remove XML/RPC system (keep only minimum for Pingbacks)</li>
<li>New blog parameter to close comments/trackbacks after a period of inactivity on the blog</li>
<li>Core: Large code review has been done, may break old code (3rd party plugins and themes)</li>
<li>Admin UI: New default icons for media items</li>
<li>Admin UI: Message look reviewed</li>
<li>Admin UX: Preserve current dir and current view of media manager</li>
<li>Admin UX: Password strength use an entropy indicator</li>
<li>Admin UX: Improve navigation in about:config and user:preferences list</li>
<li>Admin UX: Allow activation and de-activation of plugins in safe mode</li>
<li>Admin UX: Allow update of disabled/activated plugins in safe mode/normal mode</li>
<li>Admin UX: Add folding capability to widgets group</li>
<li>Theme: Cope with theme defined widget container format</li>
<li>Theme: Smilies are available for every theme (Blowup theme not more mandatory)</li>
<li>Lib: Update CKEditor to 4.20.1</li>
<li>Lib: Update Codemirror to 5.65.10</li>
<li>🐛 → Various bugs, a11y concerns and typos fixed</li>
<li>🌼 → Some locales and cosmetic adjustments</li>
</ul>
How to update to 2.24urn:md5:7e22347204e94f9525846490d369dd022022-12-13T15:26:00+01:002023-01-03T17:00:54+01:00FranckNews <p><img src="https://dotclear.org/public/feuille-dc.svg" alt="" style="width: 10em; margin: 0 auto; display: block;" /></p>
<p>We won't lie to ourselves, the next update could be ... sporty<sup id="fnref:4"><a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fn:4" rel="footnote">1</a></sup> :-)</p>
<p>I just tested several times, from an installation that runs in production (my <a href="https://open-time.net/">blog</a>) with Dotclear 2.23.1 and I noticed the following things:</p>
<ol>
<li><p>If you ever use the <a href="https://plugins.dotaddict.org/dc2/details/staticCache">static cache</a><sup id="fnref:2"><a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fn:2" rel="footnote">2</a></sup> plugin, <strong>disable</strong> it temporarily (just comment out the <code>DC_SC_CACHE_ENABLE</code> activation constant in the <var>inc/config.php</var> file, or set it to <code>false</code>).</p></li>
<li><p>Upgrading to Dotclear 2.24 in <strong>rescue mode</strong> is the best way to do it, once you know<sup id="fnref:3"><a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fn:3" rel="footnote">3</a></sup> that the plugins you use are <strong>available</strong> for 2.24<sup id="fnref:1"><a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fn:1" rel="footnote">4</a></sup>.</p></li>
<li><p>If you ever need the <a href="https://plugins.dotaddict.org/dc2/details/fakemeup">FakeMeUp</a> plugin, then log back in to normal mode, install it, run it, then log back in to rescue mode.</p></li>
<li><p>Make way for <strong>updates</strong>:</p>
<ol>
<li>Upgrade <strong>Dotclear to 2.24</strong> (still in <strong>rescue mode</strong>),</li>
<li>Reconnect in <strong>rescue mode</strong> because the previous step will bring you back to the authentication page<sup id="fnref:8"><a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fn:8" rel="footnote">5</a></sup>,</li>
<li>Do the <strong>update plugins</strong><sup id="fnref:7"><a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fn:7" rel="footnote">6</a></sup>,</li>
<li><strong>Reactivate</strong> the static cache if necessary,</li>
<li>Reconnect in <strong>normal mode</strong>.</li>
</ol></li>
</ol>
<p>This should be all good!</p>
<p>Take the opportunity to <strong>clear the template cache</strong> and <strong>the static cache</strong> (Maintenance plugin).</p>
<p>A little extra: it may be useful to install the <a href="https://plugins.dotaddict.org/dc2/details/growUp">growUp</a> plugin to clean up a bit<sup id="fnref:5"><a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fn:5" rel="footnote">7</a></sup> once the update is done<sup id="fnref:6"><a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fn:6" rel="footnote">8</a></sup>.</p>
<p>Anyway, we'll be around if there is a problem; on <a href="https://forum.dotclear.org/">the forum</a> in particular.</p>
<div class="footnotes">
<hr />
<ol>
<li id="fn:4">
<p>To be honest my first attempt ran into a problem with the static cache (see item 1 in the list), otherwise I was able to do the update in normal mode without any trouble. <a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fnref:4" rev="footnote">↩</a></p>
</li>
<li id="fn:2">
<p>Especially if you use it, like me, aggressively. <a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fnref:2" rev="footnote">↩</a></p>
</li>
<li id="fn:3">
<p>Install the <a href="https://plugins.dotaddict.org/dc2/details/checkStoreVersion">Check store version</a> plugin, it will tell you all that. <a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fnref:3" rev="footnote">↩</a></p>
</li>
<li id="fn:1">
<p>If not, wait until they are, it's better! <a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fnref:1" rev="footnote">↩</a></p>
</li>
<li id="fn:8">
<p>The authentication page may not be displayed, in which case delete the cookies associated with the site and refresh the page. <a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fnref:8" rev="footnote">↩</a></p>
</li>
<li id="fn:7">
<p>Force the update check to make sure you don't miss anything. <a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fnref:7" rev="footnote">↩</a></p>
</li>
<li id="fn:5">
<p>This is normally done during the update, but sometimes things can happen ;-) <a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fnref:5" rev="footnote">↩</a></p>
</li>
<li id="fn:6">
<p>It can be disabled or uninstalled afterwards. <a href="https://dotclear.org/blog/post/2022/12/13/How-to-update-to-2.24#fnref:6" rev="footnote">↩</a></p>
</li>
</ol>
</div>
Dotclear 2.23.1urn:md5:06f05a374eaef0ac5a90d5e58fbb68722022-08-13T10:02:00+02:002022-08-13T10:02:00+02:00FranckNews <p>And in the meantime, a maintenance version to correct a bug with the addition of comments.</p>Dotclear 2.23urn:md5:69f383be4676616073071e038d413c102022-08-13T09:02:00+02:002022-08-13T09:02:09+02:00FranckNews <p>The new version for this quarter with some improvements in the program mainly in the core code, but not only.</p>
<p>Note the disappearance of the management of icon sets, little used and potentially complicated with the use of icons in SVG format in two versions (light and dark theme).</p>
<p>The CHANGELOG of 2.23 :</p>
<ul>
<li>🐘 PHP 7.4+ is required, PHP 8.0/8.1 compliance</li>
<li>🗑 Remove Iconset management</li>
<li>Admin UI: Harmonize font size on different support (laptop, tablet, mobile)</li>
<li>Admin UX: Group more logically buttons on CKEditor toolbar</li>
<li>Core: New constant DC_DEFAULT_THEME, set to 'berlin'</li>
<li>Core: Use predefined constants for post statuses (dcBlog::POST_*)</li>
<li>Core: Use predefined constants for comment statuses (dcBlog::COMMENT_*)</li>
<li>Core: Deprecated global $core (or $GLOBALS<a href="https://dotclear.org/blog/post/2022/08/13/'core'" title="'core'">'core'</a>), use dcCore::app() instead</li>
<li>Core: Deprecated global $_ctx, use dcCore::app()->ctx instead</li>
<li>Core: Deprecated global $_lang, use dcCore::app()->lang instead</li>
<li>Core: Deprecated global $mod_files, use dcCore::app()->cache<a href="https://dotclear.org/blog/post/2022/08/13/'mod_files'" title="'mod_files'">'mod_files'</a> instead</li>
<li>Core: Deprecated global $mod_ts, use dcCore::app()->cache<a href="https://dotclear.org/blog/post/2022/08/13/'mod_ts'" title="'mod_ts'">'mod_ts'</a> instead</li>
<li>Core: Deprecated global $_menu, use dcCore::app()->menu instead</li>
<li>Core: Deprecated global $__resources, use dcCore::app()->resources instead</li>
<li>Core: REST server now accepts JSON format (experimental)</li>
<li>Fix: Use relative URL for attachments as far as possible</li>
<li>Fix: Remove select hiding mechanism when help is displayed</li>
<li>Fix: Loading of modules (plugins/themes) in safe mode</li>
<li>Fix: Message position on Quick entry submit (dashboard)</li>
<li>Fix: Select appearance on Safari (webkit engine)</li>
<li>Lib: Update CKEditor to 4.19.1</li>
<li>Lib: Update Codemirror to 5.65.7</li>
<li>🐛 → Various bugs, a11y concerns and typos fixed</li>
<li>🌼 → Some locales and cosmetic adjustments</li>
<li>📣 Warning: Internet Explorer is not more officially supported (may still work weirdly)</li>
</ul>Dotclear 2.22urn:md5:472914aec440775a2cee66215f54a0582022-05-13T08:19:00+02:002022-05-13T08:19:00+02:00FranckNews <p>The new version for this quarter — we're keeping up, that's a good thing — with some improvements to the program:</p>
<ul>
<li>🐘 PHP 7.4+ is required, PHP 8.0/8.1 compliance</li>
<li>Remove anti-FLoC system</li>
<li>Add a live preview button to standard Dotclear editor (wiki syntax)</li>
<li>Use native Javascript in scripts shiped with Berlin and Ductile theme (no more need jQuery)</li>
<li>Improve retrieval of origin metadata on Webmention or Pingback</li>
<li>Add a "Reset to now" button near the publish datetime input field (post/page)</li>
<li>Reduce number of CSS mediaqueries' breakpoints to 3 (mobile, tablet, laptop) for backend</li>
<li>Add a sticky position to "quick access to section" menu for about:Config and user:Prefs</li>
<li>Toolbar icons reviewed for standard Dotclear editor</li>
</ul>Dotclear 2.21.3urn:md5:4add8dccf8f05ff543d19fdb570105842022-03-07T10:18:00+01:002022-03-07T10:25:42+01:00FranckNews <p>A new version that fixes two bugs concerning the management of users other than administrators (or super-administrators).</p>