Closed (fixed)
Project:
Ubercart Option Images
Version:
6.x-1.4
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Dec 2010 at 17:28 UTC
Updated:
22 Feb 2012 at 18:12 UTC
Jump to comment: Most recent file
Comments
Comment #1
alb commentedconfirm this problem;
I also tested to increase the
max_execution_time, max_input_time, and memory_limit
but not work
Comment #2
SeanK commentedNew info:
Set up a localhost server with UberDrupal, core 6.20, and all module update recommended as of today.
Enabled Attributes. Worked as expected.
Tried to enable Option Images Dev version.
Recieved the following:
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 261904 bytes) in C:\xampplite\htdocs\drupal\includes\bootstrap.inc on line 1718
So now I have a place to start.
Comment #3
SeanK commentedNext try: moved the module from the UberDrupal profile modules folder into the sites\all\modules folder. New error message:
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 261904 bytes) in C:\xampplite\htdocs\drupal\sites\all\modules\uc_option_image\uc_option_image.install on line 7
Comment #4
neilnz commentedHere's a patch that'll get it to install.
The problem is a recursive loop because it's setting $no_image then checking $noimage.
I have removed the recursion and got it to just set the default.
Comment #5
SeanK commentedTested patch and it has worked successfully.
Comment #6
acouch commentedI rewrote the install file so that it no longer uses that recursive call. If anyone else knows what function that served or what it should still be in the module let me know.
Comment #8
Xermit commentedI have the same error
I applied the patch but not had other error:
PHP Parse error: syntax error, unexpected ';', expecting ')' in C:\xampp\htdocs\drupal\sites\all\modules\uc_option_image\uc_option_image.i
as result i revert patch #4 and replace symbol ';' to ',' and install is completed
Comment #9
mallton commentedI received the same error as in #8. Updating the install file to use ',' instead of ';' on line 11 resolved the issue and allowed installation to proceed. This needs to be committed.