Setting safe mode to OFF in .htaccess file does not work
It sounds like he doesn't allow you to override safe mode. Which makes sense because what would be the point in running a shared server in safe mode if anyone could disable it as they saw fit. You're probably going to need to relocate to a server without safe mode as the only options for changing that value are not going to work for you. Safe mode is already deprecated and is not meant to be used. The "safe" way for a server owner to handle security is through the OS and setting up correct account permissions.
Laravel shared hosting - Directive 'safe_mode' is deprecated in PHP 5.3 and greater
This is likely due to your error reporting level. Try ignoring E_DEPRECATED
and possibly E_WARNING
.
If you are running Laravel 3, you should be able to set your ignored error levels in application/config/error.php around line 16.
/*
|--------------------------------------------------------------------------
| Ignored Error Levels
|--------------------------------------------------------------------------
|
| Here you simply specify the error levels that should be ignored by the
| Laravel error handler. These levels will still be logged; however, no
| information about them will be displayed.
|
*/
'ignore' => array(E_WARNING, E_NOTICE, E_USER_NOTICE, E_DEPRECATED, E_USER_DEPRECATED),
shell linux don't execute commande
Finally I found a good solution for who still search :
I installed php-ssh2 with this link (i use debian 8, php7)
blog.programster.org
and in my case i use codeigniter i follow the link to implement this class
bitbucket.org
now i can execute any commande on shell without probleme
and the probleme is solved :)
Hope its help someone :)
shell linux don't execute commande
Finally I found a good solution for who still search :
I installed php-ssh2 with this link (i use debian 8, php7)
blog.programster.org
and in my case i use codeigniter i follow the link to implement this class
bitbucket.org
now i can execute any commande on shell without probleme
and the probleme is solved :)
Hope its help someone :)
Turn register_globals on for just one app
You could always try to put:
extract($_REQUEST,EXTR_SKIP); //thanks @Wayne Whitty
on top of every files. It would yeld the same results as far as I know.
But really, REALLY, its bad bad bad to use these. I'd look for a way to change the code. But sometimes you have no choice.
Any PHP framework to use SECURELY on shared hosting?
Having to declare directories with 777
permissions is only a problem on cheapo and entry-level shared hosting systems. It's common to see the safe_mode hack and openbasedir restrictions in that area, which only prevent access via PHP but not other CGI interpreters.
Contemporary server setups use suexec/suphp, where every PHP scripts runs under the current accounts permissions. Therefore you don't need any world-write directories and most PHP application should be secure against cross-account tampering at least. The framework itself doesn't make a difference here.
Related Topics
Sort an Array by a Child Array's Value in PHP
Remove Bom () from Imported .CSV File
Woocommerce: Assigning an Endpoint to a Custom Template in My Account Pages
Laravel Eager Loading with Limit
Why Does the Laravel API Return a 419 Status Code on Post and Put Methods
Get Last Insert Id After a Prepared Insert with Pdo
How to Solve Incompatible with SQL_Mode=Only_Full_Group_By in Laravel Eloquent
Google Gcm Server Returns Unauthorized Error 401
Is It Okay to Use Array[Key] in PHP
PHP - Split String in Key/Value Pairs
Get Element by Classname with Domdocument() Method
How to Generate Random 64-Bit Value as Decimal String in PHP
How to Get a Div Content in PHP
How to Display a MySQL Error in PHP for a Long Query That Depends on the User Input