Hello,

I installed 4.1.5 LS version on my server and created a survey. Everything seemed to work ok , but after some time when I tried to login to the admin page , I was presented with a window which had no Username and password fields, the issue is very similar as shared here and in this bug report .
URI of Admin login Page : /?r=admin/authentication/sa/login

I did go through the forum but couldn't find any remedy of what procedure I can use.. I have used different browsers, cptrs so its not a cache issue as far as i know.

Any guidance in this regard will be appreciated

Thanks

Relevant to the discussion board , just got this warning message after making a post ..may be the admins would want to know this so they can fix this aswell

The error of the login page is known and there is already an assigned bug report

bugs.limesurvey.org/view.php?id=15908

with some comments.

You mentioned a three year old issue with version 2.50/2.73

Joffm

Joffm wrote: The error of the login page is known and there is already an assigned bug report

bugs.limesurvey.org/view.php?id=15908

with some comments.

You mentioned a three year old issue with version 2.50/2.73

Joffm

Thanks Joffm for the reply , although that bug doesn't help me resolve my issue.
1. I did not upgrade an older installation of LS , rather I have a fresh install
2. load_error column was already 0 , so there was no change required at the db

With that said, I am still looking for a fix, while going through the thread you gave the link too ..
there is an error msg in front of Authdb , which states : Unknown error - error_get_last() returned null

Same error in front of ExportR adn ExportSTATAxml

as per the opening post, any guidance will be appreciated

Of course the bug report doesn't help you to fix it, because the bug hasn't been fixed yet. It has been reported and is still open. So you need to wait until it is fixed and then upgrade/fix on your installation.

holch wrote: Of course the bug report doesn't help you to fix it, because the bug hasn't been fixed yet. It has been reported and is still open. So you need to wait until it is fixed and then upgrade/fix on your installation.

The reporter already fix the issue

UPDATE lime_plugins SET load_error = '0' WHERE lime_plugins.id = 1;

OK, I just saw that the bug was still marked as "open".

I am even more confused...

So I have encountered a three year old bug which is still awaiting a fix ...so basically the stable release is not stable enough for use ?

You wouldn't be as confused if you would actually follow the links people post or read what they are saying.

YOU dug up a thread that was 3 years old. This doesn't make sense because it was for the version 2.x, while in the meanwhile there was 3.x and now we have 4.x which is the version you have a problem with.

Joffm posted this bug report for 4.x:
bugs.limesurvey.org/view.php?id=15908
It was submitted on 2020-02-24 13:25, so less than a week ago, and yes, it has not yet been fixed in a version, because it doesn't seem to be so clear how this actually occurred. There is a way described in the link how you can fix it in your current installation.

thanks for replying - the environment here seems generally intense....

holch wrote: There is a way described in the link how you can fix it in your current installation.

yeah, I hoped it would work out for me , but that doesn't resolve the issue

thanks

thanks for replying - the environment here seems generally intense....

Generally it isn't. But it depends, if continuously doesn't read what was already posted, yes, I can get "intense", if you want to call my post this way.

...so basically the stable release is not stable enough for use ?

This is a different topic. I would actually agree with you there. I wouldn't consider 4.x ready for productive use. At least I wouldn't use it yet.

Problem is, that during the beta testing phase almost no one from the community tests and reports bugs. We are all part of this community and if we do not report, there is no way to find and fix all issues. So the developers probably decided to go forward and do what many software developers do today: Release the software as "stable" and fix the bugs that appear. I don't agree with this approach, but it might actually be the only way a open source software like LS can do it, without huge resources.
If the users don't give back (with bug testing, translation, bug fixes, etc), it is hard for the handful of core developers and heavy contributors to make the new versions really "stable" before release.

You will most probably encounter a couple more "show stoppers" in the "stable" LS 4.x. What we can do is report them and comment on them so that the developers see that it concerns more than one user.

I have seen that you still have made no comment / contribution to this bug report. It obviously is a bug, there is no official bug fix, just a solution from a user. So you might want to add your information to this bug fix. Or it will never be fixed.

My bad, I have added my input to the bug tracker ..
although I would request that an earlier version be listed as stable as this one is not ..

thanks