Where would the UX team want to get feedback, if at all?

I think the bug tracker is not a good place to discuss issues, so I would rather discuss in a forum thread, but I adapt to what the preference is.

One example: while I agree that whitespace is good, the main screen could easily fit on a fullHD screen if we would be a little less "wasteful":

 

We have huge buttons, a lot of space between those fields and a completely useless logo and text "This is the LimeSurvey admin interface. Start to build your survey from here." (no shit?!).

Get rid of this weird logo and text, it is absolutely useless. Who needs to be reminded that they are in the Limesurvey Admin Interface and what they can do here. No one needs to be reminded of this every single time the log in. Put the logo in the black navigation bar and make it smaller.

On a FullHD screen there should be no need to scroll for this start page.

The "Welcome to Limesurvey" popup shows all the time. Is there any way to get rid of it? 

 

The incompatibility of themes between versions 5 and 6 will make the transitions very difficult.
Currently there is this situation:
- the current download version is 6.0.0, there is no trace of the latest version 5 for download. Has it been abolished, canceled, wiped off the face of the earth? I think version5 should be considered LTS like version3.
- with ComfortUpdate you can still update to 5.6.14, until when?
- in LimesurveyCloud I get a 5.6.13, until when?
In short: more than the UX of this version, I am quite scared of the migrations of the current surveys from 5 to 6.

LS 5 will become the new LTS, supported for at least one year, we're just a bit slow with the page modifications.

LS 3 will be supported until second quarter of 2023.

ollehar wrote:

LS 5 will become the new LTS, supported for at least one year, we're just a bit slow with the page modifications.
 

Great : github.com/LimeSurvey/LimeSurvey/tree/5.x-LTS

It's great that there's progress but as a friendly criticism as a long-time (paying) user this really isn't a good way to announce a new major update.

I'd suggest drafting something that covers all the issues that have been revealed piecemeal in that chat at a minimum.

Could you please unpack the comment:
"since it includes a change in the CSS framework, old survey themes will not be compatible with the new release. "

Is this a blanket incompatabilty, or will themes based on the default themes supplied maintain some compatability?

Thanks giving it a try now.

Quick feedback - default answers are extremely hard to find now - suggest adding them to the edit screen in a tab alongside "Question" and "Help"

Leithy wrote:

Thanks giving it a try now.

Quick feedback - default answers are extremely hard to find now - suggest adding them to the edit screen in a tab alongside "Question" and "Help"

 

Please report as an Ergonomy issue : community.limesurvey.org/bug-tracker/
Example : bugs.limesurvey.org/view.php?id=18735


 

Hi,

i tried to test surveymenu-function and wanted to create a new menu (index.php/admin/menus/sa/view) unfortunately when i click on the green "create-button", nothing happens, tried in Chrome and MS Edge - same

when trying to add a new menu-entry - same beaviour...

I also read the information on  www.limesurvey.org/manual/Menu_entries_configuration
Unfortunately when I press the green Save-Button, nothing happens...

 

Has someone tested if Shibboleth plugin works with version 6?

Jmantysalo wrote:

Has someone tested if Shibboleth plugin works with version 6?
 

Maybe move it to Plugins section ?

If you already have an auth system : it can be easy to test.
I need to test AuthCAS …

If you already have an auth system : it can be easy to test.

Kind of: If it does not work at all, it is fast to see. But how about changing the name, for example?

Besides, I am lazy. That's why I asked if someone has already done that.

Hello there,
  I'm a bit confused by version management. I write to ask informations about plans for LS 3.x branch security support. And, in general, about stable LTS development plans.

• Until when, 3.x branch will be supported? Download page now claims "Support end: End of June 2023 (supports PHP 5.5.9 to 7.4.x)". Today is early August 23 and the latest patch is 68+230809
• Is it LS 5.x mature enough to be stable LTS? Actually 5.6.x was patched 33 times. (supports PHP 7.2.5 to 8.0.x)
• What happened to LS 4.x branch? Is LS 6.x branch an unstable testbed? (requires PHP 7.4.x or newer)

The question covers also system administration, because of PHP lifecycle. PHP8.0 deadline is set in Nov.23. So if you plan to make 5.x branch a LTS for entire 2024 (as read in previous posts). Branch 5.x must be compatible as soon as possible with PHP8.1 deprecations.
Do you have some more informations about this? We're planning systems migration from 3.x branch and I need to report about LS roadmap.
Thank you in advance.