Skip to main content

Rentiva 6.1.3 — Vehicle galleries stop disappearing

· 3 min read
MaxHandMade
MaxHandMade
Maintainer

If your vehicle detail fields were configured before 6.1.2, adding gallery images and pressing Update could wipe the gallery you had just added. 6.1.3 stops that, and it asks nothing of you: no database change, no re-saving of settings. Installing it is enough.

Two boxes that were never real fields — an empty Image and an empty Gallery Images — sat in the Vehicle Details grid on every vehicle screen. They looked cosmetic. They were not: the second one carried the same form field name as the gallery itself, and when two fields on a page share a name, the browser sends both and the last one wins. The empty box came last, so pressing Update wrote nothing over the gallery you had just uploaded.

6.1.2 stopped new sites from ever reaching that state, but it did nothing for sites already in it — and that is most sites that had saved their vehicle settings at least once. The reason it survived is worth one sentence: the code that decides which fields exist would invent a label for any name it did not recognise, and an invented label made an unrecognised name look like a real field to every check that came after it. It now discards what it does not recognise.

So if your site is affected, updating is the whole fix. The leftover entry stays in your settings and is simply ignored from now on.

One thing to know. If you clear a custom detail's name under Edit Names, that detail now disappears from the grid instead of showing under a name generated from its internal key. Nothing is deleted — typing a name again brings it straight back — and the public side of your site was already hiding such a field, so the two now agree.

Saving an ordinary page no longer writes booking data onto it​

A handler that stores booking information was listening to every save on the site rather than to bookings only. Saving an unrelated page or post could therefore write a booking status onto it. Nobody could reach data they were not allowed to reach — the check that was in place still asked whether you may edit that page — but the plugin was writing its own fields onto objects that were none of its business.

Fifteen handlers across vehicles and bookings now confirm what kind of post they are writing to before they write. One of them was a live path that could attach vehicle ordering data to any post it was pointed at.

An admin screen that fails now says so​

When a screen's data failed to load, some screens showed a short "something went wrong, please refresh" message and others simply went blank — a white area under the WordPress menu with nothing explaining it. Every screen now shows the message, and a check keeps new screens from shipping without it.

Under the hood​

Shared admin building blocks are now loaded from a common package rather than kept as copies inside Rentiva, and duplicated style declarations were consolidated. This was verified against a before-and-after comparison in both light and dark mode: nothing on your site renders differently.

6.1.1 and 6.1.2 were never published to the WordPress.org directory; everything they fixed is included here. The full history in both languages ships with the plugin.