Black Friday: 30% OFF em todos os planos, já aplicado no carrinho Ver planos
Entrar Carrinho

Traslatability | Coming Soon and Maintenance Mode Changelog

Todas as versões registradas, da mais nova para a mais antiga, com o que mudou em cada uma.

Última 1.12.014 versões

Sem data · 14 versões

  1. 1.12.0

    Última
    1 novo13 alterações
    Novo
    • A preview link for each person, each with its own end. Access →
    Alterações
    • Preview Links lists your links: a name, the address to copy, when it ends
    • (never, or a date and time in your site's time zone), and the day it last
    • let somebody in. Remove shuts out only that link's holders from their next
    • visit, and New address gives one link a new address without touching the
    • others. An ended link lets nobody in, and the list says Ended. Your existing
    • link is the first row, Preview link, with no end and the same address, so
    • links already sent keep working. Exported settings files leave the links
    • out, and importing one keeps the site's own.
    • only then showed your page. While your page covers the whole site and new
    • accounts are refused, it now shows your page before anything is made, and
    • the link works once your page comes down. WordPress runs only
    • network-activated plugins on that page, so the plugin needs to be
    • network-activated for it.
  2. 1.11.0

    1 novo3 melhorias3 correções33 alterações
    Novo
    • Allow new accounts while your page is up. A switch in a new New
    Melhoria
    • Lighter admin screens. WordPress's Media Library and colour picker
    • Faster pages on sites in Spanish or French. The translations now
    • Opening the plugin's screens asks less of your server. To make
    Corrigido
    • New accounts wait until your site opens. With Anyone can register
    • No "deprecated" notice from Cloudflare's plugin when you save. With
    • Notes that should be hidden stay hidden. A hint or note a screen had
    Alterações
    • Accounts panel on the Access screen, off until you turn it on.
    • now load only on the Page and Design screens, which use them. The other
    • screens, and the screens the admin fetches ahead of a click, no longer carry
    • their scripts, about 55 KB of media templates or the database query listing
    • the months that have uploads.
    • also ship as PHP files, which WordPress 6.5 and later reads from PHP's code
    • cache instead of reading the translation file again on every page. Measured
    • on a French site with all fifteen of our plugins: 6.3 ms and 0.8 MB of
    • memory less on every request. Older WordPress reads the translations as
    • switching tabs instant, the plugin loads its other screens in the background
    • while you read the first one. It now loads at most four, the plugin's own
    • tabs first, and none while the browser tab is in the background; a tab past
    • the fourth loads as your pointer reaches it.
    • ticked under Settings → General, WordPress's registration form went on
    • making accounts while your coming soon or maintenance page covered the whole
    • site, and WooCommerce's My account form and checkout made them too. They are
    • now refused with one plain sentence: the registration form sends people back
    • to the sign-in form, which says why, and the Register link is gone; a shop
    • that sells to guests stops offering an account at checkout and the order
    • goes through as a guest's, while a shop that needs an account to order
    • refuses the order with the same sentence. On a network, wp-signup.php and
    • other page was shut, now show your page too. Signing in, resetting a
    • password, everybody you let in on the Access screen and anyone already
    • signed in are not affected, and nothing is refused in Shop closed for orders
    • or while your page covers only part of the site. Sites updating from earlier
    • versions get the same default: to take sign-ups before you open, tick Access
    • → New Accounts → Allow new accounts while your page is up.
    • WP_DEBUG on and a current version of Cloudflare's plugin, emptying its cache
    • printed a deprecation notice, which could stop a save from returning to its
    • screen. Cloudflare is now asked under its current name, and the old one only
    • on older copies.
    • hidden could still show, because the style that lays hints out outranked the
    • browser's own rule for hidden things. Hidden things on the plugin's screens
  3. 1.10.0

    2 novos2 correções1 de segurança21 alterações
    Novo
    • A Sign in link for the people you let in by role. Access → User Roles
    • Says when your sign-in page has been moved. If a plugin such as Login
    Corrigido
    • A page left open under Excluded addresses shows that page, and
    • Page caches are emptied only as far as a change needs. With LiteSpeed
    Segurança
    • Security or WPS Hide Login has moved your sign-in page, the Access screen
    Alterações
    • has a new switch, Show a Sign in link on the page, off until you turn it on.
    • It adds a Sign in link beside the password link that goes to your sign-in
    • page and back to the page the visitor asked for, and somebody signed in
    • whose role is not ticked is told so by name, with a Sign out link.
    • names the address under the new switch, because the link shows it to
    • everyone who sees your page.
    • nothing else, however the address asks. While your site was closed
    • ?pagename=&s= on a page you left open, in its address or in a form sent to
    • it, listed every post, page and product, because WordPress reads a word with
    • nothing after the = as a search for everything. With your front page left
    • open and a page chosen as your front page, adding ?order=asc or ?year= to
    • its address showed your latest posts. Those now get your closed page; your
    • front page, a campaign tag and a page number show as before.
    • Cache, a change to what visitors get, such as switching the page on or off
    • pressed its Purge All, which also deletes its combined CSS and JS files
    • empties the object cache and PHP's code cache, clears Cloudflare where
    • LiteSpeed is set to, and leaves "Purged all caches successfully." on your
    • next screen. It now empties LiteSpeed's cached pages only. On a network, WP
    • Super Cache is emptied for this site alone, where it emptied every site's
    • pages hold the other sites', and WP Super Cache's legacy copies, which it
    • always clears for every site).
  4. 1.9.1

    1 melhoria3 correções17 alterações
    Melhoria
    • The Dashboard says when Excluded addresses leaves your front page
    Corrigido
    • An address in another alphabet under Excluded addresses leaves that
    • A page left open under Excluded addresses shows that page, and
    • The launch email goes out as you typed it. A % followed by two
    Alterações
    • page open, and nothing else. Pasted from the browser, an address such as
    • /контакты/ was saved as //, which left your front page open to
    • everybody while the page you meant stayed closed, and a section such as
    • /блог/* as //*, which opened every page of the closed site. Addresses
    • are now kept as pasted and match however the browser writes their letters. A
    • line saved before keeps doing what it did: if Excluded addresses holds /, //
    • or //* that you did not mean, delete it and paste the address again.
    • nothing else. While your site was closed, a link to that page asking for
    • another post or a search in its query (?p=12, ?s=), or a form sent to it
    • with one, showed that content to everybody. Those now get your closed page
    • the =, such as ?pagename=&s=, or, with your front page left open, when a
    • word such as ?order=asc was added to it).
    • characters 0 to 9 or A to F was taken out of the subject and message when
    • you saved them, so an opening code typed as 20%DEAL went out as 20AL, and
    • anything in angle brackets went too. A subject or message saved before keeps
    • what was lost: check it and type the missing part again.
    • or every page, open, with a button to change it.
  5. 1.9.0

    1 novo4 correções13 alterações
    Novo
    • Once your site is open, the Dashboard tells you if WordPress still asks
    Corrigido
    • Updating while a Send from the Subscribers screen is going out no
    • A launch email your host stopped part way through a batch no longer
    • Reactivating or updating more than a week after the switch-off time
    • Saving Shop closed for orders on the Page screen, or a passed
    Alterações
    • search engines not to index it (Settings → Reading), with Let search
    • engines index it and Keep it hidden, and names a robots.txt file that asks
    • every search engine to stay away. Nothing is shown on staging, development
    • or local copies, or while your coming soon page covers the whole site.
    • longer stops it part way when the launch email is switched off. The rest of
    • your list is emailed.
    • counts as going out for good. Ten minutes after the plugin last heard from
    • it, the Dashboard offers it again.
    • now ends a launch email an earlier launch held for WooCommerce's store, as
    • the scheduled switch-off does.
    • switch-off time on the Settings screen, emails nobody if the number of
    • people waiting has changed since you opened the screen. The save still goes
    • through and says why nobody was emailed.
  6. 1.8.3

    2 melhorias4 correções28 alterações
    Melhoria
    • The scheduled switch-off no longer emails your list when it runs
    • Setting your store live in WooCommerce's own settings no longer
    Corrigido
    • Changing your site's time zone no longer upsets the scheduled
    • Putting your page back up stops a launch email that is still going
    • A question about emailing your list is answered only for the people
    • A launch email held for WooCommerce's store is no longer offered long
    Alterações
    • switch-off. After a change of time zone it could run hours early, do nothing
    • and be gone, or run hours late and email your list long after visitors could
    • see your site. Both scheduled jobs now move with the time zone. If an
    • earlier version already lost your switch-off this way, updating runs it
    • within a week of the switch-off time your list is emailed as it would have
    • been, and after that nobody is emailed and the Dashboard offers Send the
    • launch email, which asks first.
    • out. A long list is emailed 25 at a time. Pressing Enable, a save or import
    • that puts the page back up, or switching the launch email off while it was
    • going out left it telling the rest of your list that your site was live.
    • Sending now stops before the next email, and the message says how many were
    • not emailed.
    • it named. Disable, and Send to … not yet emailed and Send to everyone
    • again on the Subscribers screen, now say how many people they will email; if
    • somebody signed up since you opened the screen, they change nothing and ask
    • you to check and press again.
    • more than a week late. On a site nobody visits, WordPress runs its scheduled
    • tasks late. A switch-off run more than a week after its time now switches
    • the mode off and emails nobody; the Dashboard says how many were not emailed
    • and shows Send the launch email, which asks first. Reactivating the plugin
    • more than a week after a switch-off time does the same.
    • emails your list without asking. A launch email held for WooCommerce's Site
    • visibility stays held when you set the store live there, and the Dashboard
    • offers Send the launch email, which asks first. The Dashboard's Set Site
    • visibility to Live still asks and sends.
    • after the launch it was held for. A launch with the launch email off, or
    • with nobody waiting, now ends a hold left by an earlier launch
    • also a switch-off found more than a week late on reactivation or update).
  7. 1.8.2

    1 melhoria5 correções25 alterações
    Melhoria
    • Disable asks first while WooCommerce hides your store and the
    Corrigido
    • The Dashboard's buttons only go the way their label says. On a
    • A save after the switch-off time no longer cancels the opening.
    • Saving a switch-off time that has already passed switches the mode
    • "Without emailing" now means nobody is emailed. An OK to "Switch off
    • Importing a settings file with a switch-on time still to come no
    Alterações
    • Dashboard left open while the mode was changed in another tab, Disable no
    • longer switches the mode back on and Enable no longer takes your page down.
    • A press that finds the mode already that way changes nothing and says so.
    • Between the switch-off time and WordPress cron running, a save on any screen
    • threw away the scheduled opening: the mode stayed on and the launch email
    • never went out. A save now keeps it, unless it moves the switch-off time
    • turns automatic switch-off off or switches the mode on again. A site that
    • already lost an opening this way can send the launch email from the
    • Subscribers screen.
    • off. The settings, the Dashboard and your site now agree. Save asks first
    • and the launch email goes out only if you say yes; while WooCommerce hides
    • your store it then waits until you set the store live. A save never emails
    • your list for a time more than a week ago, and an imported settings file
    • with a passed switch-off time switches the mode off too.
    • without emailing them?" on the Dashboard, or to "Save without emailing" on
    • the Page screen, emailed the whole list if the launch email had been
    • switched on in another tab since you opened the screen, and a Disable press
    • that was never asked emailed them too. Both now carry the answer you gave
    • without a yes, nobody is emailed and the message says how many were not.
    • launch email is off. With people waiting, it asks whether to switch off
    • without emailing them, as the Page screen's Save already did, and afterwards
    • says how many were not emailed.
    • longer counts as your launch. Nothing is announced or held for later. A file
    • that takes your page down while WooCommerce hides your store now says the
    • launch email is waiting, instead of only "Settings imported."
  8. 1.8.1

    2 melhorias1 correção15 alterações
    Melhoria
    • "Keep taking orders" no longer says you are not taking orders. If
    • Closing the shop for orders over your coming soon page counts as
    Corrigido
    • Your launch email is no longer lost when the shop is closed for
    Alterações
    • orders. Setting your store live from the Dashboard while the shop is closed
    • for orders now sends the launch email that was waiting for WooCommerce's
    • Site visibility, after asking you first. Before, that email was thrown away.
    • asking.)
    • you left the notice as it was, it now says "Orders placed now are sent out
    • after" your reopening date, or "later than usual" when no date is set, above
    • the Add to cart button and on the cart and checkout. A notice you wrote
    • yourself stays as you wrote it. If your site uses a page cache, empty it
    • after updating.
    • your launch. Save asks whether to email your subscribers, as Disable does
    • and emails them only if you say yes
    • open while the launch email was switched on in another tab); while
    • WooCommerce hides your store, the email waits until you set it live. If
    • nobody was asked, nobody is emailed then, and the Dashboard suggests Send
    • the launch email.
  9. 1.8.0

    1 novo4 alterações
    Novo
    • Shop closed for orders. With WooCommerce, pause buying while every page
    Alterações
    • stays open and can still be found in search, and, with a switch-off time
    • set, tell shoppers the date you take orders again. Keep chosen products or
    • categories on sale, let chosen roles still buy, or only show the notice.
    • Nobody on your list is emailed when the shop reopens.
  10. 1.7.0

    1 novo3 correções1 removido12 alterações
    Novo
    • Subscribers has a tab for each state. All, Subscribed, Waiting for
    Corrigido
    • While confirmation emails are failing, the sign-up form no longer
    • Default words on the page follow the page's language. The headline
    • French counts zero in the singular. French writes "0 message", not "0
    Removido
    • Remove keep the tab, and a search with a plus sign or an ampersand in it
    Alterações
    • confirmation and Unsubscribed each have a tab with its count, so addresses
    • waiting to confirm can be listed on their own. A search, the page links and
    • comes back whole.
    • tells anyone who is on your list. Somebody already on the list is now sent a
    • short "you are already on the list" email and given the same answer as a new
    • address, so both depend on your mail in the same way. The first email that
    • goes out, from this plugin or any other on the site, clears the failure.
    • message, sign-up heading, button and thank-you line are no longer saved in
    • the language of whoever first saves the Page screen, so an English site set
    • up by somebody reading WordPress in Spanish shows them in English. Words
    • already saved stay exactly as they are.
    • messages", and the plugin's French now counts the way WordPress's own French
  11. 1.6.0

    2 novos1 melhoria1 correção18 alterações
    Novo
    • New subscribers can be asked to confirm their address. Switch on Ask
    • new subscribers to confirm their address under Page → Email Collection
    Melhoria
    • On some servers, "Your address is" now shows your own address
    Corrigido
    • A visitor is counted once when the server writes their address two
    Alterações
    • and each new sign-up is emailed a link and gets your launch email only after
    • following it. The only thing kept about the confirmation is when it
    • happened, addresses nobody confirms are deleted after 30 days, and the
    • Subscribers screen counts who is still waiting. It is off until you switch
    • it on, and people already on your list stay on it.
    • instead of your proxy's. On a server that writes IPv4 addresses the IPv6
    • way, behind Cloudflare or a proxy of its own, the address shown under IP
    • addresses that can see the site on the Access screen was the proxy's, such
    • as 127.0.0.1, and a line copied from it let in every visitor who came
    • through that proxy. It now shows your own address, and the copied line no
    • longer lets those visitors in, so they see your coming soon or maintenance
    • page. If the address shown has changed, put it in place of the old line.
    • ways. Some servers write a visitor's IPv4 address the IPv6 way, 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 sign-ups and on tries
    • at the password page; each visitor now has their own. On such a server
    • counts already running start again from zero, once.
  12. 1.5.0

    1 novo8 alterações
    Novo
    • Your own page while WordPress installs updates. While WordPress
    Alterações
    • installs an update it shows every visitor a plain "Briefly unavailable for
    • scheduled maintenance" message. Switch on Show your page while WordPress
    • installs updates on the Settings screen and they see your design and logo
    • instead, with a headline and message of their own, and search engines are
    • asked to come back a minute later. The panel says when your host or another
    • plugin's maintenance page stands in the way, Preview the update page shows
    • it before any update does, and on a network only a network administrator can
    • switch it on.
  13. 1.4.16

    3 correções14 alterações
    Corrigido
    • The Mailchimp and launch email failure notes no longer keep the
    • The sign-up button keeps keyboard focus while it sends. It used to
    • The documentation and knowledge base call the address field under
    Alterações
    • address of the person who was refused. Both notes on the Subscribers screen
    • quote what Mailchimp or your mail system said, and a refusal of one person
    • can name them. That address is now left out, and Tools → Erase Personal
    • Data takes it out of notes written before this update.
    • switch itself off while it held the focus, so focus fell out of the form and
    • keyboard and screen-reader visitors lost their place. It now stays on the
    • button, which looks dimmed and ignores a second press until the answer comes
    • WordPress loads them in no longer decides it, 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 them all
    • until that plugin is updated. An older plugin of ours can also no longer
    • stop this plugin's admin screens loading.
    • Access → Exclude by its name on screen, Excluded addresses. They used to
    • call it Excluded page addresses.
  14. 1.4.15

    2 melhorias4 correções29 alterações
    Melhoria
    • change, the chart listed one day twice or skipped one, and the totals
    • Repeating a search under Apply to or Exclude is answered without
    Corrigido
    • {name} in the launch email's subject now fills in the subscriber's
    • The thirty-day visitor chart, and the totals above it, count thirty
    • The search box on the Subscribers screen filters the list. Typing a
    • Moving between the plugin's screens no longer leaves the last one
    Alterações
    • name. A subject written as "{name}, {site} is open again" went to everybody
    • as "there, ...", while the message two lines below greeted each person by
    • name. A test send now shows your own name there as well, so you can see what
    • {name} does before the list goes out.
    • calendar days. Opened within an hour of midnight in the month after a clock
    • doubled or lost that day's views and sign-ups.
    • name or an address and pressing Search left the whole list on screen and the
    • box empty, with nothing to say why. The list now narrows to what you typed
    • your words stay in the box, and they go into the address as well, so a
    • filtered list can be bookmarked or sent to somebody.
    • could not read, the screen threw away the key and the list of sites using
    • it, and asked you to go and find the key again. It hit hardest where it
    • When a key is reissued, or deleted while a site still holds it, the box was
    • very screen the notice had just sent you to with "enter it again". You can
    • now paste the right key straight in.
    • box empty. None of the three reads what is in the box, but all three
    • have it put right, and one press picks it up instead of waiting hours for
    • the next automatic check. If the check cannot be made, the screen says why
    • and nothing here is changed.
    • working in the background. With a suggestion list open under Apply to or
    • Exclude, pressing the browser's Back button left the page pulling itself to
    • the top every time you scrolled. Screens you had moved away from also kept
    • their search boxes and tick lists listening, which held on to memory for
    • nothing.
    • going back to the server. On a site with more pages or products than the
    • plugin can hold in the browser, a term you searched a moment ago was asked
    • of the server all over again. It is now answered from what that screen
    • already has. On smaller sites the whole list is in the browser to begin
    • with, so nothing changes there.

Changelog publicado pelo desenvolvedor, no idioma original.