Not sure if this is the right place to report Issues for unstable versions. I'm trying this version out and have hits a number of issues, I have cleared my browser cache. So far:-

• Inn the original browser I was working on (Firefox) I can access the admin page but the home page for non logged in people is blank.
• On all other browsers the home and the login pages are blank
• Link to plugin manager doesn't work. Gives me a page without CSS
• The CSS editor template doesn't work. There is no preview
• I can see no way of changing the template for a survey

Hmm wasn't aware that unstable == unusable.

Also any click on a link spawns new tabs rather than changing the content of the current tab.

Hi,

I think best is to report bug on www.limesurvey.org/en/community-services/bug-tracker
Remind to select "2.5" for Product Version

southcot wrote: ......
Hmm wasn't aware that unstable == unusable.
......

:laugh: :laugh: :laugh: :laugh:
You're right ..... :dry:

Thank you for your encouragements.
 
- The home page for non admin has been fixed yesterday.
- If you block js, nor the admin page will show (something easy to change. But javascript is still needed for the whole admin interface...)
- What do you call link to plugin manager ?
preview.limesurvey.org/index.php?r=admin/pluginmanager/sa/index

This link is just working fine. Be more specific please.

- The CSS template editor works. The preview is no more showing since last release, will be a quick fix, thank you for reporting.
- There is two ways to change a survey's template : the usual way in survey setting, and an other one in the survey quick actions.

I also guess you're using a fast server configuration, such as alias rather than virtual hosts, that can make problem with asset manager (include with 2.06)

Don't hesitate to use the bug tracker to report correctly any bug you find :
bugs.limesurvey.org/

@LouisGac and DenisChenu thanks for the speedy responses. I had just posted this on bugtracker though it only offers 2.06+ as a version to report on.

@LouisGac

• js is not blocked. All was working fine until I upgraded.
• Not sure I can be more specific regarding the plugin page see attached
• You say CSS template editor works and now I see that if I make a copy of a standard template it does offer the option to change
• As to saving if I go through the standard properties then Save doesn't work and Save and close neither save the template change not closes the view. Access via quick actions and clicking the current template takes me to the editor page but there is no option there to change the template
• The current hosting platform I'm working on is a public shared hosting platform form Heart Internet. I have no idea what you mean by "I also guess you're using a fast server configuration, such as alias rather than virtual hosts, that can make problem with asset manager (include with 2.06)". What does this mean for my installation. As I say it was working well before I upgraded.

It seems too that data entered via the data entry screen doesn't save. Nor does save and close save the data and close the view.

The CSS isn't being applied to the surveys when they run either. This survey is using the default template.

I usually try and test RC beta versions of software as usually they aren't too bad. However this one is proving unusable. How do I wind back to a stable version or do I have to start over with the backup copy of the files and DB? I upgraded from 2.06+.

I've just install the new 2.06+ Build 160123 release ... going straight to the admin template to hide #update-alert for 3 key reasons:
1) I hate red/bold alert-message or banners
2) Actually the very last need of common users or admin (often OK using a quiet old version) is to "update" to an unstable version
3) This message was present when logging as non admin user too.

I understand perfectly that beta testers are welcome and needed but IMHO this call have to be (re)moved in the footer or elsewhere in the admin (eg. admin/globalsettings/ overview tab ).

Ben, I totally agree. But this has been discussed quite a bit and the team around the comfort update seems to be reluctant to listen to the community...

Thanks Holch for the support... At least the text should suggest to set a new installation aside a stable version... and not cause confusion with terms like "New update" & "comfort update ".

I also agree that we should either not show update messages for unstable versions at all or point out explicitly that such a version is for testing, not for production.

How about filing a bug report for this?

Interesting discussion but would be nice if someone could respond to my question.