Description
Syrus AI brings a set of AI assisted tools into the WordPress admin:
- AI Translate — translate a post of your own site into another language from the editor sidebar. The translation becomes a draft linked to the original, with its categories, tags and featured image; nothing is published and the original is untouched.
- Social sharing — when a post is published, generate a caption for it and share it on the connected Facebook, Instagram, X/Twitter and LinkedIn accounts. Which posts get shared is decided by category and tag.
- Contact forms — build a form, place it with the
[syrus_contact_form]shortcode, protect it with Cloudflare Turnstile and have submissions emailed to the address you choose. - AI featured image — generate the featured image of a post from its title and content.
Under Tools there is a second set, for running the site rather than writing it. None of it involves AI, and each one is off until you configure it:
- Code injection — add markup to the head, to the footer, around the body of an article and between its paragraphs, without editing the theme. A single post can opt out of any of it.
- Editorial checks — thirteen rules an article has to satisfy before it can go public, each one a switch. A post that breaks one goes back to Pending with the problems listed in the Publish box.
- Content filters — strip the markup Word and Google Docs leave behind, and rewrite http:// links as https://.
- robots.txt and ads.txt — serve both files from the database instead of uploading them.
- WhatsApp chat — a bubble in the corner of the site that opens a conversation on WhatsApp. It works with any theme.
- Maintenance — close the comments on older posts, drop their revisions, clear the spam and empty the moderation queue, and restrict who may upload files.
Under Security there is a third set, for the requests that reach the site rather than the content on it. Every one of these is off until you switch it on:
- Hardening — the HTTP security headers, including a Content-Security-Policy you write yourself and can test in report-only mode first. Block
?author=Nenumeration, switch XML-RPC and pingbacks off, close the theme and plugin file editors, and stop WordPress announcing its version number. - HSTS — tell browsers to use HTTPS for this site from now on. It asks for a confirmation, because it is the one setting here that can make a site unreachable.
- Login protection — lock an address out after a number of failed logins, and throttle password-reset requests, over a fixed window with thresholds you choose. It covers wp-login.php, the REST API, application passwords and XML-RPC, and a login that succeeds clears the count.
- Custom login address — move
wp-login.phpsomewhere only you know. The new address is emailed to the administrator, shown in the administration until you switch the feature off, and refused if a file, post, page or term would collide with it. Deactivating the plugin brings the standard login page back. - REST API — hide the public routes that list your posts, pages, media, comments, terms and users, while leaving the block editor and anyone who can edit posts working.
Nothing under Security writes to a file, edits .htaccess or wp-config.php, installs a drop-in or contacts any server.
Credits / Resources
This plugin bundles the following third-party assets:
- Select2 4.0.13 — MIT — https://select2.org/
- SweetAlert2 11.7.18 — MIT — https://sweetalert2.github.io/
External Services Info & Usage
This plugin relies on a proprietary server that brokers the calls to the third-party services, so the plugin itself holds no credentials for them beyond the API keys you enter. Communication uses REST over HTTPS and JSON, authenticated with a token unique to each installation. The only data sent for authentication is the domain the plugin is installed on.
-
https://developers.syrus.it/api/wp/v1/install and /uninstall
Registers and deregisters the installation, returning the token that authenticates every later call. Sent on activation and on deletion.
Terms of Use: https://syrusindustry.com/wordpress/plugin/syrus-ai/terms-of-use -
https://developers.syrus.it/api/wp/v1/{facebook,instagram,twitter,linkedin}/share and /revoke, and /auth_url
Publishes a post on a connected account, connects an account and revokes its token. Sent when you publish a post with sharing enabled, or act on the Social Network screen.
Terms of Use: https://syrusindustry.com/wordpress/plugin/syrus-ai/terms-of-use -
https://developers.syrus.it/api/wp/v1/import/configuration
Imports the plugin configuration from another installation, when you paste a configuration token.
Terms of Use: https://syrusindustry.com/wordpress/plugin/syrus-ai/terms-of-use
The AI provider you connect under Settings > Connectors is called directly by WordPress’s own AI Client, with the key WordPress holds: which service that is, and its terms, depend on the provider plugin you installed.
-
https://api-free.deepl.com/v2/translate
Translates text, using the DeepL key you enter. Sent when you translate an article.
Terms of Use: https://www.deepl.com/pro-license
Privacy Policy: https://www.deepl.com/privacy -
https://challenges.cloudflare.com/turnstile/v0/siteverify
Verifies the captcha of a contact form submission, when Turnstile protection is enabled for that form.
Terms of Use: https://www.cloudflare.com/website-terms/
Privacy Policy: https://www.cloudflare.com/privacypolicy/
Privacy
Contact form submissions are emailed to the address configured for the form and are not stored in the database. The values shown on the thank-you page are held in a transient for five minutes and then discarded.
The login rate limiting stores a counter per visitor address, keyed by a hash of that address salted with this site’s own keys: the address itself is never written to the database, and the row expires with the window. Nothing else about the request is kept, no address reaches either log table, and none of it leaves the site. The email about a changed login address goes to the site’s own administration address through WordPress.
The plugin logs its own activity in two tables: a readable log of what it did, and a technical log of the requests to the AI services, which contains the prompts and the answers. The credentials are masked. If the content you translate or generate carries personal data, that data is in the technical log too, so consider it when setting your retention policy.
Installation
- Upload the
syrus-aifolder to/wp-content/plugins/, or install the plugin from the Plugins screen in WordPress. - Activate it from the Plugins screen.
- Connect an AI provider under Settings → Connectors: that is where WordPress keeps the keys, and this plugin reads them from there. With the Syrus theme active, the plugin appears under the theme menu as AI Support.
Entering the API keys requires administrator permissions. The rest of the plugin is available to editors.
FAQ
Which API keys do I need?
None are stored by this plugin. Text and image generation go through the AI provider you connect under Settings → Connectors, which is WordPress’s own screen: install one of the provider plugins listed there, paste the key once, and every plugin on the site can use it. DeepL registers itself in the same screen and is optional — when it is configured it does the translating, otherwise the AI provider does. Social sharing goes through the Syrus backend and needs no key of its own.
Does deactivating the plugin delete my data?
No. Up to version 0.4.5 it did: deactivation dropped all four tables. Since 0.5.0 the data is removed only when the plugin is deleted.
Enable the schedule in Settings, pick the hour, then have an external scheduler call the URL shown under Scheduler URL on that same screen. The URL carries a secret key that authenticates the call, so keep it private.
I switched on the custom login address and I cannot log in
The address was emailed to the site’s administration address when you saved it, and the administration showed it in a notice until you left. If both are gone: deactivate Syrus AI from the Plugins screen while you are still logged in somewhere, run wp plugin deactivate syrus-ai over SSH, or rename the plugin folder over SFTP. Any of the three brings wp-login.php back. The address stays saved, with the switch off, so nothing is lost.
I am locked out after failing the login
Wait out the window — five minutes with the default settings — or, from another browser where you are still logged in, press Clear now under Security → Login protection. Deactivating the plugin also clears it. If the whole site gets locked out at once, the site is behind a proxy and every visitor shares one address: switch on Visitor addresses behind a proxy and name the header your proxy sets.
Why is the Content-Security-Policy field empty?
Because a policy that suits every site does not exist, and one shipped as a default would either break sites or allow everything. The field shows a starting point as placeholder text, which is never saved on its own, and the report-only switch lets you watch what a policy would block before it blocks anything.
Why is my contact form rejecting submissions?
Check the language filter under Settings. It discards submissions from browsers that do not declare it-IT. It is off by default, and was unconditional before 0.5.0.
Screenshots



Changelog
1.2.0
- A Security section, with what was in the private Syrus Security plugin. Hardening: the HTTP security headers, a Content-Security-Policy you write yourself with a report-only mode to test it, HSTS behind a confirmation, the block on
?author=Nenumeration, XML-RPC andsystem.multicall, pingbacks, the theme and plugin file editors, and the WordPress version number. Login protection: a limit on failed logins and on password-reset requests, over a fixed window, covering wp-login.php, the REST API, application passwords and XML-RPC. REST API: the public routes that list posts, pages, media, comments, terms and users can be hidden from anonymous requests. Every one of them is off until you switch it on. - The login page can be moved away from
wp-login.php. Unlike the plugin this came from, there is a way back: the new address is emailed to the administrator, an administration notice keeps showing it until the feature is switched off, the address is refused if a file, post, page or term would collide with it, and deactivating the plugin restores the standard login page while keeping what you typed. - The error reporting of that plugin is deliberately not included: it sent the visitor’s address, the whole of
$_POSTand the logged-in user’s name and email address to a configurable endpoint. No new server is contacted by this release, and nothing new was added to the external services list. - Nor is its PHP session switch: it opened a session on every request, which breaks page caching sitewide, and nothing in the plugin ever read one.
- Three things that plugin did not have, added while porting: the file editors can be closed, the pingback header and endpoints can be removed, and the login form can be made to stop saying whether it was the username or the password that was wrong.
- The known bugs of the original are fixed rather than carried over. The lockout window is fixed instead of sliding, so a slow attempt can no longer hold a lockout open indefinitely, and a successful login clears the count. The client address is read from the connection unless you say the site is behind a proxy, so one attacker behind a CDN no longer locks out every visitor. XML-RPC is recognized by its own request constant instead of by a substring of the URL, which used to answer 403 to a post whose slug mentioned it. Only the core’s own
ver=is stripped from asset URLs, never a plugin’s or a theme’s. A blocked XML-RPC request now answers 403 with a fault a client can read, where before it answered 200 with an empty body. The password-reset limit lets through as many requests as it says it will, where before it stopped one short. Andreadme.htmlis reported rather than pretended to be blocked: the web server serves that file without ever running PHP. - A site that ran Syrus Security is offered a one-time import of its settings, in the same shape as the import from the theme: it lists what it found, says where each value came from and where it will land, and writes only what is ticked. The login address and HSTS are imported with their switches left off. Nothing is deleted on either side, so the old plugin still works if it is reactivated.
1.1.0
- The settings the Syrus theme left behind can be imported. When the theme handed these features over, the data stayed in the database and every screen came up empty: robots.txt, ads.txt, the injected code, the editorial checks, the content filters, the Twitter Card, the WhatsApp chat, the DeepL key and the list of users allowed to upload. A new screen under Tools lists what it found, says where each value came from and where it will land, and writes only the items that are ticked.
- A notice in the administration says so once, on a site that has something to import, with a link to that screen and a way to say no. Nothing is imported on its own, and the theme’s own options are never changed or deleted, so the import can be run again and a site can still go back to the old theme.
- The per-post settings come over too: the posts that opted out of an in-article block, and the editorial checks already recorded on each post, so the warnings stay where they were.
- The line breaks of robots.txt and ads.txt are restored on the way in. The theme stored both files with their newlines escaped, which is why pasting the old value by hand produced a single line.
1.0.1
- The contact form on the front end is styled by the plugin at last. It was written in Bootstrap classes the plugin never loaded there, so it looked right only on a theme that happened to bring Bootstrap with it and came out as a bare stack of inputs everywhere else. It now carries a small stylesheet of its own, loaded only on a page that shows the form, scoped so it reaches nothing else, and built on custom properties a theme can redefine.
- The summary shown on the thank-you page was in the same state, and it gave up entirely unless the theme had a container with a particular id. It now finds the main container of any theme, and falls back to the end of the page.
- The form no longer needs jQuery on the front end.
- Fixed:
[syrus_contact_form]without an id, which is the form the documentation shows, raised a PHP notice. It now renders nothing, quietly, as it should. - Fixed: the consent checkbox had no id and no name, and its label pointed at neither, so selecting the label did not tick the box.
- Fixed: two forms on the same page gave their fields the same ids. The ids now carry the form’s own.
- Fixed: in the editor’s preview, changing several fields quickly could leave an older preview on screen.
- The last Bootstrap class names left anywhere in the plugin are gone. Four of them were spacing utilities in the post editor, where Bootstrap was never loaded at all, so the space they asked for was never there: the social network checkboxes in the Publish box ran into one another.
1.0.0
Everything that follows was built after 0.6.0 and is released here for the first time: a set of tools for running the site, an administration page rebuilt from scratch, and one menu to reach all of it.
New tools, under the Tools menu. None of them involve AI, none of them change anything the plugin already did, and every one is off until you configure it.
- Code injection in the head, in the footer, before and after the article and in three blocks spread between its paragraphs, with the option to leave any of them out on a single post. The in-article blocks are placed by PHP, so they are there with JavaScript disabled and the text does not shift under the reader.
- Editorial checks: thirteen rules an article has to satisfy before it can go public, each one a switch of its own. A post that breaks one goes back to Pending, with the problems listed in the Publish box. Administrators can be exempted.
- Content filters: strip the span tags and the attributes Word and Google Docs leave behind, clean the paragraphs, and rewrite http:// as https://. They act while the page is rendered and never rewrite the post, so switching one off brings the original markup straight back.
- robots.txt and ads.txt served from the database, each with its own switch. If a real file exists in the root of the install the screen says so, instead of leaving you to wonder why nothing changes.
- WhatsApp chat: a bubble in the corner of the site that opens the conversation, with an avatar, a greeting and configurable delays. It works with any theme and brings no third-party library with it.
- Maintenance: close the comments on posts older than a month, delete their revisions, delete the spam and empty the moderation queue. Each task asks for a confirmation, works on a batch of 100 rows and reports how many it touched. Comments awaiting moderation go to the trash rather than being deleted.
- An upload restriction per user. It filters the upload_files capability, so it also applies to the REST API and to WP-CLI, not only to the buttons on the page. Administrators always keep it, so the screen cannot lock out the person configuring it.
- Twitter Card meta tags, in the Social Network tab: a link shared on X shows a card crediting the account you name.
- REST routes under syrus/v1 (theme-version, site-language, site-timezone), for reading remotely what an install is running. They answer anyone; close them with add_filter(‘syrus_ai_rest_public’,’__return_false’).
- For Yoast users, the page number in front of the description of a paged archive.
All the new screens require administrator permissions, even though the plugin page itself stays open to editors.
The administration page was rebuilt. The same screens, with the same controls and the same behaviour, in the shape WordPress 7.1 gives its own: one rounded panel on a dark field, a header carrying the version, a tab bar, and cards instead of a wall of tables.
- Bootstrap 5 is gone. It was loaded in full, 228KB of it, to style sixteen admin templates, and its JavaScript was never loaded at all. In its place there is a stylesheet of the plugin’s own, enqueued on the plugin page alone. Animate.css, 71KB that nothing referenced, went with it, and so did the old admin stylesheet. The download is 312KB smaller.
- Every setting that is on or off is a switch you can see the state of at a glance, instead of a bare checkbox in the second column of a table, and long forms carry a save bar that stays at the bottom of the window.
- The placeholders for what is not built yet are gone, so the page offers only what it can actually do.
One menu. On a site running the Syrus theme, the plugin builds a single Syrus menu in the sidebar: the theme’s own settings first, then every section of the plugin, each one a direct link. The theme’s entry under Appearance is removed so there is one Syrus menu and not two; deactivating the plugin puts it back. The theme’s screen keeps its own address and its own stylesheet, because the entry is a link to where the theme registered it and not a copy of it. On any other theme nothing changes. The menu is translated, Italian included; it used to be in English whatever the language of the site.
Fixed
- With the Syrus theme active the plugin page had no link anywhere in wp-admin. It registered its menu under a slug the theme stopped using when it moved its own options screen, and WordPress silently drops a submenu whose parent does not exist, so the page was reachable only by typing the URL.
- The post editor was getting the plugin’s page background, its gutter and its amber bar, because the plugin’s admin stylesheet was loaded there too. The editor looks like the editor again.
- On the Social Network tab the Instagram Connect button carried the Twitter button’s id, so the progress spinner appeared on the wrong row, and the Twitter Disconnect button had no id although the script addressed it.
- Opening the contact form editor without a form, or with an id that no longer exists, raised a PHP warning.
Known: opening the theme’s settings from the Syrus menu highlights Appearance rather than Syrus. WordPress recomputes the current menu for pages registered under a core file and discards what a plugin asks for, so the highlight cannot be moved without taking the page over, which would leave it unstyled.
0.6.0
- AI Translate means something else now: it translates the posts of this site into another language, from the box in the editor, creating a draft linked to the original. It used to pull articles from external sites through their REST API, along with all the code that involved.
- Removed the Writesonic rewriting: the AI connector does the same thing.
- Removed newsmaking. The feature never stored a single row, because the table was missing two of the columns every insert wrote, so there is nothing to preserve: the update drops the empty table and the seven options left behind, the NewsAPI key among them. The cron REST route goes with it.
- Text and image generation go through the WordPress connectors: the provider keys are managed under Settings > Connectors and the plugin no longer holds any of them.
- DeepL is registered as a connector, so its key moves to the core screen too.
- The minimum requirement is now WordPress 7.0, the version the AI Client landed in.
- The update also drops the translate_and_publish table and the remote domain options, which are no longer needed.
0.5.0
Security, bug fixes and cleanup. No feature removed.
- Security: closed a chain that let a Subscriber reach every endpoint of the plugin. The bootstrap nonce was printed on any screen you added two parameters to in the URL, the endpoint that mints nonces accepted any action string at all, other plugins’ included, and none of the 41 endpoints checked a capability. Authorization is now centralized, with an endpoint-to-capability map.
- Security: the contact form handlers verified the nonce but not the capability, and accepted any post id: it was possible to trash any content on the site and hijack the recipient of a form’s email.
- Security: the cron REST route was public and triggered paid calls, writes and an email. It now requires a shared key.
- Security: remote domains are validated, where before they allowed requests into the server’s internal network; the OpenAI key is no longer written in clear text into the log table; the API keys are no longer visible to anyone who does not administer the site; certificate verification is restored on the two calls that carry the installation token; HTML arriving from remote sites goes through wp_kses_post().
- Newsmaking never stored a row: the table was missing two of the columns every insert wrote. The schema is fixed, with a migration for existing installs.
- Deactivating the plugin no longer deletes the data. Removal happens only on uninstall.
- Removed session_start() on every request, which stopped any caching system from serving the pages.
- A failed social share is no longer recorded as a success, and the deprecated library used to send them has been replaced.
- The filter that discarded form submissions from non-Italian browsers is now a setting, off by default.
- The Import button on the Import/Export screen never worked, because its script was tied to a tab that does not exist; the same for the button that emptied the newsmaking table and for the Instagram share test.
- Removed 910 lines of unreachable code and around 600 duplicated ones, 900 KB of unused files, and a var_dump left in production inside a live endpoint.
- The assets no longer change address on every page load, so the browser can finally cache them.
- Minimum requirements raised to WordPress 6.5 and PHP 8.1.
0.4.5
- Maintenance.