### Genesis 3.6.0 Now Available
Genesis 3.6.0 has been released! This update addresses deprecation notices that may appear on websites running PHP 8.2+ and WordPress 6.7+.
—
## How to Update
If you’re already using Genesis, you should see an update notification in your WordPress admin dashboard.
If the update prompt is missing, ensure that:
– You’re running WordPress 5.0+ and PHP 5.6+
– You’re using a Genesis HTML5 child theme
– Update notifications are enabled under **Genesis → Theme Settings → Updates**
### Updating Child Themes and Plugins
After updating to Genesis 3.6.0, if you still encounter deprecation notices, check your child theme and plugin versions. The following updates contain additional fixes:
– **Genesis Blocks 3.1.7**
– **Genesis Sample 3.4.3**
– **Altitude Pro 1.5.2**
– **Essence Pro 1.5.3**
– **Navigation Pro 1.2.2**
To update **Genesis Blocks**, go to **Dashboard → Updates**. For child theme updates, log in to your **StudioPress** or **WP Engine** account to download the latest versions. You can find more information in the [StudioPress documentation](https://my.studiopress.com/documentation/frequently-asked-questions/genesis-framework-faqs/do-i-need-to-update-my-child-theme/) or [WP Engine documentation](https://my.wpengine.com/themes/docs/frequently-asked-questions/genesis-framework-faqs/do-i-need-to-update-my-child-theme/).
—
## What’s New in Genesis 3.6.0
The [Genesis changelog](https://studiopress.github.io/genesis/changelog/#3.6.0—2025-03-20) highlights fixes for two PHP deprecation notices:
– A `_doing_it_wrong()` notice that appeared when using WordPress in non-US English locales.
– A deprecation notice in the Customizer:
“`php
PHP Deprecated: str_contains(): Passing null to parameter #1 ($haystack) of type string is deprecated
“`
—
## Developer Notes
If you develop Genesis themes or plugins, consider these steps to help users avoid deprecation notices:
1. **Update `genesis_responsive_menus()` Usage**
– If you call `genesis_responsive_menus()` in your theme’s `functions.php` or plugin file without a hook, move it to the `after_setup_theme` hook.
– This prevents the “doing it wrong” notice about loading menu translations too early.
– See [PR 412 in Genesis Sample](https://github.com/studiopress/genesis-sample/pull/412/files) for an example.
2. **Refactor `config/layouts.php` for Translations**
– If your theme registers or overrides Genesis layouts in `config/layouts.php`:
– Remove translation functions (e.g., `__()`) and replace them with plain text strings.
– Add a new `config/layouts-labels.php` file with translated text labels.
– This ensures translations load at the correct time.
– See the updated [Genesis layout documentation](https://studiopress.github.io/genesis/developer-features/genesis-layouts/#default-genesis-layouts) for details.
3. **Debugging Translation Notices**
– If you’re seeing a “doing it wrong” translation notice, the [Query Monitor plugin](https://wordpress.org/plugins/query-monitor/) can help track down the source.
4. **Stay Updated on WordPress Internationalization Changes**
– Check out the [Make WordPress blog post](https://make.wordpress.org/core/2024/10/21/i18n-improvements-6-7/) on internationalization updates in WordPress 6.7 for more context.
—
By following these steps, you can ensure compatibility with the latest PHP and WordPress versions while maintaining a smooth experience for your users. Happy updating! 🚀
