I initially created 2 homebox pages for different roles and successfully set them up with no trouble. But after coming back after a few weeks to further edit the layout and add additional blocks to my homeboxes they ignore any changes I make to the blocks when saving. i.e If I move a block out of disabled into a column and save it, the block stays in disabled. This is happening with any block and both homebox layouts.

Has anyone come across this?

CommentFileSizeAuthor
#15 homebox-block-list-1759392-15.patch2.82 KBklausi
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

wonder95’s picture

I have found that you have to click on the Save button twice. The first click hides the 'Unsaved' message, and the second one actually saves it. I'm not a jQuery guru, so I can't tell you why it doesn't save on the first click, but I'm trying to figure it out.

wonder95’s picture

On a side note, I've noticed that on the dashboard page on drupal.org, adding a block automatically saves the page. Is that something custom for d.o.?

jami3z’s picture

Clicking the save button twice did not work for me

apoc1’s picture

Any solution found yet?

chrbak’s picture

Probably the max_input_vars php variable causes the problem. At least in my case did.
Look into the error_log file locating in your site root folder ( "/public_html" for linux server). Is there a message like the bellow?

PHP Warning: Unknown: Input variables exceeded y. To increase the limit change max_input_vars in php.ini. in Unknown on line 0

If there is such a message then maybe is because of the homebox appearance page. More specific, count the number of blocks that there are in the appearance page of one of your homebox page you have created and after multiply this number with the seven (every row has seven variables that has to be saved).
If the number you have calculate is larger from the y number above then you have to increase the value of max_input_vars variable in php.ini file.
Every time a block is created you have to consider the homebox appearance page saving process.

apoc1’s picture

Thanks chrbak for your response. I couldn't locate my error_log file, but increased my max_input_vars up to 10 000 and it didn't make any difference..

wiifm’s picture

Same issue as #1 - I have to click 'Save' twice in order to actually save the data back to the database. The first click simply removes the 'Unsaved' message.

kurtzhong’s picture

Just met the same problem and got the same error log as described in #5:

2013/01/15 17:09:35 [error] 62493#0: *290 FastCGI sent in stderr: "PHP message: PHP Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in Unknown on line 0" while reading response header from upstream, client: 127.0.0.1, server: _, request: "POST /admin/structure/homebox/layout/support_manager_dashboard HTTP/1.1", upstream: "fastcgi://unix:/tmp/php-fpm.sock:", host: "vrc.local", referrer: "http://vrc.local/admin/structure/homebox/layout/support_manager_dashboard"

kurtzhong’s picture

I find that each row contains 11 variables, for me 211 blocks means 2312 variables!

My solutions is to remove some blocks that i think i would never use on the homebox pages. I can't believe the userpoints module auto-generate 128 blocks, so i remove them all. I guess now that the left 83 blocks will generate 913 variables which is below 1000. And after I've done that everything works again.

Here is the code i am using:

/**
 * Implements hook_form_FORM_ID_alter()
 */
function mymodule_form_homebox_admin_display_form_alter(&$form, &$form_state) {
  // Remove all the blocks generated by 'userpoints' module
  foreach(element_children($form) as $key) {
    if (!empty($form[$key]['module']) && $form[$key]['module']['#value'] == 'userpoints') {
      dpm($form[$key]);
      unset($form[$key]);
      $i++;
    }
  }
}

Hope this helps for some of you.

jami3z’s picture

#5 fixed it in my case. Cheers

gratefulsk’s picture

I had this same issue and increased the max_input_vars solved the issue. I added this to my .htaccess file:
php_value max_input_vars 3000

nitin.k’s picture

Thanks #5. It works out.

johnkareoke’s picture

Issue summary: View changes

Thanks. Resolved my issue with the change to .htaccess in #11.

kengrayfield’s picture

I have the same issue. Clicking the save button twice and increase max_input_vars doesn't work for me. For some reason, I only have this problem with 2nd and above homebox pages, and not the first, which has a lot more blocks.

Edit: never mind, I forgot to uncomment the max_input_vars. It works now!

klausi’s picture

Version: 7.x-2.0-beta6 » 7.x-2.x-dev
Status: Active » Needs review
FileSize
2.82 KB

Here is a patch that simply does not show all the disabled blocks. It adds a select box instead to add individual blocks one by one. That way you don't need to mess with your PHP max_input_vars setting on large sites with many blocks.

drumm’s picture

Status: Needs review » Fixed

Committed.

  • drumm committed 8c8fe9a on 7.x-2.x authored by klausi
    Issue #1759392 by klausi: Do not show all disabled blocks on homebox...

Status: Fixed » Closed (fixed)

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