View Issue Details

This bug affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
17450Bug reportsQuestion themepublic2023-03-17 16:26
Reporteruibklime1 Assigned Togalads  
PrioritynoneSeveritypartial_block 
Status assignedResolutionreopened 
Product Version3.22.24 
Summary17450: Missing file: incorrectly specified CSS file
Description

The file assets/styles-public/subquetionandansweroptions.css is reported missing (404) many times for some of our surveys.

Steps To Reproduce

Survey questions sometimes trigger this missing file

Additional Information

The file assets/styles-public/subquetionandansweroptions.css does not exist. The file assets/styles-public/subquestionandansweroptions.css DOES exist (missing "s" in "question"). The file views/admin/survey/Question/_subQuestionsAndAnwsersJsVariables.php references subquetionandansweroptions.css (without "s") . The fix is on line 55 and should be:

Yii::app()->getClientScript()->registerCssFile( Yii::app()->getConfig('publicstyleurl').'subquestionandansweroptions.css');

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)3.22.4+200212
I will donate to the project if issue is resolvedNo
Browserall
Database type & versionN/A
Server OS (if known)Linux
Webserver software & version (if known)Apache
PHP Version7.3.24

Users monitoring this issue

There are no users monitoring this issue.

Activities

galads

galads

2021-07-16 15:22

reporter   ~65475

Hello,

Can you give steps on how to reproduce the bug reported?

Attaching a simple survey will also be helpful.

uibklime1

uibklime1

2021-07-19 09:52

reporter   ~65506

I am the admin for a large installation. I see 404s in the HTTP logs for this file, and I have identified the source code in question that incorrectly tries to access the file. IT's a simple typo. Do you really need me to reproduce a survey?

galads

galads

2021-07-19 11:06

reporter   ~65507

In the steps to reproduce, you only mentioned "Survey questions sometimes trigger this missing file". I have tried to reproduce this without success. There are no typos on the main code (I just checked).

Please update to the latest version and check if the bug can still be reproduced. Thank you.

galads

galads

2021-07-19 11:07

reporter   ~65508

Hello uibklime1,
I checked this with the latest version and could not reproduce it, so this is most likely fixed for good.
Therefore, I am closing this issue. If you still can reproduce the issue using the latest version, please feel free to re-open the issue.
Thank you!

galads

uibklime1

uibklime1

2021-07-19 11:55

reporter   ~65511

@galads I cannot seem to re-open this, and you have not indicated which version this has apparently been fixed in. Can you please verify that this fix is in upstream in the LTS branch of 3.x?

uibklime1

uibklime1

2021-07-19 12:00

reporter   ~65512

@galads Nevermind. I found it: https://github.com/LimeSurvey/LimeSurvey/pull/1427 I finally saw the 'reopen' button.

uibklime1

uibklime1

2021-10-05 22:30

reporter   ~66757

@galads FYI, AFAIK this is not fixed in LTS 3.x. I am not sure why you need to reproduce a bug for which I have provided a functional code patch. Could you please apply this fix to the latest LTS 3.x.

uibklime1

uibklime1

2021-10-05 22:32

reporter   ~66758

Please see previous comment and re-open. @galads

galads

galads

2021-10-06 11:40

reporter   ~66764

@galads FYI, AFAIK this is not fixed in LTS 3.x. I am not sure why you need to reproduce a bug for which I have provided a functional code patch. Could you please apply this fix to the latest LTS 3.x.

Hello @uibklime1 , I need to check if this is not resolved already in the latest branch. This is why I need to be able to reproduce any issue. In this case, the issue is fixed already as you pointed out https://github.com/LimeSurvey/LimeSurvey/commit/e28d77c3b159882e64f41cc50ec3b828957bcff9

Please confirm you are trying this in the latest build 3.27.18+210921

uibklime1

uibklime1

2021-10-06 13:18

reporter   ~66775

Thanks @galads and sorry for the noise. I pulled the source for 3.27.19 and confirmed that the patch HAS BEEN MADE to that version.

Mazi

Mazi

2023-03-17 16:26

updater   ~74175

@ollehar, I think we can close this one?

Issue History

Date Modified Username Field Change
2021-07-16 01:00 uibklime1 New Issue
2021-07-16 15:22 galads Note Added: 65475
2021-07-16 15:22 galads Assigned To => galads
2021-07-16 15:22 galads Status new => feedback
2021-07-19 09:52 uibklime1 Note Added: 65506
2021-07-19 09:52 uibklime1 Status feedback => assigned
2021-07-19 11:06 galads Note Added: 65507
2021-07-19 11:07 galads Status assigned => closed
2021-07-19 11:07 galads Resolution open => fixed
2021-07-19 11:07 galads Note Added: 65508
2021-07-19 11:55 uibklime1 Note Added: 65511
2021-07-19 12:00 uibklime1 Note Added: 65512
2021-10-05 22:30 uibklime1 Note Added: 66757
2021-10-05 22:32 uibklime1 Status closed => feedback
2021-10-05 22:32 uibklime1 Resolution fixed => reopened
2021-10-05 22:32 uibklime1 Note Added: 66758
2021-10-06 11:40 galads Note Added: 66764
2021-10-06 13:18 uibklime1 Note Added: 66775
2021-10-06 13:18 uibklime1 Status feedback => assigned
2023-03-17 16:26 Mazi Note Added: 74175
2023-03-17 16:26 Mazi Bug heat 4 => 6