WordPress 5.2 Beta 3

WordPress 5.2 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 latest WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want […]

WordPress 5.2 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 latest WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).

WordPress 5.2 is slated for release on April 30, and we need your help to get there! Thanks to the testing and feedback from everyone who tried beta 2, nearly 40 tickets have been closed since then. Here are the major changes and bug fixes:

  • The new Site Health feature has continued to be refined.
  • Plugins no longer update if a site is running an unsupported version of PHP (see #46613).
  • It’s now more apparent when a site is running in Recovery Mode (see #46608).
  • The distraction free button no longer breaks keyboard navigation in the Classic Editor (see #46640).
  • Assistive technologies do a better job of announcing admin bar sub menus (see #37513).
  • Subject lines in WordPress emails are now more consistent (see #37940).
  • Personal data exports now only show as completed when a user downloads their data (see #44644).
  • Plus more improvements to accessibility (see #35497 and #42853).

Minimum PHP Version Update

Important reminder: as of WordPress 5.2 beta 2, the minimum PHP version that WordPress will require is 5.6.20. If you’re running an older version of PHP, we highly recommend updating it now, before WordPress 5.2 is officially released.

Developer Notes

WordPress 5.2 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers notes for updates on those and other changes that could affect your products.

How to Help

Do you speak a language other than English? Help us translate WordPress into more than 100 languages! The beta 3 release also marks the soft string freeze point of the 5.2 release schedule.

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.


Would you look at that
each day brings release closer
test to be ready
.

WordPress 5.2 Beta 2

WordPress 5.2 Beta 2 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.2 beta: try the WordPress Beta Tester plugin (you’ll want to […]

WordPress 5.2 Beta 2 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.2 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).

WordPress 5.2 is slated for release on April 30, and we need your help to get there! Thanks to the testing and feedback from everyone who tried beta 1, nearly 100 tickets have been closed since then. Here are the major changes and bug fixes:

  • We’ve added support for Emoji 12! 🪂
  • A brand-new wp_body_open() template tag (and corresponding wp_body_open action) will let themes (and plugins!) add content right after the <body> is opened (#12563).
  • Superfluous paragraph tags will no longer incorrectly appear in dynamic block content (#45495).
  • The Site Health screens have received several bug fixes, tweaks, and performance improvements.
  • Crash Protection no longer interrupts plugin editing (#46045).
  • Custom error handlers now load correctly (#46069).

Minimum PHP Version Update

As of WordPress 5.2 beta 2, the minimum PHP version that WordPress will require is 5.6.20. If you’re running an older version of PHP, we highly recommend updating it now, before WordPress 5.2 is officially released.

Developer Notes

WordPress 5.2 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers notes for updates on those and other changes that could affect your products.

How to Help

Do you speak a language other than English? Help us translate WordPress into more than 100 languages!

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.


The wonderful thing
about betas, is betas
are wonderful things.
🐯

WordPress 5.1.1 Security and Maintenance Release

WordPress 5.1.1 is now available! This security and maintenance release introduces 14 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 […]

WordPress 5.1.1 is now available! This security and maintenance release introduces 14 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.

You can browse the full list of changes on Trac.

WordPress 5.1.1 was a short-cycle maintenance release. Version 5.1.2 is expected to follow a similar two week release cadence.

You can download WordPress 5.1.1 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically.

In addition to the security researcher mentioned above, thank you to everyone who contributed to WordPress 5.1.1:

Aaron Jorbin, Alex Concha, Andrea Fercia, Andy Fragen, Anton Vanyukov, Ben Bidner, bulletdigital, David Binovec, Dion Hulse, Felix Arntz, Garrett Hyder, Gary Pendergast, Ian Dunn, Jake Spurlock, Jb Audras, Jeremy Felt, Johan Falk, Jonathan Desrosiers, Luke Carbis, Mike Schroder, Milan Dinić, Mukesh Panchal, Paul Biron, Peter Wilson, Sergey Biryukov, and Weston Ruter.

FlatPress 1.1 “Da capo” is here!

Hi all you FlatPress users out there!
I am more than happy to announce the release of FlatPress 1.1 “Da capo”.
For those who just can’t wait any longer: Proceed to download of FlatPress 1.1 “Da capo” (zip, 1.0 MiB)
What&#…

2019-02-22_flatpressisalive.jpg

Hi all you FlatPress users out there!
I am more than happy to announce the release of FlatPress 1.1 “Da capo”.

For those who just can’t wait any longer: Proceed to download of FlatPress 1.1 “Da capo” (zip, 1.0 MiB)

What’s new?

As stated in this blog entry, the new release is not completely new software. But it’s the stable foundation for all upcoming developments.

The most important steps - PHP7 and HTTPS support - were already done with the previous “emergency” release 1.0.3.php7. Now with 1.1, we took the time to fix a few more things, and to clean up a little bit. The BBCode toolbar has now graphical icons and knows a few more elements, some more languages are included, and a number of bugs and glitches have been fixed. Even one security fix is on board.

Please see the changelog for a complete list of changes.

“Da capo”?

Continuing the lovely tradition of naming FlatPress releases after music terms, I decided to go with Edoardo’s suggestion to call the new release “Da capo”.
That’s a well-matching name, since the FlatPress project was fallen asleep for more than three years, and is now revived with fresh energy. FlatPress is starting over again - or, as musicians put it: Da capo! :)

How does FlatPress continue from now on?

The FlatPress blogging engine will be evolved carefully, I do not plan to hastily stuff in crazy new things. Now that the stable release 1.1 is online, my main efforts will go into reviving the community. Coding will mainly be fixing bugs, refreshing outdated plugins et cetera.

What can you do?

As stated in my take-over posting, I can use every help I get.

  • Help me improving FlatPress.
    Send me in every bug or glitch you encounter while working with FlatPress. If you are familiar with GitHub, don’t hesitate to create issues there.

    Coders are very welcome to join the FlatPress team. If you have a bugfix or an enhancement for FlatPress, I’d be excited to receive your pull request on GitHub.

  • Join the community.
    We have a great new support forum, but it’s still quite empty. Use it to ask your questions, meet other FlatPressers, introduce your plugins and themes, or show off the blog sites you created with FlatPress.
    The most important thing for new FlatPress users is to find friendly help and support. Give them a warm welcome and answer their questions patiently - today’s newbies will be tomorrow’s pros.

    Also, you can help us to update and complete the contents of our wiki. The information there may be outdated, or linked sites may be gone 404 in between.

  • Spread the word.
    If you know a software archive or a CMS compare site that does not have FlatPress, tell them! Ask your web hosting provider if they’d like to offer FlatPress in their software installer. Recommend FlatPress to people asking you for an easy-to-use blogging engine.

After the last years of silence around the project, let’s remind the world of FlatPress again.





Image credit goes to Matthias - thanks a lot :)

New FlatPress website, forum, and wiki

Allright folks, after a few days getting everything running, here’s what we’ve got.
New forum!
Since the old one was broken, I started a completely new forum. Use it to ask your questions, meet other FlatPressers, introduce your plugins and…

Allright folks, after a few days getting everything running, here’s what we’ve got.

New forum!

Since the old one was broken, I started a completely new forum. Use it to ask your questions, meet other FlatPressers, introduce your plugins and themes, or show off the blog sites you created with FlatPress.
The most important thing for new FlatPress users is to find friendly help and support. Give them a warm welcome and answer their questions patiently - today’s newbies will be tomorrow’s pros.

New wiki!

The old wiki contained a lot of helpful information, but was also full of bot-registered spam users. I opened a new wiki and transferred just the contents (but not the users). So please re-register yourself and help us to update and complete the wiki contents.

New website!

Our project website got a renovation of its look and contents. Also, all flatpress.org content (including forum and wiki) is now served SSL-protected.

And as a little extra for our German-speaking users: Official German website!

New release?

Please be patient a few more days. My plan is to publish the new FlatPress release 1.1 still in february - let’s see if this works out!
When the new release is out, my next efforts will be to publicize it to CMS compare sites, download archives et cetera.

Feel free to get the latest development snapshot from GitHub and test it thoroughly. There will be only a few changes until 1.1 is complete.
Thank you very much for all the bug reports, suggestions, issues and pull requests I already received!

Thanks

A special “Thank you!” goes out to our friends at UD Media, who really like what we do here. UD Media generously supports the FlatPress project by hosting us, making our project revival possible.

Current status

Hello everybody,
there’s a lot of change going on in the FlatPress project lately – some of it you might notice, some not. I’d like to keep you folks up to date.
In short
Before I dive into the details, here’s the tl;dr for the impati…

Hello everybody,

there’s a lot of change going on in the FlatPress project lately - some of it you might notice, some not. I’d like to keep you folks up to date.

In short

Before I dive into the details, here’s the tl;dr for the impatient reader:
Not much to see for now, the big things will happen in February.




Still reading? Thank you :) Well then, let’s take a look at the details.

New FlatPress release

You may have noticed (and propably updated to) FlatPress release 1.0.3.php7. It looks and feels exactly like the previous release 1.0.3, but runs under PHP7 and supports HTTPS.
Use the update package to update your FlatPress instance from 1.0.3 to 1.0.3.php7, it’s really easy! (For update instructions, see the download page.)

The upcoming release 1.1 is actually quite finished (see the changelog); I’d just like to add a few more language packs. Feel free to get the latest snapshot from GitHub to play around with!
I plan to release FlatPress 1.1 in February, when we have the new forum online (see below).

Website

I did a little polishing on flatpress.org the last weeks; a shiny new version of this website will be published later. You guess the date: February.

Forums

The old Vanilla forum is quite outdated, and moreover, registration is broken. This sucks if you need (or want to provide) support :(
I will open a completely new forum - in February :)

Wiki

The FlatPress wiki is a great place to get information about FlatPress, or to download themes and plugins. But it’s also littered by spam users and content.
There will be a complete overhaul (February?^^); but since the user accounts won’t be transferred, you will need to re-register your account.

That’s it!

Did I forget something? Just ask me!
Oh, well: When the new website goes online, there will also be an official flatpress.org mail address - finally :)

I hope you guys out there feel good about the way this nice little open source project goes. Please send me your feedback and suggestions! And, more important: Spread the word - tell everybody that FlatPress will be new and fresh and shiny. In February ;)

All the best,
Arvid

Beta test for upcoming release

As a little pre-christmas treat, FlatPress is now available as version 1.0.3.php7. This marks the beta test version of the upcoming final release.
Go to download page!
Please contact me to report any bugs and suggestions.
What has changed since the las…

As a little pre-christmas treat, FlatPress is now available as version 1.0.3.php7. This marks the beta test version of the upcoming final release.

Please contact me to report any bugs and suggestions.

What has changed since the last version?

  • Runs under PHP7
  • HTTPS support
  • Plugins added: Last comments admin, Media manager

Update 1.0.3 to 1.0.3.php7

If you already have version 1.0.3 running, you may use the update package. Updating FlatPress from 1.0.3 to 1.0.3.php7 is quite simple.

  • At first: Create a backup of your blog. This enables you to rollback your changes in case of errors.
  • Simply unzip the update package and transfer its contents to your server. Overwrite existing files.