Make sure you have allow_url_fopen enabled in your php.ini
By default this is enabled in PHP, but some hosting providers may disable it due to “security reasons” ( e.g. they want to look cool )
Create empty file only with code
<?php
phpinfo();
?>And open it in browser. Then search for allow_url_fopen
If it says Off, you need to change this setting in your hosting.
http://php.net/manual/en/filesystem.configuration.php
Open wp-config.php and somewhere under database settings add
define('WP_MAX_MEMORY_LIMIT', '256M');
define('WP_MEMORY_LIMIT', '256M');This will definitely adjust WordPress memory limit to 256MBs. You can use higher number if needed – e.g. 512M for 512 MBs of Ram.
Make sure to adjust PHP limit as well, either in php
ini_set('memory_limit', '256M');.htaccess
php_value memory_limit 256M
or php.ini directly ( it will already be in php.ini file, just look it up and change the value )
memory_limit = 256M
In case you have accidentally committed your vendor folder, you can easily remove it by following these steps:
git rm -r --cached vendor git rm -r --cached composer.lock git commit -m "untrack vendor directory" git push
Boring way:
for($i = 0; $i < count($arr); $i++){
$arr[$i] = trim($arr[$i]);
}The right way:
$arr = array_map('trim', $arr);This will call function trim on every value in array $arr.
If you want to force ssl on your website and for some reason you can’t do it in vhost config directly, you got 3 ways to do it in htaccess.
Changes are you got a good hosting and all 3 will work for you ( for example on your own VPS ). Then there are some hostings without modssl, or with load balancers and then some of these generic rules, that work for 99% people out there will end up in endless loop.
Best to try all 3 of them, one by one and see which one works for you.
1st version – the most basic, works on most hostings
<IfModule mod_rewrite.c>
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
</IfModule>
2nd version – if server is using apache without modssl, then %{HTTPS} value will always be ‘off’ and therefore the rule above will cause infinite loop. Use this version instead – it checks server port instead of ^{HTTPS} variable.
It works great on websupport.sk
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{SERVER_PORT} !^80$
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
</IfModule>
3rd version – if all 2 above end in infinite loop, chances are your hosting is using some kind of load balancer.
Try this version then:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
</IfModule>
If you are doing this on Laravel project, make sure you put this in root folder. Very often your root folder will have 4 line htaccess file which redirects everything into public folder. That’s where you need to put this. Do not put http->https rules into public folder’s htaccess, unless that is your root folder as well ( on VPS for example )