The timezone is an hour off, the date shows up in a format you never picked, and the blog index is stuck at ten posts when you want more. These are the small settings that quietly annoy everyone until someone fixes them, and hunting through the General and Reading screens for each one is more clicking than the change deserves.
This reads the current values, shows you the change, and writes only what you approve, all from a tight allowlist that cannot reach anything dangerous.
Read this site's basic settings and show me the current timezone, date format,time format, week start, and posts per page. Change nothing yet.
I want to set [the timezone to Asia/Karachi], [the date format to"j F Y"], and [posts per page to 12]. Show me each current value beside whatit will become, and wait for me to approve. Only after I say go, write thosesettings, then read them back to confirm each one took. If WordPress rejects orclamps any value, tell me plainly instead of reporting success.Why this is safe to run
The first step is a read. Pulling the current settings changes nothing, so you see each value beside its proposed replacement before a single one is written, and you approve the change.
The write is boxed in by design. The update ability accepts only a short allowlist: blogname, blogdescription, timezone_string, date_format, time_format, start_of_week, and posts_per_page. Any key outside that list rejects the entire call with nothing written. It can never change the site URL, the admin email, the default role, or open registration, however the request is worded. After saving, the agent reads the values back so a setting WordPress silently reverted shows up as a real failure rather than a false success. Reading and writing these both require the manage-options capability, so this runs from an administrator connection, and every write lands in the Activity Log.
Already connected? Skip the paste. From an admin connection, ask your agent for the “tune your basic site settings” recipe, or just tell it the timezone and formats you want, and it runs the same approve-first flow on your own site.