farroyo

Hi there!

As a matter of fact, our documentation covers the creation of both API keys in detail, have a look at this article: Create Google API keys.

Best regards,

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.

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?

Hi there, thanks for writing!

I am very sorry but I am unable to reproduce your issue. I am browsing your website both in my desktop computer and in my mobile phone using different browsers (brave, firefox, safari), and the website loads just fine (see screenshot).

Does this also happen to you in other phones you may have around? Which combination of phone / browser are you trying? Please let us know.

Best regards,

Hi again,

In WP Store Locator v2.2.261, that specific line is where the plugin generates the filenames for the @2x retina markers.

The error suggests there might be a file in your markers folder with an unexpected name or a missing extension. Could you please let us know the contents of your /wpsl-markers directory? A list of the filenames or a screenshot would be very helpful to pinpoint which one is causing the conflict.

Best regards,

Hi again,

Does this issue still persist after moving all the image files and code customizations to the child theme, as suggested in my previous ticket? Let us know.

Hi, sorry for the late reply!

That is a very valid point and we are aware of that. Our next major version (3.0) will indeed include much better html markup so you can address these types of scenarios, so stay tuned!

Best regards,