21–30 of 114 posts
Regardless of how the contract was worded or the outcome of your relationship, requesting a chargeback on PayPal as your first option is really underhanded.
And not filing a complaint wasn't really an option. They have no recourse if they don't file a complaint within some short period of time.
A backend PHP framework causing browser incompatibility issues. Eh? Edit: To reply to the naysayers in one fell-swoop - unless CakePHP is identifying the browser from the request header and sending different templates/CSS accordingly (which sounds unlikely, and like a bad idea to me), there's no way for the framework to introduce cross-browser compatibility issues. Obviously the developer could create issues in the C…
Or is this just you trying to get some PR cred by saying that it was buggy/not properly done/blah blah because a bunch of people (which could be entirely made up) said so?
And in my professional opinion (no offense to the CakePHP developers) but CakePHP is about as opinionated as you get with PHP frameworks, it's almost impossible to "use it wrongly". So sorry but that sounds like a load of crock.
> Everyone who evaluated the code said the same thing, to sum it up (in their professorial opinion) the framework was not utilized correctly which resulted in the numerous bugs and browser incompatibility issues. How using PHP framework may result in browser incompatibility issues? Whole processing happens in the server side for PHP, not in browser...
I believe Cake is like Rails in that it puts out JavaScript code automatically for AJAXing things.
A backend PHP framework causing browser incompatibility issues. Eh? Edit: To reply to the naysayers in one fell-swoop - unless CakePHP is identifying the browser from the request header and sending different templates/CSS accordingly (which sounds unlikely, and like a bad idea to me), there's no way for the framework to introduce cross-browser compatibility issues. Obviously the developer could create issues in the C…
I think you're going to have a hard time here trying to convince a developer community that a "refund" is something a client is entitled to in a work for hire situation. You ask a developer to do work for you, they do the requested work, and you pay them. If you don't like the work, you end the relationship. But you still have to pay them for their time. I don't envy the next few weeks for you guys, but you definitel…
Worse is that you did a 'chargeback' on paypal which is a dirty tactic. Considering how awful Paypal's dispute process can be.
I think you're going to have a hard time here trying to convince a developer community that a "refund" is something a client is entitled to in a work for hire situation. You ask a developer to do work for you, they do the requested work, and you pay them. If you don't like the work, you end the relationship. But you still have to pay them for their time. I don't envy the next few weeks for you guys, but you definitel…
Depends what the contract is for. If it's for "programming", then you have to pay, no matter what program you receive. However, if it's for "complete and functional product", then unless they produce that, you don't need to pay. Like in a restaurant, if you order pizza, and get steak, why would you pay?