I am installing Kayako Fusion and get this error:
Reason: Magic quotes is enabled in the php.ini configuration file. Please change magic_quotes_gpc to Off
Unfortunately, Kayako cannot be installed. Either an error has occurred or your web server doesn't meet the minimum system requirements. Please review any errors shown above and retry the setup process after those items have been resolved
I have tried php.ini file also but its not working. I am on Shared Hosting.
You can disable magic quotes via .htaccess file
In the webroot of your Kayako install create a .htaccess file
paste in the following:
php_flag magic_quotes_gpc Off
Sounds like something is overriding whatever customisations you are making to your php.ini. I think this is a question for your shared hosting provider: "How can I disable magic quotes for my hosting account?"
Hope this helps.
Related
I upload my Laravel project on shared hosting. When I upload my project on the server it throws an exception then switched my PHP version 5.4 to 7.4. Now am facing this issue.
Deprecated: Directive 'allow_url_include' is deprecated in Unknown on line 0
I also disable the allow_url_include in my PHP ini file which exists in project root directory but it still says allow_url_include depreciated error.
Also, I go into the PHP Multi INI Editor and change the allow_url_include but it still throw the above error.
Remove .htaccess or change name to .htaccess.backup and WP will generate new file based on your site configuration
Log into your website host and navigate to your public_html folder and find the php.ini file. Open the file and find this code:
; Whether to allow include/require to open URLs (like http:// or ftp://) as files.
; http://php.net/allow-url-include
allow_url_include = On
Change allow_url_include = On to allow_url_include = Off and save the file.
This should fix the error.
Additional detail located here:
https://www.php.net/manual/en/filesystem.configuration.php#ini.allow-url-include
In case anyone comes across this:
Make sure that .htaccess files at all levels do not have conflicting code.
That is, I found that my ".../public_html/.htaccess" did not have any conflicts. However, I also had an .htaccess file in the folder level above that and it included code that read:
# Use PHP71 as default AddHandler application/x-httpd-php71 .php <IfModule mod_suphp.c> suPHP_ConfigPath /opt/php71/lib </IfModule>
Commenting this out resolved the error for me.
If your web host uses Cpanel, log in and under the Software section click Select PHP Version, then on the next screen click Options. Under Options, unclick allow_url_include:
Please Update PHP version of your site through CPanel to 7.3. This fixed the issue for my site. Thank you!
My client had 2 .ini files, conflicting max_input_var.
Deleting user.ini worked for me! Payment options were greyed out in WooCommerce. Now they are showing and this "allow_url" error is gone.
I have a Prestashop 1,6 with 1and1 as hosting Service and cant use the Translation Service in the Backend because of the max_input_vars settings.
Warning! Your PHP configuration limits the maximum number of fields allowed in a form: 5000 for max_input_vars.
Please ask your hosting provider to increase this limit to 5271 at least, or you will have to edit the translation files.
I tryed to set the max_input_vars settings to 6000 and didnt get a error on the server but it wont work has someone a solution to fix it or knows how to change it?
P.S. here is the PHP file i used
<?php
error_reporting(E_ALL);
ini_set('max_input_vars', 6000);
?>
if you have shared hosting then instead of php.ini you have create a file name .user.ini and
max_input_vars=6000;
and upload on root. it will take time to reflect changes based on server settings.
I think that the best way to do this is asking directly to 1and1 because is probable that you don't have permissions to change this feature of PHP.
Also, you have another options:
File .htaccess: externar link
Make a php.ini file in the root of the installation and add this:
max_input_vars=6000;
Hope it helps you.
I am unable to save any article / module etc in Joomla 3.0. When I try to save the " " is replaced by "\"\"". This messes up all my code. I tried turning off the magic_quotes_gpc in php.ini but that did not help.
How do I fix this?
I presume you did the Joomla! 3 installation by adding the .htaccess with magic_quotes_gpc = off inside the install directory, to successfully install the platform, correct?
If your server is running php 5.3+ you need to set the server php configuration to magic_quotes_gpc = off. It should be configured as so since magic_quotes_gpc is deprecated in php 5.3 and will be removed in 5.4.
In summary, you can only overcome this issue by configuring the php on the server. No .htaccess will solve your problem, unless you place an .htaccess inside each and every directory on your Joomla! installation - which is unthinkable imo.
fixing the issue where adding \" during article posts in administrator panel:
magic_quotes_gpc = Off
magic_quotes_runtime = Off
magic_quotes_sybase = Off
Disable these options from your php.ini file.
You can also overwrite the php.ini.
Please check the link for overwriting the php.ini using .htaccess
How to turn off magic quotes on shared hosting?
I have tried every possible solution for my php file 30 seconds timeout, but nothing works.
Is it possible that my new configurations that I put in my code don't take affect and still works according to the configurations which are in Goddady's default php.ini?
Quick google shows that you can't change that setting on GoDaddy shared servers. Can't be done: http://support.godaddy.com/groups/web-hosting/forum/topic/set-max_execution_time-and-max_input_time/
That was 2 years ago, and so probably not changed. Go virtual or get a new host?
Yet it is possible that a hosting provider does not allow overrides for some settings or for all settings.
That's what the httpd.conf configuration directive AllowOverride None/AllowOverride All does.
Use ini_get('max_execution_time') to check what the execution time becomes after you've tried a solutin. If it doesn't change it's obvious that solution didn't work.
Are you sure you've put it in the correct location to be identified? if so, you can look into this link
http://support.godaddy.com/help/article/5647/why-isnt-my-phpini-file-taking-effect
you've provided too little information about your server. if it is linux, here what they said:
On Linux Shared Hosting accounts, you can kill the Web processes to
get your php.ini (PHP 4) or php5.ini (PHP 5) file to take effect.
I was able to make it work on a Godaddy shared Linux account by creating a .user.ini file in the hosting root.
My changes are visible with phpinfo()
remember that when setting your own custom php.ini file with Godaddy you may pull up timezone warning messages. In which case you have to also define the default timezone in the php.ini file, for example:
date.timezone="Europe/London"
More about this problem here:
https://uk.godaddy.com/help/why-did-i-receive-a-timezone-error-with-my-php-website-6703
anyone knows if is it possible to enable php parse_ini_file() function overriding php.ini settings into .htaccess? If yes how it can be done?
Thank you all for help
If it was disabled using disable_functions, you can't reactivate it using a .htaccess php_value directive. See http://php.net/manual/en/ini.core.php
As far as I know, parse_ini_file() is a core function built into PHP, thus it can't really be enabled. I'll guess that you are facing one of these situations:
Your host has disabled it for security reasons (:-?) using the disable_functions directive.
You are providing a URL in the $filename parameter and your host has disabled loading or remote files with the allow_url_fopen directive.
You are reading an *.ini file you don't have access to.
In general, all three cases imply that you are just not allowed to do so. Even if you manage to find a hack and override the restriction, you might be violating your host's terms of use. Whatever, it's possible that you are just trying to do the wrong thing:
Local files can be read from disc, there is not need to use HTTP.
You should be able to read your own files, given that they're given the appropriate permissions.
I added a copy of php.ini under the folder where application wants to call parse_ini_file() and it helped, but my hosting provider "honors" php.ini file per directory, so each app can use different settings.
In this case the app was complaining PHP function parse_ini_file is not available not because the method was disabled, but because it could not find php.ini to parse.