MAMP, a local webserver environment for the Mac, is perfect for testing, developing and designing with WordPress. MAMP comes with a ready to use configuration of Apache, MySQL and PHP in a single folder.
But after installing and configuring a WordPress blog, you may loose the access to the MAMP start page:
Forbidden
You don’t have permission to access /MAMP/ on this server.
Apache/2.0.63 (Unix) PHP/5.2.11 DAV/2 Server at localhost Port XXXX
That’s a big issue, as the start page links to the local phpMyAdmin page for MySQL-database configuration. So you cannot admin the database anymore.
I traced down the problem to a wrong placed file: When I configured the WordPress installation via the web-interface, an .htaccess file was placed in the root directory of my harddrive. Quite scary … but a problem which can be fixed easily
As always: no guarantee and on your own risk … especially the Terminal is a wonderful tool … but if you do the wrong thing, you may be in serious trouble!
You normally do not recognize the .htaccess file within the Finder: all filenames starting with a dot are hidden files in a UNIX system … and the Finder does not show those hidden files. But if you use the Terminal, you can look at all the hidden files easily.
So fire up the Terminal app and go to the root directory of your hard drive:
cd / |
then looks at all the files in your root directory:
ls -la |
If you find a .htaccess there … you probably found your problem. But look inside the file before your rename or delete it:
cat .htaccess |
The easiest way to proceed is to rename the htaccess file:
mv .htaccess htaccess-backup |
This way the file is shown in the Finder again and does not confuse your MAMP installation. If you know what to do you can delete the renamed file now within the Finder and drag it to the trash
Adobe announced the export capability from Adobe Flash Professional CS5 to built native iPhone apps. This is the next round in the battle for market shares in the field of mobile application platforms.
Adobe tried to position Flash with their shrinked down Flash Light as a global OS independent application development platform for mobile devices. Today more than 800 million mobile devices are Flash Light enabled. It looked like they found the philosopher’s stone – but when you dig deeper, Adobe is facing a lot of issues:
But on March 6, 2008 an other threat to Flash and Flash Light appeared: Steve Jobs introduced the iPhone SDK which provided a easy way to create third party applications for the iPhone with high mobile performance and the ability to take advantage of most of the sensors – like touchsceen, accelerometer, microphone, camera. And Apple solved one of the biggest hurdles for mobile application developers: They provided an easy application store solution for the developers to sell their apps or distribute them for free. And also the market for these native iPhone applications is quite attractive: There are more than 50 million iPhones and iPod touch devices out there – all of them having the exact same screen size, all of them having a touch sceen, all of them having an accelerometer. Apple attracted a lot of independent developers as well the big names in game industry with their mobile application ecosystem.
Bringing Flash support to the iPhone Safari web browser was blocked by Apple because of those big performance issues. Apple also did not license Flash Light for the iPhone – quite logic because they built up their own developer base and their own mobile app ecosystem.
The only chance Adobe had was to built up an “injection”-strategy and develop their Flash authoring tool into an Objective-C & Cocoa code generator which allows Flash developers to create native iPhone applications by the press of a button. Then the Flash developers can upload their app to the iTunes AppStore and use it as a selling and distribution channel.
This probably wasn’t an easy job and it will be quite interesting to watch Apple’s reaction on this move. It probably will have a massive effect on the AppStore as this will flood the store with new apps: More creativity and more junk.
Louis Gerbarge spotted the technical issues of the Adobe Flash to native iPhone code generation – and takes a look on the performance and private API issues of the beta version of the CS5 solution. His post makes clear that taking the Flash way won’t offer the Flash developers the features and beauty of the uncountable iPhone SDK 3.x APIs.
Some days ago I published a first solution for reactivating printing on OKI-printers from Mac OS X 10.6 Snow Leopard … some of you managed it to reactivate the printer by following the instructions – others are still coping with that problem. Also I was disappointed to see that the solution broke again and I wasn’t able to print from Snow Leopard again. That was really annoying – so I spent some time again to find a proper solution. Here it is: Version 2 of how to solve the problem … and as always: no guarantee and on your own risk:
Problem: After updating from Mac OS X 10.5 Leopard to OSX 10.6 Snow Leopard the installed printer driver for the OKI-postscript driver does not work anymore. Here it’s an OKI MFP C5540 … but it should also work with other models, like the OKI C5450 or C8800. The printer diver was installed under Leopard and worked quite well. After finishing the update to 10.6 you are able to send a print job to the printer, but an error message shows up in the print queue.
Diagnosis: Two bugs may cause the problem: Some of the OKI-printer drivers just disregard case sensitivity in their path names – this wasn’t a problem in former Mac OS X versions – but it is a problem in Snow Leopard. The other bug – which even leads to a malfunction if the path names are right – is some wrong file permissions. And this causes Snow Leopard to hiccup when you try to print on an OKI-Printer.
Solution: The easiest way to solve the problems and get rid of the bugs is following three major steps:
You only need the OKI printer drivers and you have to put in some Terminal commands. But let’s do it step by step:
Macintosh HD/Library/Printers/ |
sudo chown -R root:admin /Library/Printers/OKIDATA |
sudo chmod 775 /Library/Printers/OKIDATA/Filters/OKfilterA |
On Sep 9th 2009 at 9am PST Apple invited selected journalists to a special event in San Francisco. Apple did not bring up the Rolling Stones with Mick Jagger on stage of the Yerba Buena Center for the Arts Theater … but their song “It’s only Rock’n Roll (But I like it)” from 1974 was the intro of the event ![]()
Steve Jobs showed up on stage the first time since his liver transplantation and got a very warm welcome. Great to see, that he is doing better, now. He and Phil Schiller shared a lot of news and innovations:
Video-on-demand Quicktime-Stream of the Apple Special Event September 2009
Here are the facts of the 75min event:
Sales figures:
iTunes & iPhone OS update:
Sneak previews of new games:
Update of the iPod product line:
Printer drivers under Mac OS 10.6 Snow Leopard are still sometimes causing trouble. After explaining how to reactivate an OKI-printer – here is the solution for an Kyocera-Mita-printer … and as always: no guarantee and on your own risk:
Problem: After updating from Mac OS X 10.5 Leopard to OSX 10.6 Snow Leopard the installed printer driver for the Kyocera-postscript driver does not work anymore. Here it’s an Kyocera Mita FS-2000D … but it should also work with other models. The printer diver was installed under Leopard and worked quite well. After finishing the update to 10.6 you are able to send a print job to the printer, but an error message shows up in the print queue.
Diagnosis:There are incorrect file permissions under Snow Leopard fort he Kyocera printer driver … and this causes some trouble. BTW a warm thank you to @kappuchino for his diagnosis and solution!
Solution:There is nothing like fixing the bug yourself
You can easily fix the problem by one command in the Terminal:
sudo chown root:wheel /usr/libexec/cups/filter/kyofilter |