support April 2013

support@drupal.org

49 participants
53 discussions

Re: [support] Fed up with Drupal 7 ... Desperately.....modules.etc
by Roger 06 Apr '13

06 Apr '13

Memory limits of 128mb or more is not uncommon. It's even stated in the online documentation: A PHP memory limit of 32MB is the minimum requirement for Drupal 7 (16MB for Drupal 6), and 64MB is recommended. Some sites may need more than 64MB if they are using certain contributed modules such as Views and Panels. Memory limits of 128MB and higher are not unusual. There are several techniques to increase the PHP memory limit and you only need to use one of them. The right one for you depends on your system configuration. http://drupal.org/node/207036 Views and Panels are heavy modules. That's the price we pay for the ease in site building they provide. The other option is to not use them and go with custom code to generate your content and displays. Any site I build I evaluate what needs to be done and what will need to be done in the future before installing Views and/or Panels. Of course that's not an easy option for people not familiar with Drupal development. As far as Views, it will get better in Drupal 8, since it is going into core and will get a lot more attention from the development side as well as tighter integration into Drupal overall. Jamie Holly http://www.intoxination.net http://www.hollyit.net On 4/5/2013 2:26 AM, John Summerfield wrote: >> >On 05/04/13 00:28, Jamie Holly wrote: >>> > >I've got a Drupal 7 site running with 60 contrib modules and about a >>> > >dozen custom modules. I got the memory limit set to 128mb and never run >>> > >out of memory. This is on CentOS6 and PHP 5.3.23. There are also >>> > >countless other Drupal 7 sites running out there with no problem. But >>> > >you can pretty much break anything with the wrong configurations and/or >>> > >modules. >> > >> >In contrast, I just created a site with a few modules and themes, and >> >without adding so much as any new content type or content, I did get >> >memory problems >> > >> >I'm using CentOS 6. PHP 5.3.3 with all the latest relevant updates. It >> >happened the first day drupal 7.22 was available and it appeared to be >> >provoked by Jackson. Not having persuaded myself I actually want >> >Jackson, it was easy to dispense with it. I do have the memory limit set >> >to 128Mbytes. >> > >> >However, this isn't Roger's problem. >> > Apologies for not snipping the above but the discussion encapsulates a number of my experiences. When installing Drupal, there should be no reason to jump through hoops to configure just because of Drupal, this seems to imply a fault with the Drupal installation or pre configuration. We can't always blame the user. Yes I agree it happened on earlier releases of Drupal 7. I find that a brand new install with minimal modules and no data or configuration changes will cause the Fatal memory error and have experienced this on 3 unrelated computers and 3 different operating systems. I have tried memory settings between 64M and 512M, even went to 1024M, half the memory on one of my machines. Interesting to note that each test resulted in a different Fatal error allowance report , except the 1024M which almost doubled the numbers of the original 64M. Side note. I just updated the server to Drupal-7.22 and the Fatal memory problem remains. But not on my home systems to which I copied the whole file system and database. I have no way of addressing shared server issues other than /settings.php so thinking if Views and Panels, etc are a problematic Drupal overhead and it's better to build from scratch, Drupal becomes an increasing burden. I think I'll gradually move away from Drupal. Seems it's pretty much, not worth the effort. Roger

2 1

Fed up with Drupal 7 Fatal error..........now module numbers.
by Roger 06 Apr '13

06 Apr '13

I'm curious that discussion comes back to how many modules are installed. Does this imply that significant commercial users are also locked in to a few core modules? We have only the modules we need, and some additional ones which overcome inequities in other modules, like Nat needed to overcome a Workbench-Taxonomy access problem that shouldn't exist in the first place. 41 modules in all, most of which are base Drupal, like Views, Pathauto, token, etc. Users don't have choice on prerequisite modules so I am at a loss to understand the number of modules as a memory issue. I would mention though that a php dev working with us a while ago pointed out how badly some modules are written. Modules, nothing more than plain text files, concatenate into a homogeneous lump, they don't add much to the over all size of the Drupal operating system, but how they handle and release memory is critical and if the number of modules assertion is true that "many modules make Drupal collapse", then perhaps someone could look into module interactions more closely. We are in 2013-4 era, with increasingly complex hardware and technologies, Should Drupal easily handle dozens even hundreds of additional modules? Sad part for us is that I have to set up the site to create newsletters and that means even more modules and possibly additional views. Is this to mean that Drupal is about to have more problems? Thanks Roger

3 2

Update failure-can I do this manually?
by Prothero William 05 Apr '13

05 Apr '13

Folks: I'm finally almost done upgrading from Drupal 6 to 7. What a trudge! MAMP was set to php 5.4.4, so I set it back to PHP 5.2.17, gave it a bunch more memory, reduced the number of modules to just essential ones, did the upgrade, then added the ubercart module. There is one error that I need to fix manually, because something fails in the update script. Eventually, it ran without error, but there is still an error and I think they're linked. The last update was: --------------- 1 pending update uc_order module 7301 - Convert view invoices checkbox to permission. ----------------- I got the following update error: The following updates returned messages uc_order module Update #7301 Failed: PDOException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'module' cannot be null: INSERT INTO {role_permission} (rid, permission, module) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2); Array ( [:db_insert_placeholder_0] => 2 [:db_insert_placeholder_1] => view own invoices [:db_insert_placeholder_2] => ) in user_role_grant_permissions() (line 3076 of /Applications/MAMP/htdocs/modules/user/user.module). When I go to store/products/view, I get the following error: EntityMalformedException: Missing bundle property on entity of type node. in entity_extract_ids() (line 7663 of /Applications/MAMP/htdocs/includes/common.inc). The website encountered an unexpected error. Please try again later. So, how can I fix this manually? I don't have that many products, and can rebuild the products, but what should I do to proceed from here? Since I can't view the products, I can't delete, set, fiddle, whatever. Thanks in advance for any help. Bill Prothero William waprothero(a)gmail.com

2 2

Updating D6 to 7
by Prothero William 05 Apr '13

05 Apr '13

Folks: I'm updating from Drupal 6 to 7. Everything looks pretty good, but I am getting an error in my ubercart store when I try to look at products. It is: EntityMalformedException: Missing bundle property on entity of type node. in entity_extract_ids() (line 7663 of /Applications/MAMP/htdocs/includes/common.inc). I have done update.php throughout the process and did get an error when updating the uc_order_module. It was 7301 Convert view invoices checkbox to permission uc_order_module. I don't know if this could have caused the products problem. Any ideas on how I can fix this manually? Thanks, Bill Prothero William waprothero(a)gmail.com

1 0

Fed up with Drupal 7 Fatal error: Allowed memory size....
by Roger 05 Apr '13

05 Apr '13

My heart just sank into oblivion. I am sooooo sad and fed up with the latest and incessant: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 9331811 bytes) in ...... when I try to add a Content Type in Drupal 7. Months of research, lots of help from this list community and carefully inspecting files apparently achieved nothing. I think I solved it on Fedora 18 on a local copy, do not know how though, but just now, working on the server in my local Fedora 18 and testing on Fedora 16 and Ubuntu 12.10 all with latest updates, except for F16 which is end of life but a good static test platform because it does not have the latest php updates. All of them give the same error. For heavens sake can't the Drupal experts please do something to stop trying to allocate inappropriate bytes, or at least create a comprehensive easy to work through tutorial about this ghastly debilitating error, highlighting all of the reasons it occurs and how to fix it. There's a lot of pages about it on the web but it's still not permanently solved and it's unfair that we have to search long and hard to find possible answers. After all said and done, it's probably a php fault or a php/apache fault and not Drupal at all, so please Drupal move to Ruby with it's inherent security and alternative web servers and get away from php entirely. My apologies for this very disheartened rant. I do not wish to offend those who love and understand php but from what I've read lately, it is old hat nowadays and struggling to keep up appearances, at least that's my take on it after a lot of reading on pro's and con's. Apologies for a convoluted rant, I'm in a hellava bind and not thinking straight at the moment. Roger

4 7

Re: [support] Fed up with Drupal 7 Fatal error: Desperately, need help
by Roger 05 Apr '13

05 Apr '13

Hi Idan Thank you for jumping in, much appreciated. In answer to your query, I have a series of bulletins in both pdf and png named as 'Bulletin January 2010', 'Bulletin March 2010' through to Bulletin January 2014. 3 per year, maximum of 150kb each. I need to display all of the bulletins including future versions as png images 350px x 500px approx., in chronological order on a bulletins page. It's a sort of historical record, accessed by member log-in. PDF display is not required. I can create a view that displays all of the images in the /images folder, including the Bulletins if they are in the images folder, and not have memory issues but cannot get it to access or display images in folders within the /images folder or folders outside the /images folder. Strange thing is that - If I could create a new content type, I could have a number of blocks on that content type page and display all the bulletin images within those, - easy as, no brainer. But it's not dynamic and has to be manually changed as new bulletins arrive. The php Fatal memory issue is not related to the above. Instead it relates to Drupal displaying the [Create Content Type] Administration page and it is my feeling that Drupal devs could bite the bullet and build in counter measures for this recurrent php fault. Like reducing the memory requirement for Creating Content Types, which after all is just another creation page like creating new Taxonomy , Views, Rules, People, Workbench, Blocks, etc but for some reason Create New Content Type frightens php out of it's wits so it hides quivering under the Fatal: bed. As was pointed out by John in reply #6 it's got to be a php problem due to upgrading and seems to have been through previous upgrades judging by the number of Google pages on the subject. I believe it has never been attended to. Yes I have set memory_limit in php.ini, and I have changed /settings.php in Drupal and these seemed to solve the problem until my Fedora 18 upgraded php from 5.3 to 5.4 a week or so ago. So in deference, it is not my machine or it's settings or the remote server but exclusively a php dev testing failure prior to release. I am looking into Centos 6.4 as was recommended by John but that's not an immediate fix, 5-6 hours to download is beyond my internet capability. Roger > just jumping in here....Can you explain what you're trying to achive, why > are you trying to access the images directly? have you increase the memory > limit in the php settings? > > Idan > > > On Thu, Apr 4, 2013 at 10:08 AM, Roger<arelem(a)bigpond.com> wrote: > >> > >>> > ><snip> My heart just sank into oblivion. >>> > >I am sooooo sad and fed up with the latest and incessant: Fatal error: >>> > >Allowed memory size of 134217728 bytes exhausted (tried to allocate >>> > >9331811 bytes) in ...... </snip> >> >Hi again. >> >Ok so I can't create a content type due to Fatal error messages, but >> >maybe I can make a view and display that in an existing page or block. >> >Problem is I have png images in a number of directories in the >> >/defaults/files/images/Seminar database. >> >Images are png and jpg. >> >I have no idea how to tell a view how to get images from certain >> >directories. >> >For some reason the view I create gets images only from the /images >> >directory and no other. I could not even figure out how to filter on >> >directory names. >> >If it can be solved how to get only png images from different >> >directories /images/Seminar/2011, /2012, /2013, /2014 file tree this >> >would be of great assistance and maybe bail me out temporarily. >> > >> >Thank you for any assistance, it will be greatly appreciated. >> >Roger >> >--

3 4

Re: [support] Restting image file type
by fathi.engineer＠gnet.tn 05 Apr '13

05 Apr '13

Thanks, What i did was to alter the file type through admin/structure/file-types/manage/image/fields and added some fields which i wanted to be imported automatically by "custom exif mapping" on upload, which didn't work. I have also created a content type and named it video (with system_name:video) which maybe could have conflicted with the file type video and that i have renamed later to videyo, in a hope to reset things back. Looking to my database through phpmyadmin, i found in table field_config_instance references to three file types: image, video and videyo in the column bundle as i have added these extra fileds like copyright, date_shot, artist, location to both image file type and video file type. So, i don't have an image content type just a file-type image which i altered, and then creted a content type image gallery with multiple values of the file type image. ---- Original Message ---- From: Info Razor To: support(a)drupal.org Sent: Ven, Avr 5, 2013, 6:12 PM Subject: Re: [support] Restting image file type Removing the fields form the content type should be enough. If the fields are used in other content types, the table will stay because it is being used by other content. If you can't use the GUI anymore, you can always use Drush to turn modules on/off and to change DB variable values. Image field does not, in itself, have extra fields defined. The extra fields are defined on your content types. Hope this helps. -- Info Razor Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Friday, April 5, 2013 at 8:56 AM, fathi.engineer(a)gnet.tn wrote: Hello, I did something on a nearly to be deployed production site, and now i can't access the admin/structure/file-types. I have added some extra fields to the image file type and now i would like to remove them as this caused me extra trouble and my approach didn't work with the "custom exif" module, which i have uninstalled. Can someone tell me which tables should i alter to get back the file type image whitout the extra fields i have added. TIA -- [ Drupal support list | http://lists.drupal.org (http://lists.drupal.org)/ ]

1 0

Restting image file type
by fathi.engineer＠gnet.tn 05 Apr '13

05 Apr '13

Hello, I did something on a nearly to be deployed production site, and now i can't access the admin/structure/file-types. I have added some extra fields to the image file type and now i would like to remove them as this caused me extra trouble and my approach didn't work with the "custom exif" module, which i have uninstalled. Can someone tell me which tables should i alter to get back the file type image whitout the extra fields i have added. TIA

2 1

Files in the cloud with drupal 7? (ownCloud functionality rebuild in drupal)
by Stefan Nagtegaal 05 Apr '13

05 Apr '13

Hi list, After been away for a while, I'm trying to get up to speed again with drupal. I have to setup a website for uploading, sharing, viewing and downloading files. A sort of personal cloud, with the ability to share files with some other users. (For people familiar with ownCloud: that's exactly what I am looking for, only the theming abilities of ownCloud are horrible, and the separation between logic vs function is even worse.) The question is, is this possible using drupal 7, and what modules do I need to accomplish such a thing? Offcourse, i looked at all the modules on the modules download page, but it's like finding a needle in a haystack. I hope to hear from someone soon. Kind regards, Stefan Nagtegaal

1 0

Domains, subdomains on D7
by John Summerfield 04 Apr '13

04 Apr '13

I am trying to create a website for a club, we'll call it's domain example.com example.com should be the administration site, no club members per se, although its registered users might be members of associated clubs, its in order for that to be the case. Associated clubs with have subordinate domains, so friends.example.com, raiders.example.com and so on. It's also in order for people to be members of more than one club, and they often are. Example.com will provide some general information that should be accessed directly by all the subordinate clubs. On the other hand, each club will provide information of its own, and that should be accessible in a menu item, "club news." Also, each club should be able to provide some specific information as an alternative to that provided at example.com. For example, example.com/About would tell its visitors about the base organisation. For example, "We promote our sport.... "We have associated clubs here, there and everywhere." raiders.example.com/About would say that "We have these competitions.... "We have school programs at .... "Our clubrooms are at 45 Raiders Way, Bordertown." and so on. What I want is for Raiders visitors see only raiders.example.com/About but not the one at example.com or friends.example.com. What happens is that a user registered for both example.com and raiders.example.com has, not one, but two /About links. An example of information that only Raiders can see is Raiders' membership list. Our law requires that membership lists of all incorporated bodies (in Australia that means Example Inc, Raiders Inc - company names are generally titles Ltd or Pty Ltd) must be available to members. For the present I don't propose to provide more than just the names of members, but I do wish it to be available only to those members, and not to General Public. Similarly, Club News would mean Raiders' news at Raiders, Friends' news at Friends, but their news should be accessible through another menu choice. I have a working list of associated clubs, so switching between domains is trivial. I an happy to have just one list of members, but they must only see member's-only content from whichever site they are looking at at the moment, and then only if they are members of that club. I have been trying to do this with the domains modules, but I am not sure that the will let me do what I want without cutting code. I am pretty feeble with PHP, but I might manage a small amount. Does anyone have any advice on how to achieve my ends? Is using the domains modules my best choice, or should I look at something else?

7 14

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

support April 2013