Every release of Enrove Folios, newest first. Sites that have it installed are offered each one on their Plugins screen.
0.7.0
Latest
Save a folio as a PDF through your browser's print window, and offer readers the same from the folio's contents menu. Sample content gets its photos back.
New
- Save a folio as a PDF: Save as PDF… in the folio editor’s Copy link menu, or on All Folios, opens the whole folio as one document in your browser’s print window, with its cover, a contents page and real, selectable text.
- Let readers save as PDF, under Publishing in the folio editor, adds a Save as PDF button to the folio’s contents menu. It is off by default, and a reader only ever gets what they could already read.
Fixed
- A Button block’s label was unreadable in every theme that colours the links in its page body, and so was the button of Enrove Proposal’s call-to-action block.
- Enrove Proposal had no style for code blocks.
- Enrove Newsletter’s contents panel cut off a long list on a short window.
- Enrove Proposal’s pages were wider than a phone’s screen.
- Sample content had no photos on a site installed from WordPress.org. A sample folio made on an earlier version keeps its empty images, so create it again.
0.6.0
Make folios from the posts and pages you already have, with classic-editor posts converted to blocks on the way in.
New
- Make folios from posts and pages you already have: Import posts and pages (in the folio editor’s Add Page menu) copies them into a folio as draft pages, and Import posts and pages… in the theme picker starts a new folio from them.
- Posts written in the classic editor are converted to blocks on the way in, so their paragraphs, headings, captions, galleries and embeds come across and their headings appear in the folio’s “On this page” list.
- The dialog says what will not come across before you add a post: a page builder’s layout, shortcodes, or a password. A post already in the folio is marked and can’t be added twice.
- You can copy only posts and pages you could already edit.
- The folio editor’s header menus look and behave like the block editor’s, and every Enrove dialog has the same header.
Fixed
- Enrove eBook, Magazine, Newsletter and Proposal garbled headings with accents or other non-English characters (“Café” showed as “Café”).
0.5.1
Security fixes: Contributors could publish folios, and pages of private folios were readable through the REST API. Fonts are now served from your site; press Download Fonts on Enrove → Settings → Fonts. Covers show a logo only if you choose one.
New
- First release on WordPress.org.
- Folios load their fonts from your own site, never from Google. Download them once from Enrove → Settings → Fonts, or use system fonts.
- A setup dialog the first time an administrator opens an Enrove screen offers the theme fonts and sample photos, and a Reset tab on Settings starts over.
- Covers without a photo show a soft gradient in the theme’s colours.
- No “Powered by” credit appears on folios.
- Installing themes from a .zip is removed; support for third-party themes is coming soon.
- A folio page’s block inserter offers only the blocks its theme styles, and the site’s WordPress theme no longer leaks into folios or the folio page editor.
- A folio’s pages go live with it. While a folio is unpublished, its pages can’t be published; unpublishing a folio returns its live pages to draft, and publishing it again brings them back as they were.
- Publish and Unpublish in the folio editor ask first, and say how many pages change with the folio.
- A page unpublished in a published folio leaves the folio’s navigation for everyone, its editors included.
- Folio covers show a logo only when you choose one; the Enrove wordmark is no longer added by default.
- Folios have a page title, and Contributors no longer see other people’s private folios in All Folios.
Security
- Contributors submit folios for review instead of publishing them, can open only folios they may edit, and can no longer add pages to other people’s folios.
- A published page of a private, password-protected or unpublished folio is no longer readable through the REST API, feeds, searches or the sitemap.
Fixed
- Duplicating a folio or starting one from sample content no longer drops backslashes from block settings.
- The folio editor fits a phone, and its remaining messages can be translated.
- Enrove Magazine now honours a folio’s font choices.
- The folio page editor’s content ran edge to edge on sites with a block theme.
0.5.0
Theme switches and theme removal now ask before hiding content, and publishing a folio no longer clears its collection tags.
New
- Change theme in the folio editor uses the same dialog as choosing a theme for a new folio.
- Switching a folio’s theme asks first when the new theme would hide blocks or proposal details, and nothing is applied until you press Switch theme.
- Removing a theme on Enrove → Themes asks on a second screen of the theme’s dialog, with a count of the folios that use it.
- The folio editor’s header shows Preview, Save, Publish and Copy link on every tab. Save is greyed out when there is nothing to save.
- Copy link on a draft folio copies the preview link until the folio is published.
- Publishing a folio no longer clears its collection tags.
- With reduced motion on, the Add New dialog no longer blocks clicks after it closes.
0.4.0
Security fix for headings in the eBook, Magazine and Newsletter themes, and published folios now return HTTP 200. Sample photos must be downloaded once from Settings → Imagery.
New
- Sample photos are downloaded on request (Settings → Imagery) instead of being bundled.
- Published folios are served with HTTP 200 instead of 404.
- Sample content works on PHP 7.1 and 7.2.
- CHANGELOG.md in the plugin folder has the full history.
Security
- Headings in the eBook, Magazine and Newsletter themes can no longer inject markup.