ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Error with Discussion Forum Threads "Next" and Forum Search Results "Next"

May 04, 2011 8:37pm

Subscribe [2]
  • #1 / May 04, 2011 8:37pm

    Robert.S

    67 posts

    This seems to have recently appeared, though no changes to my EE install recently, hoping you can help me troubleshoot!

    Version 2.1.3 Build 20101220

    Discussion Forum 3.1.2

    See issue by:

    Go to http://www.hotyogadoctor.com/index.php/site/forum/

    Search for “knee” (multiple page results)

    Click “Next” (or any subsequent page number, or “last”)

    You will see the message:

    “Search Results:

    Your search did not return any results.”

    Issue is also showing in normal pagination in forum threads:

    Go to: http://www.hotyogadoctor.com/index.php/site/forum/viewthread/143/

    Try selecting “Next” or any other paginated link.

    You will see an error:

    “You are not authorized to perform this action”

    So it seems as if I have some issue with pagination.

    I have cleared the EE cache and restarted my server.

    The Forum search templates have not been modified since last upgrade Jan 7, 2011.

    Any ideas where I should look first?

    Thanks!

    Robert

  • #2 / May 04, 2011 8:45pm

    Robert.S

    67 posts

    I can partially “fix” the issue after lookign at the urls on the EE forum.

    My install is adding a “&per;_page=” into the url, eg:

    http://www.hotyogadoctor.com/index.php/site/forum/search_results/d6bce91a3a290736fbdd8543eed4ceb1/&per_page=P20

    If I remove that “&per;_page=” part of the string, and manually paste the url, then the result shows as expected.

    I wonder what would be introducing this seemingly all of a sudden?

    Tnx

    Robert

    (Will post an answer if I find one!)

  • #3 / May 04, 2011 10:28pm

    Robert.S

    67 posts

    I fixed it for now - it seems we’ve been working on some string queries in a custom module and had modified config.php:

    $config[‘enable_query_strings’] = FALSE;

    to be

    $config[‘enable_query_strings’] = TRUE;

    Once I changed it back to

    $config[‘enable_query_strings’] = FALSE;

    Then the error goes away.

    Looks like if we still need to allow query strings, we’ll need to add in some replacement code to strip out that &per;_page= in the url.

    Thanks for reading!

    Robert

  • #4 / May 05, 2011 1:23pm

    Sue Crocker

    26054 posts

    Robert, gorgeous design! Looks like things are working again, I was able to get through two additional pages (just tried those two.) Feel free to start a new thread if you have any more questions.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases