Hi Dugchugger...
I see no one has stepped in to help you over the last few days. Let me see if I can be of assistance.
Regarding your auto prune blooper... you're screwed. Sorry.
Regarding the memory error, if you have access to your php.ini file you could increase your memory_limit to 12M or 24M. It appears to currently be set at 8M. If this doesn't work, you may need to set it higher. If you don't have access to your php.ini, you will need to ask your host to make this change for you.
Alternatively, Gemma posted
this suggestion:
Quote:
temporarily up your limits edit your includes/config.php file and add these lines right under the <?php line:
ini_set('memory_limit', 128 * 1024 * 1024);
You may need to change the 128 to 256 or 512
|
This suggestion worked for another user, but not for poor Lombardo who originally asked for help on May 9th... but apart from the initial responses he got (that didn't work for him), he received no further help that we can see.
If this doesn't help, let me know and I will try to assist further... cuz I care.
--------------- Added 07 Sep 2008 at 23:07 ---------------
Wow... thanks for the help duggy.
I initially asked my host to increase the memory_limit to 12M from 8M a few days ago. They said they upped it to 24M... but I neglected to confirm this for myself. They have a history of not following through on what they say they will do. Still experiencing the memory probs today, I double-checked my php info and noticed that it was still set to 8M. I nudged them. At first I received a reply saying I wouldn't see it in php info if it was done via .htaccess. Ookay... not like I know how it was done... I didn't do it. Then a follow-up response admitted that they erred after a change to the php. Alrighty then. Either way, it still reflected 8M.
I noticed there was an additional .htaccess file in the root arcade folder and one in the functions directory, so I tried adding this line to both (after already having it added to the main .htaccess file):
php_flag memory_limit 24M
That still didn't fix the problem. So I tried Gemma's idea above and it just made things worse. In fairness, I don't know enough about php and I think the code needed some adjusting.
Then I received another contact from my host advising that they hadn't realized I was parsed to php5 and had made another adjustment. The 24M is now showing up under memory_limit and the memory problem has been resolved... woot!!!
Thank you for your help!
--------------- Added 07 Sep 2008 at 23:07 ---------------
No prob. Glad to hear it was fixed. Party on!