[resolved] wp_get_archives and "postbypost" argument limited to only 400 posts ? (5 posts)

  1. Kowalsky
    Posted 6 years ago #

    Hello all,

    as many of you I am running a dedicated monthly archives page on my site (http://www.bassanese.org/archives/). But I do also have a postbypost archive page (http://www.bassanese.org/plan/) wich I basicaly use as a WCAG "site map" and have lately noticed an issue with it.

    Before I reached circa 400 posts on my site, I had no problem with it, everything was displaying correctly. But after, the page didn't showed entirely : it only displayed the code before the loop "wp_get_archives".

    In order to have it working again, I had to set a limit of 402. (while 403 will reproduce the issue)

    My current code (full display is ok) :
    <?php wp_get_archives('type=postbypost&limit=402&format=custom&after=<br />'); ?>

    Previous code (partial display stops before the loop) :
    <?php wp_get_archives('type=postbypost&format=custom&after=<br />'); ?>

    Of course, it is working now, but I would like to have the full list displayed, not a limited one.

    I have reviewed codex and support but found nothing related with my issue.

    Any idea on what's happening ?

  2. MichaelH
    Posted 6 years ago #

    Maybe it's a bug.

    What happens if you change type=postbypost to type=alpha? Posts will be ordered by post title but do you get them all?

  3. Kowalsky
    Posted 6 years ago #

    Hello MichaelH,

    same issue with <?php wp_get_archives('type=alpha'); ?>

    If I add the 402 limit, I have indeed the alphabetic list.

  4. MichaelH
    Posted 6 years ago #

    Well if you've deactivated all plugins and can still reproduce the problem, then you might consider reporting that as a bug to Trac.

  5. Kowalsky
    Posted 6 years ago #

    Good catch MichaelH !

    Forgot about the plugins thingy.

    Deactivated all of them and was not able to reproduce the issue.

    So did activated them one by one and found out that "ImageManager" was the root cause.

    Checked on author site and noticed that plugin support was stopped at WordPress 2.5.


    Case solved.

Topic Closed

This topic has been closed to new replies.

About this Topic