The issue the site I'm working on has been the following. I have a Nodereference field with an auto-complete that is set to an "Unlimited" amount. Thus, there's an "Add another item" button. In the cases where you used the green "+" button to get a modal frame that lets you add a new node, it works fine. But, if you ask for another field on the "Add another item" button, the request to "content/js_add_more" returns a JSON data of {"data":""}. When that happens, the entire field as a whole is removed from the form and it doesn't submit.

Looking at the code for the content_add_more_js() function, I have verified that it is not getting a valid result for the form_get_cache() function. Is adding an item or two in the Modal Frame/Node Relationships module invalidate the original form request? Is there any way to stop this from happening? Is this making any sense to anyone else? I'm afraid I don't know enough about the form system... yet.

Comments

dandaman’s picture

dandaman commented

In my case, I have now narrowed the error down to the following line in cache.inc:

      if (isset($user->cache) && $user->cache > $cache->created) {
        // This cache data is too old and thus not valid for us, ignore it.
        return 0;
      }

Something about using the Modal Frame to create a new node changes the value of $user->cache so that it is greater than when the original form we're editing was created.

dandaman’s picture

dandaman commented

So, I was able to fix this by setting the "Minimum Cache Lifetime" to "", but if we could figure out how to make this work without that requirement that'd be cool.

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented

My "Minimum Cache Lifetime" was already set to "none" and I was having this problem, but after changing "Page cache maximum age" to "none" it went away.

Hope someone finds a proper fix though so these don't need to be set to "none".

Kristen