Deprecated: Using ${var} in strings is deprecated, use {$var} instead in [...]/web/themes/contrib/thunder_admin/thunder_admin.theme on line 352
The website encountered an unexpected error. Please try again later.
RuntimeException: Failed to start the session because headers have already been sent by "[...]/web/themes/contrib/thunder_admin/thunder_admin.theme" at line 352. in Symfony\Component\HttpFoundation\Session\Storage\NativeSessionStorage->start() (line 132 of [...]/vendor/symfony/http-foundation/Session/Storage/NativeSessionStorage.php).
Drupal 10.1.2, Thunder Admin 4.0.5, Seven 1.0.0 (D7-D10 upgraded[migrated] site)
Sorry, I'm not at the level to patch anything myself :-)
cntr-r lets go, but annoying...
veskimees → created an issue.
Sorry for taking so long to reply.
I have to admit I've never used drush and I can't seem to get around to using it in the provider environment I'm using (maybe I am just stupid...) However, I repeat, mine is an old, repeatedly changed and from D7 converted site that also behaves strangely with some other modules -- so maybe it's an exception that's not worth wasting time on. Besides -- I have three tiny ECA models, I just made them manually in the live site and problem solved...
Thanks for your time!
0. Made copy of the site (live is https://algernon.ee, test is https://test.algernon.ee, only difference are in front page, site information etc)
1. Prepared ECA model in test site.
2. Exported it (admin/config/workflow/eca Operations -> export --you know)
3. Tried import it to live site
(Unfortunately, some keywords in model are in Estonian, but the idea should be understandable and the model works as it should [by the way, thanks, ECA seems to be a really awesome thing... if only the documentation would be created... :-) ]; it is a movie review functionality hidden from the normal user, which creates a link to the original movie node in the message area, taking the corresponding id from the taxonomy term.)
veskimees → created an issue.
It's still here! & #5 seems to work.
Drupal 9.5.9, PHP 8.0.28, DB 10.6.13-MariaD8-log
From D7 upgraded site, some 2000 nodes, lot of different modules.
Had different pictures in different tabs in same browser window.
There was pseudomenu made with View, in v.1 headings were w 'index.pxp' (and some messed up), in v.2 without.
Well, I just ran into the same problem. And for some reason, putting the Comments field back to Article doesn't work (Comment module is enabled, the corresponding field was simply removed from Article).
It's not hard to install a clean site to see what that Default module suggests, but it still seems... odd.
(I am working on upgrading the D7 site; an online magazine, about 2000 articles; all the content is Articles with additional fields and no comments and has been so for 12 years... I wanted to improve the search as part of the upgrade, and here I am now... :-) )
I have the same experience; #9 worked.
My problem was that it was necessary to make one site (about 2000 nodes) language neutral. The corresponding view worked for all content types except Article, where nothing happened when I clicked Apply. The script worked fine when I changed all the required fields to non-required.
i tried, didn't work (composer remove drupal/zeropoint, flush all caches, composer require 'drupal/zeropoint:^1.7' etc).
I found solution and I'll write that down, maybe it's good for others to know:
I searched the entire site database (w phmyadmin) for 'zeropoint' (after removing theme), and found a lot of matches (mostly migrated blocks w zeropoint string in name, 40 fields in migrate_map_d7_blocks etc).
The installation was successful after I manually deleted the field 'zeropoint.setting' from the config table.
veskimees → created an issue.
Yes it is. Sorry I couldn't find it and made a duplicate. But in my case, it means that I will not use CKE5 until its possible some way or until support for the insert module is created. Quite a many old sites depend on it exclusively.
I'll also add my voice here -- let's hope that the support for the insert module will remain. For example, I've been putting up my creations since Drupal 5, node number shows over 800. I'd really hate the attitude that I should until retirement and then go through all this stuff manually...
veskimees → created an issue.