Saeidbakhsh Core Settings provides a small set of conservative WordPress behaviors that can be enabled independently:<\/p>\n\n
All tweaks are OFF by default.<\/p>\n\n
Revision Limit protects revisions that existed before the setting was enabled by default. A separate, destructive, and OFF-by-default option is available for users who intentionally want the limit applied to older revisions during future post updates.<\/p>\n\n
Comment controls are separated into two independent settings:<\/p>\n\n
Existing comments are never deleted and remain manageable in wp-admin.<\/p>\n\n
The installable plugin is self-contained. It requires no Composer runtime, vendor directory, JavaScript build chain, remote service, telemetry, cron job, or third-party PHP library.<\/p>\n\n
The plugin uses documented WordPress APIs and PHP 7.4-compatible runtime syntax to keep its implementation small, predictable, and suitable for long-term maintenance.<\/p>\n\n
The plugin is translation-ready. WordPress.org language packs are provided through translate.wordpress.org; PO\/MO translation catalogs are intentionally not bundled in the plugin ZIP.<\/p>\n\n
Saeidbakhsh Core Settings is translation-ready and uses the Vazirmatn Variable Font 33.003\nCopyright 2015 The Vazirmatn Project Authors (https:\/\/github.com\/rastikerdar\/vazirmatn).\nLicense: SIL Open Font License 1.1. See assets\/fonts\/OFL.txt.\nThe bundled WOFF2 is a web-compressed copy of the supplied variable TTF (weight axis 100-900) and loads only on the Saeidbakhsh Core Settings settings page for Persian and Arabic admin locales.<\/p>\n\n Developed and maintained by Ahmadreza Saeidbakhsh.<\/p>\n\n\n The Core settings page is placed directly below General. Its sections switch without reloading the page, and changes made across every section are saved together.<\/p>\n\n\n No. All tweaks are OFF by default.<\/p><\/dd>\n No. Uninstall removes only the plugin's own stored options. It does not delete posts, comments, revisions, or other site content.<\/p><\/dd>\n No. The setting targets WordPress generator metadata only. Asset version query strings are intentionally left unchanged because they are useful for cache invalidation and are unrelated to generator metadata.<\/p><\/dd>\n Disable New Comments prevents future comments and pings from being accepted.<\/p>\n\n Hide Existing Comments on the Frontend independently hides stored comments and their displayed counts from public-facing comment queries.<\/p>\n\n Neither setting deletes existing comment rows. Existing comments remain available for management in wp-admin.<\/p><\/dd>\n No. It disables WordPress emoji assets and hides emoji characters from public rendered output.<\/p>\n\n Stored content is not rewritten, and wp-admin, REST, AJAX, cron, and XML-RPC data are not modified by the output transformation.<\/p><\/dd>\n No. When enabled, direct requests to xmlrpc.php are terminated with HTTP 403 before WordPress creates the XML-RPC server.<\/p>\n\n XML-RPC methods and the X-Pingback header are also disabled as defense in depth.<\/p><\/dd>\n When Revision Limit is enabled, the plugin records a baseline representing revisions that already exist.<\/p>\n\n By default, those pre-existing revisions are protected and the configured limit applies only to revisions created after the baseline.<\/p>\n\n The separate Also prune older revisions option intentionally allows WordPress Core to apply the configured limit to older revisions during future post updates. This option is destructive and OFF by default.<\/p><\/dd>\n No. The general WordPress REST API remains available.<\/p>\n\n When Disable Embeds is enabled, oEmbed retrieval is short-circuited, WordPress posts are marked non-embeddable, only oEmbed-related REST endpoints are removed, saved Embed blocks and [embed] shortcodes fall back to plain links, and direct \/embed\/ views redirect to the canonical local post URL.<\/p><\/dd>\n No. The setting prevents self-pingbacks while preserving external ping behavior.<\/p>\n\n Standard HTTP and HTTPS URLs are matched appropriately while non-standard ports and separate installations on the same host remain distinct.<\/p><\/dd>\n Yes. The plugin provides a modular extension API.<\/p>\n\n See docs\/developer-api.md for the module contract and extension hooks. New features can be implemented as modules without modifying the plugin bootstrap.<\/p><\/dd>\n No. The production plugin has no Composer runtime dependency, vendor directory, third-party PHP library, JavaScript framework, remote service, or package-manager requirement.<\/p><\/dd>\n No software that depends on future versions of WordPress, PHP, web servers, or hosting environments can honestly guarantee indefinite compatibility.<\/p>\n\n Saeidbakhsh Core Settings is deliberately designed to reduce long-term maintenance risk by using documented WordPress APIs, PHP 7.4-compatible runtime syntax, standard WordPress internationalization APIs, no external runtime dependencies, no remote services, and no intentional reliance on private WordPress internals.<\/p><\/dd>\n\n<\/dl>\n\n\n Hardened WordPress generator-meta suppression against generator tags added by late wp_head integrations without affecting unrelated generator tags or asset version query strings.\nImproved public-display request detection so emoji and hidden-comment transformations remain outside REST responses and internal REST preloads.\nSimplified revision-baseline queries by relying on documented get_posts() default filter behavior, with no change to runtime behavior.\nAdded no runtime dependencies, remote calls, database tables, cron jobs, endpoints, JavaScript, or CSS.<\/p>\n\n Fixed nested or non-scalar settings sanitizer input that could trigger an Array to string conversion warning.\nHardened WordPress generator suppression by removing late wp_generator registrations and filtering official get_the_generator_* output types in addition to the_generator.\nAdded no runtime dependencies, services, database tables, cron jobs, REST routes, AJAX endpoints, JavaScript, or CSS.<\/p>\n\n Fixed Disable XML-RPC so direct xmlrpc.php requests terminate with HTTP 403 before WordPress creates the XML-RPC server, while method and header filters remain as defense in depth.\nFixed Disable Emojis so WordPress emoji assets are disabled and emoji characters are hidden from public rendered output without modifying stored content or affecting wp-admin, REST, AJAX, or cron data.\nReworked Revision Limit around WordPress' documented pre-deletion filter. Revisions that already exist when the limit is enabled are protected by a stored baseline; only revisions created after enablement are eligible for pruning by default.\nAdded the separate, destructive, and OFF-by-default Also prune older revisions setting for users who intentionally want the limit applied to older revisions during future post updates.\nSplit comment controls into Disable New Comments and the independent Hide Existing Comments on Frontend setting. Existing comments are never deleted and remain manageable in wp-admin.\nHardened Disable Embeds to short-circuit oEmbed HTTP retrieval, mark posts as non-embeddable, remove only oEmbed REST endpoints, convert saved Embed blocks and [embed] shortcodes to plain links, redirect direct \/embed\/ views to canonical local post URLs, and keep the general REST API enabled.\nRenamed Remove WP Version to Remove WordPress Generator Version so the setting does not imply that asset ?ver= query strings are modified.\nImproved self-pingback matching across standard HTTP and HTTPS ports while preserving non-standard ports and separate WordPress installations on the same host.\nReturned the main composition boot to init priority 5, preserving the documented 1.x extension lifecycle while still blocking XML-RPC before xmlrpc.php creates its server.\nAdded no runtime dependencies, remote calls, custom database tables, CSS, JavaScript, package managers, telemetry, or update services.<\/p>\n\n Sanitized submitted settings values at the request boundary before the existing field-level validator runs, resolving the reported Plugin Check warning.\nLocalized the settings-page title across all ten bundled locales.\nLocalized the developer name for Persian and Arabic; other bundled locales retain Ahmadreza Saeidbakhsh.\nKept all nine tweak modules and runtime dependency boundaries unchanged.\nReplaced the deprecated string autoload value used during activation with the current boolean WordPress API form.<\/p>\n\n Replaced the options.php submission path with a dedicated admin-post.php handler using documented WordPress APIs, explicit capability checks, a nonce, update_option(), and wp_safe_redirect().\nRendered the save confirmation once, directly below the plugin page title, using native WordPress notice classes. No custom CSS or JavaScript was added.\nRemoved the settings screen's dependency on WordPress' legacy admin-notice relocation behavior.\nPreserved the existing option name, tab-preservation behavior, sanitization, module API, and all nine conservative tweaks.\nAdded no external runtime dependencies, network calls, package managers, frameworks, database tables, cron jobs, or compiled assets.<\/p>\n\n Fixed duplicate Settings API success notices by relying on WordPress Core's native notice rendering for Settings screens.\nSimplified developer attribution so the developer name itself links to the official WordPress.org profile.\nUpdated all ten bundled translations and compiled MO files.\nNo tweak behavior, option names, hooks, module contracts, or dependencies changed.<\/p>\n\n Renamed the public plugin name and prospective WordPress.org slug during an earlier pre-release review to address naming and trademark ambiguity.\nKept the existing swpct_* option keys, hooks, helper functions, and PHP namespace for upgrade and extension compatibility.\nRaised the minimum WordPress version to 6.8 and removed the manual text-domain loader call. WordPress 6.8+ supports just-in-time loading for bundled plugin translations through the Text Domain and Domain Path headers.\nReworked read-only tab selection to avoid the nonce-verification false positive reported by Plugin Check while continuing to sanitize the requested tab.\nMoved multisite uninstall-loop state into a local uninstall function while retaining bounded 100-site batches.\nLimited readme.txt to five directory tags.\nAdded a localized developer credit to the plugin settings page, linking to the official WordPress.org profile for Ahmadreza Saeidbakhsh.\nRebuilt all ten PO\/MO catalogs for the new slug, branding, and developer credit.\nCorrected the pre_ping callback registration so it requests only the single argument it consumes.\nAdded no new tweak modules; all nine conservative behaviors remain OFF by default.<\/p>\n\n Renamed the Settings submenu item to Core and placed it directly below General using WordPress' documented submenu position parameter.\nReorganized the settings screen into native WordPress admin tabs: Content, Frontend, Discovery, and Connections.\nAdded cross-tab form preservation so saving one tab cannot reset values stored on another tab.\nKept the settings screen dependency-free and visually native by using WordPress Settings API markup and built-in nav-tab classes only.\nSet the plugin author to Ahmadreza Saeidbakhsh and the Author URI to the official WordPress.org profile.\nUpdated readme.txt contributor metadata to saeidbakhsh.\nUpdated all ten bundled translations for the revised interface.\nAdded no new tweak modules; the conservative long-term feature set remains unchanged.<\/p>\n\n Added Remove Shortlink.\nAdded Remove Feed Discovery Links without disabling feeds.\nAdded Disable Self Pingbacks while preserving external ping behavior.\nKept all new features OFF by default.\nDeliberately excluded higher-maintenance or cross-feature tweaks from the long-term core feature set.\nExpanded translations across all ten bundled locales and extended regression-test coverage.<\/p>\n\n Added complete bundled gettext translations for ten locales: fa_IR, ar, de_DE, es_ES, fr_FR, pt_BR, ru_RU, zh_CN, ja, and tr_TR.\nAdded editable PO files, compiled MO files, and a POT template.\nMoved text-domain loading and plugin boot to safe init timing for modern WordPress translation compatibility.\nAdded translation-safe default_settings() support for built-in modules while retaining the 1.0 fields() fallback for third-party modules.\nHardened checkbox sanitization so only the expected submitted value can enable a toggle.\nBatched multisite uninstall cleanup in groups of 100 sites.\nUpdated compatibility metadata through WordPress 7.1 while retaining PHP 7.4-compatible runtime syntax.\nExpanded dependency-free QA, architecture, lifecycle, and long-term compatibility documentation.\nRemoved development package-manager metadata from the installable release process; the production ZIP contains no vendor directory or Composer dependency.<\/p>\n\n Added a modular plugin foundation and dependency-free autoloader.\nAdded Disable Emojis.\nAdded Disable Embeds.\nAdded Remove WP Version.\nAdded Revision Limit.\nAdded Disable XML-RPC.\nAdded Disable Comments.\nAdded a Settings API management screen.\nAdded extension hooks and a ModuleInterface developer API.\nAdded safe uninstall handling, including multisite cleanup.\nAdded dependency-free smoke tests and development tooling metadata.<\/p>","raw_excerpt":"A conservative, dependency-free, modular collection of small WordPress core tweaks designed for long-term maintainability.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/bho.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/361745","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bho.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/bho.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/bho.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=361745"}],"author":[{"embeddable":true,"href":"https:\/\/bho.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/saeidbakhsh"}],"wp:attachment":[{"href":"https:\/\/bho.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=361745"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/bho.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=361745"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/bho.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=361745"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/bho.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=361745"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/bho.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=361745"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/bho.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=361745"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}saeidbakhsh-core-settings<\/code> text domain. Translations for WordPress.org releases are managed through translate.wordpress.org and delivered as WordPress language packs. Translation catalog files are not bundled in the plugin ZIP.<\/p>\n\nThird-party assets<\/h3>\n\n
Developer<\/h3>\n\n
\n
\n
Are any tweaks enabled automatically?<\/h3><\/dt>\n
Does uninstall delete posts, comments, or revisions?<\/h3><\/dt>\n
Does Remove WordPress Generator Version remove ?ver= from CSS or JavaScript URLs?<\/h3><\/dt>\n
How do the comment controls behave?<\/h3><\/dt>\n
Does Disable Emojis delete emoji from posts or comments?<\/h3><\/dt>\n
Does Disable XML-RPC only hide the X-Pingback header?<\/h3><\/dt>\n
How does Revision Limit protect older revisions?<\/h3><\/dt>\n
Does Disable Embeds disable the entire REST API?<\/h3><\/dt>\n
Does Disable Self Pingbacks affect external pingbacks?<\/h3><\/dt>\n
Can developers extend the plugin?<\/h3><\/dt>\n
Does the plugin require Composer or third-party libraries?<\/h3><\/dt>\n
Can this plugin be guaranteed to run unchanged for many years?<\/h3><\/dt>\n
1.5.8<\/h4>\n\n
\n
1.5.7<\/h4>\n\n
\n
saeidbakhsh-core-settings<\/code> following Plugin Review Team feedback.<\/li>\nswpct_*<\/code> option keys, hooks, helper functions, and PHP namespace for compatibility.<\/li>\n1.5.6<\/h4>\n\n
\n
1.5.5<\/h4>\n\n
\n
1.5.4<\/h4>\n\n
\n
1.5.3<\/h4>\n\n
\n
1.5.2<\/h4>\n\n
1.5.1<\/h4>\n\n
1.5.0<\/h4>\n\n
1.4.3<\/h4>\n\n
1.4.2<\/h4>\n\n
1.4.1<\/h4>\n\n
1.4.0<\/h4>\n\n
1.3.0<\/h4>\n\n
1.2.0<\/h4>\n\n
1.1.0<\/h4>\n\n
1.0.0<\/h4>\n\n