As yj589794 suggested, I calmed down a little and want to excuse myself. I was a little pissed off by the fact that it seems as you only copy/pasted the suggested solutions and then head back to the board to post the same or the next error.
*sigh*
I'm always willing to help people, but I think I can help you best with pointing you in the right directions, so you can solve your problems yourself. This makes you better, since you learn something about coding this stuff.
I was a bit harsh, though.
Let me detail my "hints" a bit more:
In the API-documentation on WoWWiki you can find nearly every function, that haste has used to create oUF. If something is not working in your layout, you have to find the error. As I stated before, the error-messages are quite useful for this. You must identify in which oUF-module (element) this error occurs. Then just open that file and read through the oUF-code. You will see, which WoW-API-functions haste is using, you can look them up and with little thinking you can understand, what is causing the trouble in your layout. Try this and that, fix it!
Most oUF-stuff is fairly simple, some parts are more difficult.
In 1.4 haste has established a straight forward type of modules (elements): They have an activation (Enable), a deactivation (Disable) and some sort on Update-function.
Look at the Enable-functions. You will notice, what is necessary to make this module work. If your layout fullfills these needs, step over to the Update-function. Have a look on how the Update is done.
Additionally, haste supports various Override-functions in his modules (elements). Most of them are called SOMEPreUpdate() and SOMEPostUpdate(). These are spots, where you can change some of the oUFs behaviour (to be complete: You may override the core Update aswell on some (most) modules).
While modifying your layout, you will encounter, that jasje has used this "hooks" sometimes, latest example would be your health-bar / -text.