-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrade 6.0.28 to 6.0.40 results in jquery errors #123
Comments
Here are the logs of the container after adding
paths inside the container:
|
Upgrade |
Probably the same issue #118 |
This seems a bit confusing to me. I've just realized that
So upgrade from |
Update: Upgrade from |
Upgrade from |
I was able to reproduce the error when upgrading from 6.0.28 to 6.0.40, but if I do first upgrade from 6.0.28 to 6.0.33 which was the first Znuny version, and then to 6.0.40 I do not get the jquery error. I also found an error in the fix for issue #118 which would overwrite the value of I will push a fix shortly. |
@rdxmb were you able to test? |
Can you tell me what you want me to test exactly? Actually we are running Maybe I've copied the files manually, I do not remember ...
|
@rdxmb , well, test the bug that you reported on this issue, and see if it is present for you. |
from #118 (comment) That was the information I was missing... Ok, I am going to test that tag next week, probably on Monday. |
Fresh deploy 6.0.28 (otrs version) works The jquery issue still not fixed and the old fresh install not working issue (#97) reintroduced. |
@vadonka thanks for the debugging, I will point |
You welcome! |
The issue was introduced when working on this fix for minor updates. In a few words, what is happening is that because of that fix, the contents of the |
We were stuck on this issue for a few days now and finally found the cause and a solution. The problem is that the The If the config dir already exists, nothing will be copied. The old configuration files in the As a solution we modified the
Modified function (including the fix mentioned here):
Since we only have modified the configuration in the |
Image and OTRS versions
Upgrading a "fresh" container running
image: "juanluisbaptiste/otrs:6.0.28"
to image:"juanluisbaptiste/otrs:6.0.40"
Kubernetes Manifest (can be read similar to the docker-compose.yml) ;)
Describe the issue
After upgrading, the login-page shows jquery errors.
Expected behavior
no problems when upgrading the minor version
Screenshots
The text was updated successfully, but these errors were encountered: