Checking dependencies of packages
CONNECT ERROR: Package 'Interface_Frontend_Default_Blank' is invalid
'./app/design/frontend/default/blank/etc/widget.xml' already exists
February 24, 2014
Works Great on 1.8
Hi, I thought this was the yoast blank seo extension at first, not enough coffee yet :) I was going to say wow the top menu displays and everything!! Anyways, the one problem I ran into was during the install it gave me an error about /app/design/frontend/default/blank/etc/widget.xml already exists.... which makes sense since this theme is included with the install....anyone looking to install first rename these folders
to something else (blank_orig) or something.
Then in the admin go to system > configuration > design > Theme
And fill in blank as your theme in all the textboxes.
This theme is nice for starting from scratch and creating custom designs
November 14, 2013
It takes out the default styles and lets you implement your design.
June 11, 2013
This theme did not installed using "Magento Connect Manager ver. 188.8.131.52 " ,giving error "community/Interface_Frontend_Default_Blank:
Couldn't resolve host 'connect20.magentocommerce.com'";
I really feel bad its on magento official website and not working according the instruction mentioned in manual.
so is there any other way to install this.
advance thanks for any suggestion.
March 30, 2013
Installing this theme destroyed fresh install on 184.108.40.206. DONT USE!
November 3, 2012
After installation my magento went down, solution:
February 22, 2012
Found out the fix thanks to timmy3205396! If you've installed it and gotten the error, it means it hasn't left Maintenance mode. Just delete maintenance.flag from the root directory and it'll be back up. When installing the package from Magento Connect, ensure that the option to put maintenance mode is unchecked.
December 29, 2011
I believe that the blank theme some by default with every CE install now:
December 19, 2011
Brought my install down. Luckily just developing. Won't install again.
December 11, 2011
Tried installing it on a 220.127.116.11...destroyed the installation (503 for both front- and backend) because it wasnt compatible with the Core Package files...wasnt able to uninstall this or reinstall the core package files so I had to set up a new installation (luckily i was at the very beginning of this project)...it would be so much easier to be able to download the theme in a zip file and deploy it manually...
December 6, 2011