Pixeldust Drupal Support Service

Errors when passing in URL Parameters for Views uncovered filters which are choice lists

I’ve a Content material View that has some a number of uncovered filters and I added a filter identifier to them in order that I can go filters in via through URL Parameters.

This works as anticipated for some fundamental filters like a area with a ‘true/false’ worth or a mixed fields textfield filter, and many others. I’m able to go in a parameter like ?key phrases=check and this works for Drupal Developer mixed fields filter completely. Nevertheless, I’ve a problem when Drupal Developer filter is an inventory of some kind like an integer listing or a taxonomy time period reference.

Area | Sort | Filter identifier

field_length | Record(integer) | size field_topic | Taxonomy Time period Entity Reference | subject

Listed here are Drupal Developer totally different challenge’s I am dealing with:

ISSUE 1

enter image description here

For these filters if their widget is ready to default (a easy choice listing like in Drupal Developer image above), and I put in a URL parameter like ?subject=Awards, it would not work. Drupal Development Service Awards choice in Drupal Developer filter listing isn’t highlighted neither is it utilized to Drupal Developer question.

ISSUE 2

enter image description here

For these filters if their widget is ready to a checkboxes area (see picture above) and I put in a URL parameter like ?subject=Awards, then I get Drupal Developer following error

Drupal Development Service web site encountered an sudden error. Please strive once more later. Error: Can't create references to/from string offsets in DrupalComponentUtilityNestedArray::setValue() (line 155 of core/lib/Drupal/Part/Utility/NestedArray.php). DrupalComponentUtilityNestedArray::setValue(Array, Array, NULL) (Line: 1250) DrupalCoreFormFormBuilder->handleInputElement('views_exposed_form', Array, Object) (Line: 1001) DrupalCoreFormFormBuilder->doBuildForm('views_exposed_form', Array, Object) (Line: 1071) DrupalCoreFormFormBuilder->doBuildForm('views_exposed_form', Array, Object) (Line: 1071) DrupalCoreFormFormBuilder->doBuildForm('views_exposed_form', Array, Object) (Line: 575) DrupalCoreFormFormBuilder->processForm('views_exposed_form', Array, Object) (Line: 321) DrupalCoreFormFormBuilder->buildForm('DrupalviewsFormViewsExposedForm', Object) (Line: 134) DrupalviewsPluginviewsexposed_formExposedFormPluginBase->renderExposedForm() (Line: 1238) DrupalviewsViewExecutable->construct() (Line: 390) DrupalviewsPluginviewsdisplayPathPluginBase->execute() (Line: 180) DrupalviewsPluginviewsdisplayPage->execute() (Line: 1630) DrupalviewsViewExecutable->executeDisplay('advanced_search_page', Array) (Line: 81) DrupalviewsElementView::preRenderViewElement(Array) call_user_func_array(Array, Array) (Line: 101) DrupalCoreRenderRenderer->doTrustedCallback(Array, Array, 'Render #pre_render callbacks have to be strategies of a category that implements DrupalCoreSecurityTrustedCallbackInterface or be an nameless perform. Drupal Development Service callback was %s. See https://www.drupal.org/node/2966725', 'exception', 'DrupalCoreRenderElementRenderCallbackInterface') (Line: 786) DrupalCoreRenderRenderer->doCallback('#pre_render', Array, Array) (Line: 377) DrupalCoreRenderRenderer->doRender(Array, ) (Line: 201) DrupalCoreRenderRenderer->render(Array, ) (Line: 241) DrupalCoreRenderMainContentHtmlRenderer->DrupalCoreRenderMainContent{closure}() (Line: 578) DrupalCoreRenderRenderer->executeInRenderContext(Object, Object) (Line: 242) DrupalCoreRenderMainContentHtmlRenderer->put together(Array, Object, Object) (Line: 132) DrupalCoreRenderMainContentHtmlRenderer->renderResponse(Array, Object, Object) (Line: 90) DrupalCoreEventSubscriberMainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object) call_user_func(Array, Object, 'kernel.view', Object) (Line: 142) DrupalComponentEventDispatcherContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 163) SymfonyComponentHttpKernelHttpKernel->handleRaw(Object, 1) (Line: 80) SymfonyComponentHttpKernelHttpKernel->deal with(Object, 1, 1) (Line: 57) DrupalCoreStackMiddlewareSession->deal with(Object, 1, 1) (Line: 47) DrupalCoreStackMiddlewareKernelPreHandle->deal with(Object, 1, 1) (Line: 191) Drupalpage_cacheStackMiddlewarePageCache->fetch(Object, 1, 1) (Line: 128) Drupalpage_cacheStackMiddlewarePageCache->lookup(Object, 1, 1) (Line: 82) Drupalpage_cacheStackMiddlewarePageCache->deal with(Object, 1, 1) (Line: 47) DrupalCoreStackMiddlewareReverseProxyMiddleware->deal with(Object, 1, 1) (Line: 52) DrupalCoreStackMiddlewareNegotiationMiddleware->deal with(Object, 1, 1) (Line: 23) StackStackedHttpKernel->deal with(Object, 1, 1) (Line: 717) DrupalCoreDrupalKernel->deal with(Object) (Line: 19)

How am I suppose to go URL Parameters for Uncovered Filters which are lists?

UPDATE

I discovered that if I go Drupal Developer parameter as subject[]=<subject id> that Drupal Developer filter is utilized to a question, however Drupal Developer view filter kind doesn’t have that subject marked… Moreover, if I go Drupal Developer parameter as subject[]=<subject title> I get an error saying that an unlawful alternative has been detected..

How am I suppose to configure up a view with a checkbox listing uncovered filter that’s able to receiving Drupal Developer filter as URL Parameters utilizing Drupal Developer listing merchandise title as a substitute of id? It looks like a reasonably widespread characteristic that might work out of field like Drupal Developer different filters…

Right here is my configuration on Drupal Developer subject uncovered filter FWIW:

enter image description here enter image description here

This article was republished from its original source.
Call Us: 1(800)730-2416

Pixeldust is a 20-year-old web development agency specializing in Drupal and WordPress and working with clients all over the country. With our best in class capabilities, we work with small businesses and fortune 500 companies alike. Give us a call at 1(800)730-2416 and let’s talk about your project.

Let's Talk About a Project

FREE Drupal SEO Audit

Test your site below to see which issues need to be fixed. We will fix them and optimize your Drupal site 100% for Google and Bing. (Allow 30-60 seconds to gather data.)

Powered by

Errors when passing in URL Parameters for Views uncovered filters which are choice lists

On-Site Drupal SEO Master Setup

We make sure your site is 100% optimized (and stays that way) for the best SEO results.

With Pixeldust On-site (or On-page) SEO we make changes to your site’s structure and performance to make it easier for search engines to see and understand your site’s content. Search engines use algorithms to rank sites by degrees of relevance. Our on-site optimization ensures your site is configured to provide information in a way that meets Google and Bing standards for optimal indexing.

This service includes:

  • Pathauto install and configuration for SEO-friendly URLs.
  • Meta Tags install and configuration with dynamic tokens for meta titles and descriptions for all content types.
  • Install and fix all issues on the SEO checklist module.
  • Install and configure XML sitemap module and submit sitemaps.
  • Install and configure Google Analytics Module.
  • Install and configure Yoast.
  • Install and configure the Advanced Aggregation module to improve performance by minifying and merging CSS and JS.
  • Install and configure Schema.org Metatag.
  • Configure robots.txt.
  • Google Search Console setup snd configuration.
  • Find & Fix H1 tags.
  • Find and fix duplicate/missing meta descriptions.
  • Find and fix duplicate title tags.
  • Improve title, meta tags, and site descriptions.
  • Optimize images for better search engine optimization. Automate where possible.
  • Find and fix the missing alt and title tag for all images. Automate where possible.
  • The project takes 1 week to complete.
MASTER YOUR DRUPAL SEO
Pixeldust and Pantheon Drupal Development
256