MontraFolio

Changelog

1.1.3

• The blocks are found by words in the site’s language. The search words of the three blocks — the ones the editor’s inserter matches — live in block.json, and the translation catalog did not carry them, so they stayed in English whatever the language of the site. The catalog now holds them, with the title and description written there too, and a language pack translates them along with everything else.
• The help under the address parameter reads as a pattern. The two lines that explain it — ?name={portfolio} and ?name={collection} — used angle brackets, which translators and their tools took for HTML and asked to keep untouched. Braces say what they mean: put the name of the parameter here and the address there, in any language.

1.1.2

• A changed icon is fetched again. The icon in the wp-admin menu, the one in the browser tab and the one beside the blocks in the editor were served from an address that never changed, so a browser that had already seen an older one went on showing it — sometimes long after the update, with nothing to explain why. They now carry the version of the file, as everything else the plugin serves already did.
• The three blocks now describe themselves on WordPress.org. Each block’s name, title, description and icon move into its own block.json, the file the directory reads — so the Blocks section of the plugin page tells what MontraFolio – Details, – Portfolio and – Collection each do, instead of listing only their names. Nothing changes in the editor: the same titles, the same descriptions and the same mark as before.

1.1.1

The name is written MontraFolio, with a capital F. It reads that way wherever the plugin names itself: the header WordPress shows, the titles of the three blocks in the editor, the menu of wp-admin, the settings screens, the export and the erasure of personal data, and the line above the title of the pages the plugin serves, for sites that did not put a name of their own there.

• Nothing that addresses anything changed. The folder of the plugin, the shortcodes, the blocks, the REST addresses and the private folder of the images are written exactly as in 1.1.0. A page built with 1.1.0 needs nothing done to it, and an update is only an update of the text.
• The translations were rebuilt with it, so the Portuguese and the Spanish name the plugin the same way.

1.1.0

MontraFolio. The plugin carries its name through everything it names: the blocks, the REST addresses, the folder the images live in and the graphics.

• It has a mark of its own. The monogram appears on the menu in wp-admin, in the tab of every page the plugin serves, and beside its blocks in the editor.
• The blocks and the shortcodes are named for it. MontraFolio – Collection, – Details and – Portfolio, and [mtfl_collection], [mtfl_details], [mtfl_portfolio]. A page built with an earlier set shows the blocks as unrecognised, and an earlier shortcode prints nothing, until each is written with these names.
• What the plugin stores is named for it too, and moves there on the first request after the update: the tables, the settings, the permissions granted by role and what each person’s account remembers. Nothing is copied and nothing is rebuilt — the names change and the rows stay where they are. In the one case where a table cannot move because a table of the new name already holds rows, every screen says so and neither set is touched.
• The private folder is uploads/montrafolio, and an earlier one is renamed to it on the first request after the update. Nothing is copied and nothing is rebuilt — the folder is renamed with everything in it, and the images go on being served from the same addresses. A site that named its own folder is left alone. In the one case where the rename cannot be done, every screen of the plugin says so plainly, names both folders and says that nothing was deleted.

• The REST addresses are montrafolio/v1. Only something written against them by hand would notice.

• Translations now come from WordPress.org instead of travelling inside the plugin. They are delivered as language packs and installed into wp-content/languages/plugins, the folder WordPress keeps for them — which means a translation now survives an update of the plugin instead of being replaced by it, and a site can put a language of its own in that same folder for a language nobody has published yet. Settings → Plugin → Plugin language, which makes the plugin speak a language the rest of the site does not, reads from there too; a language that is not installed reads in English. Until the packs for a language exist, the plugin reads in English unless its file is placed by hand — the manual says how.

• Every form and every address the plugin reads is now taken apart field by field, each value through the sanitizer that field deserves, instead of the request being read whole. Nothing a person does changes: what a form was allowed to save, it still saves, and what it refused, it still refuses. It is the reading itself that is narrower — a field the form does not have never reaches the plugin at all.
• The pages the plugin serves on its own — the sign-in, the portfolio area and the public galleries — now hand their stylesheets and scripts to WordPress instead of writing the tags themselves. Nothing a visitor sees changes: the same files load, in the same order, deferred as before. What it buys is that these pages are no longer invisible to everything that works through WordPress’s own asset list — a caching or optimisation plugin now sees them like any other page, and a site that wants to add a stylesheet of its own, or take one away, has a name to call it by.

1.0.1

• A portfolio now says it changed when its photographs change. The date each portfolio carries only moved when somebody edited a setting of it — a title, a description, a collection created or renamed. An afternoon of uploading moved nothing, so the portfolios that had seen the most work looked exactly like the ones nobody had opened in months. Two screens read that date and both were misleading because of it: the Updated column of the list in wp-admin, and the portfolio picker, which offers the most recently updated first when nothing is typed in it. Photographs arriving and leaving, captions written and images reordered now all move it, and those two screens say what actually happened.
• A collection’s date follows what its images say, and the order they are in. Images arriving and leaving already moved it. Editing a caption, an observation or a capture date moved nothing at all — an afternoon spent captioning a collection left it looking untouched — and neither did reordering by hand or arranging by capture time. All of those are printed on the public page, so all of them are changes now. What it buys today is that a Portfolio block set to Recent orders collections by when they last actually changed; what it buys later is a date worth trusting for anything that needs to know whether a collection is still what it was.

Nothing a visitor sees was changed by this version, and nothing needs doing on update.

1.0.0

First version published on WordPress.org.

What it is: portfolios of images for an organisation, one for each person who wants one and as
many shared ones as the staff need; collections shown as tiles or as a carousel; images kept in
a private folder the plugin serves itself, never in the Media Library; uploads from a phone’s
camera, resized on the device before they travel; limits at four levels; videos hosted elsewhere
added beside the images without a visitor being handed to anybody until they press play; a portfolio
area built for a phone, and management screens in wp-admin for whoever runs the site; the personal
data export and erasure of WordPress, a retention rule for portfolios nobody uses any more, and no
telemetry of any kind.

The development that got here — fifteen versions, from 0.5.0 to 0.9.5 — is in changelog.txt.