First seen the report by blogger Ruchira. Now I also start to get emails containing subject “Interested in Purchasing Advertising: site address“. Here I will share details of the proposal, why its sounds bad, and surely bad and why you should not fall for it.
split() is a very common PHP function. Here I am not going to discuss its usage. But I will give a super simple solution for the error “Deprecated: Function split() is deprecated“. This error is annoying, and will happen to everyone using
split() function. So, keep reading for the super easy solution.
Why We Are Getting This Error Suddenly?
preg_split(), which uses a Perl-compatible regular expression syntax, is often a faster alternative to split(). If you don’t require the power of regular expressions, it is faster to use explode(), which doesn’t incur the overhead of the regular expression engine.
And, apparently “split” is removed as of PHP 5.3.x, in the preparation for PHP 6.0.
I wrote about W3 Total Cache 0.9.2.7 issue, which caused few issues including MaxCDN custom domain name not working. Frederick, the plugin author was fast enough to release updated version 0.9.2.8, but it caused a Fatal error like below, and here I will show a quick workaround to fix the issue.
Fatal error: Uncaught exception 'FileOperationException' with message '<strong>/public_html/wp-content/w3tc-config/master.php</strong> could not be created, please run following command:<br /><ul><li><strong style="color: #f00;">chmod 777 /public_html/wp-content/cache/tmp</strong></li><li><strong style="color: #f00;">chmod 777 /public_html/wp-content/w3tc-config</strong></li>' in /public_html/wp-content/plugins/w3-total-cache/inc/functions/activation.php:127 Stack trace: #0 /public_html/wp-content/plugins/w3-total-cache/lib/W3/ConfigWriter.php(159): w3_throw_on_write_error('/...', Array) #1 /public_html/wp-content/plugins/w3-total-cache/lib/W3/Config.php(71): W3_ConfigWriter->save() #2 /public_html/wp-content/plugins/w3-total-cache/lib/W3/CloudFlare.php(174): W3_Config->save() #3 /public_html/wp-content/plugins/w3-total-cache/lib/W3/Plugin/CloudFlare.php(52): W3_CloudFlare->update_ip_ranges() #4 /h in /public_html/wp-content/plugins/w3-total-cache/inc/functions/activation.php on line 127
This blog also use W3 Total Cache to handle caching. Few days ago W3 EDGE company behind this super popular (Downloads: 1,622,242) plugin pushed updated version 0.9.2.7. They actually introduced a revamp look and seems like a great update. But after update, Asif.im broke down completely, as MaxCDN, the Content Delivery Network(CDN) I use was not working with the updated version of W3TC. Here is a quick semi-fix.
Evernote is cool. I love their basic idea. Their business model is also nice. But my question was why they have so many different apps? Like I could see they are currently offering 7 different apps for iOS. Basic thing is always same, keeping note. Without Skitch, which is for making annotation and drawing, all apps are for taking notes. But why 7 different apps?
List of all apps and my thoughts inside.
If you just updated to current latest version of WordPress 3.4.2 and finds out the custom fields is not updating and broken you are not alone. Its happening for everybody. Its a known bug for WordPress 3.4.2. Here we have a quick fix before WordPress 3.4.3 arrive.
Cant find App Store in your iPhone, iPod Touch & iPad? It could be any version of the device. And you really cant find App Store even in Spotlight Search? No Clue?
We have solution for it, Lol! Its weird situation, with easy solution.
From Probably WordPress 2.7.1 there is auto update feature, so you don’t have to do it manually like long ago, and don’t have to use “WordPress Automatic Upgrade” plugin. Its nice and very cool feature to keep up-to-date and stay protected. But a lot people face problem to make it work. It fails to work as expected if there is file permission issue or something like file system issue. Now as WordPress 3.1 Released with a lot update, everybody should update to latest. Those who has Update error here I will talk about a simple solution.
This is a very common Error if you have a big site in WordPress. Mostly site with huge post count suffers in this error. It could occur while posting new or editing any existing post. I also had this error while creating large sitemap, doing some batch function. You will see any empty screen with the message below –
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 80 bytes) in /home/*****/public_html/wp-includes/wp-db.php on line 958
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 80 bytes) in /home/*****/public_html/wp-includes/wp-setting.php on line 958
It occurs as WordPress tries to access more memory then its allowed to by “Server PHP configuration” or “WordPress Setting”. Increasing Memory will solve it. Here is solution for all user, who have shared hosting or dedicated or VPS, just FTP access to server will be enough.
Here is Solutions: Read more…