Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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?
Comment | File | Size | Author |
---|---|---|---|
#15 | homebox-block-list-1759392-15.patch | 2.82 KB | klausi |
Comments
Comment #1
wonder95 CreditAttribution: wonder95 commentedI 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.
Comment #2
wonder95 CreditAttribution: wonder95 commentedOn 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.?
Comment #3
jami3z CreditAttribution: jami3z commentedClicking the save button twice did not work for me
Comment #4
apoc1 CreditAttribution: apoc1 commentedAny solution found yet?
Comment #5
chrbak CreditAttribution: chrbak commentedProbably 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?
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.
Comment #6
apoc1 CreditAttribution: apoc1 commentedThanks 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..
Comment #7
wiifmSame 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.
Comment #8
kurtzhong CreditAttribution: kurtzhong commentedJust 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"
Comment #9
kurtzhong CreditAttribution: kurtzhong commentedI 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:
Hope this helps for some of you.
Comment #10
jami3z CreditAttribution: jami3z commented#5 fixed it in my case. Cheers
Comment #11
gratefulsk CreditAttribution: gratefulsk commentedI 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
Comment #12
nitin.k CreditAttribution: nitin.k commentedThanks #5. It works out.
Comment #13
johnkareoke CreditAttribution: johnkareoke commentedThanks. Resolved my issue with the change to .htaccess in #11.
Comment #14
kengrayfield CreditAttribution: kengrayfield commentedI 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!
Comment #15
klausiHere 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.
Comment #16
drummCommitted.