One site running twenty ten, the other twenty thirteen. Both themes are up to date, unmodified. Not very exotic. Menus on both sites quit working with the same update of s2. Both working again after reverting to v 150102.
Your explanation of strange coincidental behaviour isn’t credible. A strange interaction that has survived a year of use in one case, several years in the other, numerous WP, plugin and theme updates? A strange interaction that keeps menu items perfectly synced with user level, ccaps and page protection?
And if I look in the support forums more than a year ago, before your time, I see people being advised that this does work. That is the reason I and others used it.
I’d like to hear Jason’s take on this.
I agree with roysmyth. S2Member Pro has supported navigation menu customization for the three years that I’ve been using it on my Twenty Ten site. We designed the whole site around levels, custom capabilities, and custom menus for each level of authorization. Now it is not working.
We’ll revert to the old version of s2 Member for now, but this is a huge issue.
@roysmyth,
Your explanation of strange coincidental behaviour isn’t credible. A strange interaction that has survived a year of use in one case, several years in the other, numerous WP, plugin and theme updates? A strange interaction that keeps menu items perfectly synced with user level, ccaps and page protection?
You obviously don’t know about Chrome’s font-rendering bug. It was at least partially fixed last year (though maybe not completely: see here) but, before then, it had lasted for several years, over four versions of Windows, hundreds or thousands of updates per Windows version, and untold millions of different sets of personal computers and websites. It was utterly stable. At the same time, most users were so oblivious to it that it became the most popular browser on the Windows platform.
Whether WordPress or a browser, code is just code. If the relevant bits of code remain unchanged, so does the behavior (good or bad) that they produce.
@everyone
Thank you for reporting this important issue! We have opened a bug report here: https://github.com/websharks/s2member/issues/475
I wanted to add that this is currently marked as a high-priority bug and a fix will go out with the next release. Please follow the GitHub Issue for progress updates. We’ll also come back here and let everyone know when a fix has been released.
Thanks Raam for grounding this discussion.
This morning, out of frustration with the discussion here, I went to GitHub, filed bug report, and received a quick response from Jason. Good customer service!
But what is the average user to do? Someone who would never work out how to get to GitHub, let alone know it is there or how to file a bug report? And then they fall prey to misinformation as in this thread.
I’d like better monitoring of the WordPress.org forum by s2.
But what is the average user to do? Someone who would never work out how to get to GitHub, let alone know it is there or how to file a bug report? And then they fall prey to misinformation as in this thread.
I’d like better monitoring of the WordPress.org forum by s2.
If you are a s2Member Pro customer, you can open a ticket with our support department.
The free version of s2Member here on WordPress.org is developed alongside s2Member Pro, so it receives an equal amount of attention and priority when it comes to development, but the free version does not include access to any official support channels; it is solely supported by these community forums, which the WebSharks staff and other community volunteers monitor.
If you have an issue with the free version of s2Member that you feel is a bug, you’re more than welcome to file a bug report on GitHub (which requires a free GitHub account) and share the steps required to reproduce the bug (but keep in mind that we reserve GitHub for filing bug reports; it is not a support channel).
@everyone
This has been fixed in the development trunk and the fix will go out with the next release.
In the meantime, there is patched file available here: https://github.com/websharks/s2member/issues/475#issuecomment-73844902
Thank you everyone for your patience and for helping report and identify this issue!
thanks for fixing. this was killing me too!
