diff --git a/ReleaseNotes.html b/ReleaseNotes.html
index 7b598e440..4ee9a8a8b 100644
--- a/ReleaseNotes.html
+++ b/ReleaseNotes.html
@@ -20,23 +20,22 @@ Wt Release notes
the way you build Wt, the way you configure Wt or the Wt API and
behaviour.
-Release 4.10.0 (TBD)
+Release 4.10.0 (May 30, 2023)
+
+
+ Wt 4.10.0 mainly features back-end improvements and some new features that provide some convenience.
+ There were some issues with persisting dates and time in Sqlite3.
+
+
+
+ In some cases user will have to change some things about their CMake set-up:
+ If users wish to use OpenGL, they may need to provide a GLEW installation with GLEW_ROOT,
+ since GLEW is no longer bundled with Wt.
+
+
+New features
- -
- Issue #11210:
- WTable::headerCount()
- has been made
const.
-
- -
- The obsolete CMake options
-
ENABLE_EXT, WT_NO_STD_LOCALE and WT_NO_STD_WSTRING
- were removed.
-
- -
- Issue #7814:
- The
SameSite attribute of the Set-Cookie HTTP header is now rendered by Wt. To avoid adding yet another parameter to the WApplication::setCookie() method, the class Http::Cookie was introducted that allows configuring all cookie attributes using setters. Objects of this type can be passed to the new setCookie() and removeCookie() methods in WApplication.
-
-
Issue #7279:
added WEmailEdit and
@@ -44,11 +43,20 @@
Release 4.10.0 (TBD)
a <input type="email">.
-
- Issue #11377:
- when using wtisapi with WebSockets enabled in the
wt_config.xml, Wt would
- try and fail to establish a WebSockets connection (this is not supported by ISAPI). Wt
- now disables WebSockets (and notifies this in the logs) when using ISAPI.
+ Issue #8760:
+ extended Auth::AuthWidget with the option to resend verificiation emails. When email verification is configured to be required and the email somehow got lost, the user would be stuck not being able to log in.
+ When the user tries to log in now, an info message will be shown saying they need to verify their email first along with a new button to resend the verification email. The user must then enter the email address again in a dialog before the email is sent.
+ The virtual methods AuthWidget::letResendEmailVerification() and AuthWidget::createResendEmailVerificationView() can be used to customize the UI.
+ -
+ Issue #7814:
+ The
SameSite attribute of the Set-Cookie HTTP header is now rendered by Wt. To avoid adding yet another parameter to the WApplication::setCookie() method, the class Http::Cookie was introduced that allows configuring all cookie attributes using setters. Objects of this type can be passed to the new setCookie() and removeCookie() methods in WApplication.
+
+
+
+Other improvements
+
+
-
Issue #11384:
it was possible for
@@ -62,24 +70,48 @@
Release 4.10.0 (TBD)
send() was fixed to log an error and return false instead.
-
- Issue #11376:
- fixed an issue with redirects when using wtfcgi.
-
- -
- Issue #8760:
- extended Auth::AuthWidget with the option to resend verificiation emails. When email verification is configured to be required and the email somehow got lost, the user would be stuck not being able to log in.
- When the user tries to log in now, an info message will be shown saying they need to verify their email first along with a new button to resend the verification email. The user must then enter the email address again in a dialog before the email is sent.
- The virtual methods AuthWidget::letResendEmailVerification() and AuthWidget::createResendEmailVerificationView() can be used to customize the UI.
+ WServer::addResource()
+ can now take a shared_ptr instead of a raw pointer,
+ enforcing that the resource lives at least as long as the server, unless removed with
+ WServer::removeEntryPoint().
+ The overload that takes a raw pointer is now deprecated.
+ This also fixes issue #11301, where there
+ could be a use-after-free in test.http.
-
Issue #11412:
shift-click to open a new window did not work for links to internal paths. Shift-click is now handled by the browser, like ctrl- and meta-click.
-
- Issue #11423:
- WResource::internalPath()
- now returns the empty string for static resources, since it doesn't make sense for static resources.
+ Issue #11604:
+ added a virtual destructor to WAbstractFormDelegate
+ to ensure proper deletion and explicitly removed the copy and move constructor and assignment operator.
+ -
+ Issue #11562:
+ The tutorials
+ (Wt,
+ Dbo, and
+ Auth)
+ were updated to be built with Asciidoctor instead of the legacy Python implementation,
+ its style was updated to match the JWt website style, and the text was brought up to
+ date a bit. The blog example was likewise updated to use Asciidoctor.
+
+ -
+ Issue #11210:
+ WTable::headerCount()
+ has been made
const.
+
+ -
+ The obsolete CMake options
+
ENABLE_EXT, WT_NO_STD_LOCALE and WT_NO_STD_WSTRING
+ were removed.
+
+
+
+Bug fixes
+
+
-
- WServer::addResource()
- can now take a shared_ptr instead of a raw pointer,
- enforcing that the resource lives at least as long as the server, unless removed with
- WServer::removeEntryPoint().
- The overload that takes a raw pointer is now deprecated.
- This also fixes issue #11301, where there
- could be a use-after-free in test.http.
-
Issue #11578:
fixed an issue with the Dbo forms not correctly validating
@@ -137,9 +160,15 @@ Release 4.10.0 (TBD)
correct it before saving the form.
- Issue #11604:
- added a virtual destructor to WAbstractFormDelegate
- to ensure proper deletion and explicitly removed the copy and move constructor and assignment operator.
+ Issue #11377:
+ when using wtisapi with WebSockets enabled in the wt_config.xml, Wt would
+ try and fail to establish a WebSockets connection (this is not supported by ISAPI). Wt
+ now disables WebSockets (and notifies this in the logs) when using ISAPI.
+
+
+ Issue #11423:
+ WResource::internalPath()
+ now returns the empty string for static resources, since it doesn't make sense for static resources.
Issue #10485:
@@ -150,14 +179,8 @@ Release 4.10.0 (TBD)
The GLEW_ROOT CMake variable can be used if it is installed elsewhere.
- Issue #11562:
- The tutorials
- (Wt,
- Dbo, and
- Auth)
- were updated to be built with Asciidoctor instead of the legacy Python implementation,
- its style was updated to match the JWt website style, and the text was brought up to
- date a bit. The blog example was likewise updated to use Asciidoctor.
+ Issue #11376:
+ fixed an issue with redirects when using wtfcgi.