OVERLEAF_RIGHT_FOOTER not rendering HTML, but only on /project page · Issue #1340 · overleaf/overleaf · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using latest docker image (5.4.0) community edition.
Not sure what might be wrong, but I'm having problems with OVERLEAF_RIGHT_FOOTER rendering in the browser correctly.
If I pass in OVERLEAF_RIGHT_FOOTER as [{"text": "Another page I want to link to can be found <a href=\"here\">here</a>"} ]
then it will show up as Another page I want to link to can be found <a on my project's page. (<site-url>/project) In the browser's inspector the full text is there in the source code, but not as valid html.
But I was testing anonymous link sharing previously and I have a private browser window open to my overleaf instance as well. And in this one, that env_var correctly renders as valid html with a link on the login page...
If I go back to my regular browser window (which was displaying text as cut-off on /project) and log out, the login page there also shows correct rendering. Logging back in shows cut-off text again on /project. While logged in, the /admin and the /user/settings pages/routes show footer rendered correctly (Though of note: the /user/settings page loses it's header's black background)
I looked through issues for "footer" or "html" and din't find anything.
Also if I pass in OVERLEAF_RIGHT_FOOTER as [{"text": "Text <a href=\"https:\/\/duckduckgo.com\/\">DuckTest<\/a> more text"}] I get similar results:
Text <a href="https://duckduckgo.com/">DuckTest</a> more rendered in the web browser. The text is cut off, but I can see no related error code in /var/log/overleaf/clsi.log with this var. Shorter examples will show up in browser still as text and not a link.
I can then pass in malformed JSON as the env_var and see in the container's /var/log/overleaf/clsi.log file an error of could not parse OVERLEAF_RIGHT_FOOTER, not valid JSON
Is there some spelling error I am missing, or another log file I should be investigating?
Thanks.
The text was updated successfully, but these errors were encountered:
Using latest docker image (5.4.0) community edition.
Not sure what might be wrong, but I'm having problems with OVERLEAF_RIGHT_FOOTER rendering in the browser correctly.
If I pass in
OVERLEAF_RIGHT_FOOTER
as[{"text": "Another page I want to link to can be found <a href=\"here\">here</a>"} ]
then it will show up as
Another page I want to link to can be found <a
on my project's page. (<site-url>/project
) In the browser's inspector the full text is there in the source code, but not as valid html.But I was testing anonymous link sharing previously and I have a private browser window open to my overleaf instance as well. And in this one, that env_var correctly renders as valid html with a link on the login page...
If I go back to my regular browser window (which was displaying text as cut-off on /project) and log out, the login page there also shows correct rendering. Logging back in shows cut-off text again on /project. While logged in, the /admin and the /user/settings pages/routes show footer rendered correctly (Though of note: the /user/settings page loses it's header's black background)
I looked through issues for "footer" or "html" and din't find anything.
Also if I pass in
OVERLEAF_RIGHT_FOOTER
as[{"text": "Text <a href=\"https:\/\/duckduckgo.com\/\">DuckTest<\/a> more text"}]
I get similar results:Text <a href="https://duckduckgo.com/">DuckTest</a> more
rendered in the web browser. The text is cut off, but I can see no related error code in/var/log/overleaf/clsi.log
with this var. Shorter examples will show up in browser still as text and not a link.I can then pass in malformed JSON as the env_var and see in the container's
/var/log/overleaf/clsi.log
file an error ofcould not parse OVERLEAF_RIGHT_FOOTER, not valid JSON
Is there some spelling error I am missing, or another log file I should be investigating?
Thanks.
The text was updated successfully, but these errors were encountered: