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
{{ message }}
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
Steps to reproduce (using acmi 00dc06e69364 and icekit 18ea0d8 - it should be possible to reproduce by reinstating the {% extends %} block in the ACMI contact_person template):
Preview a fluent page that contains a File
On local, you'll get a console error (it can't render the technical 500 page) TypeError: coercing to Unicode: need string or buffer, NamespaceOrigin found, On staging you get https://sentry.ixcsandbox.com/ic/acmi-stg/group/5714/
NB that the path to the template is namespaced, and is a result of the template at templates/icekit/plugins/contact_person/default.html calling {% extends "icekit_plugins_contact_person:icekit/plugins/contact_person/default.html" %}
Amusingly, this template should be nothing to do with the File content plugin - though the file template is namespaced the same way.
For now, I'll workaround by removing the {% extends %} override.
The text was updated successfully, but these errors were encountered:
Turns out the file template was incorrectly extending "icekit_plugins_contact_person:icekit/plugins/contact_person/default.html" I assume the error is some sort of namespace violation.
Steps to reproduce (using acmi 00dc06e69364 and icekit 18ea0d8 - it should be possible to reproduce by reinstating the
{% extends %}
block in the ACMIcontact_person
template):File
TypeError: coercing to Unicode: need string or buffer, NamespaceOrigin found
, On staging you get https://sentry.ixcsandbox.com/ic/acmi-stg/group/5714/NB that the path to the template is namespaced, and is a result of the template at
templates/icekit/plugins/contact_person/default.html
calling{% extends "icekit_plugins_contact_person:icekit/plugins/contact_person/default.html" %}
Amusingly, this template should be nothing to do with the
File
content plugin - though thefile
template is namespaced the same way.For now, I'll workaround by removing the
{% extends %}
override.The text was updated successfully, but these errors were encountered: