Last updated: 14th April 2022
Released: 14th April 2022
There are no known issues with version 6.8.2 of Site Studio.
When using WYSIWYG field on a component and linking to both a WYSIWYG element and a hide if not data field, it would add extra br tag for each line break.
Rendered WYSIWYG will not longer output extra br tag.
You need to re-save effected entities or perform a rebuild.
None.
When exposing filters on a view and utilising a module/library such as Select2 the select2 library was not attaching as expected on page load
Following a cache rebuild the select2 library will attach to select elements as expected
Cache rebuild
None.
Fixes a bug where a modal that had the autoload functionality enabled was not autoloading as expected and a browser console error was displayed.
Modals that should autoload will now automatically load as expected.
Run an API import drush cohesion:import when upgrading.
None.
When editing a translated page, the edit buttons would not show when using the Visual page builder
You can now edit component on translated pages
None.
None.
When exporting single entities (like components) via UI, full package settings for entity type restrictions were applied. This has been fixed and full package export settings now only apply to full package exports.
Individually exported entities will no longer follow full package export settings. This will resolve some unexpected behaviour, such as files with zero bytes content being exported when single entity packages export would contain items restricted by full packace export settings.
If you have single entity packages exported with zero bytes content, exporting the same entities again
None.
Fixes a bug when attempting to upload font and icon font files would produce an error.
Fonts and icon fonts can be uploaded correctly without error on a path based multi-site.
Run a cohesion API import drush cohesion:import when upgrading.
None.
When importing Drupal config, if the Site Studio module has been initialised, templates generation will occur if relevant content types are imported.
Templates will be generated when Drupal config is imported.
None.
If templates are generated during deployments, CLI output will have additional output - we recommend additional testing of automation tools that rely on such output.
We have added new drush command sitestudio:templates:regenerate that will trigger templates regeneration manually. This is useful in case a non-standard workflow was used to introduce content type changes (for example direct database manipulation) or if Drupal is in a state of templates misalignment due to config import completed prior to Site Studio 6.8.2.
None.
None.
If templates are generated during deployments, there will be additional CLI output - we recommend additional testing of automation tools that rely on such output.
When exporting packages via UI using the new package management non super-admin role users would encounter "access denied" screen when trying to download generated package, even if they would have "access coheison_sync" permission assigned to their role.
Only users with "access cohesion_sync" permissions will be able to export packages via UI.
None.
None.
As with any version of Site Studio, we recommend that you backup your websites database and code before upgrading the version of Site Studio. There are no other specific steps to carry out before upgrading to this version.
It is recommended that you backup and upgrade your website on a development environment before applying to a production website. You can upgrade your version of Site Studio by following our upgrade guide.
If this content did not answer your questions, try searching or contacting our support team for further assistance.