The internet has dissolved the borders separating different countries to a great extent. Today, we can connect with someone miles apart within a fraction of a second, all thanks to internet technology. The internet, powered by incredible technologies such as Drupal 9 and multilingual websites, has broken down borders and connected people from all corners of the globe.

It depends on us whether we opt for internet calling, emailing, or chatting, but one thing is certain we are just a click away from those we aspire to connect with. Such incredible advancements have not only empowered human relationships, but have also opened monumental opportunities for businesses. If you have an inner hunger to establish your brand globally, nothing can confine you today. All you require to do is build a multilingual website and you are ready to reach a global target audience effortlessly.

In a recent blog post, I asked, "Is there no future for the Schema.org Blueprints module?" I wrote the blog post to determine what is next for the Schema.org Blueprints module. The overall feedback was positive, with very constructive criticism and advice. Reading the replies on Twitter, the comments on my blog, the pings in Drupal Slack, and tickets in the module's issue queue, I realized that people are interested in the Schema.org Blueprints module's overall goal, which is to build standardized and reusable content models in Drupal. Most of the questions and feedback I received were around clarifying the Schema.org Blueprints module's use case, getting started, and the project's roadmap.

Within the feedback, people raised many questions about the Scheme.org Blueprints module. I collected their questions and created a reasonably large FAQ page.

The first question I am answering is, "What problem is the Schema.org Blueprints module trying to solve?"

The FAQ page further defines the goals, use case, process, and best practices for the Schema.org Blueprints modules. I am still perfecting my elevator pitch for why someone should take a Schema.org-first approach and use this module. Once I can entice someone to try the module, the next step is to be helping them install,...Read More

Matt has always been fascinated with Drupal and knows it to be an extremely powerful framework for building applications.

Understanding Update and Post Update Hooks for Successful Site Updates Ankitha Shetty 25 Apr, 2023 Subscribe to our Newsletter Now Subscribe Leave this field blank

During core updates or module updates, it is crucial to ensure the stability and integrity of your Drupal website. Luckily, the Update API module and Update/Post Update Hooks are here to help.

The Update API module provides the hooks that are necessary for updating code and modules on your Drupal site. These hooks are nothing but Update and Post-Update Hooks which allow developers to customize updates according to their needs.

In this article, we’ll discuss the Update API, what are update and post-update hooks and when and how they should be used. By understanding both types of hooks, you can successfully update your Drupal site with minimal effort. Let’s get started!

The Update API

While working on an existing site, when you update code in a module, you may need to update stored data so that the stored data is compatible with the new code. You might have noticed errors like ‘The website encountered an unexpected error’ flash in front of you. Scary right!? I know! This is where Drupal’s Update API comes to our rescue.

If the update is between two minor versions of your module within the same major version of Drupal core, you can use the Update API to update the data. Update API allows you to provide code that performs an update to stored data whenever your module makes a change to its data model. The data model change refers to any change that makes the stored data on an existing site incompatible with that site's updated codebase. These Data model changes involve:

Updating the Configuration Schema

• Adding/removing/renaming a configuration key.
• Changing the data type of the configuration key.
• Changing the expected default value of a configuration key, etc.

Updating the Database Schema

• Adding/changing/removing a database table or field.
• Moving the stored data to a different field or table.
• Changing the format of stored data, etc.

Updating the Entities & Fields

• Adding a new base field to an existing entity type.
• Updating a field from an obsolete type to a new type, etc.

Updating the Data

• Manipulate the stored data on an existing site.

Working with Update hooks

Hook hook_update_N() is used to introduce an update between minor versions of a module. These hooks are placed within your module in the *.install file.

The hook_update_N() is written in the form of (module name)_update_(number). Here N comprises of:

• 1 or 2 digits refer to the  Drupal core compatibility (Drupal 8, 9, 10, etc.)
• The next 1 digit is for your module's major release version
• The last 2 digits for sequential counting, starting with 01

Example:

example_update_9201(): The first update for the 9.x-2.x versions.
Where ‘example’ is the name of the module, the first digit refers to Drupal core version ‘9’, the number ‘2’ refers to the module’s major release version and the last two digits ‘01’ indicates the first update function written for module ‘example’.

The numeric part of the hook implementation function (i.e, 9201 in the above example) is stored in the database to keep track of which updates have already been executed. So you should never renumber update functions.
To know the current schema version of a module ‘example stored in database’, use:

drush php-eval "echo drupal_get_installed_schema_version(‘example’);"

 

To manually set the current schema version of a module ‘example’ back to ‘9201’, use:

drush php-eval "echo drupal_set_installed_schema_version('example', '9201');"

 

Note: Please try to avoid using  drupal_set_installed_schema_version() function on production sites as it directly updates your database. You can use it on your local or lower test environments during development to reset the schema version.

Add a proper description in the document block comment before the update hook function as it will be printed for the users while running it.

Structure of hook_update_N(): /**  * A aimple hook_update_N() hook.  */ function example_update_9201() {  // Code goes here. }

These hooks are executed in sorted order, i.e., example_update_9201() hook executes before example_update_9202(), next is 9203, 9204 and so on.

You can also change the sorted order of these hooks, by introducing dependencies between the hooks. Use the hook hook_update_dependencies() to run updates between two update hooks.

 

All the update hooks are executed in batch and they also support batch processing of items. All update hooks have access to a $sandbox parameter which can be used to create batch processes in the update hooks in order to process huge data at once without causing any PHP to timeout.

A simple example of an update hook to add a new configuration key:

Currently, the example_module.settings.yml file contains:

 

 

To add a new key ‘description’ to the configuration:

• Add the ‘description’ key to the settings file

 

• Add the update_hook in example_module.install file:

 

• Use  drush updb to run the hook.

 

• Check the updated configuration, the new key ‘description’ is updated.

Working with Post Update hooks

Hook hook_post_update_NAME(), similar to the update hook, is used to introduce an update. But this hook is mostly intended to update data, like entities. These hooks are executed after all the hook_update_N() hooks are run. At this stage, Drupal is already fully repaired so you can use any API within the site.

These hooks are placed in a *.post_update.php file in your module.

The hook_post_update_NAME()is written in the form of (module name)_post_update_(any name). Here NAME can be any arbitrary machine name. This alphanumeric naming of functions in the file is the only thing that ensures the execution order of this hook.

Similar to update hooks, add a proper description in the docblock comment before the post_update hook. Also, do not reuse the same hook name.

Structure of hook_post_update_NAME():

/**  * A aimple hook_post_update_NAME() hook.   */  function example_post_update_test() {   // Code goes here. }

Just like with update hooks, use the $sandbox parameter to indicate that the Batch API should be used for your post_update hooks.

A simple example on the usage of post-update hook to update the term data:

• Currently, all the terms under Tags vocabulary have a disabled ‘Test example’ field.

• Add a post_update hook in example_module.post_update.php file to enable the ‘Test example’ field for all the existing terms.

 

• Use  drush updb to run the hook.

 

• Verify the updated term data, the checkbox ‘Test example’ must be enabled.

How to Run these hooks!

You can use the Drush command to execute these hooks, drush updb.It builds the batch in the following steps:

• All the update hooks are discovered.
• Resolves dependency and sort their order.
• Hooks are placed for batch processing.
• Next, all the Post hooks are discovered.
• If there are post_update hooks, and if update_hook has run previously, then caches are cleared.
• Then, push each post_update hook into the batch.
• Execute the batch.

One major advantage the post-update hook has over the update hook is that Drupal is fully functional at the time post-update is run. This allows developers to use any Drupal services while using the post-update hook. With the update hook, one must not assume that Drupal is fully repaired and avoid invoking other hooks, entity APIs, etc.

Final Thoughts

When trying to fix your site by updating config/database schema try to use update hooks. When comes to manipulating stored data, resaving configs, updating content entities, clearing the cache, etc then post-update hooks are more appropriate to use.

To be honest, there is no clear documentation on Drupal.org regarding when to use which hook! There is an open issue requesting to improve documentation on the usage of these two hooks to which you can contribute if you like.

But based on the developers' experience and by looking at the Drupal 9 & 10 core modules as an example, use update hooks to perform CRUD operations on configurations or databases (i.e repair the site) and use post-update hooks for CRUD content entities (then fix the data on the updated site), as post-update hooks are run after update hooks.

Enjoyed reading this article? Show us some love and subscribe to our weekly newsletter today!

Author: Ankitha Shetty

Meet Ankitha Shetty, a certified Drupal 9 developer. She loves attending and presenting at Drupal Camps and is a very active community member. Ankitha enjoys watching cricket and traveling to hill stations. Binge-watching web series is her current favorite pass time while she’s not cheering for her favorite cricket team :)

Email Address Subscribe Leave this field blank Drupal Drupal 9 Drupal 10 Drupal Development Drupal Planet

Leave us a Comment

  Recent Blogs Image Understanding Update and Post Update Hooks for Successful Site Updates Image Embracing Achievements - Gagana Girish’s Living Dream Image Data Security Matters: Marketers' Guide to Securing Your CMS Want to extract the maximum out of Drupal? TALK TO US Featured Case Studies

Upgrading the web presence of IEEE Information Theory Society, the most trusted voice for advanced technology

Explore

A Drupal powered multi-site, multi-lingual platform to enable a unified user experience at SEMI

Explore

Great Southern Homes, one of the fastest growing home builders in the US, sees greater results with Drupal

Explore View all Case Studies

Writing drupal hook_update_N() in Drupal 8, Drupal 9, Drupal 10. This also describes why hook update is needed, how it is formed.

Today we are talking about Drupal Security with Mark Shropshire & Benji Fisher.

For show notes visit: www.talkingDrupal.com/396

Topics

• Why do you care about security
• Best tips for securing Drupal
• Common Security Issues people have with Drupal
• Convincing module maintainers to do full releases
• Testing to ensure security
• Guardr Drupal security distribution
• What does the Drupal Security team do
• Finding issues
• Review compromised sites
• Becoming a member
• Process for writing security notices
• Helping the security team

Resources

• How to Join the Drupal Security Team
• How to get involved
• Passwords:
  • xkcd
  • Spaceballs
• Discussed at this BadCamp talk - Sleep Better at Night with a Secure Drupal Site
• OWASP
• OWASP Zap baseline
• Benji’s talk introducing the OWASP Top Ten
  • Current
  • Other versions
  • Source code (markdown)
• Github repo building and testing guardr
• Sam Mortenson talk
  • https://drupal.slack.com/archives/C1DD80ZKM/p1550697032017600
  • https://drupal.tv/external-video/2018-02-06/how-write-insecure-drupal-8-code
• Guardr core

Guests

Benji Fisher - tag1consulting.com @benji17fisher Mark Shropshire - shrop.dev @shrop

Hosts

Nic Laflin - www.nLighteneddevelopment.com @nicxvan John Picozzi - www.epam.com @johnpicozzi Jordan Graham - @jordanlgraham

MOTW Correspondent

Martin Anderson-Clutz - @mandclu CrowdSec Integrates your Drupal site with the open source CrowdSec Security Engine, a collaborative malicious activity detection and remediation tool.

Most of us want to be better versions of ourselves. Individuals, communities, organizations, and nations strive to progress in these changing times. However, it is not an easy task to achieve.

Progress comes through the knowledge of the present and a vision of the future. It begins with introspection. It requires one to point fingers at themselves rather than at others. It needs us to know our depths.

Apart from that, one needs to keep your eyes and ears open to new things. To new developments, new people, and new inspirations. Fresh water must keep flowing in to help a river do justice to its name.

A strong belief in our abilities must be at the heart of the journey forward. We must not forget who we are. We must not take our eyes off the goals that are there for us to achieve.

Progress isn’t a mechanical activity. Mind you; it won’t happen on its own. It awaits only mindful individuals or organizations that are self-aware. Open your eyes and ears. Humble yourselves to learn more. Above all, never let go of any chance to improve.

Now, let me walk you through the handpicked stories from the past week:

Drupal founder Dries Buytaert made some exciting announcements through his blog. Mautic, the marketing automation firm owned by Acquia, has now gone independent. Like Drupal, the community will drive its development. In another blog post, Dries disclosed the details of the Pitch-burgh contest that aims to encourage innovation. It will happen alongside DrupalCon Pittsburgh. Interestingly, Pitch-burgh is inspired by Shark Tank, the famous US TV show.

In another article published on opensource.com, Dries goes on to explain why it is essential to promote the Open-Web. Co-founder of PreviousNext, Owen Lansbury, has published a blog post on how a culture of open-source contribution helps his organization.

Aaron Winborn Award nominations are about to close. Do not forget to nominate Drupal community members who you think deserve the prize.

TDT conducted an in-depth interview with Jill Moraca. Princeton University’s Web Development Services Director responds to the questions posed by our Sub Editor, Alethia Rose Braganza.

We published a list of 5 YouTube videos for Drupal beginners. Another listicle presents 5 known Drupal modules you may not have installed.

Talking about security updates, two important ones were released last week. A new update to the DXPR theme helps its users comply with European privacy rules. Drupal has published a security update that clears an access bypass vulnerability.

Regarding Drupal events, DrupalCon Lille has released the last call for session submissions. Drupal Camp Asheville has extended the deadline to submit sessions. The Drop Times is now an official partner of the event.

The organizers of DrupalCamp Finland have published the final schedule. Those attending DrupalCamp Poland will get to explore Wrocław. The 2023 edition of MidCamp is set to begin on the 26th. The organizers of DrupalCamp Ruhr have designed Tshirts for the event on May.

Forms API helps to make forms in websites more enjoyable. Specbee has published a post on how to set up the same. Specbee also offers insights on how to use BEM methodology with Drupal and Data Security for Marketers who use CMS.

Velir has published a blog post on three new interesting modules for Drupal 10. Chapter Three shares information about hosting decoupled sites. LN Webworks has published a how-to guide on website personalization. Drupixels shares insights on the uses of the Automatic Entity Label module. OpenSense Labs writes about Drupal 10 Recipes.

A blog post published by Valuebound shows how to setup PHPUnit in Drupal 9 and 10. Opensources.com shared an article on how to use Autoloading and Namespaces in PHP. Drupal sites can now access Jonckers language services through a connector developed by the company.

A free webinar hosted by Drupal Partners will provide insights into Digital Marketing. Drupal Meetup at Zurich will discuss AI-powered search indexes and Splash Awards. The Drupal Bangalore User Group is all set to hold its monthly meetup on the 29th.

That’s all from the past week. We will update you with exciting stories from this week following Monday.

Sincerely,
Thomas Alias K
Sub Editor, TheDropTimes

Smartphones have taken the world of the internet to a whole new sphere. Today, consumers can effortlessly access a plethora of websites anytime and from anywhere through their mobile phones. It is fascinating to note that mobile devices contribute to around 62% of all e-commerce traffic globally. Without expending much energy on thinking, we can easily figure out why this exactly happens. After all, we all are smartphone users. Whenever we find some time, the first thing we do is look at our mobile phones. Besides, a whopping 56% of people spend their daily free time shopping online through their smartphones.

“Nothing worthwhile comes easily. Work, continuous work, and hard work, is the only way to accomplish results that last.” - Hamilton Holt

Drupal has undeniably been the most eminent enterprise content management system (CMS) since its inception. Once it started its journey of customer acquisition, there was no looking back. Even today, Drupal enjoys the stature of being the most admired CMS in the world. One of the major factors that contribute to its immense success is the brand’s relentless pursuit to deliver unmatchable services to its clients. This bespeaks its customer-first approach. Every two-to-three years Drupal updates its systems to ensure cutting-edge security and top-notch features.

READ MORE

Drush often serves as a utility knife for Drupal developers. It can be used to set up drupal,  maintain it and deploy it.  Drush is a command line shell and Unix scripting interface for Drupal. It runs update.php, executes SQL queries, runs content migrations, along with utilities such as cron or cache rebuild.  The word Drush is a combination of two words: Drupal + Shell. A shell is a command line tool for simplifying the management of websites by writing commands.   Why Use Drush Here are the main advantages of using Drush:

Modern businesses must provide customers with an engaging web experience to keep up with rising customer expectations. Mobile-first strategies and fast response rates have become standard practice, making a robust content management system (CMS) vital to businesses. Therefore, Drupal web development stands out as a suitable option for enterprises seeking to develop robust apps tailored towards meeting customers' requirements.

 Drupal's open-source CMS architecture combined with advanced security features has made it the platform of choice for well-known establishments such as Twitter and BBC. Businesses using Drupal can enhance customer experiences while increasing productivity; its advanced features also make it ideal for enterprise web development where tailored and engaging experiences are key.

Single Directory Components (SDC) is the biggest change to Drupal theming since the introduction of Twig. Here's an "unboxxing" walkthrough of how it works.

Releasing quality content is still the end goal of organizations, but as digital assets start to pile up and fly across your design, marketing, and content teams, how will you know when it’s time to adopt DAM (Digital Asset Management) as your source of truth for rich media over your standard Drupal Media Library?

I’ll walk you through the key differences between Drupal Media Library and Acquia DAM (Widen) to help you make the right call for your content management, organization, and publishing workflows. 

See also: “Managing your Content Smarter (Not Harder) with DAM” 

Acquia DAM by Widen 

The Digital Asset Management (DAM) platform is designed to manage a brand's vital assets throughout the content lifecycle. 

Acquired by Acquia in 2021, the Widen DAM product was one of the pioneers of DAM technology. Now known as Acquia DAM, it serves as a central hub and primary source of truth that facilitates the efficient management, organization, and distribution of digital assets with speed, intention, and control.

When asked what DAM does most effectively for day-to-day content and branding workflows, Nathan Holmes (Sr. Product Marketing Manager at Widen) attests to the impact of implementing DAM for your media-rich content: 

 "There's a lot of questions when it comes to working with creative files. Where is it? Do we have the rights to use it? What audience is this for? DAM is designed to answer these and many other questions for our teams."

Drupal Media Library 

Drupal Media Library is a module in the Drupal content management system that provides a central repository for storing and managing media assets such as images, videos, and audio files. 

Image Source: Drupal.org

It provides an easy-to-use interface for selecting and inserting media assets into content, as well as basic editing functions. It also integrates with other media management tools for added flexibility and customization.

Why DAM and Drupal Make Sense Together

If you’re using Drupal as your CMS and Content Editor, then you’re already halfway to using Acquia DAM since it’s such an easy integration. 

Acquia DAM makes integrating assets into your Drupal web pages seamless, ensuring that multiple teams have access to the same assets from a centralized location. Goodbye to those back-and-forth messages in search for the correct file. 

Here’s what you can do with Acquia DAM + Drupal: 

• Search and select assets from DAM in the Drupal WYSIWYG editor
• Position and align images from DAM through embed codes
• Track and manage which assets are being used where across your Drupal site(s)
• Configure and govern granular permissions to manage access to assets in Drupal
• Save storage space in Drupal by storing your assets as media entity references linked back to DAM
• Support requirements for SEO, site responsiveness, and accessibility

 

What the DAM module looks like in the WYSIWYG Editor

Formatting an image in the DAM module for Drupal’s WYSIWYG Editor 

To DAM or Not To DAM? 

Let’s start off with what kinds of questions we need to ask ourselves when considering whether to stick with Drupal Media Library or integrate DAM into your workflow. 

1. How many people need access to your assets? 

Depending on how granular you need to get, combined with the number of assets you’re dealing with, DAM can make sense, especially if you have longer workflows and multiple types of roles, from asset creators and approvers to content publishers. 

Acquia DAM can accommodate even the most fine-grained permissions. Via the Admin settings, you can assign specific permissions for adding, editing, and managing categories, metadata, and more within an intuitive interface. 

You can also provide access to users inside or outside of your organization via Portals, sharing selected assets with consultants, branding agencies or any other collaborators with a link, an access code, or a user login for added security. 

With clear channels of collaboration and full control over permissions, outside collaborators could even upload project files and final versions to an asset group for easy access and governance. 

Creating & managing user roles with associated permissions in Acquia DAM’s administration panel

2. How fast do you need transformation? 

If your teams are regularly publishing assets to multiple platforms, from social media channels to print campaigns, you’re probably spending more time converting, resizing and testing your assets for quality. 

With Acquia DAM, you can convert assets on the fly by selecting from a number of predefined formats (for example, Facebook, Instagram or Twitter) as well as defining your own dimensions. Drupal can do some of that, but expect to rely on additional contributed models via source plugins, as these extra formats are not part of the Drupal core.

Conversion Formats for assets in DAM to maximize usability across platforms 

Source: Widen Community

Dynamic embed codes in DAM for programming tasks such as changing file formats, adjusting the size, setting the crop ratio and background colour.

3. Do you know how your assets are being governed across departments? 

If you’ve ever hit “Publish”, only to realize that your content contained an out of date asset, you’ll know the importance of strong version control. We’ve all been there!

Version Control is built into Acquia DAM, and includes the option to either store multiple versions of assets, ensuring the most recent one is available for use, or to simply replace assets with the same file name to avoid conflicts or the infamous naming conventions “color-logo-DO-NOT-USE”. 

Even better, by allowing you to select which users can view versions, you can prevent content mixups and ensure that your publishing team only has access to approved or finalized assets, saving everyone time and headaches.

Furthermore, DAM administrators can also monitor asset use to gain valuable insights on the number of views, plays, average time watched, and geolocation data (among others).

“When your goal is to craft better content and campaigns, DAM is better to understand and measure the value, impact and engagement of individual assets to drive data-informed decisions.”

Real-time asset insights within DAM 

4. Is your storage busting at the seams? 

Depending on the volume of assets you’re managing, storage costs and performance times can become an issue when you’re relying solely on Drupal’s Media Library. 

Because Acquia DAM relies on embed codes in Drupal, serving them through a content delivery network (CDN), you can reduce storage space - not only for assets, but for all associated metadata, versions and accompanying information. 

Embed codes mean that there is no additional storage space required in Drupal, and you can benefit from the full suite of DAM functionalities available in Acquia’s product.

If you find yourself weighing your options for whether to just pay for more storage space or invest in DAM, consider some of the ways that DAM helps cut down on storage costs: 

• It reduces duplicate asset storage costs by helping you identify duplicate files and store the highest resolution version, and transform as needed.
• It enables a centralized repository of accessible assets across your organization rather than duplicating storage in shared servers. That way you’re only investing in one storage location within the DAM system. 
• Acquia DAM’s storage costs are competitive with what’s out there since they prioritize the value of the system versus high volume of assets and storage 

The Flexibility of Drupal, the Power of DAM

Whether DAM is the right call right now or in the future, the good news is that the benefits of leveraging Drupal’s scalability and flexibility as an open source technology include its seamless compatibility with the power and control of Acquia DAM (Widen). 

Making the call between using Drupal Media Library or switching to Acquia DAM boils down to the needs of your organization and just how much content needs to be managed, organized, and governed across your content teams.

Ready to know more? We’re here to help.

//--> //-->

+ more awesome articles by Evolving Web

Your business's success is heavily reliant on selecting the appropriate platform for creating an online store. There are tons of solutions out in the market, and finding the right platform can seem overwhelming. These two names appear as one of the top solutions for building your E-commerce business: Drupal Commerce and Magento 2 (Adobe Commerce). Both platforms have their strengths and weaknesses, and we’ll be exploring them in detail.

Don't worry if you're having difficulty deciding on a platform for your company. This article's got you covered! It explains everything you need to know about E-commerce platforms and helps you make the best decision.

The story of the website's performance importance is never-ending since users need accessible and fast web resources to complete desired conversions. One of the best solutions to timely boost website speed is Quicklink, that Five Jars reviews in today's article.

We understand that website design isn't just about aesthetics; it's also about complying with privacy laws and regulations. Our latest DXPR Theme update takes care of both design and privacy concerns, including the following enhancements:

Better Privacy for Google Fonts

The old way of loading Google fonts is not compliant with privacy laws in Europe. In fact, German courts have ruled that loading fonts from Google CDN equates to leaking PII (Personally Identifiable Information), such as the user's IP address, and have fined websites €100 for loading Google fonts this way. One of our clients was recently threatened with legal action due to their use of Google CDN in DXPR Theme, which prompted us to take action.

The German court's ruling threatens a fine of €250,000.00 for each case of infringement or, alternatively, six months imprisonment if the site owner does not comply and continues to provide Google with IP addresses through their use of Google Fonts. At DXPR, we take data privacy very seriously, which is why we've modified our DXPR Theme to serve Google fonts from the local public file system, avoiding any leakage of PII.

Security Update or Compliance Update?

Technically, leaking PII is considered a security bug. Because DXPR Theme is hosted on Drupal.org, the Drupal security team governs what is and isn't considered a security update. The team decided they see no benefit in marking this update as such. However, as an Amsterdam-based company, we do consider this issue a security issue because EU law does consider leaking IP addresses to 3rd parties without user consent as a security problem. Therefore, we published the Google Fonts update on all branches of the DXPR Theme, including the Drupal 7 branch.

More Color Schemes and Enhanced Theming

In addition to better privacy for Google Fonts, our DXPR Theme update also includes eight new color schemes, including "dark mode" palettes. We've also enhanced the theming of tabs, tables, and collapsibles to work better with color palettes. This update ensures that our client's websites are visually appealing and offer a great user experience.

Check out all color schemes on Drupal.org/project/dxpr_theme

Bug Fixes

Our DXPR Theme update also fixes several bugs, including the issue with vibrating pages when using a sticky header and page content height close to or equal to the viewport height. We've also fixed the issue with full-screen search and breadcrumb styling not working in DXPR Theme 5.x  (Bootstrap 5) sub-themes. Finally, we've improved the styling for threaded comments.

Risks of Using @font-your-face Module

It's important to note that if you're using the popular @font-your-face module to load Google fonts or other fonts from a CDN, you're still risking the fine. It’s essential to make sure your website is fully compliant with privacy laws and regulations, and our DXPR Theme update ensures just that.

About DXPR Theme

DXPR Theme is a low-code Drupal theme that allows you to customize over 200 settings for your website design. It offers mobile optimization and improved SEO to ensure your site is accessible on any device. Additionally, DXPR Theme comes with comprehensive documentation and customer support to help you every step of the way. Give DXPR Theme a try on our online admin demo site to simplify your Drupal website creation process and launch your ideal website.

The Drupal Association is excited to host "Pitch-burgh", an innovation contest, at DrupalCon Pittsburgh and to invite community members to propose their ideas for innovating Drupal, with the top ideas receiving funding.

Beyond just hosting the contest, the Drupal Association is committing funds to make a direct financial investment in the best ideas and will provide management resources to support taking pitches from idea to implementation. Additionally, we will work with other “sharks” to put together the necessary resources to make these ideas a reality.

Information about how to participate and submit your ideas can be found here.

The brainchild of Dries Buytaert, “Pitch-burgh” is the first of a series of initiatives that the Drupal Association will be undertaking to speed up innovation of Drupal as part of a strategic plan created by the Association’s Board of Directors To maintain Drupal as the best CMS in the world and an impactful champion of the Open Web, we need to continually explore where it needs to go next. What better way to do that than to tap into our very creative and very dedicated global community?

Let the pitches begin!

Tim Lehnen joins us! Tim is the Drupal Association’s Chief Technology Officer and is one of the voices in the room when it comes to decisions around Drupal 7’s End-of-Life. We talk with Tim about that as well as how he thinks about sites still on Drupal 7, modern Drupal’s growth being better than the usage graphs show, and even Drupal.org still being on Drupal 7 (for now)!

xdebug not working in vscode