Thema: WordPress ...

[SiLæncer]

Release Notes

WordPress 5.1 Beta 3 is now available!

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.

There are two ways to test the WordPress 5.1 beta: try the WordPress Beta Testerplugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).

WordPress 5.1 is slated for release on February 21, and we need your help to get there!
Site Health Check

One of the features originally slated for WordPress 5.1—the PHP error protection handler—will target WordPress 5.2 instead. Some potential security issues were discovered in the implementation: rather than risk releasing insecure code, the team decided to pull it out of WordPress 5.1. The work in #46130 is showing good progress towards addressing the security concerns, if you’d like to follow development progress on this feature.
Additional Changes

A handful of smaller bugs have also been fixed in this release, including:

    TinyMCE has been upgraded to version 4.9.2 (#46094).
    The block editor has had a couple of bugs fixed (#46137).
    A few differences in behaviour between the classic block and the classic editor have been fixed (#46062, #46071, #46085).
    When adding rel attributes to links, ensure the value isn’t empty (#45352), and that it works as expected with customizer changesets (#45292).

Developer Notes

WordPress 5.1 has many changes aimed at polishing the developer experience. To keep you informed, we publish developers’ notes on the Make WordPress Core blog throughout the release cycle. Subscribe to the Make WordPress Core blog for updates over the coming weeks, detailing other changes in 5.1 that you should be aware of.

[close]

https://wordpress.org/

[SiLæncer]

Release Notes

The second release candidate for WordPress 5.1 is now available!

WordPress 5.1 will be released on Thursday, February 21, but we need your help to get there—if you haven’t tried 5.1 yet, now is the time!

There are two ways to test the WordPress 5.1 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip).

For details about what to expect in WordPress 5.1, please see the first release candidate post.

This release includes the final About page design. It also contains fixes for:

    New WordPress installs not setting the database table prefix correctly (#46220).
    A HTTP error occurring when opening browser developer tools (#46218).
    The legacy media dialog having incorrect pagination link styling (#41858).
    The comment form not appearing when clicking “Reply” on comments loaded via Ajax (#46260).

[close]

https://wordpress.org/

[SiLæncer]

Whats new:>>

Version 5.1 of WordPress, named “Betty” in honour of acclaimed jazz vocalist Betty Carter, is available for download or update in your WordPress dashboard.
Following WordPress 5.0 — a major release which introduced the new block editor — 5.1 focuses on polish, in particular by improving the overall performance of the editor. In addition, this release paves the way for a better, faster, and more secure WordPress with some essential tools for site administrators and developers.

https://wordpress.org/

[SiLæncer]

Changelog

WordPress 5.1.1 is now available! This security and maintenance release introduces 10 fixes and enhancements, including changes designed to help hosts prepare users for the minimum PHP version bump coming in 5.2.
This release also includes a pair of security fixes that handle how comments are filtered and then stored in the database. With a maliciously crafted comment, a WordPress post was vulnerable to cross-site scripting.
WordPress versions 5.1 and earlier are affected by these bugs, which are fixed in version 5.1.1. Updated versions of WordPress 5.0 and earlier are also available for any users who have not yet updated to 5.1.
Props to Simon Scannell of RIPS Technologies who discovered this flaw independent of some work that was being done by members of the core security team. Thank you to all of the reporters for privately disclosing the vulnerabilities, which gave us time to fix them before WordPress sites could be attacked.

Other highlights of this release include:

Hosts can now offer a button for their users to update PHP.
The recommended PHP version used by the “Update PHP” notice can now be filtered.
Several minor bug fixes.

[close]

https://wordpress.org/

[SiLæncer]

Infos zu dieser Version :  https://wordpress.org/news/2019/03/wordpress-5-2-beta-1/

http://wordpress.org/

[SiLæncer]

Infos zu dieser Version :  https://wordpress.org/news/2019/04/wordpress-5-2-beta-2/

http://wordpress.org/

[SiLæncer]

Infos zu dieser Version :  https://wordpress.org/news/2019/04/wordpress-5-2-beta-3/

http://wordpress.org/

[SiLæncer]

Infos zu dieser Version :  https://wordpress.org/news/2019/04/wordpress-5-2-release-candidate/

http://wordpress.org/

[SiLæncer]

Infos zu dieser Version :  https://wordpress.org/news/2019/05/wordpress-5-2-rc2/

http://wordpress.org/

[SiLæncer]

Infos zu dieser Version :  https://wordpress.org/news/2019/05/jaco/

http://wordpress.org/

[SiLæncer]

Infos zu dieser Version :  https://wordpress.org/news/2019/05/wordpress-5-2-1-maintenance-release/

http://wordpress.org/

[SiLæncer]

Infos zu dieser Version :  https://wordpress.org/news/2019/06/wordpress-5-2-2-maintenance-release/

http://wordpress.org/

[SiLæncer]

Infos zu dieser Version :  https://make.wordpress.org/core/2019/08/22/wordpress-5-2-3-rc-1/

http://wordpress.org/

[SiLæncer]

Changelog

    This security and maintenance release features 29 fixes and enhancements. Plus, it adds a number of security fixes—see the list below.
    These bugs affect WordPress versions 5.2.2 and earlier; version 5.2.3 fixes them, so you’ll want to upgrade.
    If you haven’t yet updated to 5.2, there are also updated versions of 5.0 and earlier that fix the bugs for you.
    Security Updates
    Props to Simon Scannell of RIPS Technologies for finding and disclosing two issues. The first, a cross-site scripting (XSS) vulnerability found in post previews by contributors. The second was a cross-site scripting vulnerability in stored comments.
    Props to Tim Coen for disclosing an issue where validation and sanitization of a URL could lead to an open redirect.
    Props to Anshul Jain for disclosing reflected cross-site scripting during media uploads.
    Props to Zhouyuan Yang of Fortinet’s FortiGuard Labs who disclosed a vulnerability for cross-site scripting (XSS) in shortcode previews.
    Props to Ian Dunn of the Core Security Team for finding and disclosing a case where reflected cross-site scripting could be found in the dashboard.
    Props to Soroush Dalili (@irsdl) from NCC Group for disclosing an issue with URL sanitization that can lead to cross-site scripting (XSS) attacks.
    In addition to the above changes, we are also updating jQuery on older versions of WordPress. This change was added in 5.2.1 and is now being brought to older versions.

[close]

http://wordpress.org/

[SiLæncer]

Infos zu dieser Version :  https://wordpress.org/news/2019/09/wordpress-5-3-beta-1/

http://wordpress.org/