This is most likely due to a long standing issue that emerged when we migrated to the new servers and, particularly, to the new salt based packaging. @yolile can comment on this migration if needed.
Summary of the problem:
There are a few assets in the site that are never rails are not able to retrieve, even when they are properly compiled when the site is redeployed. I don't know why this happens.
This happens with the form to write a message in the forum. This is a haml template that is compiled app/assets/templates/posts/new_custom.html. Assets are correctly compiles and copied intopublic/assets/posts/new_custom-HASHCODE.html. However, the app keeps trying to retrieve public/assets/posts/new_custom.html (without the hashcode at the end of the name that rails adds
This is the list of assets that for some reason are not compiled and moved into the correct path:
This is most likely due to a long standing issue that emerged when we migrated to the new servers and, particularly, to the new salt based packaging. @yolile can comment on this migration if needed.
Summary of the problem: There are a few assets in the site that are never rails are not able to retrieve, even when they are properly compiled when the site is redeployed. I don't know why this happens.
This happens with the form to write a message in the forum. This is a haml template that is compiled
app/assets/templates/posts/new_custom.html
. Assets are correctly compiles and copied intopublic/assets/posts/new_custom-HASHCODE.html
. However, the app keeps trying to retrievepublic/assets/posts/new_custom.html
(without the hashcode at the end of the name that rails addsThis is the list of assets that for some reason are not compiled and moved into the correct path:
Current workaround is to manually copy the assets without the hashcode into
public/assets/posts/
Estimated hours to develop: 10h