Front End User - having trouble with sign out

[johnboyuk1]

I wonder if anyone with experience of this module can help me out as its giving me real headaches!

I've got the basics set up - some 'protected' page content types, and 403 error page with {FrontEndUsers} in it. On my protected pages the {FrontEndUsers} tag is in the header area of the html template so users have access to a logout button

I've then created a login page (unprotected) - which seems to work fine in terms of logging in - if also also click 'sign out' on the options that have replaced the login form inline that works - if I stay on this page I can keep logging in and out no problem

BUT

Once I leave this page - to go and look at some of the protected pages - if I want to logout I'm using the sign out link that's now in the header area of the pages - when I click this I'm taken to the '403' page which features the login form again. If I now try and login using this form it fails and I get the message 'Could not determine logged in uid'

Whats going on?!

I did also need to get a page redirect on the login page (see my other post) but that also seemed to introduce more of these login/out issues

I can PM a link if anyone was interested in looking at this for me - happily buy you a coffee if you can solve it!

[velden]

I think I've seen about the same behavior at a client's website.
They get the message 'Could not determine logged in uid' right after log-out.

I also believe it's a bug in FEU 3.x but not 100% sure. I noticed (and saw in the code) that something may have to do with the 'after' parameter in the url of the page or form action.

I didn't solve the problem btw. Client accepted this error.

[johnboyuk1]

ok, bit of a pain! maybe it doesn't play nicely with pretty URLs ... as I have this enabled

[AccentAvondschool]

Hi,

I'm currently working on this voluntarily school project and am getting the same error 'Could not determine logged in uid' on the website.
But the school finds the error confusing for the logged-in students.

I came to this page through Google with comments from two years ago. I read that it might be a bug in FUE? But there will have been updates from FUE by now? Does anyone know if there is a solution or work-around for this?

Thanks in advance.

Regards,
René

[DIGI3]

FEU was abandoned by its developer some time ago. The supported replacement is http://dev.cmsmadesimple.org/projects/mams but it's a fork of FEU 2.x, so if you're on 3.x you likely won't be able to migrate directly. You should be able to export your users and groups, however, and import them into MAMS.

[AccentAvondschool]

DIGI3, thanks for your comment.

So now there is MAMS as a fork of FUE. As a fork means that you still need both plugins (?) and also mean that you have to reconfigure everything ;(

I fully understand that a CMS like CMSMS is open source and largely depends on external developers who put together code such as plugins in their spare time.
I also fully understand that it can be quite time-consuming for such a person to keep such a plugin up to date and/or to build in new features and that such a person stops developing after a while.
What I don't understand is that an indispensable/essential plugin like FEU that has been around for quite a while - and has been downloaded by a lot of users - is then not picked up as a CMSMS core plugin?

This is a big problem with many open source CMSs where the core is maintained but as a user you are dependent on external developers for essential plugins who could stop developing/maintenance at any time. And that may result that people may shop further, resulting in a decline in the community.

I wish I had the skills to program.

[DIGI3]

A fork does not require the original to be installed. It can be removed completely when the migration is done.

We can't legally take over someone else's project without permission. We attempted to obtain permission, including offering to purchase their library of modules, but the author was not interested. Forking is the only option we had.

We did learn from this, and now encourage developers to include the CMS Made Simple Foundation as an owner of their projects, in which case the Foundation can assign new developers. MAMS is one of these projects.

[AccentAvondschool]

DIGI3, thanks again for the explanation.

I'm glad to read that the Foundation has put a lot of effort into adopting the original plugin, which gives us a lot of confidence to continue using CMSMS.

When I read about MAMS I immediately thought of YAP (Yet Another Plugin) but now it turns out that the Foundation is the owner, we will fully embrace the plugin

Perhaps a condition for (external) developers should be included that every plugin that is developed for CMSMS the Foundation becomes the owner? Because they make use of CMSMS and without CMSMS there plugin will not work, therefore there may well be a condition attached to it! But not sure if this is legally achievable.