I see now where the problem is.
1 - Clean installation of Drupal 10.3.0 + devel (I generated 50 nodes) - the table with the sticky header works correctly
2 - I installed the new Droopler 4.0.0-alpha2 profile and the generated subtheme.
3 - default Claro skin - everything works fine
4 - default subtheme skin - headers are static
5 - my subtheme does not inject the sticky-header class, hence the static header when a theme other than Claro is set.
Is there an easy way to tweak the subtheme to make this work?
If not, I suggest closing the topic and contacting the Droopler designers on how to correct it.
Thank you very much for your help so far and valuable comments on what and how to check.
The fix
https://www.drupal.org/node/3440477 →
is already included in version 10.3.0 - so I didn't add anything.
I tested on https://simplytest.me (Umami) with an array both in the form of a block and a page - everything works. Unfortunately not for me.
I only applied the fix mentioned in #8
https://www.drupal.org/node/3440477 →
I did not make any other corrections
I applied these fixes in version 10.2.7 and they did not work. After updating to 10.3.0, I did not apply any corrections and the headers in the views block still do not work correctly.
I don't really know what's going on, because in my opinion it should work in 10.3.0, because the problem was reported earlier and from what I saw, it was apparently solved.
I applied two fixes as suggested:
https://www.drupal.org/project/drupal/issues/3451738
📌
Remove JavaScript from Views configuration form now that it is only CSS
Needs review
https://www.drupal.org/node/3439580 →
I tried the solution
https://www.drupal.org/node/3439580 →
but it produced no results.
I was hoping that the stable version 10.3.0 would solve this problem, but unfortunately it didn't.
pingwin_cracow → created an issue.
I tried to update according to the given concepts and unfortunately the sticky header table does not work.
After updating Drupal to version 10.3.0, unfortunately the table headers are still static and the sticky application does not work.
I updated to Drupal 10.3.0 and the problem still persists which is very irritating.
Is there a chance for a quick solution so that I can edit the text format settings?
pingwin_cracow → created an issue.
Confirmed, I have the same problem after updating to Drupal 10.3.0-beta1
Exactly the same errors mentioned above.
pingwin_cracow → created an issue.
{
"name": "droptica/droopler-project",
"description": "Project template for Droopler with Composer",
"type": "project",
"license": "GPL-2.0-or-later",
"homepage": "https://www.droopler.com",
"support": {
"docs": "https://www.droopler.com/developers",
"issues": " https://www.drupal.org/project/issues/droopler?categories=All → "
},
"repositories": {
"drupal": {
"type": "composer",
"url": "https://packages.drupal.org/8"
},
"asset": {
"type": "composer",
"url": "https://asset-packagist.org"
}
},
"require": {
"composer/installers": "^2.0",
"cweagans/composer-patches": "^1.6",
"dompdf/dompdf": "^1.0.2",
"droptica/droopler": "^8.3.3.0",
"drupal/core-composer-scaffold": "^10.2",
"drupal/core-recommended": "^10.2",
"drupal/csv_serialization": "^4.0",
"drupal/eca": "^1.1",
"drupal/inline_entity_form": "^1.0@RC",
"drush/drush": "^12.0",
"oomphinc/composer-installers-extender": "^2.0",
"phpmailer/phpmailer": "~6.1",
"phpoffice/phpword": "v0.18.*",
"zaporylie/composer-drupal-optimizations": "^1.1"
},
"require-dev": {
"drupal/core-dev": "^10.2"
},
"conflict": {
"drupal/drupal": "*"
},
"minimum-stability": "dev",
"prefer-stable": true,
"config": {
"sort-packages": true,
"allow-plugins": {
"dealerdirect/phpcodesniffer-composer-installer": true,
"composer/installers": true,
"cweagans/composer-patches": true,
"drupal/console-extend-plugin": true,
"drupal/core-composer-scaffold": true,
"oomphinc/composer-installers-extender": true,
"zaporylie/composer-drupal-optimizations": true,
"drupal/core-project-message": true,
"drupal/core-vendor-hardening": true,
"phpstan/extension-installer": true,
"php-http/discovery": true
},
"preferred-install": {
"droptica/droopler": "source",
"*": "dist"
}
},
"extra": {
"enable-patching": true,
"drupal-scaffold": {
"locations": {
"web-root": "web/"
}
},
"installer-types": ["bower-asset", "npm-asset"],
"installer-paths": {
"web/core": ["type:drupal-core"],
"web/libraries/{$name}": ["type:drupal-library", "type:git", "type:bower-asset", "type:npm-asset"],
"web/modules/contrib/{$name}": ["type:drupal-module"],
"web/profiles/contrib/{$name}": ["type:drupal-profile"],
"web/themes/contrib/{$name}": ["type:drupal-theme"],
"drush/Commands/contrib/{$name}": ["type:drupal-drush"],
"web/modules/custom/{$name}": ["type:drupal-custom-module"],
"web/themes/custom/{$name}": ["type:drupal-custom-theme"]
}
}
}
this is my composer.json file.
I don't remember exactly in what order I uninstalled lazy and rdf.
You definitely need to check the editor's text format settings and turn off lazy in each profile.
.../admin/config/content/formats
Try to install Droopler 3.2 and only after Droopler updates the requirements will you be able to uninstall lazy.
Rdf is in core D9, it is removed automatically by D10 during update. It does not need to be removed manually with Droopler 3.2 - it is not necessary.
You are very right @Aanjaneyam, the update instructions are not very clear. I had to fiddle a bit. In short, I did this.
Drupal 9 - I checked modules that are incompatible with D10 and uninstalled them, or introduced a patch for a given module to avoid a fatal error.
Then I compared the Droopler 3.3 requirements in Droopler's composer.jons and updated the modules version to the versions required by D10.
Next in composer.jons I changed the requirement to "droptica/droopler": "^8.3.3.0", and started the installation on D9. Having Droopler version 3.3 and D9, I changed the requirements to D10 and restarted the installation. It worked. Just in case, after each update I ran update.php to avoid database errors.
If an error occurs during installation, pay attention to which module causes it.
And finally, an important thing - uninstall the Droopler subtheme (if you use it) before installations. After installing Drooplerr 3.3, customize your subtheme to version 3.3 based on Droopler 3.3 Theme. Otherwise, you will initially have an incompatibility conflict between Theme Profile and Droopler's Subtheme.
Good luck and let me know how it goes.
Regards.
Thank you very much,
I came to the conclusion that the requirements of Droopler 3.3 are lower than those of Drupal 10.
After the corrections, the update went well. Now it works almost fine with Drupal 10.2.-beta2.
There are a few more minor warnings, but they are more related to module errors than Droopler.
Regards
pingwin_cracow → created an issue.
pingwin_cracow → created an issue.
Additional information:
a)
D9.5.11
php 8.2
Droopler 3.2.0-rc1
Drupal Mega Menu 8.x-1.16 (or Drupal Mega Menu 8.x-1.14) + patch
This menu setup works fine
After update:
b)
D10.1.4
php 8.2
Droopler 3.3.0-rc1
Drupal Mega Menu 8.x-1.16 (or Drupal Mega Menu 8.x-1.14) + patch
Unfortunately, it either doesn't work at all or develops and disappears.
pingwin_cracow → created an issue.
Thank you very much for help,
I compared the files and it turned out that during the conversion from CKE4 to CKE5 I removed the full HTML format (CKE4) too early and switched to CKE5. The option to select an editor has disappeared.
After restoring the full HTML format (CKE4), you can go to the settings again.
Conclusion: First, you need to set the HTML editor settings to CKE5 in Webform (/admin/structure/webform/config/elements) and only then you can safely delete the CKE4 editor profile.
Maybe my mistake will be useful to someone who, like me, is in a hurry to delete the old CKE4 profile.
Now everything works properly.
Best Regards
pingwin_cracow → created an issue.
I have made the code corrections presented
https://git.drupalcode.org/project/views_natural_sort/-/merge_requests/11...
Unfortunately, there are still errors in the sequence.
I wonder if there are still errors in the code, or maybe it's in another module?
I use it
D 10.1.4
php 8.2
new errors detected:
Deprecated function: Creation of dynamic property Drupal\views_natural_sort\IndexRecord::$type is deprecated in Drupal\views_natural_sort\IndexRecord->generateType() (line 213 of modules/contrib/views_natural_sort/src/IndexRecord.php).
Drupal\views_natural_sort\IndexRecord->generateType() (Line: 100)
Drupal\views_natural_sort\IndexRecord->setEntityType('paragraph') (Line: 66)
Drupal\views_natural_sort\IndexRecord->__construct(Object, Array) (Line: 397)
Drupal\views_natural_sort\ViewsNaturalSortService->createIndexRecord(Array) (Line: 342)
Drupal\views_natural_sort\ViewsNaturalSortService->storeIndexRecordsFromEntity(Object) (Line: 92)
views_natural_sort_entity_insert(Object) (Line: 102)
views_natural_sort_entity_update(Object)
call_user_func_array(Object, Array) (Line: 409)
Drupal\Core\Extension\ModuleHandler->Drupal\Core\Extension\{closure}(Object, 'views_natural_sort') (Line: 388)
Drupal\Core\Extension\ModuleHandler->invokeAllWith('entity_update', Object) (Line: 408)
Drupal\Core\Extension\ModuleHandler->invokeAll('entity_update', Array) (Line: 217)
Drupal\Core\Entity\EntityStorageBase->invokeHook('update', Object) (Line: 900)
Drupal\Core\Entity\ContentEntityStorageBase->invokeHook('update', Object) (Line: 564)
Drupal\Core\Entity\EntityStorageBase->doPostSave(Object, 1) (Line: 781)
Drupal\Core\Entity\ContentEntityStorageBase->doPostSave(Object, 1) (Line: 489)
Drupal\Core\Entity\EntityStorageBase->save(Object) (Line: 806)
Drupal\Core\Entity\Sql\SqlContentEntityStorage->save(Object) (Line: 339)
Drupal\Core\Entity\EntityBase->save() (Line: 303)
Drupal\entity_reference_revisions\Plugin\Field\FieldType\EntityReferenceRevisionsItem->preSave() (Line: 233)
Drupal\Core\Field\FieldItemList->delegateMethod('preSave') (Line: 191)
Drupal\Core\Field\FieldItemList->preSave() (Line: 938)
Drupal\Core\Entity\ContentEntityStorageBase->invokeFieldMethod('preSave', Object) (Line: 888)
Drupal\Core\Entity\ContentEntityStorageBase->invokeHook('presave', Object) (Line: 529)
Drupal\Core\Entity\EntityStorageBase->doPreSave(Object) (Line: 753)
Drupal\Core\Entity\ContentEntityStorageBase->doPreSave(Object) (Line: 483)
Drupal\Core\Entity\EntityStorageBase->save(Object) (Line: 806)
Drupal\Core\Entity\Sql\SqlContentEntityStorage->save(Object) (Line: 339)
Drupal\Core\Entity\EntityBase->save() (Line: 270)
Drupal\node\NodeForm->save(Array, Object)
call_user_func_array(Array, Array) (Line: 114)
Drupal\Core\Form\FormSubmitter->executeSubmitHandlers(Array, Object) (Line: 52)
Drupal\Core\Form\FormSubmitter->doSubmitForm(Array, Object) (Line: 597)
Drupal\Core\Form\FormBuilder->processForm('node_news_edit_form', Array, Object) (Line: 325)
Drupal\Core\Form\FormBuilder->buildForm(Object, Object) (Line: 73)
Drupal\Core\Controller\FormController->getContentResult(Object, Object)
call_user_func_array(Array, Array) (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 592)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 121)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext(Array, Array) (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 182)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 50)
Drupal\ban\BanMiddleware->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 704)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)
If you can help, I will be grateful.
Best Regards
Thank you very much, I use:
Drupal 10.1.4
php 8.2
NTT 1.0.2
something went wrong while updating from D 9 to D10.
Uninstalling NTT, clearing the cache several times and reinstalling it had a positive effect and everything returned to normal.
Works correctly.
I think this topic can be closed.
Best Regards
Thank you very much, the version 8.x-1.16 works correctly without errors.
The topic can be closed.
Regards.
pingwin_cracow → created an issue.
pingwin_cracow → created an issue.
pingwin_cracow → created an issue.
pingwin_cracow → created an issue.
pingwin_cracow → created an issue.
I have a new type of content: gallery
Unfortunately, I can't define the function correctly.
Can you tell me exactly what it should look like?
I will be very grateful.
I added:
function step_subtheme_preprocess_page(&$variables) {
$variables['main_attributes'] ='container-fluid';
}
unfortunately it still doesn't work properly.
Have I done something wrong?
pingwin_cracow → created an issue.
pingwin_cracow → created an issue.
P.S. v. 8.x-1.14 works fine - upgrading from 8.x-1.14 to 8.x-1.15 causes bugs.
pingwin_cracow → created an issue.
When can we expect Droopler 3.2 to be released?
Will the update to Droopler 3.2 be associated with the automatic transition to the D10 bed of additional complications?