Patch from MR # 140 without tests.
The patch in # 148 for Drupal 11
hmdnawaz → created an issue.
hmdnawaz → made their first commit to this issue’s fork.
hmdnawaz → created an issue.
The drush command drush solr-reload <server_id> is not available anymore. Any alternative for that?
I don't see any warning before that TypeError occur. I do see array offset warnings after that if ($cache = $this->getCacheBackend()->get($this->generateResultsKey())) {
But that is because of the results are null.
I also noticed this warning which has search api in backtrace.
Warning: unserialize(): Error at offset 35560 of 168513 bytes in Drupal\Component\Serialization\PhpSerialize::decode() (line 21 of /var/www/core/lib/Drupal/Component/Serialization/PhpSerialize.php) #0 /var/www/core/includes/bootstrap.inc(108): _drupal_error_handler_real(2, 'unserialize(): ...', '/var/web/vd1642...', 21)
#1 [internal function]: _drupal_error_handler(2, 'unserialize(): ...', '/var/www...', 21)
#2 /var/www/core/lib/Drupal/Component/Serialization/PhpSerialize.php(21): unserialize('a:4:{s:6:"resul...')
#3 /var/www/modules/contrib/redis/src/Cache/CacheBase.php(390): Drupal\Component\Serialization\PhpSerialize::decode('a:4:{s:6:"resul...')
#4 /var/www/modules/contrib/redis/src/Cache/PhpRedis.php(68): Drupal\redis\Cache\CacheBase->expandEntry(Array, false)
#5 /var/www/modules/contrib/redis/src/Cache/CacheBase.php(159): Drupal\redis\Cache\PhpRedis->getMultiple(Array, false)
#6 /var/www/modules/contrib/search_api/src/Plugin/views/cache/SearchApiCachePluginTrait.php(192): Drupal\redis\Cache\CacheBase->get('search:search_o...')
#7 /var/www/core/modules/views/src/ViewExecutable.php(1479): Drupal\search_api\Plugin\views\cache\SearchApiTagCache->cacheGet('results')
#8 /var/www/core/modules/views/src/ViewExecutable.php(1514): Drupal\views\ViewExecutable->execute(NULL)
#9 /var/www/core/modules/views/src/Plugin/views/display/Block.php(133): Drupal\views\ViewExecutable->render()
#10 /var/www/core/modules/views/src/ViewExecutable.php(1690): Drupal\views\Plugin\views\display\Block->execute()
#11 /var/www/core/modules/views/src/Element/View.php(81): Drupal\views\ViewExecutable->executeDisplay('search_overview', Array)
I don't know whether it is related or not.
But the latest commit indeed fixes the error.
I use Drupal 11.0.12, search API 8.x-1.38, and search API Solr 4.3.8. In view, I'm using the cache as a Search API tag-based.
TypeError: Drupal\search_api\Utility\QueryHelper::addResults(): Argument #1 ($results) must be of type Drupal\search_api\Query\ResultSetInterface, null given, called in /var/web/vd16430/app/releases/303/web/modules/contrib/search_api/src/Plugin/views/cache/SearchApiCachePluginTrait.php on line 201 in Drupal\search_api\Utility\QueryHelper->addResults() (line 86 of /var/web/vd16430/app/releases/303/web/modules/contrib/search_api/src/Utility/QueryHelper.php).
I used the patch from `MR 101`, then cleared the cache, re-indexed all the items but I still see that error.
While on Drupal 10.4, search API 1.35 and search API solr 4.3.4 and everything works fine with the views cache set to Search API tag based.
hmdnawaz → made their first commit to this issue’s fork.
hmdnawaz → made their first commit to this issue’s fork.
Patch for Drupal 11.1
hmdnawaz → changed the visibility of the branch 11.x-2784233-multiple-vocabularies-deprecated-vid to hidden.
hmdnawaz → made their first commit to this issue’s fork.
Patch for 11.1.x without tests from the MR 4294
hmdnawaz → created an issue.
It differs from MR 22 because MR 22 is for version 2.1 and this new MR is for the 2.2.x version.
I will try to fix the phpcs and eslint issues in the new MR
hmdnawaz → made their first commit to this issue’s fork.
hmdnawaz → made their first commit to this issue’s fork.
hmdnawaz → created an issue.
When patch config split is created for the view mode with layout builder, the actual field display is moved to the patched version but the config left with this config
437151a9-12cd-4d10-a578-08901f92206f:
configuration:
context_mapping: { }
formatter:
settings: { }
third_party_settings: { }
additional: { }
third_party_settings: { }
Which doesn't contain an id so that is why we get that error. Just remove it from the actual config and the import will be fine
This error still exists in 2025.
I'm also facing the issue. The error occurs in view modes that use the layout builder.
Is there any workaround?
hmdnawaz → created an issue.
Patch for 10.4
For 10.4
Patch for 10.4.x
The dev version supports Drupal 11. Please create a new release from it.
hmdnawaz → created an issue.
hmdnawaz → created an issue.
Added the dependency on
JS Cookie →
as core/js-cookie is deprecated
hmdnawaz → made their first commit to this issue’s fork.
Patch for version 2.0.8
Then the 1.x branch will be different from the 1.0.1.
The PR does not apply to the 1.0.1 and dev versions of the module. Here is the patch for 1.0.1.
hmdnawaz → made their first commit to this issue’s fork.
hmdnawaz → made their first commit to this issue’s fork.
hmdnawaz → made their first commit to this issue’s fork.
hmdnawaz → made their first commit to this issue’s fork.
hmdnawaz → made their first commit to this issue’s fork.
For 2.13 version use this patch.
hmdnawaz → made their first commit to this issue’s fork.
hmdnawaz → made their first commit to this issue’s fork.
Also, in version 3, when you filled in the lat-long, it automatically adjusted the map with a marker at that position. Now, in dev-4.x, that is not the case anymore.
In 4.x with fit shapes the issue persists.
Please check these settings. I'm using the 4.x dev version.
What should be the workaround then? Which settings do we need now? Is there any documentation?
So It should be active then. We are having the same issue. The markers are not displayed on the maps instead we see center of the map
hmdnawaz → created an issue.
Updated the MR.
hmdnawaz → created an issue.
Closing as it is working already.
hmdnawaz → created an issue.
hmdnawaz → created an issue.
Fixes other deprecations as well.
hmdnawaz → created an issue.
After Update to Drupal core from 10.2 to 10.3, we are also facing the same issue.
hmdnawaz → made their first commit to this issue’s fork.
Patch for Drupal 10.3
Patch for Drupal 10.3
Patch for Drupal 10.3
Patch for Drupal 10.3
There is an issue when using the RedisSessionHandler. When you clear the cache from the UI or use Drush, the logged-in user gets logged out.
In case of Drupal redis module, can we use?
services:
redis.client:
class: Drupal\redis\Client\PhpRedis # Your Redis client class.
factory: [ '@redis.factory', 'getClient' ]
session_handler.storage:
class: Symfony\Component\HttpFoundation\Session\Storage\Handler\RedisSessionHandler
arguments: [ '@redis.client', { prefix: 'drupal_session:' } ]
@kksandr
How your redis.client class looks like?
batigolix → credited hmdnawaz → .
The image displays fine, but when you right-click on it and select open the image in a new tab, you will see some strange characters.
I have a file field in my content type, I attached a file to the node. I can see an entry in the file_managed and file_usage table for that file.
Now I deleted the node, I see the file entry removed from the file_usage and the entry is still present in the file_managed table.
But I don't see that file nor in the orphaned files and neither in the unmanged files.
hmdnawaz → created an issue.
The comment in #8 also fixes my issue.
All the tests are passed for Drupal 10.2 now.
Please use the MR 41 for Drupal 10.2
hmdnawaz → changed the visibility of the branch field_encrypt-3421958 to hidden.
hmdnawaz → made their first commit to this issue’s fork.
Re-rolled the patch for 10.2
Hi RandalV,
But on the module page, with version 1.1.1, it is mentioned that it is compatible with ^9.4 || ^10.
If it is not working on Drupal 9, then it should be mentioned on the module page that it will only works ^10
I'm using Drupal version 9.5.11 and PHP version 8.1
hmdnawaz → created an issue.
The other types like jpg, and png are removed from the tmp directory but not the webp, I tried to remove the webp as well, but then the image upload not work.
So now I will not write a cron function to remove the .webp files from the tmp directory. until the issue is fixed.
These files are removed in the __destruct function in the ImageAPIOptimizePipeline.php, but I think that function is not called or temporaryFiles is empty.