Hello, I have the similar issue with fontawesome and CKE5. I am using CDN 6.5.2 version. Drupal 10.1.8. This is blocking one of our important release, unfortunately. Tried to use local fontawesome library, but failed.
When an icon is added CKE5 (eg: ). to shows up, but not able edit the page as it locks up!
I applied patch #44 above (CKE5 compatibility). Still edit page locking issue is not going away.
Fontawesome 5.13.1 version (CDN) is working fine with CKE5, but we need to upgrade it to latest version to get the latest icons.
I have the same issue in CKE5. fa icon disappears when switch out from 'source' mode. This is happening with fa version6 and CKE5.
Update: I encountered same issue for one of our sites, and resolved it by:
- enable Devel Entity Update module
- run drush entup
This is reproducible in Drupal 10.1.8, CKEditor 5.
#10 didn't help in my case.
Is there any other recommendation/solution for this issue, please?
I had the same issue with a multi-site Drupal 10.1.8
Site1 was fine
Site2: After updated and cim, it was showing the similar message as in #5
As mentioned in previous comments, only known solution was to create tables manually.
drush --uri= sql-query "CREATE TABLE ultimate_cron_log ( lid varchar(176) NOT NULL COMMENT 'Lock ID', name varchar(166) NOT NULL COMMENT 'Name', log_type int(11) NOT NULL DEFAULT '0' COMMENT 'Log type', start_time double NOT NULL DEFAULT '0' COMMENT 'Timestamp of execution start', end_time double NOT NULL DEFAULT '0' COMMENT 'Timestamp of execution end', uid int(11) NOT NULL DEFAULT '0' COMMENT 'User ID', init_message text COMMENT 'Initial message', message text COMMENT 'Message', severity int(11) DEFAULT '-1' COMMENT 'Max severity level of the execution', PRIMARY KEY (lid), KEY idx_last (name(80),start_time,end_time,log_type)) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Logs'"
drush --uri= sql-query "CREATE TABLE ultimate_cron_lock ( lid bigint(20) NOT NULL AUTO_INCREMENT COMMENT 'Lock ID', name varchar(166) NOT NULL COMMENT 'Name', current bigint(20) NOT NULL DEFAULT 0 COMMENT 'Current lock', expire double NOT NULL DEFAULT 0 COMMENT 'Expiration time of lock', PRIMARY KEY (lid), UNIQUE KEY idx_name (name,current)\n) ENGINE=InnoDB AUTO_INCREMENT=2241728 DEFAULT CHARSET=utf8mb4 COMMENT='Locks'"
drush --uri= sql-query "CREATE TABLE ultimate_cron_signal ( job_name varchar(166) NOT NULL COMMENT 'Name of job', signal_name varchar(166) NOT NULL COMMENT 'Name of signal', claimed tinyint(4) NOT NULL DEFAULT 0 COMMENT 'Is signal claimed', PRIMARY KEY (job_name,signal_name)\n) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Signals'"
@gbyte: Yes, I searched the queue and didn't find the same issue. Sorry, if I missed something.
Yes, I am using domain_simple_sitemap (Domain Access Simple XML Sitemap) already.
Appreciate your suggestion about opening bug report against dev version only.
bennyjos → created an issue.
I am seeing the same issue mentioned above by lindsay.wils (comment #75).
Drupal 10.1.7
simple_sitemap 4.1.8
domain_simple_sitemap 3.0.0-beta1
Link count is very high for each domain because links from other domains are added in addition to the correct domain links.
Tried rebuild queue and reiteration again, but still same issue.
This is a blocker for our D10 upgrade.
#32 worked! Quick solution. Thanks @tgoeg
bennyjos → created an issue.
When simple_sitemap is upgraded to 4.1, I am also seeing the Container Dependency issue:
Fatal error: Declaration of Drupal\domain_simple_sitemap\Controller\DomainSimpleSitemapController::create(Symfony\Component\DependencyInjection\ContainerInterface $container) must be compatible with Drupal\simple_sitemap\Controller\SimpleSitemapController::create(Symfony\Component\DependencyInjection\ContainerInterface $container): Drupal\simple_sitemap\Controller\SimpleSitemapController in /app/web/modules/contrib/domain_simple_sitemap/src/Controller/DomainSimpleSitemapController.php on line 59
This is a blocker for us to upgrade simple_sitemap to 4.1
Regarding comment #8: There is an issue with Class naming between domain_simple_sitemap and simple_sitemap.
Drupal\simple_sitemap\Controller\SimplesitemapController. (Notice Simplesitemap Vs SimpleSitemap).
May need to install the compatible versions with correct naming to fix this issue.
Please verify the source control system (eg: git) to make sure that the updates to the files are properly done after an update of the simple_sitemap module to fix the names.
I am getting this message when a module is enabled (Drupal 9.5.10)
> [notice] Checked es translation for admin_toolbar.
> [warning] No configuration objects have been updated.
> [notice] Message: No configuration objects have been updated.
Module enabled successfully, despite these notices/warnings