Environment: Drupal 7.22 , Views 7-3.7
Every Time I edit the cache settings and set the cache to time based
of any View I get 4 times
Notice: Undefined index: #multiple in form_process_select() (Zeile 2601 von /home/www/vtad7/includes/form.inc).

#14 views-cache_time-2037749-14.patch989 bytesJvE
PASSED: [[SimpleTest]]: [MySQL] 1,664 pass(es). View


ferrangil’s picture

Same warnings in my instalation.
Editing the views to add a 1 hour cache worked just fine, but then on the logs I had these notices too.

totocol’s picture

Experiencing same issue here when trying ti add time-based options to cache views

MPankau’s picture

Same issue here.

markisatacomputer’s picture

Same here

mbdev’s picture

Environment the same as original: Core 7.22, Views 7.x-3.7, and same issue here.

Displayed error:

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /admin/structure/views/ajax/display/view_name/page_name/cache_options

Notice: Undefined index: #multiple in form_process_select() (line 2601 of /includes/form.inc).

In my case, although some AJAX error happens, the cache can be enabled and disabled. However, I can only enable default "1 hour/1 hour", and disable it, because no settings are accessible. I'm looking for a place where cache settings are stored, as a temporary workaround - can anyone point me in any direction?

Is the issue present in dev?

Exploratus’s picture

Same here.

dojorob76’s picture

Drupal 7.23, Views 7.x-3.7, Same issue.

No problem changing/saving the cache settings in Views, but same 4 messages in Error Log.

(Also using Views Cache Bully Module)

do_ocrat’s picture

same same. Ben battling similar errors for quite some time but this is the first time it's keeping me from being able to change a setting. I'd like to change cache timing option - no go.

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: .../admin/structure/views/ajax/display/news/block/cache
StatusText: parsererror
ResponseText: Notice: Undefined index: #multiple in form_process_select() (line 2601 of ...\includes\form.inc). =>

Weird Work Around

I hate workarounds, but...if I copy the url to the cache settings link and paste it in my address bar I can make the changes successfully.


yelvington’s picture

Issue summary: View changes

I hate to be a dittohead, but ... same here. For months now.

AlfTheCat’s picture

same here

AlfTheCat’s picture

Problem is now also that, since the views in question are on the homepage, visiting the homepage as UID1 crashes the site.
It does appear to involve view panes only though, in my case.

phil.stphns’s picture

I get this only when editing certain views, in this case, map views using OpenLayers.

RedEight’s picture

Ran into this issue with my site... I was able to silence the error by adding a check to includes/form.inc on line 2615. (Yes, I killed kittens)

changed it from
if ($element['#multiple']) {
if (isset($element['#multiple']) && $element['#multiple']) {

Seems like something is failing to set the value that gets passed... not entirely sure what is causing the issue though. I suspect it has something to do with the select fields on the cache settings page.

JvE’s picture

Version: 7.x-3.7 » 7.x-3.x-dev
Status: Active » Needs review
989 bytes
PASSED: [[SimpleTest]]: [MySQL] 1,664 pass(es). View

Views was adding form_process_select to the #process array of a textfield element.

andrewfn’s picture

Applied patch and it solved the problem for me.

jelo’s picture

Applied patch from #14 and it solved the problem for me too. Will this be committed?

web226’s picture

Patch in #14 also worked for me - thank you

jenlampton’s picture

Status: Needs review » Reviewed & tested by the community

Patch in #14 works great for me too. Thanks!

Dean Reilly’s picture

+1 worked for me as well.

cosolom’s picture

It's work. Thanks!

jcnventura’s picture


blasthaus’s picture

+1 to patch #14. It would be nice to see in core soon so we don't have to keep patching views on every release.

JvE’s picture

2013 bug submitted
2014 patch created
2015 patch reviewed & approved
2016 fix commited to dev
2017 fixed version released

colan’s picture

We've recently switched our testing from the old qa.drupal.org to DrupalCI. Because of a bug in the new system, #2623840: Views (D7) patches not being tested, older patches must be re-uploaded. On re-uploading the patch, please set the status to "Needs Review" so that the test bot will add it to its queue.

If all tests pass, change the Status back to "Reviewed & tested by the community". We'll most likely commit the patch immediately without having to go through another round of peer review.

We apologize for the trouble, and appreciate your patience.

jamieja91’s picture

More confirmation, #14 solves issue.

JvE’s picture

JvE’s picture

Status: Reviewed & tested by the community » Needs review
JvE’s picture

Status: Needs review » Reviewed & tested by the community
DamienMcKenna’s picture

Another +1.

DamienMcKenna’s picture

joshuautley’s picture

#14 worked for me. Thank you.

jcnventura’s picture


ron_s’s picture

rtbc+++ ....

oranges13’s picture

Another ++ on this one.

colan’s picture

Do we need to open a D8 issue for this one?

joelpittet’s picture

@colan in D8, those #process form callbacks are not being setup on the field.

  • colan committed 4301e37 on 7.x-3.x authored by JvE
    Issue #2037749 by JvE: Removed form_process_select from the process...
colan’s picture

Status: Reviewed & tested by the community » Fixed

Thanks all!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

jcnventura’s picture

Great that this finally saw a release!