Sounds like either a setting/config error, or possibly a plugin or theme conflict.
I just created those two locations on my test server, and added a couple of members to each location, and set up new pages with the locations set in the shortcode, and it works just fine for me.
What else have you changed recently? Double-check the shortcodes on those pages, and that locations are enabled and properly defined & spelled the same.
Not much else I can tell you, since I can’t reproduce the issue. Works just fine on my server with WordPress 4.3.1.
Thread Starter
wla
(@wla)
I have temporarily enabled public viewing at http://kmsail.com/officers/ — works fine with shortcode: [pta_member_directory Location=”Officers”]
But http://kmsail.com/Members/ does NOT work with shortcode: [pta_member_directory Location=”Members”]
That doesn’t really help that much, as I can’t see any of your WordPress settings, although turning on Firebug and loading your members page reveals:
“NetworkError: 500 Internal Server Error – http://kmsail.com/members/”
Again, sounds like a WordPress configuration issue, or a server issue, and not anything to do with the plugin.
Check your permalink structure, perhaps trying a different setting, and saving to clear old settings. Also check to see if you have any other plugin that uses “members” as a custom post type, in which case the url to your members page might be conflicting with the post type archive.
My plugin works fine on my own site with a page that is using /members as the page (how I usually set it up)… so, again, something with your site or server, and not a problem that I can reproduce.
Thread Starter
wla
(@wla)
In case there was a conflict with use of “members”, I changed the Locations of all 118 members and the page Location, but that didn’t help.
Eventually, I found that the list works fine with any number of members up to 91. With more than 91 members, it refuses to show. And it makes no difference which 91 members.
If I have the page Location reset back to “Members” and I change the Location of any members to exclude “Members”, it is fine as long as not more than 91 members have the Location “Members”.
OK… that information is more helpful. I will do some testing later to see if I can reproduce the issue with that many members. Not sure why that specific # of members would cause an issue, though, as there is nothing in my plugin or WordPress that should limit the number of posts returned, at least not which I can think of off the top of my head.
My best guess right now is that you are running up against a PHP memory limit. Perhaps try increasing the amount of memory available to WordPress and see if the # of members you can show changes. See this for increasing memory:
http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
Thread Starter
wla
(@wla)
Success! I first tried increasing memory to 64M — that made no difference. I then increased to 96M and that worked!
Thanks for the suggestion.
Great plugin and excellent responsiveness to my problem.
Great! Glad that worked for you. WordPress can be memory hungry, especially if you have a lot of plugins. I usually set my live sites to 128 or even 256MB.
