In today’s quick tip screencast you’ll learn how you can profile a PHP application, such as WordPress, using Xdebug and WinCacheGrind on XAMPP for Windows.
To enable Xdebug, modify the following settings in your php.ini configuration file:
zend_extension = "\xampp\php\ext\php_xdebug.dll" linexdebug.profiler_enable_trigger = 1xdebug.profiler_output_name = "cachegrind.out.%u.%H_%R"Save php.ini and restart Apache.
Click image to view full phpinfo() output PDF
You heard it right, you can now run PHP 5.3 applications on HostMonster. I’ve only testing this on HostMonster, but I would assume the same applies to BlueHost.
Simply add this line to the beginning of your website’s root .htaccess file:
AddHandler application/x-httpd-php53 .phpAfter making this change you can test it using phpinfo() and it will show you the version at the top, and as of the time of this post Hostmonster is keeping right up to date, running version 5.3.9.
This is exciting news for Zend programmers and other PHP developers ready for the upgrade. Enjoy!
I know you’ve probably seen this topic a hundred times, and so have I, but this one has a different twist. We already know that there are many ways to get the extension of a file, but which one is the fastest? That’s what I’m going to address right now.
In each of the code examples $file is set to c:\\xampplite\\htdocs\\index.php.
<?php
$ext = end(explode('.', $file));
echo $ext; // outputs 'php'
?>
<?php
$ext = substr($file, strrpos($file, '.')+1);
echo $ext; // outputs 'php'
?>
<?php
$ext = pathinfo($file, PATHINFO_EXTENSION);
echo $ext; // outputs 'php'
?>
To test each of the contenders I put together a script that timed the execution of 1,000,000 iterations of each command. If you would like the script you can download it here.
Sub-String Method: 0.778156 seconds
String-to-Array Method: 1.889744 seconds
Path Info Method: 2.020036 seconds
Our winner? The Sub-String Method! Next time you reach for that line of code to get a file’s extension, go for gold, and choose the Sub-String Method.
<?php
$ext = substr($file, strrpos($file, '.')+1);
echo $ext; // outputs 'php'
?>
OpenCart’s default image upload size is 300KB and that is simply too small for clients that don’t have the knowledge to resize their images before uploading them. Although uploading digital camera images does use more bandwidth, sometimes it can not be avoided. To adjust the image upload size make the following changes around line 446 of admin/controller/common/filemanager.php:
if ($this->request->files['image']['size'] > 10485760) {
$json['error'] = $this->language->get('error_file_size');
}
In this case we have increased the upload size limit to 10MB, also make sure that your php configuration will allow file uploads and posts of this size.
Now you have these big images uploaded, but sometimes GD can run out of memory trying to resize these large images. You can solve this by using imagemagick, if available. So what we’re going to do is resize all images larger than 1000×1000 down to 1000×1000. Make the following changes around line 490 of admin/controller/common/filemanager.php:
if (!isset($json['error'])) {
if(substr($this->request->files['image']['type'],0,5)=='image'){
$imageinfo = getimagesize($this->request->files['image']['tmp_name']);
if($imageinfo[0]>1000 || $imageinfo[1]>1000){
exec('convert -colorspace RGB "'.$this->request->files['image']['tmp_name'].'" -resize 1000x1000 "'.$this->request->files['image']['tmp_name'].'"');
}
}
if (@move_uploaded_file($this->request->files['image']['tmp_name'], $directory . '/' . basename($this->request->files['image']['name']))) {
$json['success'] = $this->language->get('text_uploaded');
} else {
$json['error'] = $this->language->get('error_uploaded');
}
}
That’s it, your image upload file size limit has been lifted and memory usage issues have been dealt with!