Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7499035
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 29, 20262026-05-29T19:40:42+00:00 2026-05-29T19:40:42+00:00

Trying to track down an bad image replacement error. An image of a different

  • 0

Trying to track down an bad image replacement error. An image of a different size pops in the original img source.

Unfortunately, on my PC, regardless of browser (Firefox, chrome, safari) the error is ‘silent’ and doesn’t cause the problem.

However, tracking it with firebug and chrome tools, seems to show that it is because of a ‘Node was not found’ error in Firefox (chrome: “NOT_FOUND_ERR: DOM Exception 8” )

This should be all standard code from jigoshop, a WordPress plug-in. It could be because whoever put the images in the first place, didn’t understand the relationship of the image sizes.

In any case, it is breaking here:

document.body.removeChild(this.node);

About 13 lines down here (line 653 in jquery.jqzoom-core.js)

this.fetchdata = function () {
var image = $(this.node);
var scale = {};
this.node.style.display = 'block';
$obj.w = image.width();
$obj.h = image.height();
$obj.pos = image.offset();
$obj.pos.l = image.offset().left;
$obj.pos.t = image.offset().top;
$obj.pos.r = $obj.w + $obj.pos.l;
$obj.pos.b = $obj.h + $obj.pos.t;
scale.x = ($obj.w / smallimage.w);
scale.y = ($obj.h / smallimage.h);
el.scale = scale;
document.body.removeChild(this.node);
$('.zoomWrapperImage', el).empty().append(this.node);
//setting lens dimensions;
lens.setdimensions();
};

the node it can’t find is: , which is found after loaded html here:

<div class="zoomWrapperImage" style="width: 100%; height: 496px;">
<img style="position: absolute; border: 0px none; display: block; left: -5000px; top: 0px;" src="http://xyz.com/shop/wp-content/uploads/2011/10/go-291x496.jpg">consoleName="jQuery.data"consoleKind="Element"consoleFramework="jQueryUI-1"consoleId="73"
</div>

I have delved into jquery too much. So, 2 questions:

  1. How to fix this exact problem?
  2. What is a general process of fixing these type of errors?
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-29T19:40:45+00:00Added an answer on May 29, 2026 at 7:40 pm

    I’ve found a workaround. I wouldn’t call it a correct solution, though. The workaround is:

    1. Add the following to the top of jquery.zqzoom.core.js (function found from some forgotten source):

      function isInDocument(el) {
      var html = document.body.parentNode;
      while (el) {
      if (el === html) {
      return true;
      }
      el = el.parentNode;
      }
      return false;
      }

    2. at line 665, just before:

      document.body.removeChild(this.node);

    add this:

    if(isInDocument(this.node))
    

    This will stop the exception from happening and allow the script to continue.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm currently trying to track down the source of some lazy loading calls in
I've spent about three weeks on trying to track down this error, so forgive
Trying to track down a LNK2019 Unresolved External Symbol error on a function that
Trying to track down this error I get when I have NSZombieEnabled . I
I'm trying to track down who is making an allocation of a certain size,
I'm trying to track down an 0x8badf00d error which is caused by the watchdog
I'm having a hard time trying to track down an error. I'm using a
I'm trying to track down an issue in our system and the following code
We're trying to track down some .Net assembly dependency problems. On Windows XP, does
I'm trying to track down a memory leak and I think it has to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.