grmbl.

WordPress 3.6 is now: upload_max_size=….

Was: upload_max_filesize=….

Hmmm, maybe also put:

post_max_size=…

to the same size.

Not happy about this and finding out afterwards.

Note: for a php problem I recently encountered this message:

ALERT - script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker 'aa.bb.cc.dd', file '/home/user/www/wordpress/wp-admin/admin.php', line 109)

After some google I found: http://wordpress.org/support/topic/adminphp-tries-to-increase-memory_limit

A solution is given, but the post is rather old (solution is not in admin.php anymore) so search for the locations of the WP_MAX_MEMORY_LIMIT setting in your WordPress directory: find . -exec grep -H WP_MAX_MEMORY_LIMIT {} \;

Or check directly: vi .....www/weblog/wp-includes/default-constants.php

Change this limit to whatever it’s set to in the php settings. To find out what they are, use the following info.php script in a location you can use from the web:

<?php
phpinfo();
?>

After installing a new server, I got the upload_max_filesize message from WordPress (from php) after I tried to upload a large image file:

Of course I forgot to edit the /etc/php5/apache2/php.ini file at line 877:

; Maximum allowed size for uploaded files.
; http://php.net/upload-max-filesize
upload_max_filesize = 2M

Just 2Mb is not much… Can be altered though!

Some time ago I was asked to allow developers use the short “<?” tag instead of the “<?php” on my server. The php manual clearly discourages this, especially when using code that is going to be redistributed.

On the other hand, why are both possible and if the first isn’t more dangerous then it doesn’t matter does it?

Anyway, the proper way to handle it is to change the short_open_tag = Off/On option in php.ini