V7 update causes problems

If you waited for support, I could almost assure you we could get it to the “works” position again.

I do appreciate what you do, and without wanting to sound combative, I AM waiting for support. I would like to get it past the “works” position (2-stars) and back up to 5 and I assure you that once that happens I will rectify the current rating.

As a developer myself I do sympathise with the position you’re in.

I can see you’re spending time trying to limit the damage that negative comments and low ratings can cause, and I sense that you’re a bit pissed off by the situation that you AND your plugin users are in. Rightly so.

We are where we are however, V7 HAS caused a lot of problems. The best thing to do is to spend that time proactively and don’t rise to the negativity as that is counter-productive. Once the problems are addressed then the ratings and reviews will be back up there with the best of them.

So what can we do to get your review back up?

The original reason for me posting was that the V7 update causes the existing plugin behaviour to change, changing the flow of the whole login/out/account process.

When I was logged in and navigated to the login page, the log OUT button would be displayed. When I was logged out and navigated to the login page, the log IN button would be displayed. There was a “my account” / “profile” button there too, which is now gone. There isn’t a slug for the users’ profile page.

Now when I use the website, and am logged in, all I see is the “log in” button. Doesn’t make sense.

Now the logout process takes you to a very basically styled “Are you sure?” page.

I hope I’ve been able to demonstrate the change in behaviour of the plugin. The V7 update shows a lack of consideration as to how it used to work prior to V7. Someone made the decision to change it without really considering backward compatibility and just ran with it. Now myself and, I’m guessing many existing users, have to intervene and “fix” their websites due to the update.

In order to get my review back up, please consider making the plugin work like it used to.

What also doesn’t make sense is visiting the Log In page while logged in. We will not be reverting that functionality. There are many alternate ways of showing the proper status, using the proper functions or a nav menu.

As far as logout going to a AYS page, you need to make sure that whatever you are using for your Log Out page slug matches the slug in TML’s slug settings.

Furthermore, I suggest you read up on semantic versioning (which TML follows) and see what a major version change entails.

I think you may have missed my point!

Before the V7 patch this wasn’t an issue. The Login form showed the appropriate actions depending whether the user was logged in or out. It *didnt* show the login page when logged in, it showed the logout page, properly formatted.

My point is that since the patch, behaviour has changed and many of your existing users are having to put extra effort in to fix this change in behaviour. The work needs to be scheduled and carried out and you will always meet resistance in these situations.

Regarding versioning, while major version increments do introduce new features and functionality they generally respect backwards compatability. The V7 update appears to be ignoring some aspects of this, to the detriment of the users.

The “Log Out” page was never displayed – it was merely used for the literal action of logging out. What was displayed on the Log In page when logged in, as mentioned before, was an unintended side-effect of using the same code for the shortcode and widget. This functionality was intended for the widget.

Regarding versioning:

Major version X (X.y.z | X > 0) MUST be incremented if any backwards incompatible changes are introduced to the public API. It MAY include minor and patch level changes. Patch and minor version MUST be reset to 0 when major version is incremented.

We would have released 6.5 had we not made any backward compatible changes.

Ok, well thanks for your time. I give up. I surrender! I was wrong to question your decision to break backwards compatability and you were right to change the functionality of the plugin.

Unfortunately for me, that doesn’t help at all so I need to uninstall this version and use a different plugin.

I would further have to state that, “no longer works like it used to” does not mean the same thing as “doesn’t work at all”.

Well durr…