--- title: "Site Studio 8.2.8 - September 17, 2026" date: "2026-09-17T12:41:18+00:00" summary: "Discover what's new in Site Studio 8.2.8—Drupal 11.3 Navigation support, key bug fixes, and improved Page Builder stability." image: type: "announcement" url: "/drupal-starter-kits/add-ons/site-studio/release/2026-09-17/99406-site-studio-828-september-17-2026" id: "b90e32af-bda9-485e-afe2-bc132858040b" --- Last updated: 17th September 2026 Released: 17th September 2026 Important When you upgrade your website to the latest version of Acquia Site Studio, the system applies database updates. These updates prevent the database from rolling back to the previous version. Acquia recommends that you apply updates in your development environment and back up your website, including the database, before you upgrade Acquia Site Studio. * [Highlights](#highlights) * [Bug fixes](#bug-fixes) Highlights ---------- ### Navigation module support in Drupal 11.3+ #### What is it? Site Studio Page Builder supports Navigation module in Drupal 11.3+. The Page Builder button opens in the Navigation top bar to enable access to visual edit mode. #### What impact will there be? The Page Builder button opens in the Navigation top bar after the Navigation module is enabled in Drupal 11.3+. On Drupal 10, the button continues to open in Admin Toolbar. #### What actions do I need to take? None. #### Are there any risks to be aware of? No. Bug fixes --------- ### Fixes an issue where the token browser does not display all available tokens #### What is it? Resolves an issue where the token browser does not display all available tokens on components. An unnecessary context restriction prevented token display. #### What impact will there be? All tokens display in the token browser on components. #### What actions do I need to take? None. #### Are there any risks to be aware of? No. ### Fixes view rows that repeat the first item inside a component drop zone #### What is it? Resolves an issue where a View row rendered inside a component drop zone displays only the first result across every row, instead of iteration through the view results. #### What impact will there be? Views render each row correctly. #### What actions do I need to take? None. #### Are there any risks to be aware of? No. ### Fixes invalid tokens passed to Site Studio API on rebuild #### What is it? Resolves errors during a rebuild process after modules such as Event-Condition-Action (ECA) are enabled. Site Studio validates tokens before transmission to Site Studio Application Programming Interface (API) and omits invalid tokens from processing. #### What impact will there be? Modules such as ECA do not cause errors during a rebuild. #### What actions do I need to take? None. #### Are there any risks to be aware of? No. ### Fixes an issue where component preview image upload fails to update with one tag attached #### What is it? Resolves an Asynchronous JavaScript and XML (AJAX) error that occurs during a new preview image upload for a component with one attached tag. #### What impact will there be? Users can upload a new preview image for a component with one attached tag without error. #### What actions do I need to take? None. #### Are there any risks to be aware of? No. ### Fixes a fatal error during translation requests through Translation Management (TMGMT) #### What is it? Resolves a fatal error triggered during a translation request through TMGMT on content with an empty or uninitialized Layout Canvas field. #### What impact will there be? Translation requests through TMGMT execute without fatal errors when content contains an empty or uninitialized Layout Canvas field. #### What actions do I need to take? None. #### Are there any risks to be aware of? No. ### Video URL field in component form retains empty state after clearing #### What is it? Resolves an issue where a cleared Video URL field in a component form repopulates default values during component re-render. #### What impact will there be? Content editors can clear video URLs from component forms and maintain empty fields without default URL repopulation. #### What actions do I need to take? None. #### Are there any risks to be aware of? No. ### Fixes the dx8-gateway service lockups during style compilation #### What is it? Resolves two input issues that lock the dx8-gateway Node service during posts to the `/build/style` endpoint. Both inputs drove the Cascading Style Sheets (CSS) value parser into an infinite loop and caused request expirations: * A font stack that contains a Google Fonts stylesheet Uniform Resource Locator (URL) with pipe characters. * A style value that contains a non-breaking space (U+00A0) adjacent to a function, such as a box-shadow or RGB value pasted from a rich-text editor. #### What impact will there be? Style compilation completes for these payloads. URL-shaped font stacks stay preserved as quoted values. Non-breaking spaces in style values convert to regular spaces before parsing. #### What actions do I need to take? None. #### Are there any risks to be aware of? Only affected inputs change behavior. URL-shaped font stacks emit as quoted values, and non-breaking spaces convert to regular spaces. Output for all other styles remains unchanged. ### Fixes missing entity logs during the rebuild process #### What is it? Resolves an issue where the rebuild process did not log all rebuilt entities. The process logs all entities during execution. #### What impact will there be? Execution of a rebuild through Drush logs all rebuilt entities. #### What actions do I need to take? Run a rebuild in verbose mode to access all logged information. #### Are there any risks to be aware of? No. ### Fixes default value field visibility in Style guide form fields #### What is it? Resolves an issue where the Default value field did not display during form field element edits in Style guide builder. #### What impact will there be? Users can set default values for Style guide form field elements. #### What actions do I need to take? Site Studio import is required to ensure that updated JavaScript assets load. #### Are there any risks to be aware of? No. ### Fixes leftover Representational State Transfer (REST) resource config entries #### What is it? Resolves an issue where leftover REST resource configurations in the database or config export cause errors after upgrade to version 8.2.7. Database updates remove unused REST resource configurations. If configurations remain in exported files, import operations ignore those specific REST resource configurations. #### What impact will there be? Database updates remove REST resource configurations from the database. #### What actions do I need to take? Run a database update and remove REST resource configurations from config exports. #### Are there any risks to be aware of? No. ### Page Builder in-place editing for deeply nested components #### What is it? Resolves an issue where in-place editing targeted incorrect fields or displayed empty values in nested component structures. #### What impact will there be? In-place editing opens the correct input or WYSIWYG field in nested component structures and retains values during edits. #### What actions do I need to take? Clear caches after updates to rebuild nested component templates. #### Are there any risks to be aware of? No. ### Fixes tokenized values with HTML tags rendered literally on templates #### What is it? Resolves an issue where tokenized values with HyperText Markup Language (HTML) tags rendered literally instead of executing on templates due to token replacement changes. #### What impact will there be? Templates render HTML tags in tokenized values correctly. Unsafe tags continue to render literally. #### What actions do I need to take? Resave affected templates or run a Site Studio rebuild. #### Are there any risks to be aware of? No. ### Fixes error log entries for menu templates with external menu links #### What is it? Resolves error log entries generated when rendering Site Studio menu templates mixed with links from other modules, such as Taxonomy Menu or Views. #### What impact will there be? Applications prevent unnecessary error log entries when rendering mixed menus. #### What actions do I need to take? None. #### Are there any risks to be aware of? No.