October 29th, 2009 | Hosting, Magento, Magento Hosting
We've installed Magento commerce platform on many shared hosting servers and they have all suffered. We've found the fastest, most reliable magento hosting is Simple Helix. They offer a $20 a month premium bandwidth and fast server speeds, which is great for anything but especially awesome for Magento's cart software. This compared to a $100+ a month dedicated server is a bargain especially for start up magento system and new ecommerce stores. Simple Helix also offers a magento one-click install which is great for our fellow developers! Go Simple Helix for your next magento commerce client.
Ping Statistics from San Diego
--- www.simplehelix.com ping statistics ---
34 packets transmitted, 34 packets received, 0% packet loss
round-trip min/avg/max/stddev = 70.182/73.322/83.744/2.919 ms
Ping Statistics from Atlanta
--- www.simplehelix.com ping statistics ---
60 packets transmitted, 60 received, 0% packet loss, time 59003ms
rtt min/avg/max/mdev = 32.001/34.268/40.002/2.122 ms
September 18th, 2009 | Web Development
To access an object in PHP you use a pointer. For example when using Browscap (http://code.google.com/p/phpbrowscap/) extract the values like so
$current_browser->Parent;
September 1st, 2009 | How to, iPhone Development
Below is the code to call a number within a function.
NSURL *phoneNumberURL
= [NSURL URLWithString
:@"tel:3053729787"];
[[UIApplication sharedApplication
] openURL
:phoneNumberURL
];
I've tested this call function on both the iphone and ipod. The iphone opens a UIAlert and prompts the user to call or cancel. The ipod ignores the call without causing a crash (same as the simulator)
August 31st, 2009 | XCode, iPhone Apps, iPhone Development
To have a UILabel print out a price float with 2 decimal places you'll want to cast a string with to except a float with 2 decimal places.
myFloatLabel.text
= [NSString stringWithFormat
:@"$%3.2f",
[self.floatValue floatValue
]];
August 31st, 2009 | CSS, Debugging, Web Development, ie6
A Frequent Problem with ie6: The bottom of the text (e.g. g y p) get cut off and make text illegible. This mostly happens with two line breaks and can be fixed by using a larger line-height in css.
To fix the problem we are going to create a class using the internet explorer 6 box hack.
We need to locate the exact area that we are having the problem with. For me the text was being cut off at .description h4 a
* HTML .description h4 a {
line-height: 1.2em;
}
To fix the text cut off issue without the box hack just simply created a css class and adjsut the line-height
p { line-height: 1.2em; }
August 29th, 2009 | XCode, iPhone Apps, iPhone Development
After updating the iPhone in iTunes to Software OS 3.0.1 I was unable to access it through the xcode organizer. After reinstalling the newest xocde (failed) and some digging I found a line of code you need to copy and paste into your terminal once, restart xcode, and you have access to pushing onto the iphone again.
Open up Terminal, copy below, paste and enter into terminal, restart xcode.
ln -s /Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.0\ \(7A341\) /Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.0.1
August 28th, 2009 | CoreData, Debugging, iPhone Apps, iPhone Development
One of my CoreData applications started acting buggy, and was spitting out a huge error dump on app close in the debug console. The errors spitting out didn't tell me anything but CoreData Error 1560 and 1570. Upon inspection I found on google that another layer of errors is stored in the CoreData foundation. On Stack OverFlow found a very useful function but re-wrote it because
![[survey managedObjectContext] save:&error]
was causing an error.
Add this into you applicationWillTerminate function in your Application Delegate
/**
applicationWillTerminate: saves changes in the application's managed object context before the application terminates.
*/
- (void)applicationWillTerminate:(UIApplication *)application {
NSError* error;
if(![[self managedObjectContext] save:&error]) {
NSLog(@"Failed to save to data store: %@", [error localizedDescription]);
NSArray* detailedErrors = [[error userInfo] objectForKey:NSDetailedErrorsKey];
if(detailedErrors != nil && [detailedErrors count] > 0) {
for(NSError* detailedError in detailedErrors) {
NSLog(@" DetailedError: %@", [detailedError userInfo]);
}
}
else {
NSLog(@" %@", [error userInfo]);
}
}
}
The original post can be found here
The cause of Error in my CoreData Application was an Attribute in my xcdatamodel file. An optional field was checked as indexed and not optional. The simple action of unchecking indexed and checking optional fixed a whole mass of errors.
