1waytoheaven

No support response after 4 days!

Sorry, I gave a 5star review in 2022, but this is simply not good enough.

Deleted the plugin.

Warning: this plugin has not been tested with your current version of WordPress.

We also get the Warning message for the latest version of WP.

In addition, WP Admin>Tools> “Site Health” nags us to install Persistant Object cache on our server, and yet another plugin called “Redis Object Cache”

https://www.ads-software.com/support/article/optimization/#persistent-object-cache

Too many cooks spoil the broth methinks.

I’m in Asia, so by the time I’d read your reply, “webp-converter-for-media” had aleady sent a small update to their plugin.

So I merely updated their plugin, then resumed trying to use your backup plugin, as before, and it worked first time ??

Perhaps you sent them a note to nudge them?

Thanks for the quick response ??

Colin

• This reply was modified 2 years, 6 months ago by 1waytoheaven. Reason: Sp

Bump

Interesting observation.

I was going to suggest, that perhaps you’d not yet added a child theme, but I looked more closely at our own site, where we do have a child theme, and like you, our Neve theme footer has vanished since we updated to the latest Neve version.

I didn’t really require our footer, so no skin off our site’s nose, but I wonder if the footer vanishing in the latest Neve update is a bug rather than a deliberate bait and switch.

Hopefully, it is a bug that will be corrected on the next update.

If not, like you, we’ll be looking for a new theme.

• This reply was modified 2 years, 8 months ago by 1waytoheaven.

The site is:

https://www.born-again-christian.org/news/

However, since I received no reply here, I had to delete the Simple Membership plugin Redirect AddOn.

I asked the addon’s Developer about the bug, and they set up their own test site using Default Neve, and confirmed their Redirect Addon does work with basic Neve, so my particular Neve setup is where the bug lies.

I’m using Neve with a child master, and the site uses the LiteSpeed caching plugin on a LiteSpeed server.

I’ve now re-activated the SMP redirect addon, for you to test the Neve sidebar Login widget and Neve Top Menu.

Active Members ought to be redirected to the page where they used the Login widget (as in my settings), but currently they all get sent to the site homepage, which means the Redirect addon isn’t working.

Thanks for your assistance ??

Here’s the Support thread where the Redirect Addon Developer comments…

https://www.ads-software.com/support/topic/redirection-addon-not-working-yet/page/2

• This reply was modified 2 years, 9 months ago by 1waytoheaven.
• This reply was modified 2 years, 9 months ago by 1waytoheaven.

Okey-dokey: Noted for future reference.

My Neve child theme is quite modified, and I also read today that the recent WP “Block Widget” has wrecked many site’s widgets, doubtless that will have something to do with it. I’ve installed the Classic Widget plugin to get round that “new feature”.

Let’s call this resolved after your labours ??

Thank you Chad, happy to see you posting again.

I’ve been experimenting with an alternative Membership site plugin whilst you were AWOL ??

Looking forward to seeing the updated 3.4.2 “any day now”.

Thank you for your diligence, and welcome back!

Thank you for your testing, I do appreciate your diligence, but switching themes on our live site is too dodgy.

Perhaps you could chose Neve theme on you development site to run the tests you suggest.

This bug is taking too long to resolve, so I’m afraid I’ll have to delete the Redirect addon altogether.

Thank you again.

Ahh! I see now. Thank you ??

Thank you for responding again ??

I looked at the linked page you gave and it helped me to confirm that both the sidebar widget login and the top menu Login are indeed using the SMP shortcode [swpm_login_form] so ought to be working with the SMP Redirection plugin, but they are not!

Why they are not is the subject of this thread.

I’d really like to get it solved soon.

Where is the Developer?

I’ve also asked at Neve Support here:

• This reply was modified 2 years, 9 months ago by 1waytoheaven. Reason: Added link

I’m not sure what the difference is.

I’m talking about logging into our site, not WP itself.

I made the side bar Login widget by using the Neve Child Master Customiser pane in my WP admin of our site. I don’t know if that would be a Neve theme widget or a WP login form widget. How could I tell.

I have made a Login page, that is linked to in the top menu.

And I have also a sidebar Login widget.

Neither of those redirect to the page where the user logs in, they both go to the site homepage (what some people at Neve call the “Blog” page.)

I’ve asked at Neve Support, but so far no replies.

Thank you for your help, I hope WPinsider is not ill?

Whilst waiting for a reply, I’ve noticed something of interest.

I am testing the Redirect by using the Login input boxes in the sidebar (the Neve theme widget Login)

BUT if I go the circuitous route of clicking the LOGIN text link under a protected post, that takes me to a url with ?swpm_redirect_to= in it, and I AM then redirected to where I logged in. (Which is progress)

So how do I get redirection to work when visitors use the more logical and obvious sidebar Login input area and the Top Menu Login page? Currently neither works with your redirection addon.

• This reply was modified 2 years, 9 months ago by 1waytoheaven.

Thank you.

I should mention the first lnes of the debug log above are from the General debug file, the rest from the Login debug file.

Perhaps of relevance...
[2022/06/06 14:22:19] - SUCCESS: Log file reset
------------------------------------------------------------------

[2022/06/06 14:25:06] - SUCCESS: After login redirection addon. Checking if member need to be redirected.

I notice there’s nothing in the debug file after the phrase, “Checking if member need to be redirected.”

I would have expected a SUCCESS entry because it redirected test to the Homepage, although I’ve set the SMP Redirect plugin to redirect logged in Users to the page where they logged in, which in this case was NOT the homepage.
So no SUCCESS or FAILURE entry after that phrase is an anomaly, isn’t it?

• This reply was modified 2 years, 9 months ago by 1waytoheaven. Reason: Sp

Debug report:

After adding the cookie URI to my LiteSpeed exclude, in the proper exclude cookies pane, I tested again in debug mode as User: test (which is already a Member on our site.)

I chose a page other than the Homepage, and from there logged in with the correct data.

The browser “hung” again (annoying because I thought that was fixed), and after refreshing the browser view I was redirected to the site Homepage (ie. not the page I logged in at, and wanted to see.)

Here’s the Debug logs:

[2022/06/06 14:22:19] - SUCCESS: Log file reset
------------------------------------------------------------------

[2022/06/06 14:25:06] - SUCCESS: After login redirection addon. Checking if member need to be redirected.

2022/06/06 14:22:19] - SUCCESS: Log file reset
------------------------------------------------------------------

[2022/06/06 14:23:14] - SUCCESS: wp_authenticate action. Empty username provided. Adding set_current_username hook to catch potential login attempt.
[2022/06/06 14:25:06] - SUCCESS: Authentication request - Username: test
[2022/06/06 14:25:06] - SUCCESS: Authentication successful for username: test. Executing swpm_login action hook.
[2022/06/06 14:25:06] - SUCCESS: Trying wp_signon() with username: test
[2022/06/06 14:25:06] - SUCCESS: wp_authenticate action. User with username: test is already logged in.
[2022/06/06 14:25:06] - FAILURE: wp_signon() failed for the corresponding WP user account.
[2022/06/06 14:25:06] - SUCCESS: Triggering swpm_after_login hook.

The User test does not have a WP account, I just made it to test our site.

Does that give you any clues why the SMP Redirect addon is not working as set?

• This reply was modified 2 years, 9 months ago by 1waytoheaven.