WordPress updates from the chat, and messages that finish the job
Rekhu Builder 0.9.38 updates WordPress itself after you agree. A message now works until the job is done, within a cost per message you set.
Two changes for maintaining a site from the chat: WordPress itself can be updated there, and a long job no longer stops halfway.
WordPress updates, in two steps
Ask Rekhu Builder to update WordPress and it first tells you which version runs and which one is offered, and what to do before: a backup of files and database. Nothing changes until you say yes. Then it runs WordPress's own upgrader and checks that the home page still loads.
Plugins were already updated from the chat; now the core is too. When WordPress.org does not answer the site's update check, the chat says so instead of guessing.
A message works until the job is done
Until now one message stopped after a fixed number of steps, and a page rewrite needed "continue" several times. Now what limits a message is its cost:
- Cost per message. A message works until the job is done or the amount set under Preferences is reached, $2.00 unless you change it. Then it stops, says so, and "continue" goes on.
- Stuck means stop. When the same step fails three times in a row, the message stops at once and says which step and why, before it spends more.
- Fewer steps for the same work. Changes to an Elementor page are now sent together: rewriting the texts of three sections takes one change, not one per heading.
Discover, and Rediscover
After the first run, the Discover button on a project reads Rediscover. It reads the site again and replaces the Site profile, so the knowledge stays current after a big change.