No, 5.2.4 is not beta anymore. Which does not mean that there couldn't be any bugs, but do you have set the correct permissions in the different folders?

I am stuck with this same problem. I can upload any image but I cannot set it as a logo. Since the upload is successful, does this not mean that the correct permissions are set?

I have a test theme where value seems not saved , but was saved in DB and work online.

It's an issue in the dropdown.

I don't find how to reproduce the issue …

Alright, I did some testing and think I have a clue. Steps to reproduce.

1. Deleted all the extended themes and made sure they were gone from the template_configuration table.
2. Extended a single theme.
3. Queried the template_configuration table to find new template config row.
4. In the options field, the default logo is displayed as \"brandlogofile\""invalid:themes\\/survey\\/vanilla\\/files\\/logo.png\"
5. Notice where it says invalid. Possible clue?

Moving on.

1. Upload a new image.
2. Select image using drop down and click save.
3. In the options field, the new value for brandlogofile is \"brandlogofile\""invalid:image::theme::files\\\\usa_logo2.jpg\"
4. Notice where it still says invalid.

I am no expert in LS but it looks as though the relative root path has an issue. Could be mistaken. Leaving it to you experts to decide.

Regards

Can you please create a bug report on bugs.limesurvey.org with the detailed instructions? Thank you!

I understand that the impossibility to reproduce the issue is a major problem. I suspect that my installation is somehow flawed. I am considering installing another instance of LimeSurvey to see if the problem persists. Do you think this might help? As far as I can understand, you can have two different instances on the same server.

Yes, you can have several instances on the same server. Place them in different directories and use separate databases.

Finally, someone who managed to reproduce the issue! Thank you very much. I too suspect that this is a problem related to the relative path, but I am not sure. I hope that it will be resolved if reported as a bug. Strange, though, that no one else seems to have encountered this problem.

Could the problem with the relative path be caused because PHP LDAP library is not enabled or available?

No, PHP LDAP is for something completely different. If you do not use LDAP, then a missing PHP LDAP library should have no impact on the functionalities of your Limesurvey installation, despite not being able to use LDAP.

c_schmitz wrote:

Can you please create a bug report on bugs.limesurvey.org with the detailed instructions? Thank you!

Should a bug report be created by usautomatic who managed to reproduce the problem or should I create it?