{"id":82,"date":"2026-03-03T12:30:00","date_gmt":"2026-03-03T11:30:00","guid":{"rendered":"https:\/\/aipublisherwp.com\/blog\/wordpress-7-release-candidate-checklist-preparazione-sito\/"},"modified":"2026-03-03T12:30:00","modified_gmt":"2026-03-03T11:30:00","slug":"wordpress-7-release-candidate-checklist-site-preparation","status":"publish","type":"post","link":"https:\/\/aipublisherwp.com\/blog\/en\/wordpress-7-release-candidate-checklist-preparazione-sito\/","title":{"rendered":"WordPress 7 Release Candidate: Complete Checklist to Prepare Your Site - Plugin Testing, PHP 7.4 Compatibility, Collaborative Editing, and New Blocks"},"content":{"rendered":"<p>The transition to <strong>WordPress 7.0<\/strong>, expected on <strong>April 9, 2026<\/strong>, represents one of the most significant moments in the roadmap of the world's most widely used open source CMS. <cite>With a timeline of Beta 1 released on February 19, 2026 and Release Candidate 1 scheduled for March 19, 2026<\/cite>, technical readiness requires a structured approach to ensure business continuity and take full advantage of the new features. This release marks the entry of WordPress into the <strong>Phase 3 of Project Gutenberg: Collaboration<\/strong>, introducing profound architectural changes that impact infrastructure, PHP compatibility, editing system and blocks.<\/p>\n<p>The technical checklist presented here was developed by analyzing official Core Team documentation, Release Squad reports, and early-adopter deployments on enterprise environments. The goal is to provide systems, developers, and technical managers of WordPress sites with an operational framework to validate compatibility, mitigate risks, and plan for deployment to production.<\/p>\n<p>After a 2025 marked by <cite>Legal issues such as the WP Engine lawsuit and the temporary pause in Automattic contributions to the Core<\/cite>, WordPress 7.0 takes the form of a <strong>Release of consolidation and innovation<\/strong>, with a focus on collaborative editing, artificial intelligence APIs, and administration interface redesign. For those managing complex sites, preventive dependency analysis and legacy code auditing are priority interventions to avoid service disruptions during upgrades.<\/p>\n<h2>PHP System Requirements and Compatibility: WordPress 7.0 Abandon PHP 7.2 and 7.3<\/h2>\n<p>One of the most impactful technical interventions in WordPress 7.0 concerns the <strong>Termination of support for PHP 7.2 and 7.3<\/strong>. <cite>Support for PHP 7.2 and 7.3 will be removed in WordPress 7.0, with the new minimum supported version becoming PHP 7.4.0<\/cite>. This strategic choice, justified by the <cite>Reduction in combined PHP 7.2 and 7.3 usage below 4% of monitored installations<\/cite>, aims to reduce technical debt and unlock modern features such as more rigorous type hinting.<\/p>\n<p>The development team documented that <cite>outdated PHP versions force WordPress to maintain compatibilities that weigh down the codebase and slow down development, while PHP 7.4 allows for more consistent typing making it easier for both developers and AI systems to understand the code<\/cite>. The recommended version remains <cite>PHP 8.3<\/cite>, considering that WordPress Core is <cite>Fully compatible with PHP 8.0-8.3 and in beta compatibility with PHP 8.4 and 8.5<\/cite>.<\/p>\n<h3>PHP Verification and Upgrade Procedure<\/h3>\n<p>Verification of the active PHP version can be performed through several technical channels:<\/p>\n<ul>\n<li><strong>WordPress Dashboard:<\/strong> Access to <em>Tools \u2192 Site Health<\/em> to identify the current PHP version and receive specific support level recommendations.<\/li>\n<li><strong>cPanel or hosting panel:<\/strong> Most managed environments provide graphical interfaces to change the PHP version by individual domain or directory.<\/li>\n<li><strong>phpinfo.php file:<\/strong> Create a file containing <code>&lt;?php phpinfo(); ?&gt;<\/code> in the root of the site and access it via browser to get complete details about the PHP configuration.<\/li>\n<li><strong>CLI SSH:<\/strong> Execute <code>php -v<\/code> from terminal to check the version in use from the command line.<\/li>\n<\/ul>\n<p>Before proceeding with the PHP upgrade in production, the following testing procedure in a staging environment is recommended:<\/p>\n<ol>\n<li><strong>Cloning the site:<\/strong> Set up a test environment identical to production, replicating databases, files and server configurations.<\/li>\n<li><strong>Install compatibility check plugin:<\/strong> Use tools such as <em>PHP Compatibility Checker<\/em> (available in the official repository) to scan themes, plugins and custom code for deprecated or incompatible features.<\/li>\n<li><strong>Applying PHP 7.4+ on staging:<\/strong> Change the PHP version of the test environment via control panel or server configuration.<\/li>\n<li><strong>Perform functional tests:<\/strong> Check all critical functionality: forms, e-commerce, membership, API integrations, publishing processes.<\/li>\n<li><strong>Analyzing error logs:<\/strong> Monitor <code>error_log<\/code> e <code>debug.log<\/code> (by activating <code>WP_DEBUG<\/code> at <code>wp-config.php<\/code>) to identify warnings, notices or fatal errors.<\/li>\n<li><strong>Testing critical plugins:<\/strong> Particularly check caching, security, SEO, page builder, and payment system plugins.<\/li>\n<\/ol>\n<p>If incompatibilities are detected, options include: upgrading plugins\/themes to the latest version, searching for compatible alternatives, contacting developers for specific patches or, for custom code, refactoring deprecated functions.<\/p>\n<h2>Real-Time Collaborative Editing: Architecture and Infrastructure Implications.<\/h2>\n<p>One of the most anticipated features of WordPress 7.0 is the <strong>Real-time collaborative editing system<\/strong>, which allows multiple users to simultaneously edit the same content. <cite>WordPress 7.0 introduces real-time collaboration that allows teams to edit posts and pages together from multiple locations, with offline editing and data synchronization enabled, using an HTTP polling-based sync provider as the default, with options for plugins or hosts to integrate websocket support<\/cite>.<\/p>\n<p>This represents a paradigm shift for WordPress, historically designed as a single-user tool. <cite>Synchronization engine enables simultaneous editing by multiple users, showing sliders in real time and automatically synchronizing changes<\/cite>, with an experience comparable to Google Docs.<\/p>\n<h3>Infrastructure Requirements for Real-Time Collaboration<\/h3>\n<p>The implementation of real-time editing requires specific infrastructural considerations:<\/p>\n<ul>\n<li><strong>HTTP Polling (default):<\/strong> The native solution uses periodic HTTP requests to synchronize status between clients. This approach is compatible with any standard WordPress hosting but generates incremental HTTP traffic.<\/li>\n<li><strong>WebSocket (optional\/hosting-specific):<\/strong> <cite>WordPress VIP has open-sourced its WebSocket-based real-time collaboration plugin on GitHub, demonstrating that the technology works but requires a WebSocket server<\/cite>. Hosts that offer WebSocket support can implement custom sync providers for superior performance.<\/li>\n<li><strong>Opt-in during Beta:<\/strong> <cite>During the beta period, real-time collaboration is opt-in to gather wider feedback and test<\/cite>.<\/li>\n<\/ul>\n<p>For high-traffic sites or geographically distributed editorial teams, it is advisable to assess with the hosting provider the availability of dedicated WebSocket infrastructure. Otherwise, standard HTTP polling provides full functionality but with slightly higher latencies.<\/p>\n<h3>Notes and Commenting System: Advanced Editorial Workflow<\/h3>\n<p>In parallel with simultaneous editing, WordPress 7.0 enhances the <strong>Notes<\/strong> Introduced in 6.9. <cite>Users will be able to select specific text within a paragraph and leave notes on that precise selection, reviewers can propose changes related to specific content that authors can accept or reject with one click, and comments can now cover multiple blocks<\/cite>.<\/p>\n<p>These features turn WordPress into a platform for <strong>native content collaboration<\/strong>, reducing dependence on Google Docs, Slack or external tools. For agencies and newsrooms, this translates into faster review cycles and centralized editorial governance within the CMS.<\/p>\n<h2>Plugin and Theme Compatibility Testing: Pre-Upgrade Audit Methodology<\/h2>\n<p>Verifying the compatibility of plugins and themes is the most critical stage of preparation. WordPress 7.0 introduces changes to Core that can generate incompatibilities with outdated extensions, particularly those that interact with the Gutenberg editor, manipulate DOMs or depend on deprecated functions.<\/p>\n<h3>Plugin Compatibility Checklist<\/h3>\n<p>The following structured approach to plugin auditing is recommended:<\/p>\n<ol>\n<li><strong>Complete inventory:<\/strong> Generate list of all active plugins with their versions via <em>Plugins \u2192 Installed Plugins<\/em> o WP-CLI query <code>wp plugin list<\/code>.<\/li>\n<li><strong>Check official repository:<\/strong> For each plugin, check the WordPress.org page by checking: date last updated, WordPress version tested, recent reviews reporting problems with beta versions.<\/li>\n<li><strong>See developer changelog:<\/strong> Look for explicit references to \u201cWordPress 7.0 compatibility\u201d or \u201cGutenberg 22.x support\u201d in official plugin changelogs.<\/li>\n<li><strong>Testing in an isolated environment:<\/strong> Install WordPress 7.0 Beta\/RC in staging and gradually activate plugins, testing core functionality after each activation.<\/li>\n<li><strong>Monitor JavaScript console:<\/strong> Use Developer Tools in the browser to identify JS errors that might indicate incompatibility with the new React components in the editor.<\/li>\n<li><strong>Verify critical plugins by category:<\/strong>\n<ul>\n<li><strong>Page Builder:<\/strong> Elementor, Divi, Beaver Builder require specific updates to interface with the iframe editor.<\/li>\n<li><strong>SEO:<\/strong> Yoast, Rank Math, All in One SEO must support the new WordPress 7.0 meta patterns.<\/li>\n<li><strong>E-commerce:<\/strong> WooCommerce and alternatives need full validation of checkout flow and admin panel.<\/li>\n<li><strong>Security &amp; Cache:<\/strong> Plugins that manipulate HTML output or implement cache layers must be tested with the new cross-document transitions.<\/li>\n<li><strong>Form Builder:<\/strong> Gravity Forms, WPForms, Contact Form 7 require rendering tests and submissions.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<h3>Theme Management and Compatibility Block Editor<\/h3>\n<p>For themes, the analysis should focus on:<\/p>\n<ul>\n<li><strong>Block Theme vs Classic Theme:<\/strong> <cite>Gutenberg 22.3 and 22.4 introduced Font Library support for classic and hybrid themes<\/cite>, but native block themes get more benefit from the new features.<\/li>\n<li><strong>Custom CSS and admin selectors:<\/strong> <cite>Custom blocks that target admin selectors such as .wp-admin or .editor-styles-wrapper, which rely on global document queries or initialize libraries globally, now consistently fail<\/cite> Because of the iframed editor.<\/li>\n<li><strong>Custom templates:<\/strong> Verify that custom templates do not depend on legacy editor-specific DOM structures.<\/li>\n<li><strong>JavaScript of the theme:<\/strong> Scripts that interact with the editor must be compatible with the iframe environment.<\/li>\n<\/ul>\n<p>For more details on the strategic evolution of WordPress and its implications, we recommend reading our <a href=\"https:\/\/aipublisherwp.com\/blog\/en\/wordpress-7-0-roadmap-2026-collaboration-ai-news\/\">full analysis on WordPress 7.0 and Roadmap 2026<\/a>.<\/p>\n<h2>New Blocks and Editor Features: Grid, Icons, Breadcrumbs and Responsive Controls<\/h2>\n<p>WordPress 7.0 significantly expands the block ecosystem with targeted introductions and stabilization of experimental components. <cite>Version 7.0 introduces new and improved blocks making the sites more customizable, with embed video backgrounds in the Cover block, a responsive-enabled Grid block, and new Icons, Breadcrumbs and Heading blocks<\/cite>.<\/p>\n<h3>Introduced or Stabilized Blocks<\/h3>\n<p>The complete inventory includes:<\/p>\n<ul>\n<li><strong>Grid Block:<\/strong> <cite>Experimental Grid block is stabilized for use in production<\/cite>, allowing responsive grid layouts without custom CSS.<\/li>\n<li><strong>Icons Block:<\/strong> Native insertion of SVG icons with sizing, color and alignment controls.<\/li>\n<li><strong>Breadcrumbs Block:<\/strong> Automatic generation of breadcrumb navigation to improve UX and SEO structured data.<\/li>\n<li><strong>Cover Block with video embed:<\/strong> Ability to use embeddable videos (YouTube, Vimeo) as background of hero sections.<\/li>\n<li><strong>Improved Navigation Block:<\/strong> <cite>Updated Navigation block makes menu changes easier and more reliable in fewer steps, with more intuitive and clearer workflow<\/cite>.<\/li>\n<\/ul>\n<h3>Responsive Controls and Visibility by Device<\/h3>\n<p>One of the most requested innovations concerns the <strong>native responsive controls<\/strong>. <cite>Mobile-friendly controls in WordPress 7.0 allow you to hide or show blocks based on screen size<\/cite>, eliminating the need for conditional CSS or third-party plugins to manage differentiated desktop\/mobile layouts.<\/p>\n<p>This functionality integrates with the <strong>pattern editing<\/strong> and the new isolated modes (<em>Spotlight Mode<\/em> e <em>Isolated Editor Mode<\/em>) that <cite>introduce pattern-level editing, tree view for button and list blocks, and the ability to opt out of the default content-only mode<\/cite>.<\/p>\n<h2>Administration Interface Redesign and Cross-Document Transitions<\/h2>\n<p>WordPress 7.0 marks the start of the <strong>visual refresh of the administrative area<\/strong>, first systemic intervention since 2013. <cite>WordPress 7.0 enhances the wp-admin experience with a new default color scheme and a cleaner, more modern-looking dashboard while keeping the interface familiar, while the dashboard upgrade improves the editing experience with new visual comparisons of revisions and smooth transitions between screens<\/cite>.<\/p>\n<p>Le <strong>cross-document transitions<\/strong> represent a UX innovation that reduces the perception of fragmentation when navigating between admin sections. Technically implemented via View Transitions API, they offer visual continuity without requiring full page reloads for common operations.<\/p>\n<h3>Design System and Accessibility<\/h3>\n<p>The redesign is not purely aesthetic but part of the alignment to the <strong>WordPress Design System<\/strong>, unified framework to ensure consistency between legacy admin screens and block-based interfaces. <cite>Goals for 7.0 include an admin-wide design refresh, making continuity of accessibility a priority<\/cite>.<\/p>\n<p>For those managing sites with stringent accessibility requirements (PA, healthcare, education), specific audits with screen reader and WCAG 2.1 AA validation tool on staging environment are recommended.<\/p>\n<h2>WP AI Client and Abilities API: Foundations for AI Integration.<\/h2>\n<p>WordPress 7.0 introduces <strong>WP AI Client<\/strong>, architectural framework for integrating artificial intelligence models in a provider-agnostic manner. <cite>The new WP AI Client in WordPress 7.0 introduces a layer in the Core that allows AI templates to be leveraged from any provider within the WordPress framework<\/cite>.<\/p>\n<p>This approach avoids tying WordPress to specific providers (OpenAI, Anthropic, Google), allowing users to configure their own API credentials and plugins to access AI capabilities via standardized interface. <cite>The AI Web Client API allows users to securely store AI credentials and provides plugin\/theme developers with a standardized way to integrate AI functionality, allowing credentials for the preferred AI template to be securely stored inside WordPress<\/cite>.<\/p>\n<h3>Implications for Content-Intensive Developers and Sites.<\/h3>\n<p>Practical applications include:<\/p>\n<ul>\n<li><strong>Automatic alt-text generation:<\/strong> Plugins can invoke AI to describe uploaded images.<\/li>\n<li><strong>Summarization:<\/strong> Automatic creation of excerpts from long body content.<\/li>\n<li><strong>Content moderation:<\/strong> Automated analysis to detect problematic content.<\/li>\n<li><strong>Editorial assistance:<\/strong> SEO improvement suggestions, tone analysis, fact-checking support.<\/li>\n<\/ul>\n<p>For sites that produce AI-assisted content, maintaining human editorial control and review process is critical. We recommend reading our in-depth discussion on <a href=\"https:\/\/aipublisherwp.com\/blog\/en\/content-to-proof-strategy-eeat-original-data\/\">How to create AI-proof content with EEAT strategy<\/a> To balance automation and quality.<\/p>\n<p>With a view to visibility on new AI-powered search engines, it is strategic to optimize content to be cited by systems such as ChatGPT and Perplexity: our <a href=\"https:\/\/aipublisherwp.com\/blog\/en\/geo-generative-engine-optimization-practical-guide-italian-sites\/\">GEO (Generative Engine Optimization) guide for Italian sites.<\/a> Provides specific operational framework.<\/p>\n<h2>Staging Environment and Secure Deployment Procedure<\/h2>\n<p>Preparation for WordPress 7.0 should include appropriate testing infrastructure. The recommended sequence includes:<\/p>\n<ol>\n<li><strong>Staging environment setup:<\/strong> Clone production in identical isolated environment (same PHP version, same server stack, same WordPress configuration).<\/li>\n<li><strong>Install WordPress 7.0 Beta\/RC:<\/strong> Use the plugin <em>WordPress Beta Tester<\/em> for controlled upgrade, or manual installation from wordpress.org\/download.<\/li>\n<li><strong>Perform comprehensive functional testing:<\/strong> Validate all critical user flows, forms, API integrations, e-commerce checkout processes.<\/li>\n<li><strong>Performance benchmarking:<\/strong> Measure TTFB, LCP, TBT metrics pre- and post-upgrade to identify performance regressions.<\/li>\n<li><strong>Security audit:<\/strong> Verify that all security mechanisms (2FA, login protection, firewall rules) are working properly.<\/li>\n<li><strong>Full backup:<\/strong> Create database and filesystem snapshots immediately before deployment production.<\/li>\n<li><strong>Deploy in maintenance window:<\/strong> Schedule upgrades during periods of low traffic, with technical team available for quick rollbacks if needed.<\/li>\n<li><strong>Post-deployment monitoring:<\/strong> Enable intensive monitoring of error logs, performance metrics, and user feedback in the first 24-48 hours.<\/li>\n<\/ol>\n<p>For mission-critical sites, progressive deployment is recommended: first on public staging subdomain for beta-testing with selected users, then on reduced percentage of traffic (blue-green deployment or canary release if the infrastructure supports it), finally full rollout.<\/p>\n<h2>Integration with Marketing AI Ecosystem: ChatGPT, Threads and Siri<\/h2>\n<p>The introduction of native AI in WordPress 7.0 is part of a larger ecosystem of AI-first platforms that are redefining content discovery and distribution. For those managing content marketing strategies, it is strategic to consider the interoperability between WordPress and:<\/p>\n<ul>\n<li><strong>ChatGPT Ads:<\/strong> OpenAI has launched its own advertising system. Learn more with our guide on <a href=\"https:\/\/aipublisherwp.com\/blog\/en\/ads-chatgpt-marketer-italian-openai-advertising-system\/\">How ChatGPT's new advertising system for Italian marketers works<\/a>.<\/li>\n<li><strong>Threads:<\/strong> Meta platform for text content is surpassing X as a distribution channel. Read the <a href=\"https:\/\/aipublisherwp.com\/blog\/en\/threads-surpasses-x-2026-strategy-brand-creators-italians\/\">comprehensive strategy for Italian brands and creators on Threads<\/a>.<\/li>\n<li><strong>Siri AI 2026:<\/strong> Apple is enhancing Siri as an answer engine. See the <a href=\"https:\/\/aipublisherwp.com\/blog\/en\/siri-ai-2026-answer-engine-apple-optimize-wordpress-voice-search\/\">Guide to optimizing WordPress content for voice search and Siri AI<\/a>.<\/li>\n<\/ul>\n<p>Optimization for these channels requires robust structured data, semantically rich content, and information architecture designed for answer extraction. WordPress 7.0, with its native AI API, provides the ideal infrastructure for implementing automated content enrichment pipelines.<\/p>\n<h2>FAQ<\/h2>\n<h3>When will the Release Candidate of WordPress 7.0 be released?<\/h3>\n<p>Release Candidate 1 of WordPress 7.0 is scheduled to be released on <strong>March 19, 2026<\/strong>, followed by the final release on <strong>April 9, 2026<\/strong> in conjunction with WordCamp Asia. Beta phase 1 is already available from February 19, 2026 for early testing. It is recommended to start compatibility testing during the RC phase to identify issues before release production.<\/p>\n<h3>My site uses PHP 7.3: what should I do before WordPress 7.0?<\/h3>\n<p>WordPress 7.0 <strong>Will not support PHP 7.2 and 7.3<\/strong>, requiring at a minimum PHP 7.4.0 (with recommendation for PHP 8.3). Prior to release, it is necessary to: 1) Test the site on a staging environment with PHP 7.4+, 2) Use plugins such as PHP Compatibility Checker to identify incompatible code, 3) Upgrade problematic plugins\/issues, 4) Coordinate with the hosting provider to upgrade PHP in production. Proceeding with PHP upgrades is a priority for security and performance even regardless of WordPress 7.0.<\/p>\n<h3>Does real-time collaborative editing require special server configurations?<\/h3>\n<p>The functionality of <strong>real-time collaboration<\/strong> works out-of-the-box on any standard WordPress hosting using HTTP polling as the synchronization mechanism. For optimal performance on distributed teams or large editorial staffs, it is recommended to check with the hosting provider for the availability of WebSocket support, which reduces latency and HTTP traffic. During the beta phase, the feature is opt-in. Managed WordPress enterprise hosting such as WordPress VIP offers optimized WebSocket-based implementations.<\/p>\n<h3>Which plugins are most at risk of incompatibility with WordPress 7.0?<\/h3>\n<p>The most exposed categories of plugins include: <strong>page builder<\/strong> (Elementor, Divi) that need to adapt to the iframed editor, <strong>caching plugin<\/strong> To handle the new cross-document transitions, <strong>custom Gutenberg extensions<\/strong> with CSS selectors based on .wp-admin or .editor-styles-wrapper, <strong>SEO plugin<\/strong> manipulating meta patterns, and <strong>form builder<\/strong> interacting with the editor DOM. Systematic verification on staging and consulting official developer changelogs for explicit statements of WordPress 7.0 compatibility is recommended.<\/p>\n<h3>How to take advantage of the new AI API in WordPress 7.0 without depending on a specific vendor?<\/h3>\n<p>The <strong>WP AI Client<\/strong> introduced in WordPress 7.0 is designed as a provider-agnostic layer: it allows configuring API credentials for any AI service (OpenAI, Anthropic Claude, Google Gemini, Azure OpenAI) via unified interface in the WordPress backend. Compatible plugins can invoke AI capabilities (text generation, image analysis, summarization) via standardized API without implementing custom integrations for each provider. Users retain control over which template to use and can switch providers without changing plugin configurations. This approach provides flexibility and reduces technology lock-in.<\/p>\n<h2>Conclusions: Proactive Preparation to Maximize ROI of Upgrade<\/h2>\n<p>WordPress 7.0 represents one of the most significant releases in the project's recent history, with implications that go beyond superficial functionality to touch architecture, editorial workflows, and integration with emerging AI ecosystems. Methodical preparation-PHP audit, plugin\/theme compatibility testing, validation on staging, AI API configuration-turns a potential risky event into a strategic opportunity to modernize technology stack and operational processes.<\/p>\n<p>Teams that invest time in Beta\/RC testing will be able to identify critical issues in advance, plan mitigations, and train users on the new collaborative features before go-live. For enterprise or high-traffic sites, this approach dramatically reduces the risk of downtime or post-upgrade functional regressions.<\/p>\n<p>The native introduction of AI, collaborative editing, and responsive controls marks the transition of WordPress from a traditional CMS to <strong>content operations platform<\/strong> modern, able to compete with proprietary SaaS solutions while maintaining the advantages of open source: data ownership, unlimited extensibility, no vendor lock-in.<\/p>\n<p>We invite the technical community to share in the comments testing experiences, specific use cases of the new AI APIs, and deployment strategies adopted. Collectively documenting edge cases and best practices will accelerate safe adoption for the entire Italian WordPress ecosystem.<\/p>","protected":false},"excerpt":{"rendered":"<p>Complete technical guide to preparing your WordPress 7.0 site: PHP 7.4 checklist, plugin testing, collaborative editing and new blocks.<\/p>","protected":false},"author":1,"featured_media":83,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_robots_primary_cat":"","_seopress_titles_title":"WordPress 7 RC: Checklist Preparazione Sito | PHP, Plugin, AI","_seopress_titles_desc":"Checklist tecnica WordPress 7.0: compatibilit\u00e0 PHP 7.4, test plugin\/temi, editing collaborativo real-time, nuovi blocchi e API AI. Guida completa.","_seopress_robots_index":"","footnotes":""},"categories":[7],"tags":[60,21,57,58,18,59],"class_list":["post-82","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress","tag-ai-integration","tag-gutenberg","tag-php-compatibility","tag-real-time-collaboration","tag-wordpress-7-0","tag-wordpress-core"],"_links":{"self":[{"href":"https:\/\/aipublisherwp.com\/blog\/en\/wp-json\/wp\/v2\/posts\/82","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aipublisherwp.com\/blog\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aipublisherwp.com\/blog\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aipublisherwp.com\/blog\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aipublisherwp.com\/blog\/en\/wp-json\/wp\/v2\/comments?post=82"}],"version-history":[{"count":0,"href":"https:\/\/aipublisherwp.com\/blog\/en\/wp-json\/wp\/v2\/posts\/82\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aipublisherwp.com\/blog\/en\/wp-json\/wp\/v2\/media\/83"}],"wp:attachment":[{"href":"https:\/\/aipublisherwp.com\/blog\/en\/wp-json\/wp\/v2\/media?parent=82"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aipublisherwp.com\/blog\/en\/wp-json\/wp\/v2\/categories?post=82"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aipublisherwp.com\/blog\/en\/wp-json\/wp\/v2\/tags?post=82"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}