Changes were rebased on 6.1.x branch. Helper service was tested in update hook and worked as expected: string translations were updated.
Tested profile installation with the changes. Email registration module was installed during RS profile installation and user was able to register and login via email.
trafo → made their first commit to this issue’s fork.
Rebased on top of 2.1.x, renamed category config files and updated some translations to reflect changes in v2.
Rebased changes on top of 6.1.x
cli_language module only locks language in the CLI, but not in the UI. So dev is still able to create config in another language.
This might fix weird issues during config import/export when language is switched in the middle and config translations are overridden.
The 🐛 Prevent saving config entities when configuration overrides are applied Needs work gained again some momentum and looks more like fix to this issue.
trafo → made their first commit to this issue’s fork.
Successfully imported layout section templates into LB library during module install.
For testing was used 1.4.x-dev version of single_content_sync with required changes, so new release of single_content_sync is needed.
Once this is done, it's ready to go.
As a user with webadmin role I was able to add block to top and bottom region on multi-column section.
Run into this issue and tracked it to EasyBreadcrumbBuilder. It calls Router::matchRequest($request) which applies route enhancers. One of the enhancers is LayoutBuilderTempstoreRouteEnhancer which has private temp store that will try to start session. Fix is to disable it while indexing (see
#3274158-3: RuntimeException while trying to render item →
).
Not sure if this module can do much about it.
Run into this issue again and tracked it to EasyBreadcrumbBuilder from easy_breadcrumb module. It calls Router::matchRequest($request) which applies route enhancers. One of the enhancers is LayoutBuilderTempstoreRouteEnhancer which has private temp store that will try to start session.
Found a fix in #3274158-3: RuntimeException while trying to render item → , #3274158-19: RuntimeException while trying to render item → , #3274158-27: RuntimeException while trying to render item → . This might be added into this codebase.
Reviewed MR and after applying changes error is fixed. Changing to RTBC.
Patch solves the issue. Be aware that with this change module also loses compatibility with Drupal 8.
Changing status to Reviewed and Tested by Community.
Reviewed and applied patch. It solves the issue.
Changing status to Reviewed and Tested by Community.
Reviewed and applied patch. It solves the issue.
Changing status to Reviewed and Tested by Community
I fixed reported issues in code and UI.
The best approach seems to be to upgrade to latest 3.x version and then upgrade to version 4.x.
During entity_legal_update_9002 I've got error The field has already been deleted and it is in the process of being purged. and update failed.
What helped was catching the exception.
My bad, it works. Must have been some cache issue while I was doing module update, although I remember frantically cleaning it. Thank you for your time.
Updating from 3.10 to 4.1.6:
[notice] Update started: simple_sitemap_update_8401
[error] SQLSTATE[23000]: Integrity constraint violation: 1062 ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '1' for key 'PRIMARY': ALTER TABLE "simple_sitemap" CHANGE `id` `id` INT unsigned NOT NULL auto_increment COMMENT 'Sitemap chunk unique identifier.'; Array()
In my case problem was that there was already sitemap chunk with id 0 in simple_sitemap table.
Solution could be just simply delete all records with \Drupal::database()->query('DELETE FROM {simple_sitemap}');.
Other possibility would be update with MAX(id) + 1
jQuery.once was replaced in MR.
Replaced jQuery.once library.
I created the fix.
Hooks have been replaced.
trafo → created an issue.
jquery.once was replaced by core/once.
jquery.once was replaced by core/once.
jquery.once was replaced by core/once.
Changes were backported.
Changes were backported.
jquery.once was replaced by the core/once.
jquery.once was replaced by core/once.
jquery.once was replaced by core/once
I've created plugin for CKEditor 5. It uses structure/tag of the current plugin, so it should be backwards compatible with already created content.
I had to update code and `cookie-content-blocker` library dependency to use `core/js-cookie`, since `jquery.cookie` was removed in D10.
Backported changes from #3368155
Widget class was removed.
In the project was $variables passed by reference in THEME_responsive_table(). This let into discovery that rows are not constructed correctly and it's even not necessary to do that since $cell['attributes'] is an object.
I've just cleaned up the code and removed unnecessary assignments.
Changes were backported.
Changes were backported.
Changes were backported.
Backported changes from ✨ Switch default front-end theme to Olivero Fixed
Backported changes from version 6.x.
Just config files clean-up. Profile update and fresh installation were successful.
Config files were cleaned-up and updated, update hook was removed. Ready for review.
Changes were backported.
Changes were backported.
Template entity-page-title.html.twig was added to storybook.
CSS styles were added to make layout builder entity form sticky. Be aware, that sticky position does not play nicely when parent element adjusts overflows e.g. .page-wrapper and just stops working.
Required/Optional marker was added and will be displayed based on the condition.
trafo → made their first commit to this issue’s fork.
Expression 'form-actions' in attributes.class|keys is translate into this PHP code in_array('form-actions', [ 0 ], FALSE).
In PHP 7.4 in_array would return TRUE since it uses loose comparison and 'form-actions' == 0 is TRUE.
Since PHP 8.0.0 this is fixed as note in PHP doc states it: https://www.php.net/manual/en/function.in-array.php
Proposed solution is to remove keys twig filter, since it doesn't make sense.