Bug? Debug.log error message

Ross Moderator

#11364

Did you manage to test it? 🙂

Anonymous

#11473

Hi Ross,

Sorry for the delay in responding; I had a migraine yesterday and have been catching up with my backlog 😉 Thank you for the update. I uninstalled the old version and installed 1.4. It seems to work ok, and the previous error has disappeared, except that a search now returns results in a page devoid of all stylesheets rendering it text only without layout and formatting. The header and footer have been omitted. Presumably this can be fixed easily?

Ross Moderator

#11474

Hi Laura

If you switch back what happens? I imagine the same thing as this update barely changes a thing – I think you have just discovered a new problem in your site.

Are you using shortcode to display results? (under the display results tab)?

I’m guessing you are also using Ajax to display results?

If so, then there is a JS error on your page, JS errors on your page will interfere with the ajax request and instead of loading the results on the page, it will redirect the user to the ajax url (which as you mentioned is devoid of headers/footers etc – it should only be the results – used for the ajax request).

Thanks

Anonymous

#11478

You’re right; switching back throws up the original error in debug.log *and* a results page devoid of stylesheets. SFP has been added via a widget sidebar, and was displaying results in the homepage main content section until now when it loads a CSS-free admin-ajax.php?action=get_results page. I haven’t inserted any additional ajax/js – it just uses what came with the ClassifiedEngine theme. I’ll check for js errors, but they aren’t showing up in the log – should they feature there?

Ross Moderator

#11482

Hey Laura

Essentially then what caused this latest issue is another change in your setup – that wasn’t upgrading the plugin.

To check for JavaScript errors you need to use something like firebug, and check the javascript console there – backtracking the changes you have recently made is probably the easiest option – for example installing other plugins.

Thanks

Anonymous

#11483

JS errors on homepage from a FF web dev extension:

SFP v1.3:

Timestamp: 04/02/2015 15:26:27
Error: TypeError: $field.attr(…) is undefined
Source File: http://localhost/horsehawkv2/wp-content/plugins/search-filter-pro/public/assets/js/search-filter-build.js?ver=1.3.0
Line: 472

Timestamp: 04/02/2015 15:27:10
Error: TypeError: document.getElementById(…) is null
Source File: chrome://web-developer/content/overlay/javascript/overlay.js
Line: 7333

With SFP 1.4:

Timestamp: 04/02/2015 15:29:34
Error: TypeError: $field.attr(…) is undefined
Source File: http://localhost/horsehawkv2/wp-content/plugins/search-filter-pro/public/assets/js/search-filter-build.js?ver=1.4.0
Line: 558

I’m afraid it’s referencing the SFP plugin, not the theme… If I should be looking elsewhere too, let me know.

Ross Moderator

#11486

You’re right Laura however I’m confused, if it was working before on 1.3 why would it stop working when reverting back to 1.3?

Was there anything you did that you can recall?

I’m afraid I’d have to see your setup to be able help further as I can’t recreate this issue. S&F 1.3 did have an issue like this but 1.4 resolved it for any users that had reported it.

Can you get a temp staging/demo link so I can see the problem in action?

Thanks

Anonymous

#11540

“I’m confused, if it was working before on 1.3 why would it stop working when reverting back to 1.3?”

Yes, that had occurred to me too! I can’t think of anything I did, as I literally performed the actions in succession. I have deactivated non-essential plugins to rule them out and made functions.php blank; still the issue persists. I’ll send you details of a testing server.

Anonymous

#11541

This reply has been marked as private.

Anonymous

#11582

This reply has been marked as private.

[Author]

Posts