Changelog do Dark Mode by Traslatability

Correção

• Your theme's dark style is kept when you try another theme. Saving the Colours screen on a theme that has no dark style of its own no longer replaces the style you chose for your other theme, so switching back to that theme uses your style again.

Correção

• French counts zero in the singular. French writes "0 message", not "0 messages", and the plugin's French now counts the way WordPress's own French does.

Correção

• On servers that write addresses the IPv6 way, each visitor's presses count against their own limit. Some servers write a visitor's IPv4 address as ::ffff:203.0.113.7, and it is now read as 203.0.113.7 however it is written. On such a server behind Cloudflare or a proxy of your own, every visitor was taken for the proxy, so they all shared one limit on counting presses of the switch and, on a busy site, presses past it were left out of your usage statistics; each visitor now has their own.

Correção

• With several of our plugins on one site, licensing and updates run on the newest licence code among them. That no longer depends on the order WordPress loads them in, with one exception: while the first of our plugins that WordPress loads (usually the alphabetically first) is on a release from before this one, its older code still serves all of them until that plugin is updated. An older plugin of ours on the same site can also no longer stop this plugin's admin screens loading.

Correção

• Choices that were never counted. A visitor's choice is reported to the site with a quiet background message, which some browsers refuse to take, and the plugin then gave up instead of falling back to the ordinary request written underneath it. Those choices never reached Switches to dark or Share choosing dark on the Dashboard. It falls back now.
• The light and dark figures on the Dashboard cover thirty calendar days. They were counted back in fixed twenty-four hour lumps, so a clock change could make the window a day longer or a day shorter than it says. The sixty days of history kept behind them are trimmed on the right day too, which on a site west of Greenwich was a day late and left an extra day of rows in the database.
• A browser error on your pages when a visitor's choice could not be saved. For a signed-in visitor the choice is also saved to their account, and a request that did not get through, on a dropped connection or behind something blocking the site's API, came out as an uncaught error on the page and in whatever you watch front-end errors with. It is handled quietly now.
• The search boxes on Display Rules work when you reach the screen by its tab. Typing under Specific pages or Excluded pages brought up nothing at all until the page was reloaded. The Common exclusions ticks there also grey out again the places you have already chosen under Display on.
• A failed activation no longer clears the licence key you typed. When the licence server could not be reached while you were activating, the Licence screen threw away the key and the list of sites using it, and asked you to go and find the key again. Only an answer from the server about the key itself changes what is stored now.
• A key the licence server does not recognise can be replaced on the spot. When a key is reissued, or a licence is deleted, the notice on every admin page asks you to enter it again, but the Licence screen had locked the box and offered only "Deactivate this site". The box now stays open with the Activate button beside it, and the site count left over from the old key is no longer printed next to it.
• "Deactivate this site" and "Free" work with the key box empty. Neither of them reads that box, but pressing one was answered with "Enter your licence key first." and nothing happened. It caught the Free button beside each site on your licence every time, and "Deactivate this site" whenever the browser had not left the focus on it.
• Display Rules no longer fights your scrolling. With a list of suggestions open under Specific pages or Excluded pages, pressing the browser's Back button left the page jumping to the top every time you tried to scroll. Screens you have moved away from now let go properly, so their search boxes and tick lists stop running in the background.

Correção

• Your usage statistics cannot be padded by a stranger. The word a page carries so that a press can be counted is one per site and never changes, so anybody who opened a single page of your site could go on posting presses and leave Switches to dark and Share choosing dark saying whatever they wanted. One address may now count sixty presses a minute, and the rest are refused. Nothing about the visitor is written down: the counter behind that limit is named after a one-way hash of the address…
• Network activation sets up only the sites of the network you activated it on. On an installation running more than one network, switching the plugin on for one network also wrote its settings onto the other network's sites.
• Pressing "Check again" looks for a new version straight away. When the site could not reach our server, every one of our plugins stood down for fifteen minutes, and "Check again" on the Updates screen could not get past that wait. It now clears it, so the check happens when you ask for it.

Correção

• Saving the Colours screen keeps your colour scheme in charge. The four colour boxes show your scheme's colours when you have not chosen your own, and saving the screen without changing them stored those as your own choices. A colour that matches the scheme is now kept as "follow the scheme".
• A schedule that runs past midnight keeps to its days. In the Schedule panel, a Friday window from 22:00 to 02:00 now stays on until 02:00 on Saturday. It used to stop at midnight, and to come on between midnight and 02:00 early on Friday instead.

Correção

• The Dark mode switch block used a block format WordPress has deprecated. Since WordPress 6.9 the block editor warns about blocks built to the older format each time one is used, because the editor now runs inside a frame. The block now uses the current format, which it was already written for, so the warning is gone and nothing about how it looks or saves changes. Checked in the WordPress 7.1 editor: inserted, valid, and no warning.

Correção

• The switch and a prize-wheel launcher in the same top corner sat on each other. The bottom corners already stacked the two; the top corners now do too. Measured with both at top-right: one above the other, each pressable.

Correção

• The switch in a top corner stood under a top banner or bar. It now adds the height of whatever the range has pinned to the top of the window: a shipping bar, a cookie banner, WordPress's admin bar for anyone signed in, to its distance from the edge, as it already did at the bottom.

Correção

• A wp-admin that would not load when our licence server could not be reached. Each of our plugins checked for its own updates, and if the server was unreachable each one waited out its own fifteen-second timeout, so a site with several of them could spend minutes on a single admin page, twice a day, for something entirely outside its control. The first one to find the server unreachable now says so for the whole site, and the others stand down until it is worth trying again. Measured on a site…

Correção

• The switch tally was losing more than a quarter of what it counted. Every press read the running total, added one, and wrote it back, so two visitors pressing at the same moment both wrote the same number and one of them vanished. Measured on a test site: forty presses counted as twenty-three. Each day is now kept on its own and the database does the adding, so forty presses count as forty. It is also a much smaller write: the old shape stored sixty days of history again on every single press.

Correção

• The colour preview no longer jumps the page to the top when you click its sample link. It was a link that went nowhere by a means some sites block for safety; it is now plain sample text, which is all it was ever meant to be, and one less thing announced as a link that leads nowhere.

Correção

• "1 switches total" on the dashboard now reads "1 switch total". In Spanish and French as well.

Correção

• A setting that is waiting on another one is readable again. A field held back until you switch something else on is dimmed, so it does not look identical to one you simply have not used, but it was dimmed so far that its label and explanation fell below the contrast a person with ordinary eyesight needs. Measured on the rendered screen at 2.55:1 against the 4.5:1 minimum, and now 4.75:1 and 5.02:1. The greying, the sunken background and the blocked cursor carry the rest of the signal.

Correção

• The Audience panel heading had no icon. It asked for a mark the plugin did not carry, so it drew nothing and sat unmarked beside the panels that were.

Correção

• Two things on the Licence screen were never translated, the screen's own heading, and the "2 of 3" activation count. Both read in your language now.

Correção

• The shortcode documented values the panel above it does not use. It said style="round" while the Button Style panel calls it Circle, so typing what the screen said did nothing.
• A pasted web address saved and then matched nothing. Only the part after your domain name is ever compared. The field says so, and an address pasted out of the browser bar is reduced to the part that is matched, so old entries keep working.
• Latitude and Longitude gave no idea what a right answer looks like, and rejected values in silence. They now say what they take and what was not saved.

Correção

• Tabbing onto a "Remove" or "Undo" link showed the wrong ring, or none. Those quiet link-shaped buttons in a table row are WordPress's own kind, and WordPress rings them in its blue with a rule stronger than the one this plugin writes, strong enough that it also cancelled the ring the plugin draws. Somebody working down a screen with the keyboard either saw a colour that belongs to no part of this plugin, or lost sight of where they were altogether. They now wear the same ring as every other…

Correção

• The Basic method no longer leaves your theme's own words unreadable. On a standard WooCommerce shop it was painting the navigation at 1.4:1, the basket total at 1.2:1, a whole table as pale text on a white block at 1.2:1 and the footer credit at 3.5:1, because a theme's own colours and panels survived the darkening. The page is now dark all the way through, including a plain block of text a theme has coloured for a white page, which is most footers and most meta lines. Over eleven hundred…
• The preview drew Layers' and Bold's frames wrong. The preview on the Colours screen wears the scheme's shape as well as its colours, and the frame was the one part still painted from the palette: Layers, which has no frame at all, drew one, and Bold, whose frame is a two-pixel rule in the text colour, drew a quiet grey hairline. Both now show what the scheme actually does.
• Captions and quotation credits can be read. They kept the grey a theme picked for a white page, which measured 3.1:1 on a dark one. Each scheme now works out its own quiet grey and stops lifting it the moment it clears 4.5:1, so a caption is still quieter than the words above it.
• A form field on a dark page has an edge again. The colour was there and many themes drew no line at all to put it on, so the search box and the comment fields had no visible boundary under the Basic method. The colour now holds too: a theme that names its own field colour with a heavier rule than ours was leaving its light-page grey on a dark field, which on Bold meant a search box that was a hole in a black page next to a button with a white rule round it. Bold's fields are drawn with the…
• Layers and Bold draw the same under both methods. Under Basic, Layers' table steps and its raised buttons and Bold's two-pixel fields and outlined buttons were being overruled by the plugin's own darkening, so both schemes came out flatter than their swatch promised. Under Automatic, Bold's fields were given a two-pixel edge on a theme that had drawn no line for it to sit on, so there was nothing to see. Bold's code in a sentence is framed now as well, rather than being the one thing on that…

Correção

• The switch no longer disappears in a browser that blocks cookies and site data. A visitor whose phone was set to dark got a white page that then turned dark, with no button to turn it back. The page is now dark from the first paint and the switch is always there.
• The floating button no longer covers "Proceed to Checkout" on phones. It is left off the cart and the checkout, where it sat over the checkout button and the address fields; dark mode itself still applies there. You can turn this off under Toggle Button → Hide on cart and checkout.
• Plugin updates now reach visitors straight away. The darkening engine was loaded without a version number, so browsers and CDNs kept an old copy for years after an update.
• On a dark page the button stands out again. A dark button used to all but vanish once the page went dark; the lighter of your two button colours now becomes the button there, with the darker one as the icon.
• New sites show the colour scheme exactly as picked. Contrast now starts at 100% and Warmth at 0%, so True black is really black. Sites set up earlier keep their current look, and the Colours preview and its contrast figure now include Fine-Tuning, so they show what visitors actually see.
• Display Rules no longer offers a second schedule that looked like the dark-hours setting but hid dark mode instead, and that a page cache could freeze. For dark hours use General → Automatic Switching. A schedule you already saved still works and is shown with a note, so you can clear it.
• The default keyboard shortcut is now Shift+Alt+D. Alt+D is the browser's own "go to the address bar" key on Windows and Linux, so it is no longer offered, and a site that used it moves to Shift+Alt+D.
• The Dashboard no longer asks for a dark logo on a site that has no logo, and it now leads with Preview on site, so you can see your site dark straight away.
• The Links colour picker is greyed under the Automatic method, as Borders already was. There, links keep your theme's own colours, darkened.
• On a site translated with WPML or Polylang, a page's Dark Mode box now applies to its translations too, unless a translation has a setting of its own. A page set to never go dark was dark in other languages.
• The button shapes look as they should again. Since 1.2.4 a pill or rounded square with a label had its words pressed against both edges, and Minimal, the icon with no background, was drawn as a dark square. On a page darkened by Invert, Minimal's icon now turns light with the page rather than staying dark.

Correção

• Button text follows each visitor's language, whichever language saved it. A default label stored by an earlier save in one language, "Modo oscuro" say, was still shown as your own text to visitors in other languages, so French visitors saw Spanish. The default "Dark Mode" and "Light mode" are now recognised in every language the plugin comes in, and each visitor sees their own. Anything else you typed is still shown exactly as you typed it.

Correção

• The button now shows a sun once the page is dark. On the default icon-only button the moon stayed up in both states, so the button looked the same before and after it was pressed.
• Excluded Elements keep their colours under the Automatic method. Only colours written into the element itself were kept before; a badge or chart coloured by your theme's stylesheet was darkened with the rest of the page. Now each excluded element, and everything inside it, keeps its light-mode colours.
• Button text follows each visitor's language again. Saving any settings screen stored the default "Dark Mode" and "Light mode" in the language of whoever pressed Save, so a Spanish site with an English-speaking administrator showed English to every visitor. Empty fields now always mean the translated default, and a label stored that way by an earlier save is read as the default again.
• Importing settings from another site no longer carries its page rules across. Rules naming particular pages or categories pointed at whatever had the same number on the new site, so dark mode could vanish from an unrelated page. They are left out, along with the dark logo, and the message after the import says so. Importing a file this site exported keeps everything.
• Usage statistics now count presses on pages served from a page cache however long ago they were cached. They stopped counting a day or two after caching. Pages cached before this update go on counting for two weeks.
• "Sunset to sunrise" said it used the visitor's location. It uses the latitude and longitude you enter, and without them follows each visitor's device setting, which the screen now says. Without coordinates, a visitor whose device is dark also no longer sees a white page first.
• A page set to open in dark mode now does so while Automatic Switching is on. The schedule used to decide first, so the page was light outside the dark hours. The choice is now called "Open in dark mode".
• The Dark Mode box in the editor now works on the WooCommerce Shop page and on the page chosen as your Posts page.
• The toolbar switch shows a moon or a sun instead of an empty space, and appears on phones, where WordPress hid it.
• The contrast reading under the Colours preview is now in your admin
• Page rules: an excluded URL such as /contact/ now matches on a site installed in a subfolder or on a subdirectory multisite site; "Shop and product pages" now also covers brand and attribute archives; and a rule about the shop, cart or checkout is no longer turned into "Everywhere" while WooCommerce is switched off.
• Activating the plugin from an older WP-CLI or a site-management tool could stop with a fatal error.

Correção

• "Delete all data on uninstall" now also removes the licence key and the update records, which were left behind in the database.
• In the search-as-you-type picker, screen readers now hear "1 result" rather than "1 results".

Correção

• The Page weight card contradicted itself. Under the Invert and Basic methods it printed a size in kilobytes and then said "No additional assets" underneath. Every method loads the switch's own stylesheet and script; what those two skip is the darkening engine, and that is what it says now.
• The "No way to switch modes" warning claimed to know something it cannot. A menu item is a link in one of your theme menus, not a setting, so the plugin has no way of seeing it, and a merchant who had added one was told they had not, with no way to stop being told except switching on a button they did not want. It now says what it can actually see, and names the setting that acknowledges a placement you made yourself.

Correção

• The Colours screen offered every control to every method, and the three do not use the same things. On Invert you could pick a colour scheme, set four colours and watch a preview, and none of it changed anything on your site, Invert turns the page negative rather than recolouring it. On Basic the four Fine-Tuning dials did nothing, because that method writes a small stylesheet instead of filtering the finished page. Whatever the chosen method does not use is now greyed out, with a line saying…
• The Links colour was ignored in the one place it mattered most. If the darkening engine could not be downloaded, the plain fallback painted links a fixed blue: it asked for your colour through a variable that nothing ever set. It now uses the colour you chose.
• On a WordPress network, a site created after the plugin was installed had settings written into it whether or not the plugin runs on the network at all. A network using this on one site out of fifty was seeding all fifty.

Correção

• The usage-statistics endpoint accepted a count from anything at all. It has to be open, because a visitor pressing the button may be on a page served from a cache and there is no WordPress nonce to have, but that left an address anyone could point a script at, writing a row to your database on every request. Pages now send back a word the site issued, so a caller that never loaded a page is turned away. It is derived from the date and your site's own salt, it is the same for every visitor, and…

Correção

• Image dimming only worked under one of the three methods. The Automatic engine took it; Invert ignored it completely, and Basic dimmed every image by a flat six per cent whatever the field said, including when it said none. All three now do what the field says, which for most sites using Basic means images are no longer dimmed unless somebody asked for it.
• A user-role rule went on filtering after the screen stopped showing it. The role ticks on Display Rules appear only once "Signed in" is ticked, and whatever had been chosen before that carried on being applied from a panel nobody could see. A site that had once picked a role and then switched to "Signed out only" ended up with two rules cancelling each other out, one of them invisible, and nothing on the screen to explain why nobody was seeing anything. The rule now applies exactly when it is…