🇮🇳India @vandanasom.123

vandana → created an issue.

vandana → created an issue.

vandanasom.123 → made their first commit to this issue’s fork.

The error ContainerNotInitializedException occurs because the container is being accessed before it's fully initialized in Drupal.

If your custom module or the empowerid integration is trying to access Drupal services (\Drupal::service(), \Drupal::entityTypeManager()) too early (before the container is fully initialized), this error will occur.

Ensure you’re not calling services in hook_enable(), hook_install(), or any code that runs too early in the lifecycle.

Fix:

1. Use Dependency Injection in your custom module instead of directly calling \Drupal::service() wherever possible.
2. Make sure you're not accessing services before Drupal is fully bootstrapped (e.g., not in hook_enable()).
3. Clear cache

vandanasom.123 → created an issue.

vandanasom.123 → created an issue.

@orbmantell, thank you for the patch. However, I encountered the following error:

Could not apply patch! Skipping. The error was: Cannot apply patch https://www.drupal.org/files/issues/2025-02-27/views_dependent_filters-3... →

Please try the patch provided:

@orkut murat yılmaz, its fixed check MR

vandanasom.123 → made their first commit to this issue’s fork.

vandanasom.123 → created an issue.