Categories
Entertainment

Alabama Barker Threatens to Go on “Highest Dose” of Ozempic

Alabama BarkerAlabama Barker is not feeling this hate.
Travis Barker and Shanna Moakler’s daughter clapped back at body-shaming comments online by threatening to up her dosage of Ozempic, the Type 2 diabetes…
​E! Online (US) – Top Stories

Categories
Alaska News

Mark Mitchell enters transfer portal after receiving fifth year of eligibility

An injunction gave Mark Mitchell and other high school class of 2022 athletes a fifth year in the fall.

Categories
Uncategorized

Gutenberg Times: WordPress 7.1 is afoot, Gutenberg 23.6, iframed post editor, Abilities API, Studio Code and more — Weekend Edition 371

Hi there,

This week I realized, I have been building websites for 30 years. from Notepad and hand-coded HTML to HomeSiteX over Coldfusion to WordPress, Nodejs and ReactJS to Python and Claude. It’s been a fantastic journey. It never gets old. I still learn new things every single day. I cherish most the friends I made along the way. I also found my notes about the WordCamps I attended, spoke at and organized. The first one was WordCamp Tampa in 2014. In 2026, I will probably attended my 30th WordCamp as well, Athens in December 2026. It’s a bit out, so let’s see if it works out.

Back to the here and now: It’s finally here the WordPress 7.1 Source of Truth with all the big and small changes coming to a WordPress instance near you. It’s again more like a book. Digest in small dosis.

Have a fabulous weekend!

Yours, 💕
Birgit

WordPress 7.1 updates


On the WPBuilds podcast series At the Core, Anne McCarthy and I talked with Nathan Wrigley about WordPress 7.1. We cover responsive styling, the persistent admin bar, and richer inline notes, plus why the new image crop modal and customisable viewports change your day-to-day editing. You’ll also hear how community feedback saved the Classic Block, where the collaborative editing outreach stands, and which developer changes to test now.

Birgit Pauli-Haack, Anne McCarthy and Nathan Wrigley recording the podcast episode.

Responsive styling finally lands in the block editor, and The WP Minute+ podcast has release lead Anne McCarthy demoing it with Eric Karkovack. You’ll also get the reasoning behind what didn’t make 7.1, including collaborative editing, plus how Classic Block deprecation is being paced. Anne talks about her first turn as release lead and points out hidden gems like the ‘On This Day’ widget and custom icon registration for the Icon block. The episode Why WordPress 7.1 Will Improve Your Workflow is also available as video.

More Devnotes:

There are still more to come and they will be published next week, together with the WordPress 7.1 Field Guide.

A list of all the dev notes can be reviewed from the Make Core blog


Anne McCarthy gives a candid account of the punted inherited styles indicator and its design dead ends. If you’ve ever watched someone style a template expecting it to apply site-wide, that’s the problem she’s chased since the FSE Outreach Program. Blue dots, diamonds, tooltips versus infotips, two competing reset paths — none settled, and summer holidays thinned the reviewer pool. She’s aiming at 7.2.

Gutenberg 23.6 released

Last week, Gutenberg 23.6 was already released. The WordPress 7.1 tech co-lead. Aki Hamano highlighted in his post What’s new in Gutenberg 23.6? (July 22, 2026)


This week on the Gutenberg Changelog podcast, my guest was Faith Imokol from Uganda. We began with the wonderful work of the WordPress community there, who have put together a series of events — WordCamps, Campus Connect, and a website competition — bringing WordPress to schools, colleges, and universities, and to thousands of students and users. Then we turned to the latest release and had a great time going through the details. As always, the episode drops in your favorite podcast app over the weekend.

Plugins, Themes, and Tools for #nocode site builders and owners

No PHP template, no shortcode, no custom block — Meta Box fields can now feed core blocks directly through block bindings for custom fields. Lua Nguyen shows the setup: select a Paragraph, Heading, Image, or Button, open Attributes in the sidebar, pick a Meta Box source, choose your field. Sources cover post, term, author, and settings-page fields, and an image field binds URL, alt, title, and caption separately. WordPress 6.5+, though the Attributes panel needs 6.9.

Theme Development for Full Site Editing and Blocks

Coming to the Site Editor from Elementor or Divi means learning new vocabulary, and Ollie’s ground-up guide to the WordPress Site Editor by Gina Lucia covers it: templates, template parts, patterns, global styles, navigation, the Font Library, and each toolbar button, starting at Appearance → Editor. A comparison table weighs both approaches on performance, flexibility, and portability. Ollie-specific tips sit alongside the core explanations, so you can read past them if you use another theme.


A typical Elementor page ships 200–400 KB of extra frontend assets, three to five times a native block build — the number behind Bikash Pun Magar‘s case for custom Gutenberg blocks over page builders on client sites. You get conditional per-block asset loading, HTML you control line by line, and content stored in native block grammar rather than a proprietary format. He’s fair about where Elementor still fits: prototypes and solo builders wanting pixel control without code.


The theme.json schema resolves to more than 40MB across hundreds of nested properties, which is why Sérgio Santos built a form-driven visual editor for theme.json as a VS Code extension. Fields come from the official schema rather than hand-written forms, and a weekly scan of core and Gutenberg adds experimental properties with honest badges. The feature Santos says changed his workflow: every preset shows the CSS variable name it will generate as you type the slug.

There’s also a companion WordPress plugin that mounts the same editor under Appearance. There will be dragons though: 🐲 Santos flags it as an experiment as it overwrites theme.json in place with no revisions or backups.

“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 for the Block editor.

If your custom blocks touch the global window or document, WordPress 7.1 will break them. Ryan Welcher walks through the forced iframed post editor canvas, landing August 19th with no flag to check and no opt-out. Five demos cover viewport detection, click-outside handlers, editor styles, admin body-class CSS, and unmaintained third-party libraries, with fixes using ownerDocument, defaultView, useRefEffect, editorStyle in block.json, and patch-package. His demo plugin ships broken and fixed versions of each.

Welcher also published a detailed tutorial: The post editor is going full iframe: what block developers need to know before WordPress 7.1

What’s new in Playground?

Some people still assumed every Playground was temporary. Persistence, multiple sites, Blueprints, file editing — all already there, just easy to miss, which is what the new WordPress Playground interface sets out to fix. A customizable Dock gathers those tools into one bottom toolbar: New, Playgrounds, Blueprint, Site Settings, Database, Files, Logs, Export. It’s navigation, not new capability. The design came out of the Playground table at WordCamp Europe Contributor Day, after Adam Zieliński used AI to explore 400+ variations.


Point a coding agent at WordPress Playground and it reads an instruction file first. The wp-playground agent skill now splits that file into a 52-line router plus focused references, so your agent loads the CLI details only for a local run and the sharing rules only for a share link — encoding, CORS, public hosting. Fellyph Cintra‘s four-scenario benchmark scored 24/24 against 22/24 for the old version, one run per prompt. All this is explain in more details in the post One Playground, three workflows: Consistent agent guidance across surfaces in the team’s Make Blog.


In a third post, Fellyph Cintra walks you through programmatic site management in WordPress Playground: from DevTools you can list, create, save, rename, and switch sites, change PHP or networking, and run PHP inside a site to check active plugins. Order matters — temporary sites must be saved before you can rename or reconfigure them.

One caveat worth knowing if it runs alongside the other Playground item: this API belongs to playground.wordpress.net only. It isn’t in the @wp-playground/client package, the CLI, or embedded Playgrounds via /remote.html — those need the JavaScript API instead.

AI and WordPress

Carlo Daniele‘s guide to the Abilities API for plugin developers stays on fundamentals: the input schema, output schema, callback, and permission check that together form an ability’s contract, and the WP-CLI commands that let you inspect one. A fresh install ships three — site info, user info, environment info. His example registers an audio-to-blocks process from an existing plugin and triggers it over the wp-abilities/v1 REST route.


Where Carlo Daniele registers a single ability, Jonathan Bossenger composes three into your first AI-powered WordPress plugin. Two call the AI Client, a third orchestrates them via wp_get_ability() and execute(), turning an image URL into a draft post. The same ability then answers over curl, from a React settings page, and from Claude Desktop through the MCP Adapter. Gotchas included: base64 data URIs for vision providers, stray markdown fences, and request timeouts.


One rule for this stream: no hand-written code. Ryan Welcher takes a full WordPress site build with Studio Code end to end for his son’s hockey team, and you watch a custom post type, a teams taxonomy, an Advanced Query Loop roster, and junior/intermediate/senior tabs come together by direction alone. The highlight is the agent reaching for block bindings unprompted. The lowlight: rogue PHP metaboxes, and a PHP-first answer where he wanted a SlotFill.

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 changelog@gutenbergtimes.com


Featured Image:


Categories
Alaska News

Screenshot 2026-07-31 171317.png

Post Content

Categories
Alaska News

First week of third gasline special session ends with no action by Dunleavy or Alaska Legislature

The Alaska House of Representatives is seen on Friday, July 31, 2026, during a technical sesison. (James Brooks photo/Alaska Beacon)

The Alaska Legislature ended the first week of its third special session on the proposed trans-Alaska natural gas pipeline with no action.

The session is for lawmakers to consider a property tax break to incentivize the proposed trans-Alaska natural gas pipeline, but Gov. Mike Dunleavy, who called the session and set the agenda, has yet to propose legislation for lawmakers to work on. 

The state House failed to pass a compromise bill earlier this month, during the second special session of 2026, after Dunleavy threatened to veto it. 

The governor has said he is holding closed-door negotiations to try to draft an alternative, but his office has released no details about those discussions.

Two members of the House and one member of the Senate held perfunctory “technical sessions” on Friday. 

Article II, Section 10 of the state constitution requires regular meetings unless lawmakers approve a resolution allowing a different schedule.

The House has scheduled another technical session for Monday morning, and the Senate has scheduled one for Tuesday morning.

SUBSCRIBE: GET THE MORNING HEADLINES DELIVERED TO YOUR INBOX.

Categories
Entertainment

Customers Are Calling This McDonald’s Breakfast Biscuit One Of The Best New Fast Food Items Of 2026

It’s been a while since McDonald’s switched things up on its breakfast menu. The breakfast biscuit just got a makeover, and this is what people are saying.

​Mashed – Fast Food, Celebrity Chefs, Grocery, Reviews

Categories
Alaska News

After federal report, Alaska pilots grapple with unanswered questions in tragic Nome crash

Empennage, or the tail of the plane, during post-recovery examination in Nome. (NTSB photo)

The National Transportation Safety Board on Thursday released the final report for the February 6, 2025, accident involving Bering Air flight 445 that killed all 10 people on board.

While the NTSB’s report identifies airspeed and load issues as the main causes of the crash, the Alaska aviation community is still reeling over how it could have happened with such a well-trained pilot from a company with an excellent safety record.

The Board determined the crash was caused by the pilot’s inadequate airspeed management and operation above gross weight. It also faulted the company for allowing overweight operations and the Federal Aviation Administration for inadequate oversight.

The Board’s team was composed primarily of investigators from outside the Alaska region, which is not uncommon when an accident is considered significant. But their lack of familiarity with the state’s aviation industry was evident in interviews as they sought to understand daily operations in rural Alaska. They also did not know about Bering Air’s unique reputation as, statistically, one of the safest small commuters in state history.

While Alaska has had a challenging flight safety record for decades, that was not the case with Bering Air  prior to this accident. That is what has made the crash of flight 445 so shocking to the aviation community here, and has led it to more nuanced scrutiny into the cause of this crash. 

Airspeed

That February afternoon, Flight 445 departed Unalakleet for Nome at 2:37 p.m. in a Cessna Caravan. Pilot Chad Antill was not an inexperienced pilot, but he wasn’t a seasoned veteran either. He began flying for Bering Air in 2022 and had about 2,500 total hours of flight time with 1,060 hours in the Caravan — flight hours are incredibly subjective as a measure of experience and dependent on a variety of factors including the type of flying, type of aircraft and location. At 3:05 p.m. Nome reported light snow, broken ceiling at 2,700 ft, overcast ceiling at 5,500 ft, and visibility of 10 miles. An icing forecast issued at 1 p.m. noted constant moderate icing between 2,000 and 8,000 feet in the region. Trucks were active on the runway and taxiways to keep surfaces clear for landing aircraft.

Flight 445 initially proceeded without incident and at 3:11 p.m. the pilot contacted Anchorage Center while descending from 7,725 feet for Nome. At 3:13 p.m., according to data obtained after the accident from the onboard Garmin 1000 flight system, the aircraft was flying at 163 knots and 6,575 feet. The Anchorage controller notified Antill that Nome Flight Service was reporting the available runway was closed for 10 to 15 minutes for snow removal and he might want to slow a bit to “not get there too early.”

U.S. Coast Guard rescue swimmers from Coast Guard Air Station Kodiak inspect the wreckage of a crashed plane near Nome, Alaska, Feb. 7, 2025. (U.S. Coast Guard photo courtesy of Air Station Kodiak)

The aircraft’s speed then decreased to 152 knots; it was reduced even further to 111 knots two minutes later — below the required Caravan speed of 120 knots for known icing conditions. At 3:16 p.m., Anchorage cleared the flight to descend at pilot’s discretion and maintain 4,000 feet. Antill gave a “good readback” of the instructions to the controller. Then, in one minute, things get out of control. At 3:19 p.m., the air speed briefly climbed to 121 knots; the aircraft was entering a rapid descent — an extremely dangerous situation. The last data point from the Garmin 1000 was at 3:20 p.m. when it reported 200 feet and 52 knots. The wreckage was later found about 34 miles from Nome on the sea ice.

Weight

In its investigation, the NTSB used data from several sources, including the Garmin, to conclude that the flight was about 800 pounds overweight out of Unalakleet for standard operations and 1,000 pounds overweight for flight into known icing conditions. There are different weight standards for flight into known icing conditions. Based on the Garmin data, the agency also asserted that flights on five previous days, which involved pilots other than Antill, were also overweight. That information generated significant attention when released to the public earlier this year, effectively directing the conversation onto fuel weight. 

Weight can become a factor in conjunction with some other event or action. For example, if the aircraft is loaded improperly, as in the 2013 Soldotna accident, or if an aircraft suffers a mechanical failure, or encounters severe weather conditions. 

It’s tough for FAA inspectors to check the weight on flights — they would need reasonable cause to unload the plane. The air service bears the responsibility for every load as it is company employees who manage those loads. For the FAA, Garmin data is not easily available, and absent reasonable cause an inspector cannot demand a company unload and weigh everything onboard an aircraft. This would be particularly onerous in Alaska where combinations of passengers, freight and mail are common. How the FAA can accomplish load oversight, without being unduly invasive on daily operations, is a question the NTSB is not required to address but the FAA will likely puzzle over for some time. 

It is indisputable Antill was flying heavier than his flight manifests reflected on February 6. While the Garmin 1000 is not infallible, based on the fuel weight he ordered when he departed Nome that morning and standard fuel burn calculations for his flight from there to St. Michael’s and then on to Unalakleet and back to Nome, the aircraft was overweight.

However,it is the air speed in icing conditions that should command the most attention from the report. Understanding air speed, many Alaska pilots say, far more than weight, is how to prevent future accidents like flight 445.

 

Flying in icing conditions

The Caravan was equipped with an aircraft deicing system, the Tecalemit-Kilfrost-Sheepbridge Stokes, named for the three British companies that first invented the process in 1942. The system, which is used to prevent ice from adhering to, and consequently building up on, wing surfaces and the tail assembly, is not designed for prolonged flight in icing conditions. Instead, it is intended to protect the aircraft while the pilot exits them. According to the Cessna Caravan Aircraft Flight Manual, even with the TKS deicing system on, the minimum air speed when icing has been encountered is 120 knots. From 3:15 p.m. until the crash, flight 445 failed to maintain that air speed. 

In NTSB interviews with several Bering pilots, management and the company’s FAA-assigned Principal Operations Inspector, the question of minimum air speed in icing conditions came up repeatedly. In each instance, the response was that 120 knots was the minimum acceptable. Not only was 120 knots listed in the Caravan manual but also in Bering Air’s checklist, standard operating procedures and its cold weather training materials. As one pilot told investigators, “…120 is what is the minimum recommended by Cessna so obviously that’s the minimum that would be recommended by the company.” 

To try and understand why Antill remained in icing conditions even as the aircraft slowed down, the TKS deicing system was discussed frequently in interviews. The regularity of icing forecasts in large swaths of Alaska was also addressed, along with the need for pilot reports to confirm or refute forecast validity. As the company’s operations inspector explained to investigators in the report: “We have forecast weather issues. Big State. Broad Forecast. Lots of changing weather.”  

Absent a confirmation pilot report, pilots depart into forecasted but not yet confirmed icing conditions. The TKS deicing system was designed exactly for this sort of potential icing environment. But, according to Chris Magerkurth, a former engineering specialist with Cessna who had seventeen years with the company working on ice protection systems, pilot over-reliance on systems like TKS is a concern. “The systems are designed to provide brief encounters with icing, not to hold or fly around indefinitely in any icing conditions,” he explained to me. “A pilot has no idea what ice conditions they are in or how quickly those conditions can change. They need to ask for a higher or lower altitude and get out of it.”

It is possible that the prevalence of icing conditions in the Norton Sound area has led to a subtle perception of the TKS deicing system as more “anti-ice” than “escape from ice” among pilots there. Coupled with the fact that many Alaska companies fly single-pilot aircraft, over-reliance on equipment like TKS while in tough conditions might be happening. This is especially true among the current generation of pilots who learned to fly in cockpit environments that emphasize automation. If anything is to be taken from this accident, many pilot sources stress, Cessna’s mandate to escape icing as quickly as possible would be the primary message, regardless of the accessibility to TKS.

In its recommendations, the NTSB called for the FAA to develop certain “surveillance criteria” for small commuter or charter services, known as Part 135 companies, who experience what the Board describes as “rapid growth, increased complexity of operations, accidents and/or incidents,” etc. But as he discussed with investigators, Bering Air’s operations inspector was physically present in Nome one week of nearly every month and the company had not markedly altered its route structure in recent years, even after the bankruptcy of Ravn Air Group in 2020. 

Further, based on a review of the NTSB’s database, Bering has maintained for decades the safest record among any small commuter or charter service of similar size in the state. Prior to flight 445, Bering was involved in seventeen accidents in the previous thirty-five years with only two in the previous ten years. There were no fatalities and only one serious injury when a passenger intentionally walked into a spinning propeller. In comparison, the company with the worst record in the period, Hageland Aviation Services, had 43 accidents before it went out of business in 2020 as part of Ravn Air. There were 29 fatalities and seven serious injuries in those crashes, its last occurring three months before the company shutdown. As Bering’s operations inspector noted to investigators, the company did not exhibit “risk indicators.”  That is part of what made the crash of flight 445 so shocking. Simply put, Alaskans did not see this one coming. 

Unanswered questions

A well-trained pilot with a seemingly reasonable amount of experience and reputation, according to his co-workers, for conservative flying, departed Unalakleet overweight into forecasted moderate icing conditions. He flew directly across Norton Sound rather than choosing one of Bering’s approved shore routes. When asked to “slow down a bit” by Anchorage Center he did not respond that conditions made such a request unacceptable. When told minutes later to descend at his discretion he agreed rather than ask for an immediate altitude out of the ice. He never declared an emergency. There is no record of him contacting Nome Flight Service to ask the trucks to leave the runway so his landing would not be delayed, which is a common request in such situations in Alaska. Finally, for several minutes his air speed steadily decreased and he appears to have done little to stop it, or to alert anyone that he was in trouble.

For people familiar with the aviation industry in Alaska, this behavior is troubling and frustrating to contemplate. In its recommendations the NTSB said nothing about further training in icing conditions. It is unclear what more could have been done to stress the importance of 120 knots in the Cessna Caravan. 

Magerkurth was part of the group that certified various anti-ice and deicing equipment over the years, including on the Cessna Caravan, and his thinking is quite straightforward: “The minimum icing air speed as set by the manufacturer is based on the changes in aerodynamic characteristics of the airframe such as drag created by various ice shape configurations,” he explained. “The company tests worst case scenarios based on the continuous maximum and intermittent maximum icing envelopes developed in federal regulations. When it sets an air speed limit, it is the result of that research.”

“The limit,” he said, “cannot be ignored.”

Editor’s note: The author worked with the principal operations inspector, who is a source in this story, at Larry’s Flying Service in Fairbanks in the 1990s.

SUPPORT: YOU MAKE OUR WORK POSSIBLE

Categories
Entertainment

Met Gala 2027: John Galliano to Be Honored With Costume Exhibit Theme

John Galliano and Kim Kardashian attend The 2024 Met GalaMet Gala 2027 will honor a fashion icon.
Anna Wintour and the Metropolitan Museum of Art’s Costume Institute announced “John Galliano: Horizons” as its spring 2027 exhibit, which will be the…
​E! Online (US) – Top Stories

Categories
Food

Why Restaurants Serve Water With Lemon Slices In It

If you ask for water at just about any restaurant, you’re going to get a slice (or wedge) of lemon in it as well. This is the reason why it’s so popular.

​Food Republic – Restaurants, Reviews, Recipes, Cooking Tips

Categories
Entertainment

Jack Osbourne Shares Baby Ozzy’s “Mischievous” Smile in Sweet Photo

Jack OsbourneJack Osbourne’s daughter is already taking after her late grandpa.
A year after Ozzy Osbourne’s July 2025 death, his son shared a sweet update on his 4-month-old baby girl Ozzy Matilda Osbourne,…
​E! Online (US) – Top Stories