Closed (duplicate)
Project:
Featured Content
Version:
6.x-1.4
Component:
Code
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
4 Nov 2011 at 21:54 UTC
Updated:
29 Jul 2025 at 23:48 UTC
Jump to comment: Most recent
Comments
Comment #1
kristen polHmmm... wondering if the D7 api changed. Which version of D7 are you using?
Kristen
Comment #2
kmare commentedHello Kristen,
I'm using the latest version of D7 (7.9). Also I'm using the latest dev version of views. Let me know if I could help in any way providing more info.
Thank you in advance,
Yiannis
Comment #3
kristen polI will try to look into it this week but, in the mean time, if you haven't already, you can try turning on error reporting in your settings.php file per these instructions:
http://drupal.org/node/158043
to see if there are any other errors mentioned. Though it seems like you have that covered.
If you are comfortable with editing a module, then you could install the devel module and add a devel backtrace call like in:
http://blog.anselmbradford.com/2009/03/14/2-invaluable-drupal-developmen...
within the function that is giving the error (field_view_mode_settings). That should show the trace of what function in the FC module causes the eventual call of that field_view_mode_settings function. This would help narrow down the issue.
Thanks!
Kristen
Comment #4
kmare commentedHello Kristen,
I'm sorry, but this week and probably the next one I won't be able to test anything as I'll be away, but I'll surely start tracking down the problem as soon as possible and report back.
Thank you again
Comment #5
kristen polI have upgraded drupal to 7.9 and am not getting that error. Perhaps there is another module that is causing the conflict? Can you turn off all the other contrib modules and then check if the error still occurs?
Thanks,
Kristen
Comment #6
kristen polComment #7
kristen polI'm closing for now since I can't reproduce. Please reopen if you continue to have the problem after turning off all other contrib modules and we can go from there.
Thanks,
Kristen
Comment #8
kmare commentedHello Kristen,
I'm sorry for the late answer, but unfortunally I lost the partition with the specific drupal setup and since I didn't keep any backups ( :( ) of that disk, I'll have to restart the project from scratch. As soon as I have more news, I'll report back.
Thank you again for your work and everything.
Comment #9
kristen polSorry to hear that!!! That is NO fun... hope you recover from it quickly.
Best wishes,
Kristen
Comment #10
ajayg commentedI am able to reproduce this consistently (although I am on 6.x)
I get out of memory error when I try to create featured content block.
Fatal error: Allowed memory size of 199229440 bytes exhausted (tried to allocate 83 bytes) in .../httpdocs/includes/form.inc on line 1062
I have increased memory in stages all the way upto 190M and still get the error. I started with 150M in steps and every time it says it need only a few more bytes. And even though I add 10 MB per step it is few bytes less.
Please note I am not getting any memory issue with other modules or block creation, even if I do not increase the memory. So there something different with featured content block creation and is happening in 6.x too.
Comment #11
ajayg commentedI also wonder if Featured content block creation tries to load all the content(or node titles) in a form. Because I have a very large site and loading all the URL etc will certainly crash any form. Perhaps putting a limit where ever you are creating a list of node etc. would be a starting point?
Comment #12
kristen polSince I'm not able to reproduce locally, I would need you to send me a database dump & a zip/tar of the site. You can send this to me directly. If you have any sensitive data, please make sure to remove it from your database copy as necessary.
Alternatively, you can try debugging the problem and let me know on what line it is getting stuck. I have some instructions above in comment #3. Also, you can install the dtools module and enable the wsod module and see if that helps though it doesn't always show what is going on.
[update] I'm also wondering if you had issues with older versions of the module. If you are able, please try out some older ones, e.g. 1.0 or 1.1.
Thanks,
Kristen
Comment #13
kristen polp.s. In the shorter term you could just send a full screenshot of your FC block settings so I can try out the same settings locally.
Thanks,
Kristen
Comment #14
ajayg commentedMy database is really huge ( I am running my site for 15 years) so I can't send to you.
I can not go to FC block creation. That is the problem. It gives WSD when I click on the create FC block tab under blocks menu in admin. So I have no FC block settings to share. So when you trying to load something in the block creation form that is causing this. The key to ask, which fields in FC create block form will be so huge if the site is 15 years old, thousands of nodes with , 40K+ active users ?
I followed the instruction in #3 (instrumenting index.php) and that is where it is showing error as running out of memory. Till I followed the instruction in #3, it was just showing blank with no error message, nothing.
As you can see below it is getting stuck on line 1062 of forms.inc. Even if you increase memory, the number of bytes differ but it always get stuck there on 1062.
Fatal error: Allowed memory size of 199229440 bytes exhausted (tried to allocate 83 bytes) in .../httpdocs/includes/form.inc on line 1062
If you give me some hints, I can try commenting out some fields so those don't show up and pinpoint which field is getting out of the hand.
I am sorry, but looks I am really stress testing your baby.
Comment #15
kristen polAh, I think you have figured out the problem. Yes, it does show a list of the users so you can choose from them for filtering. So, this must be the issue. I should put a limit on that.... I'll do that now and let you know when it's up.
Kristen
Comment #16
kristen polOk, I have updated the 6.x-1.x branch so it will be available in dev once the drupal.org cron runs. I haven't updated D7 or 6.x-2.x.
Please test once it's up. I'm feeling like it will fix it. Note that performance still needs to be addressed for large databases. I have created the 2.x branches to work on performance there.
Thanks,
Kristen
Comment #17
kristen polComment #18
ajayg commentedI confirm this WSOD issue is fixed in the latest 6.x dev branch. I was able to play and try multiple blocks. Great module !
You may want to consider changing UI so it can handle large number of uses. Like an input box or something like comma separated list.
Comment #19
kristen polGlad it worked for you... it will get pushed out in 6.x-1.5 when that is released. I still need to change this in the D7 branch too.
Thanks,
Kristen
Comment #20
kristen polThis is in version 6.x-1.5.
Kristen
Comment #21
kristen polComment #22
kristen polComment #23
ggevalt commentedHi,
I am seeking to reopen this as I just experienced the same issue with the 6.x-1.5 version. So, for me, this is not fixed. I have a site that I've been using for 6 years, and it has a lot of users and nodes...
I am presuming from this thread that the fix you referred to that was in the .dev version was put in 1.5, however, it does not fix the issue for me... getting a similar
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 81 bytes) in /var/www/vhosts/xxMYSITE/includes/form.inc on line 1062
Thoughts?
geoff
Comment #24
kristen polHi @ggevalt. Since you have a lot of nodes & users, it might not work for you. Do you get the issue right when going to the blocks page, the FC block config page, or ? Please provide details on how to reproduce. You might try the *dev* version though I am thinking it won't make a difference in your case.
Thanks,
Kristen
Comment #25
ggevalt commentedKristen,
Thanks so much for your quick and thoughtful response. It is a pleasure and way beyond the call of duty.
I uninstalled the 1.5 and installed the .dev and had the same result, though slightly different message:
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 75 bytes) in /var/www/vhosts/MYSITE/includes/form.inc on line 1019
So this only occurs when we click the "add featured content" tab on the blocks admin page.
FYI, we have more than 68,000 nodes and 100,000 comments. I did not know that the size of the site impacted the module. In any event, sorry this module doesn't work for us. It looks perfect for our reconfiguration of the site. I'll contact you separately with more detail.
If you do make tweaks for larger sites, make sure to contact me and I'll be happy to test for you.
geoff
Comment #26
kristen pol@ggevalt - Let's dialog via email... I do have a note on the project page:
http://drupal.org/project/featured_content#problems
but maybe I should update it to note what errors you might get. If you have other suggestions on how to make this more obvious to new people, please let me know.
Thanks,
Kristen
Comment #27
killua99 commentedI got the same result than @ggevalt our site (idealista.com/news) got 100k+ nodes and 300k+ comments also 40k+ taxonomy tags, 70k+ users.
If I can help with something. This module looks pretty fancy.
I'm development in a "tiny" db with only 1.5 years of contents (db size 800M) and I cannot image this result in deploy.
Let me know
Luigi --
Comment #28
kristen polSee the #720364: caching for performance issue.
Comment #29
kristen polunassigning old issues