@DamienMcKenna
I've updated the page. Kindly review.
Sorry it took such a shockingly long time.
You might consider adding an entry to the new page from here: Performance problems on entity (node) edit forms →
Completely forgot to write the tutorial. Its my first and I hope its ok.
Hello,
5 years later, this issue is becoming large for us! With 3k of files, all multi mb PDFs, our key_value table has ballooned to an unmanageable size.
I noticed that text files essentially aren't cached. Do you have any opinions on using the filesystem to store extracted text rather than the key_value table?
Yes, I will... this solution is still being worked on, once I have it in the wild+tested I'll give all the info. Implementing the form display can all be done in the UI but it still needs a custom module to add to local tasks.
I was doing too much at the time to properly trace why the error was happening so I’m afraid this will be hard to replicate. I’m working with a very old site (all be it up
to date) and there is a lot going on in local tasks.
In general, I would say the if statement as it stands isn’t doing enough to ensure the integrity of the array. I guess this is why we are here?
Mohd's patch almost worked...
Added an is_array check prior to array_key_exists..
With the schema modules enabled, every ajax request has around 800 items added to the payload. Removing metatags completely from display greatly improved our relationship with the content team. One of them even asked me out on a date.
For anyone reading this, our workaround was to have the metatag fields accessible only via a specific content form mode [called seo].
Editing meta tags is now done done via a separate local task that uses the seo form mode. This was enabled using https://www.drupal.org/project/form_mode_control →
Same here, but in cron, downgrading the algolia search client to 3.3.2 fixes it
[INFO] [cron] [2023-09-07T10:32:56] Starting execution of search_api_cron(), execution of purge_processor_cron_cron() took 39.31ms. | uid: 0 | request-uri: http://default/ | refer: | ip: 127.0.0.1 | link:
PHP Fatal error: Declaration of Algolia\AlgoliaSearch\Http\Psr7\Uri::withScheme(string $scheme): Psr\Http\Message\UriInterface must be compatible with Psr\Http\Message\UriInterface::withScheme($scheme) in /var/www/vendor/algolia/algoliasearch-client-php/src/Http/Psr7/Uri.php on line 439
[warning] Drush command terminated abnormally.