• Resolved mpserellis

    (@mpserellis)


    Hello,

    Please could you check what appears to me as a bug. To replicate the bug you will need many products to make at least 2 pages. Without filtering change to page 2. Now using the filter choose options will result in only 1 page of products. Because we are on page 2 when we click filter (ajax enabled) we now get a 404 Not Found page.

    I have been looking at the front.js javascript and can see that in most places just before calling woof_submit_link(woof_get_submit_link()) you reset woof_ajax_page_num back to 1. However, the click event of the filter button doesn’t do that:

    Version 1.2.2.1
    lines 412 – 421:

        jQuery('.woof_submit_search_form').click(function () {
    
    	if (woof_ajax_redraw) {
    	    woof_ajax_redraw = 0;
    	    woof_is_ajax = 0;
    	}
    	//***
    	woof_submit_link(woof_get_submit_link());
    	return false;
        });

    I think therefore the filter is applied to page 2 and when there are not enough products returned by the filter to make up 2 pages we get not found error. Please let me know if you need any more information.

    Thank you
    Mark

Viewing 16 replies (of 16 total)
Viewing 16 replies (of 16 total)
  • The topic ‘Possible bug causes 404 Not Found page’ is closed to new replies.