WeDispatch 1.9.0: the WordPress plugin takes its place
The WordPress plugin moves out of Settings, gains its own screens, reads every content type and speaks French. On the service side, a rejected API key stops pretending to work. A tour of version 1.9.0.
This release comes down to one move: what used to be set elsewhere is now set where you work. Inside
WordPress for the most part, and in your client area for the rest.
New
The WordPress plugin has its own place in the menu, instead of sitting under Settings. Four
screens: Overview, Settings, My plan, Help and checks. The old address redirects, nothing needs
reconfiguring. The overview answers the three questions you actually have: is it connected, what is it
using this month, what is left to do. Every line is worked out on your site, not copied from a manual.
"My content and audio", one more screen. All your posts, pages and products, with their audio
state, the voice that will read them, and what remains to be done. Narrate or redo one item, or
several at once. A batch of fifty goes through the queue rather than the page: it no longer expires
halfway with nobody knowing what got sent.
The plugin no longer reads posts only. Pages, products, and any content type your theme declares:
you tick what should be narrated. Until now the rest was ignored in silence, and a site whose content
lives in pages got nothing, with no screen saying why.
A block and a widget, on top of the shortcode. The "WeDispatch audio player" block inserts from the
editor like any other, the widget places the player in a sidebar. The [wedispatch] shortcode is
unchanged.
The plugin is translated, and French travels with it. Its source strings move to English, as the
official WordPress directory requires, but a French settings screen does not change a single word.
Improved
Connection status sits at the top of every plugin screen, and it tells a rejected key apart from
an unreachable service. The two call for opposite moves: paste a new key, or simply wait. Confusing
them sends you regenerating a key that was never the problem.
A rejected API key no longer pretends to work. It used to receive the public voice catalogue: the
settings screen filled up and looked healthy while nothing could actually run. Along the way,
one-click connections from an assistant were also getting the default catalogue instead of their own,
without their signature voices. They now see the right one.
Release notes are no longer narrated. A release note is scanned, you look for one point in a
list; read aloud it becomes a list with no through-line. Feature articles keep their player.
"Sites & integration" no longer goes black. Opening the configuration of a site other than the
default one made the page disappear.
The service's most exposed path finally has a rate limit, and the ceiling for creating audio from
pasted text goes from three to twenty per hour: we were throttling the guided route, the one we
recommend, and leaving the other one wide open.
Automatic image description can say it does not know, rather than inventing a plausible detail.
And the "context" field now asks for the article title: it is the lever that changes the result most,
and nothing said so.
The player is announced to screen readers as a named landmark you can jump to, instead of hunting
for it in the page.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo