• paulrichardsonmadwire

    (@paulrichardsonmadwire)


    When I click on “Store Locator” in the backend of WordPress, it tries to load this page “https://pellearning.com/wp-admin/edit.php?post_type=wpsl_stores” but it says it does not exist.

    It won’t let me see “All Stores”, “Settings” or “add-ons”, but it will let me see “Add New Store” and “Store Categories”.

    I am simply trying to update information about one of our locations.

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • farroyo

    (@farroyob)

    Hi, thanks for writing.

    It sounds like your WordPress Permalink rules or user capabilities for the plugin have glitched. Here are the quick fixes to get those menus back:

    Flush Permalinks: Go to Settings > Permalinks in your WordPress dashboard and simply click “Save Changes” at the bottom (you don’t need to change any settings). This usually forces WordPress to recognize the plugin’s URLs again.

    User Role Check: If you can see “Add New” but not “All Stores,” your user role might have lost specific permissions. Check if you have an SEO or Security plugin that might be restricting access to certain post types.

    Let us know how that goes.
    Best regards,

    Thread Starter paulrichardsonmadwire

    (@paulrichardsonmadwire)

    Thanks for your quick response. I flushed the Permalinks with no success as the link is still not working when I click on “Store Locator” along the left side.

    I am able to see both “Add New Store” and also “All Stores” along the left side. The Add New Store link works, but not the All Stores. https://madshot.net/8cb46725deaa.png

    Hi @paulrichardsonmadwire,

    Thanks for the update and the screenshot. Since flushing permalinks didn’t work and the menu items are visible but lead to a ‘not found’ page, we can rule out standard URL routing issues. This points to a conflict during the Custom Post Type registration in the backend.

    Please try the following steps to narrow it down:

    Check for Plugin Conflicts: Temporarily disable any plugin that manages Custom Post Types (like ‘CPT UI’) or any Security/Role Manager plugins. Then, check if the ‘All Stores’ page loads.

    Theme Test: Switch to a default WordPress theme (like Twenty Twenty-Four) for a moment. If the link works, the issue is a function within your theme’s functions.php interfering with the wpsl_stores post type.

    Direct Access Test: Try to access the list by manually entering this URL (replacing your domain): https://pellearning.com/wp-admin/edit.php?post_type=wpsl_stores&post_status=all. Sometimes the default view is what’s broken.

    If none of this works, could you check if you have any custom code in your functions.php that uses the register_post_type_args filter?

    Thread Starter paulrichardsonmadwire

    (@paulrichardsonmadwire)

    Check for Plugin Conflicts: disabled all plugins. Still recieved a 404 error. Not a plugin conflict.

    Theme Test: Switched to the 2025 theme, no change. not a theme conflict.

    Direct Access Test: attempted direct access, still results in the same 404 page.

    functions.php not modified from other installations of the theme, including instances that are running store locator. 

    The only thing i can think of is maybe there is something going on with their host that is blocking this specific call. They aren’t on our hosting and that, at this point is the only difference from the one I’m seeing that is working since we can rule out theme and plugin conflicts.

    Hi Paul,

    Thanks for the thorough testing. Since you’ve ruled out plugins and themes, this is definitely an unusual case.

    You might be right about the hosting/server environment. Sometimes security rules (like ModSecurity or a WAF) can trigger a 404 when they see specific query strings (like post_type=wpsl_stores) if they mistake them for an injection attempt.

    Before reaching out to the host, let’s try two last things to confirm where the breakdown is:

    Check for Slug Conflicts: Go to Posts > All Posts and Pages > All Pages and search (including the Trash) for anything with the slug wpsl_stores. Sometimes a trashed page with the same slug can cause a 404 in the admin routing.

    Server Error Logs: This is crucial now. Please check your hosting control panel for ‘Error Logs’. If the server is blocking the request, you will see a entry mentioning edit.php?post_type=wpsl_stores. If you find a ‘403 Forbidden’ or ‘404’ entry there, your host will need to whitelist that specific query string.

    Database Health: If you have access to phpMyAdmin, check if the wp_posts table is marked as ‘in use’ or needs repair. Also, verify that the wpsl_stores entries exist in that table.

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.