A.R. Van Halleorg

There’s a good chance that you’ve probably seen this before and weren’t able to come up with a solution and ripped your hair out trying to get it and maybe that’s what you were about to do before you stumbled on this. I was shown this by a coworker this morning and I decided to add it to my ever growing list of reasons why IE6/IE7 reminds me of a mother-in-law with it’s horrific ability to nag for details. (Not my case, my mother-in-law doesn’t care about anything)

So! Actually there are 2 things I’ve seen that work :

1. Remove the margin-top from the element (especially things like headers and put padding or line-height instead)

2. (from coworker) set your element to have vertical-align:top and suddenly it disappears!

Hope that helped someone. If not, well I guess I’ll keep looking.

Isn’t this an annoying bug? Just when you think your troubles are over and you’ve got the file all figured out, it goes and denies you the video portion of your video.

This really isn’t Viper’s fault, but one parameter in particular seems to have a problem with a lot of MOV files.

So go into the plugin’s file and find the following bit of code:

Then comment it out :

Save and then refresh your blog page and see if it shows your video now.

If so, YAY.

If not, I’m sorry, it’s all I found.

Hope it helps!

I was messing around with this yesterday. I was trying to get the javascript loaded by colorbox to fire when it showed on the screen. I wanted a default width to something and provide the default result in another box at the same time.
If you’re using jQuery, which is what I was using, don’t bother trying to make it work with your CSS style call for the element to capture the click/key events. Put it directly into the click=”" onkeyup=”" etc. Sounds lame, and it is, but that’s the easiest way to do it. You can still keep the functions you made (just call them). You can still call it like $(“#element”).val(‘value’). It just avoids the lack of event capture issue.
If you have another tip, add it to the comments of this post! I’d certainly like another workaround!

I’ve had this issue coming up in searches for my site, so I thought I would address it. In my older version of the NFB Video Plugin, the Simple HTML Dom is incapable of opening a ‘huge’ file when you are on a host online due to their default memory in PHP. Mainly this is an issue where Vimeo has too many comments on their page to be able to read for the missing information. In any case, this error shows up all over the web, so here is what you do to fix it!

ERROR MESSAGE : Fatal error: Allowed memory size of…

There are 2 easy solutions for it.

1) If you have access to the php.ini file, you can change it to:
memory_limit = 30M ;

2) If you don’t have access to the php.ini there is still hope! You can modify it in the PHP code itself, it returns to normal when the script stops running.

<? ini_set(‘memory_limit’, ’64M’); ?>

(I’ve found this works for me on Servage)

Hope this helps you guys!