title: Do we still able to re-configure php.ini 'on the fly' when we don't allow to access to the file?
body: <p>I'm using Laravel Framework and I have a problem when I put my Laravel application on my shared hosting. 
  When I execute my site url, this message below is appear;</p>
  
  <pre><code>Unhandled Exception
  
  Message:
  
  Directive 'safe_mode' is deprecated in PHP 5.3 and greater
  Location:
  
  Unknown on line 0
  </code></pre>
  
  <p>And I search around with that keyword. I found the message above appear because my php.ini <strong>safe_mode</strong> is <strong>on</strong>. </p>
  
  <p>I execute phpinfo() and give me information that php.ini path is /usr/local/lib/php.ini</p>
  
  <p>That's make me disappointed :( because I can't access php.ini. (I am using cPanel &amp; WHM 11 shared hosting.)</p>
  
  <p>Would you please tell me any other solution to this problem?</p>