• Resolved Serena Zehlius

    (@thezanyprogressive)


    I installed the plugin—Thank you! I also added the code provided to remove posts from the admin ALL list. I’m not a coder by any means. I used SFTP to get to the mu-plugins folder, created a blank php file and added your code to it. However, I did the same thing with code from my hosting provider and it showed up in different colors as Im used to seeing when viewing PHP code. Your code was all in white. I added <?php to the line above it, but still looks the same. Is that how it should look?

    My broken link checker also filled up with links from posts I archived, Im guessing because the scanner doesn’t have access to read private posts? Google bot will have the same problem I guess? I’m talking to the plugin devs to help me add code as a workaround, I’m just curious about search engine bots.

    Thank you!

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Joshua David Nelson

    (@joshuadnelson)

    Hey Serena!

    Apologies for my delayed response, only just now seeing your message for some reason.

    If you archive content it will no longer be public, so any links to that content will result in a 404. I would recommend either creating redirects (through your host, or a plugin) or removing the old links.

    Alternatively, if you want archived content to be publicly viewable, you can add these filters to your functions.php file or plugin:

    add_filter( 'aps_status_arg_public', '__return_true' );
    add_filter( 'aps_status_arg_private', '__return_false' );
    add_filter( 'aps_status_arg_exclude_from_search', '__return_false' );

    As for the php coloring, that will be specific to the tool you’re using to view the code. It sounds like you have it working?

    Plugin Author Joshua David Nelson

    (@joshuadnelson)

    Hey there, just checking in to see if you needed any further help or if the proposed solution worked for you?

    Plugin Author Joshua David Nelson

    (@joshuadnelson)

    I’m closing this issue due to inactivity, but if you need further help please reach out!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.