Colombia, De la Espriella denuncia un piano per assassinarlo

Gutenberg Times: How WordPress decides a theme is a “block theme”
by Ryan Welcher on Luglio 21, 2026 at 6:57 pm
The term “block theme” is used a lot in WordPress but it was never really clear to me what that meant exactly from a code point of view. While researching The post editor is going full iframe: what block developers need to know before WordPress 7.1, I learned that the outcome of testing WordPress 7.1 Beta 1 may soften the plan: instead of forcing the iframe for everyone, core might force it only for block themes, while classic themes using blocks with apiVersion 2 or lower keep the current 7.0 behavior. (The linked article covers the 7.0 state of things in full.)If that’s the split, then the exact definition of “block theme” suddenly matters a great deal. So what does core actually check? The public API is wp_is_block_theme(), which just asks the active theme: PHP// wp-includes/theme.php (guard clause trimmed) function wp_is_block_theme() { return wp_get_theme()->is_block_theme(); }// wp-includes/theme.php (guard clause trimmed) function wp_is_block_theme() { return wp_get_theme()->is_block_theme(); } And WP_Theme::is_block_theme() is, in its entirety, a file-existence check: PHP// wp-includes/class-wp-theme.php (caching trimmed) public function is_block_theme() { $paths_to_index_block_template = array( $this->get_file_path( '/templates/index.html' ), $this->get_file_path( '/block-templates/index.html' ), ); foreach ( $paths_to_index_block_template as $path ) { if ( is_file( $path ) && is_readable( $path ) ) { return true; } } return false; }// wp-includes/class-wp-theme.php (caching trimmed) public function is_block_theme() { $paths_to_index_block_template = array( $this->get_file_path( '/templates/index.html' ), $this->get_file_path( '/block-templates/index.html' ), ); foreach ( $paths_to_index_block_template as $path ) { if ( is_file( $path ) && is_readable( $path ) ) { return true; } } return false; } A theme is a “block theme” if it ships an index.html block template, either in templates/, or in block-templates/, the pre-5.9 legacy location. Nothing else is consulted. That has a few consequences that may surprise people: theme.json doesn’t make you a block theme. Neither do patterns, block template parts, or add_theme_support( 'block-templates' ). A theme can adopt every one of those “hybrid” features and still land on the classic side of this check, because the test only looks for a top-level index.html template. Child themes inherit the answer. get_file_path() looks in the child theme first and falls back to the parent, so a child theme of a block theme is a block theme even if the child ships no templates of its own. It’s a filesystem check, not a declaration. There’s no header in style.css that opts you in or out. Drop a templates/index.html into a theme and, as far as WordPress is concerned, it is a block theme. The minimum files required for block and classic themes This is the entire minimum viable block theme — two files: Markdownmy-block-theme/ ├── style.css ← standard theme header └── templates/ └── index.html ← this file IS the decidermy-block-theme/ ├── style.css ← standard theme header └── templates/ └── index.html ← this file IS the decider (WordPress considers a theme valid if it has style.css plus either index.php or templates/index.html, which means for a block theme, index.php, functions.php, and even theme.json are all optional.) And this is a theme that is guaranteed to stay classic: Markdownmy-classic-theme/ ├── style.css └── index.php ← the classic fallback templatemy-classic-theme/ ├── style.css └── index.php ← the classic fallback template Staying on the classic side of the check comes down to two conditions: No templates/index.html and no legacy block-templates/index.html. Other block templates don’t matter: a theme with `templates/single.html` but no `templates/index.html` still tests as classic. (In practice, though, if you’re shipping block templates, ship the index and be a block theme on purpose.) No block-theme parent. The check falls back to the parent theme, so a child of Twenty Twenty-Five is a block theme no matter what the child contains. To be classic, the whole chain has to be. Everything else is fair game. theme.json, patterns, add_theme_support( 'block-template-parts' )` custom templates registered from plugins — none of them flip the switch., patterns, add_theme_support( 'block-template-parts' ), custom templates registered from plugins: none of them flip the switch. Where real themes land Running that check against some current releases from the theme directory Tests classicTests blockTwenty Twenty-One and every earlier defaultTwenty Twenty-Two and every later defaultAstra, Kadence, Blocksy, Botiga, Sydney, Hello Elementor — all ship theme.jsonGeneratePress, Neve, OceanWP, Storefront Six of the themes in the first column ship theme.json, the marquee “block” feature, and still test classic, because the check never looks at theme.jsonTwenty Twenty and OceanWP are another good gotcha: both ship a templates/ directory and are still classic, because it’s full of PHP page templates (template-cover.php, landing.php). The check wants templates/index.html specifically, so “does it have a templates folder” is not the indicator you might assume. How the editor reads it On the JavaScript side, the block-theme flag surfaces in two different places, which is worth knowing if you go source-diving. As an editor setting: PHP// wp-includes/block-editor.php, get_block_editor_settings() $editor_settings['__unstableIsBlockBasedTheme'] = wp_is_block_theme();// wp-includes/block-editor.php, get_block_editor_settings() $editor_settings['__unstableIsBlockBasedTheme'] = wp_is_block_theme(); and on the REST themes endpoint, which is where @wordpress/core-data picks it up: PHP// wp-includes/rest-api/endpoints/class-wp-rest-themes-controller.php $data['is_block_theme'] = $theme->is_block_theme();// wp-includes/rest-api/endpoints/class-wp-rest-themes-controller.php $data['is_block_theme'] = $theme->is_block_theme(); The one-file switch For all the weight the term carries, “block theme” boils down to a single file: templates/index.html exists, or it doesn’t. Not theme.json, not patterns, not any amount of hybrid adoption. Just one index template, checked up the parent chain. That’s worth keeping in mind if 7.1 does end up drawing the iframe line at wp_is_block_theme(). A hybrid theme that has adopted everything except block templates would keep the classic editor behavior, while adding a single templates/index.html (even accidentally, even in a parent theme you don’t control) would flip a site to the forced iframe. If your theme or your users’ sites sit anywhere near that line, now is a good time to check which side of it you’re actually on: it’s one is_file() call away.
Open Channels FM: The Growth of Domain Names and the Future of AI in Internet Identity
by Bob Dunn on Luglio 21, 2026 at 1:41 pm
This episode looks at the evolving online landscape, focusing on domain names, digital identity, and AI's influence. Key insights include rising domain registrations, AI in managing abuse, and the importance of open source.
Open Channels FM: Open Source and the Open Source Initiative
by Bob Dunn on Luglio 21, 2026 at 12:15 pm
People think Open Source is just about having access to the source code. Actually, there’s a much longer history behind it. Open Source existed before the term Open Source was even coined, back in the late 60s. Universities started giving away software like Unix for free under small licenses like BSD or MIT, coincidentally named
WordCamp Central: WordCamp Rajshahi 2026: Celebrating Community, Learning, and Open Source
by Nazmul Hosen on Luglio 20, 2026 at 7:05 pm
WordCamp Rajshahi 2026, held on July 2nd-3rd, 2026, at the Rajshahi University of Engineering & Technology (RUET) Auditorium, brought together WordPress enthusiasts, developers, designers, business owners, students, and open-source contributors from across Bangladesh and beyond. As a non-profit, community-driven conference, the event demonstrated the strength of collaboration, knowledge sharing, and the spirit of open source. More than just a technology conference, WordCamp Rajshahi became a place where people connected, exchanged ideas, and inspired one another to contribute to the future of WordPress. Sharing Knowledge That Matters The conference featured a diverse lineup of local and international speakers who shared practical experiences, real-world case studies, and emerging trends shaping the web today. Artificial intelligence was one of the most discussed topics throughout the event. Sessions explored how AI is transforming the way developers and businesses work—from integrating AI into WordPress without writing code to building customer support agents, using modern Large Language Models (LLMs) for development, debugging applications, and improving everyday workflows. Performance, architecture, and security also received significant attention. Speakers demonstrated advanced WordPress optimization techniques, object caching strategies, no-code animations using GSAP, methods for identifying system vulnerabilities, and practical approaches to cleaning malware-infected WordPress websites with AI. Beyond technical sessions, the conference emphasized personal and professional growth. Attendees learned about building successful careers, transitioning from startups to multinational companies, product marketing, the realities of remote work, and maintaining mental well-being while working in the technology industry. Contributor Day: Giving Back to WordPress Contributor Day, held on July 2, served as one of the most meaningful parts of the event. Participants worked alongside experienced WordPress contributors and Table Leads to improve the WordPress project itself. Whether they contributed to Core, Accessibility, Themes, Plugins, Polyglots (translations), Education, or Photos, attendees experienced firsthand how community collaboration built the global WordPress ecosystem. For many first-time contributors, it was their first opportunity to make a direct contribution to one of the world’s largest open-source projects. Campus Connect: Inspiring the Next Generation One of the highlights of WordCamp Rajshahi 2026 was the Campus Connect initiative. To encourage student participation in open source, 40 university students received complimentary tickets to attend the event. This initiative introduced young learners to the WordPress community, allowing them to interact with experienced professionals, attend technical sessions, and discover opportunities to contribute to open source. By investing in students today, the community hopes to cultivate the next generation of developers, designers, and contributors who will help shape the future of WordPress. Sponsors Who Made It Possible WordCamp events are made possible through the generous support of organizations that believe in strengthening the open-source ecosystem. Rather than simply sponsoring an event, these companies invest in community growth and knowledge sharing. This year, the sponsorship tiers celebrated Rajshahi’s famous mango heritage. Fazli Majesty (Platinum Sponsors) WebAppick, FluentCart, xCloud. Himsagar Legacy (Gold Sponsor) Hosting.com Amrapali Delight (Silver Sponsors) PaymentForm.io Kirki Community Sponsors Crowd Zone, Exprovia, NT Tech Innovation, Padmazon Limited, ShapedPlugin, Sigmative, Timetics AI, WPBakery. Official Partners FM Networks (Internet Partner) TNR Soft (Payment Gateway Partner) Their support enabled the community to deliver a world-class experience while keeping the event affordable and accessible. Thank You to Everyone Behind the Scenes An event of this scale is never the work of a single person. Our sincere appreciation goes to every speaker and Contributor Day table lead who generously shared their knowledge and experience with the community. We are equally grateful to our organizers and volunteers. From sponsorship coordination, website management, registration, design, photography, audiovisual production, venue operations, food management, and attendee support, every team member played a vital role in ensuring the event ran smoothly. Their dedication transformed months of planning into an unforgettable experience for every attendee. Looking Ahead WordCamp Rajshahi 2026 demonstrated what is possible when passionate volunteers, contributors, sponsors, and community members work toward a common goal. The event was more than a conference—it was a celebration of learning, collaboration, and the open-source values that make WordPress one of the world’s most successful communities. As the community continues to grow, the relationships built, ideas shared, and contributions made during WordCamp Rajshahi 2026 will inspire future events and encourage even more people to participate in the global WordPress ecosystem. Here’s to many more WordCamps, more contributors, and a stronger open-source community in Bangladesh and beyond.
Gutenberg Times: #WCUS Schedule, iframed Post Editor, WooCommerce 11.0 and so much more — Weekend Edition 369
by Birgit Pauli-Haack on Luglio 18, 2026 at 1:15 pm
Hi there! What a week! WordPress 7.1 Beta 1 (and Beta 2) arrived with a huge array of updates. We’ll unpack them together over the next four weeks, right up to the final release on August 19, 2026. One thing shouldn’t wait, though: the security release WordPress 7.0.2. Go update your production sites now — this newsletter will still be here when you’re back. In this edition, you’ll also find the first speaker lineup for WordCamp US, a fourth page-builder migration story, WooCommerce 11.0 on the horizon, and plenty of block development goodness: from iframed editors to on-brand maintenance pages. Grab your favorite Saturday beverage and dig in. Yours, Birgit WordCamp US 2026: Four Tracks, Three Workshops, 33 Speakers The first wave of WCUS 2026 speakers is live — and it reads like a who’s-who of WordPress in practice. WordCamp US just published its opening lineup for August 16–19 in Phoenix: 34 confirmed speakers so far, including K Adam White, Brian Coords, Jamie Marsland, Kathy Zant, Miriam Schwab, and Robert Abela, all experienced developers, educators, security specialists, community builders. The program runs four tracks. AI in Action leads with sessions on agentic workflows, AI search, and guardrails for AI-assisted development. Honing Your Skills covers the practical side: maintenance, privacy compliance, creator commerce, security. Technical WordPress digs into block migrations at scale, WP-CLI automation, and plugin pipelines. Beginning WP101 is the on-ramp for newcomers — or for clients you’re bringing along. Three hands-on workshops round out the program, where you build something real in the room and leave with it. The full session schedule isn’t out yet, but the speaker list alone is a useful signal. If someone on that page is a voice you follow, a tool you depend on, or a corner of WordPress you’re actively navigating, you now have a specific reason to be in the room. us.wordcamp.org/2026/tickets — $100 General Admission · $750 Micro-Sponsor (includes listing on the sponsors page) Full speaker list → Developing Gutenberg and WordPress WordPress 7.1 Beta 1 was release on July 15, 2026. is now available for testing. The release post offers instructions how to sent up a test side and shows an extensive list of new features. The security team released WordPress 7.0.2 with the urgent appeal to update right away. The security fixes were also backported in 6.9.5 and 6.8.6. The security fix was also included in WordPress 7.1 Beta 2, so testing sites are also protected during this release cycle. Huzaifa Al Mesbah, from the Core Test team, published the accompanying Help Test WordPress 7.1 post. A few WordPress 7.1 Dev Notes are already available: Consistent navigation in WordPress 7.1 with persistent toolbar The Classic block stays in the inserter for WordPress 7.1 The latest episode is Gutenberg Changelog #132 – Proposals for Core, Calls for Testing, WordPress 7.1 and Gutenberg 23.4 and 23.5 Plugins, Themes, and Tools for #nocode site builders and owners In about 10 days, WooCommerce 11.0 release is schedule. Brain Coords has the skinny for you in what’s coming for developers in WooCommerce. Performance leads the release with 28 PRs — product object caching becomes the default for new stores, speeding up variable products by 9–12%. You’ll also find email verification connecting guest orders to accounts, new phone validation hooks, video embeds in the block email editor, and the final removal of the Product Editor beta. The beta is ready for your testing now. Jamie Marsland followed his instincts and build Jamie’s Front-End Editor for Content Teams, a plugin that lets your editors click any paragraph or heading on the live page and start typing — no block editor required. With the latest updates, you can now edit text, links, buttons and images right on the live page. No wp-admin, no block editor, just click and change it in place. Built on the Interactivity API with no build step, it preserves block markup on save, records edits as native block notes for an audit trail, and lets you restrict chosen roles to front-end-only editing. Let Marsland what you think. Last week, I shared three migration stories from page builders to the Core block editor and block themes. Here’s a fourth perspective: The team at WP Expert, an Ottawa agency founded by Frederic Sune, put together a comprehensive post on migrating agency sites from page builders to Gutenberg, should you go on that journey, too. You’ll find the strategic arguments (better Core Web Vitals, smaller attack surface, less technical debt) alongside a practical playbook covering backups, staging, block theme selection, pattern development, and SEO safeguards. The post also explores what block-based architectures mean for an agency’s business model, from premium modernization packages to fewer layout-related support tickets. An FAQ rounds it out. Theme Development for Full Site Editing and Blocks Brian Coords tackles a common WooCommerce pain point: custom product templates for block themes. He combines two core WordPress features — the plugin template registration API from 6.7 and the venerable single_template_hierarchy filter — to serve custom templates for product collections, like all products in a category. His example plugin falls back to your Single Product template unless you override it. Clone the repo and give it a try; custom Product fields are next on his list. On the WordPress Developer Blog, Troy Chaplin shows you how to build an on-brand maintenance mode for block themes. You add one small hook to your theme’s functions.php once, then design and manage the maintenance page entirely in the Site Editor with full access to your Global Styles. Renaming or deleting the template toggles maintenance mode on and off, no code needed. An SEO-friendly variant adds 503 headers so crawlers know the downtime is temporary. “Keeping up with Gutenberg – Index 2026” A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2024 on. Updated by yours truly. The previous years are also available: 2020 | 2021 | 2022 | 2023 | 2024 | 2025 Building Blocks and Tools On WP Mayor, Jean Galea untangles when to reach for WP-CLI, the REST API, or the Abilities API. His mental model: they’re layers, not rivals. WP-CLI lives on the server for bulk work, REST serves off-server callers like headless front ends, and the Abilities API tells AI agents what they’re allowed to do, complete with schemas and permission checks. Galea also shares how his own sites lean on all three at once. Get up to speed how to make your custom blocks plugin work in the iframed post editor, if you haven’t yet. After five years of ruminating and communicating the switch is coming to WordPress 7.1. In his post, Ryan Welcher explains why the post editor is going full iframe in WordPress 7.1 and what that means for your custom blocks. You’ll find the fixes for the most common breakage — global window and document references, editor styles enqueued into the wrong document, stale admin-scoped CSS, and third-party libraries — plus a companion demo plugin with broken/fixed block pairs, Playground blueprints for testing both states, and a handy pre-flight checklist. The video volunteers at WordCamp Portugal uploaded all recordings to WordPressTV and two of the talks caught my eye: Imran Sayed walks you through the fastest way to build Gutenberg blocks with modern tools, scripts, and AI. If custom block development has felt complex or time-consuming, you’ll appreciate his focus on practical, real-world workflows you can adopt immediately — moving fast without over-engineering. The recording is available on WordPress.tv, and the presentation slides are linked below the video for easy reference. Jorge Costa shows you how to use the AI building blocks already shipped in WordPress core (the WP AI Client, the Abilities API, and the MCP adapter) to bring AI-powered features into your own plugins, themes, and sites. He also tackles the bigger question: when agents can spin up entire projects on any stack, why is WordPress still the right bet? Slides are linked alongside the recording. Check out the not so new any more Talk Devy to Me series on Ryan Welchers YouTube Channel! In the latest epsiode, Antonio Sejas demos Studio Code, the agentic AI assistant built into WordPress Studio’s desktop app and CLI. You can spin up sites, run performance audits, add content, and install plugins and themes through natural language conversation — all locally, so nothing you break goes public. Sejas explains how it works under the hood before building something live with the host. Studio Code is free while in beta, so now’s a good time to experiment. If you rather want to read about the updates in WordPress Studio, Fredrik Rombach Ekelund shares three big updates to WordPress Studio: a new default Native PHP runtime makes your local sites load 30–50% faster while using a third of the memory, the Studio CLI now installs with one dependency-free command — no Node.js or npm required — and Claude Sonnet 5 is the new default model in Studio Code, improving multi-step work like tracing bugs across files. A Sandbox runtime remains available for testing untrusted code. Need a plugin .zip from Gutenberg’s master branch?Gutenberg Times provides daily build for testing and review. Now also available via WordPress Playground. There is no need for a test site locally or on a server. Have you been using it? Email me with your experience. Questions? Suggestions? Ideas? Don’t hesitate to send them via email or send me a message on WordPress Slack or Twitter @bph. For questions to be answered on the Gutenberg Changelog, send them to [email protected] Featured Image:

RSS di Mondo - ANSA.it Updated every day - FOR PERSONAL USE ONLY

Brasile esclude ritorsioni contro i dazi Usa, 'la risposta non sarà la vendetta'
on Luglio 21, 2026 at 11:47 pm
Il vicepresidente punta sul negoziato mentre entra in vigore la tariffa del 25%
Usa, lanciati nuovi attacchi contro target militari in Iran
on Luglio 21, 2026 at 11:46 pm
L'annuncio del Us Centcom, 'è l'undicesima serata consecutiva'
Trump, dazi zero sui farmaci generici che entrano in Usa per 2 anni, poi salgono
on Luglio 21, 2026 at 11:15 pm
Al 100% per il primo anno poi al 200%
Moody's promuove il debito dell'Argentina e migliora l'outlook a positivo
on Luglio 21, 2026 at 10:52 pm
Il ministro dell'Economia esulta, il vice Daza vede nuovi investimenti esteri
Prestito di 7,5 miliardi all'Ecuador dalla Banca Interamericana per lo sviluppo
on Luglio 21, 2026 at 9:50 pm
Focus su progetti in materia di sicurezza e sviluppo sociale ed economico

SENTENZA

sentenza.eu