<div dir="ltr">Yes, that is a sure way to break sites.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jan 22, 2013 at 12:34 PM, Earnie Boyd <span dir="ltr"><<a href="mailto:earnie@users.sourceforge.net" target="_blank">earnie@users.sourceforge.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This should be brought up in the Drush issue support as a feature<br>
request to leave php.ini alone.<br>
<div class="HOEnZb"><div class="h5"><br>
On Tue, Jan 22, 2013 at 8:31 AM, Shai Gluskin <<a href="mailto:shai@content2zero.com">shai@content2zero.com</a>> wrote:<br>
> Hi Roger and all,<br>
><br>
> Drush will delete non-drupal files that are not in the sites directory.<br>
><br>
> It sounds like you typically have a php.ini file installed at the Drupal<br>
> root. Did you put it back after Drush erased it? Can you verify that it is<br>
> still there?<br>
><br>
> Even though I have a dedicated server, I run it like a shared server using<br>
> cPanel. I've updated 12 Drupal 7.19 sites on 12 different cPanel accounts<br>
> and have not had any problems. However, my situation is different in that I<br>
> have the server-wide php.ini file tuned for my Drupal set-ups, so I don't<br>
> need to have any php.ini files installed at the Drupal root.<br>
><br>
> But I do manage a Drupal site on another cPanel server and ran into problems<br>
> similar to what you ran into. Drupal erased the php.ini file installed at<br>
> the Drupal root. Once I figured out that was the problem (with some help<br>
> from the HostGator customer support), I just put back the php.ini file<br>
> (which I had a backup of) and everything got better.<br>
><br>
> Shai<br>
><br>
><br>
> On Tue, Jan 22, 2013 at 4:21 AM, Roger <<a href="mailto:arelem@bigpond.com">arelem@bigpond.com</a>> wrote:<br>
>><br>
>> Hello<br>
>> I updated drupal using drush successfully on the shared server<br>
>><br>
>> When trying to open permissions I got bytes exhausted error and had to<br>
>> increase memory_limit to 256M to at least access permissions.<br>
>><br>
>> Now have a problem, in /admin/structure/types/add I get error:<br>
>> *Fatal error*: Allowed memory size of 134217728 bytes exhausted (tried<br>
>> to allocate 79 bytes)<br>
>><br>
>> I have tried various memory settings in php.ini on the server and find<br>
>> that memory_limit = 128M seems to try to allocate less bytes than if I use<br>
>> 96M, 128M or 256M.<br>
>><br>
>> Why does drupal exhaust memory, this seems most strange<br>
>> Can you please tell me what causes this error and how to fix it. Google<br>
>> has not helped much.<br>
>> Thanks in advance<br>
>> Roger<br>
>><br>
>> --<br>
>> [ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
><br>
><br>
><br>
> --<br>
> [ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
<br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
Earnie<br>
-- <a href="https://sites.google.com/site/earnieboyd" target="_blank">https://sites.google.com/site/earnieboyd</a><br>
</font></span><div class="HOEnZb"><div class="h5">--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
</div></div></blockquote></div><br></div>