Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
I've upgraded a Drupal 7 site to Drupal 8 which has a large amount of content that has images inserted into the rich text editor using the IMCE module.
These images therefore, haven't been migrated into Drupal 8 as managed files and they don't have a uuid.
My question; is it possible to scan the content for inline images that don't have a uuid and make give them a uuid and make them managed files, so that they can then be post processed by modules such as image_resize_filter?
Thanks for looking at my post. I'm interested in learning how to transport a local Drupal 8 site to a remote location, and vice versa. I noticed an informative page in the official Drupal site. Here it is for reference:
I have a Drupal version 8.2.4 installation using Aegan 8.x-1.0 theme, up and running, hosted on inmotionhosting.com for about one year by now. Recently I noticed the Drupal Configuration tab bringing this error:
"Fatal error: Call to a member function setDefaultValueCallback() on null in /home/aaa/public_html/aaa.aaa.com/core/modules/comment/src/Entity/Comment.php on line 221"
I had upgraded to Drupal 8.4 but then realized my theme was not compatible with that version and was forced to downgrade back to 8.3.7 for the time being.
I was having some issues with Mismatch entity issues and I found posts in forums suggesting uninstalling modules that were related to the issue. I therefore uninstalled the Blocks module, used drush entup to fix the issue and reinstalled Blocks again. However, now I lost all the links, tabs, titles and breadcrumbs in the backend/admin pages.
I try to upgrade Drupal 8.3.7 to 8.4.2 today and anything is Okay except for a drush issue. After upgrading, running drush cr or drush --version and throwing out the following warning.
------------------------------------------------
$ drush cr
PHP Warning: exec(): Unable to fork [stty size 2>&1] in /opt/bitnami/apps/drupal/htdocs/vendor/drush/drush/src/Config/Environment.php on line 389