documentHtml Helper is not parsing the scripts correctly

Please share your problem in details will try to resolve.

Thanks manishkrag.

I’ll try to be specific here.

When I activate the free version of the plugin, everything works great.
After I deactivate the free one and enable the Pro version, the site breaks showing the following text in the screen:

News – My Site
window._wpemojiSettings = {"baseUrl":"https:\/\/s.w.org\/images\/core\/emoji\/72x72\/","ext":".png","source":
{"concatemoji":"http:\/\/localhost:8888\/wp-includes\/js\/wp-emoji-release.min.js?
ver=4.4.2"}}; !function(a,b,c){function d(a) ... a lot of stuff here ...

which is part of WordPress, but got broken because of a failure.

I can see the following error in the console:

Uncaught TypeError: Cannot read property 'top' of undefined

The portion of the js code that is running is this:

} else if ( 1 == aws_data['transitionfade'] ) {
	$content.fadeToggle('slow', function() {
	$('.aws-overlay').remove();
	$content.html(contentHtml).fadeToggle('slow', function() {
           load_inbuilt_script_file(rootUrl);
           load_extra_script_file(rootUrl);
           if ( '' != $('#ajax-search a').attr( 'href')) {
	      jQuery('html, body').animate({
		  scrollTop: jQuery(jQuery('#ajax-search a').attr( 'href')).offset().top
              }, 2000);
	   }
       });
     });
  }

Lines 160 – 173, AWS Pro version 1.5

The line with problem is this one:

scrollTop: jQuery(jQuery('#ajax-search a').attr( 'href')).offset().top

I may say that I don’t have the search field in my site, so no ‘#ajax-search’ exist in the dom.

Hope this may give you some clues.

If you think you need to see the entire code, or to make some test or investigate with my site, just let me know, I can give you access.

Thanks for any help in advance.

Hi manishkrag

After 9 months, this issue came back to me, I continued using the free version of the plugin since the pro version was giving me this issue.

By looking at the code, I realized that settings are not compatible between the free and pro version.

What was causing the issue is that the pro version expects the ajaxify container to be either a class or an ID, so you, the user, need to specify that in the selector (prefix # or . respectively), which is not the case for the free version.

So this reported issue is not a reail issue, thanks for your time!

Please mark this as resolved.

• This reply was modified 8 years ago by mariodlg. Reason: typos