Releases for AdaptiveTheme

Creating Drupal 11 compatible branch

Adding dependency for contributed stable theme for compatibility with D10

This is the initial release of the version that will eventually support Drupal 10

This is a long-overdue release of a bunch of bug fixes. It's also the dev release that was updated a few weeks ago.

This is the first release of the 8.x-4.x branch. 4.0 is compatible with Drupal 9.

Minor release to account for:
- weights of custom CSS stylesheets
- duplicate ID issue on main content

Internally AT Core now uses Libsass instead of Ruby Gems etc, this does not affect sub themes or normal usage (only of interest to AT Core developers).

Stable updated release for the 8.x-2.x branch.

Continue to use the 8.x-2.x branch if your theme was generated using 8.x-2.x or is currently using 8.x-2.x branch.

Stable release for the 1.x branch, for all sub-themes created using this branch please stick with it. For those using 2.x please carry on with that branch.

This branch follows on from 8.x-1.x as of 16th Feb 2017.

Please see this important issue regarding versions and what to upgrade to next for your sub-theme: #2853031: Git versions and Release Issues

Major update for the RC.

Code name: Isadora
Time in development: 2.5 years
Headaches endured: uncountable :)

No code - no problem!

Adaptivetheme for Drupal 8 is designed for people who don’t code, or for those who only want to write a bit of CSS but still want a sleek and sophisticated theme for todays mobile web.

Development release for Adpativetheme Drupal 8.

The D8 version of Adaptivetheme is a total re-write of the core theme and sub-themes. The admin theme has been removed also.

You MUST enable AT Core

This theme uses OO PHP and autoloads classes - this does not work in Drupal 8 when the base theme is not enabled - if you try to enable a sub-theme without first enabling AT Core you will get fatal errors on both the sub-themes Appearance settings page and in the front end.

Everything is treated as a Block

NOTE: this current version anticipates the commit to Drupal 8 of the "convert everything to a block" patches. This means that if you enable this theme you will not see things link the Logo, Site name or slogan, Page titles, Tabs, Actions links etc etc. The one page level variable I have included as a legacy support feature is the Messages variable, because we really need that during development. When the D8 patches are finally committed this will be removed.

I have created a small sandbox module that implements these blocks - you can use this if you prefer not to apply core patches, note I will try to keep the module up to date:

https://drupal.org/sandbox/jmburnz/2122067

Please see these issues and help out if you can:

#1053648: Convert site elements (site name, slogan, site logo) into blocks
#1869476: Convert global menus (primary links, secondary links) into blocks
#507488: Convert page elements (local tasks, actions) into blocks

Initial stable release for Adaptivetheme 7.x-3.0

If you have used previous release candidates please check settings for the Unset CSS feature - the setting names changed and if you save your theme settings without updating your settings (by re-checking unset files in theme settings) your settings will be lost.

RC5 fixes an issue with the type juggling for theme settings introduced in RC4 where the font settings caused a fatal error due to bad return value of the setting (which in turn caused a file not be included and thus the fatal error for an undefined function).

This juggling has been removed and instead I have changed some comparison operators where they were known to cause issues on some systems, namely in theme_breadcrumb.

Other small changes and improvements:

This release is to update form states since they changed in Drupal 7.14, which fixes the issue with hidden max-width settings and other issues surrounding form states (mainly cases where some theme settings could not be seen or properly enabled).

RC2 is the last of our Release Candidate releases. Hereafter we will go for a stable release. The theme has been in development now for many months and is very stable.

Included in this release are mostly usability/user experience improvements, bug fixes and small feature enhancements - there are no "new features", only adjustments to existing features.

- Responsive Panels and Gpanels system will now only load what is used. This means if you are not using Panels only the settings for Gpanels that are actually used in the theme will show up. If you are using Panels they will all show, and if you are using both (e.g. using Panels with Pixture Reloaded) then they will all show and the theme will tell you which Gpanels layouts you are using. If Panels is not enabled and you have no Gpanels, a likely scenario when first starting, then nothing shows and you get a friendly message about this. This is a UX improvement - users got confused and thought they needed to install the Panels module, or that it was a requirement. Also the default "show all" overwhelmed some users when in fact they were only using one or two Gpanels.

OK, this is it, the Release Candidate is a go!

From here on in new features will not be added, only bugs and minor tweaks will be applied, so we're really looking for those bugs or small oversights that may have occurred at some stage during dev, and we can only find those by actually using the theme in real everyday site and theme builds, so time to get hacking ;)

There were quite a few changes from beta1:

- Google fonts got a total overhaul. I was never really happy with it so when it was suggested we use a text field and allow users to just paste in the font name and make a few settings I jumped on it. Its now more flexible, faster and requires far less maintenance, and you are not held to the list the theme maintains, use any font the moment it gets released on Google. Its a win win and while a little harder to use, its just a lot better. #1534416: Use text input instead of select for Google fonts option

- Stylesheet load failure warning system. This was built to ease migration and deployment issues for large sites using GIT or other VCS that migrate on a daily basis from dev to staging etc but do not version control the files directory. This warnings tell the admin the theme settings must be re-saved to regenerate the CSS files: #1543990: Set message if generated files are missing, document file generation

- Old generated files are now removed, instead of saving them all.

- adds Unset CSS extension, themers can now easily unset any core, contrib module or library CSS file from the UI or use info file declarations.

- improve many docblock comments and add new comments for developers

- improve hook_css_alter() implementation for the Unset CSS feature

Note this is quite likely to be the last alpha, the code is coming very stable now, unless we hit any snags this will be it, next round will be into a beta or even strait into an RC. Its getting very close.

- Improves cache handling for the Plugins system to speed up admin operations.
- Adds new feature for wrapping panels layouts when used in Display suite nodes, see http://drupal.org/node/1514216
- Adds new documentation to many functions, improved documentation for most functions already documented.

Initial stable release of 7.x-3.x

This is a major upgrade of the base theme will almost every line of code rewritten and many new features for site builders, theme developers and those hard core PHP developers out there using this framework.

Please see the Project page, there is a brief run down there of the main features and changes, also check the issue queue, there are a couple of exisiting issues (mainly tasks) but I envision there will be some bugs and other issues that will crop up in the next weeks or so prior to a full stable release.

None of the existing sub-themes have been update to work with this, but for the most part should work, see below.

Notes About Existing Subthemes:

Daily snapshot for the 7.x-3.x series, with responsive Panels and Gpanels layouts baked in.

Adaptivetheme 7.x-2.0 is out!

In short this new version brings in a slew of new features including mobile device support with media queries and configurable layouts for these devices, much improved back-end performance, improved UX and usability, we've made it easier and faster to complete routine theme building tasks to save us (and you) time and cost when building new themes.

We've also improved the accessibility features in the theme, better body class handling and more options for body classes. We have made some very minor adjustments to the markup - namely put a wrapper on breadcrumbs and moved the user picture inside the article and comment wrappers respectively, other than that we did not touch the markup.

The admin theme has had a major make over and now for the first time we have been able to work around Drupal's inherent bugs and you can actually use the admin theme for real! Amazing! And it looks great as well.

Of course the big feature in AT 7.x-2.0 is the layout engine with mobile device support - we really hope you like this, it took a hell of a lot of development and we're really quite chuffed with it - we'll be working hard on documentation this week and putting some other nice freebies out there, such as Footheme.

7.x-2.0-beta1 is the first release node for the 2.x series and includes the all new layout engine for mobile support.

This version also includes a workaround for the admin theme so it will work in Drupal 7 (there is a bug in D7 that prevents an admin theme and the front end theme using the same base theme, it cannot be fixed in D7 and this workaround is the best we can do).

Due to git problems I am making a new release - these changes should have been mostly in the previous version but for one reason or another did not get committed.

Changes include fixed forum icon, subtheme theme settings now use the vertical tabs of the core theme, added new dark.css file with new white arrows for menus. Some other minor fixes to CSS and comments.