Roger, sounds like the situation is unclear. My assumption was that the Drupal root and the domain root were the same, in your case public_html. It sounds like that is not the case. Drush would not have gone outside the Drupal root to delete a php.ini file. So I think my theory as to your problem is probably wrong. FYI, since my early days of using Drupal I standarized on always making the Drupal root and the domain root the same. In theory, Drupal doesn't require that, but I have just been plagued by problems whenever I try otherwise. I'm not saying that is your problem here, just sharing my (bad) experiences with implementing Drupal outside the domain root. Shai On Wed, Jan 23, 2013 at 3:38 PM, Roger <arelem@bigpond.com> wrote:

<snip> Drush will delete non-drupal files that are not in the sites directory. It sounds like you typically have a php.ini file installed at the Drupal root.

Did you put it back after Drush erased it? Can you verify that it is still there? </snip>

Hello Shai and everyone. thank you for your replies.

Our ISP installed a special version of php.ini in /public_html so that apache does not have to be restarted. I did not think to look for a php.ini in the drupal root, thanks, I will investigate.

ISP also lso found that the Token module was causing the failure of Drupal Permissions and Create New Page.

I find, as of last night, that I am prevented from using IMCE as administrator. I get error message that Page cannot be viewed, You do not have permissions, etc. What a load of rubbish, if you pardon my expression, Admin not having correct perms seems very strange.

Investigation shows that this php.ini thing has been an ongoing issue, seems unresolved since Drupal 5.

Regards Roger -- [ Drupal support list | http://lists.drupal.org/ ]