Today, we’re releasing Genesis 2.5.1, which addresses a few issues that have been reported since Genesis 2.5 was released. In addition, Genesis 2.5.1 has also been tested and is compatible with the latest WordPress 4.8 update.
In Genesis 2.5, we introduced a Layout API that allowed developers to register a layout with different types depending on context. You can register and apply a layout to, for instance, only category archives, or only for a specific author’s archives, etc.
However, there was a problem with the method we used for determining layout priority internally. That has been fixed, and everything should work fine in Genesis 2.5.1.
Exclude Posts Widget Setting
In the featured post widget, if you selected the option to exclude posts that had already been displayed, there were certain circumstances where this wouldn’t work. We fixed the issue that was causing the problem.
In Genesis 2.5.0, we deprecated several unnecessary constants. When switching to the references in the Genesis source away from these deprecated constants, we missed a few that caused some issues for users in some circumstances. We removed the internal references to those constants, eliminating the possibility for Genesis to throw an error as a result.
Double Loading of Files
In Genesis 2.5.0, we tried to switch to the use of require rather than require_once for files. However, if a child theme or plugin tries to include a core Genesis file, it will throw an error. Therefore, we switched back to require_once in Genesis for the future.
Attribute Filters Running Twice
Because of the use of the Markup API to output opening and closing tags now, filters on attributes can run twice (on opening and closing) for a given context. This is usually not a problem, but in certain cases it was causing issues. For those cases, we have limited the filter to only running on the opening tag.