Skip to content
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

Theme activation fails if partner has no logo #3821

Closed
timlinux opened this issue Jun 2, 2018 · 0 comments
Closed

Theme activation fails if partner has no logo #3821

timlinux opened this issue Jun 2, 2018 · 0 comments
Assignees
Labels
minor A low priority issue which might affect only some users and /or not the main functionality tested Issue has been tested on named setups

Comments

@timlinux
Copy link
Contributor

timlinux commented Jun 2, 2018

I tried to make a partner with no logo (dumb I know :-P ) and then associate it with my theme. When I pressed activate in admin I got this error:

Traceback (most recent call last): File "/usr/src/geonode/geonode/client/admin_actions.py",
 line 54, in enable_theme value = activate_theme(theme) 
File "/usr/src/geonode/geonode/client/utils.py", line 164, in activate_theme theme_css_content = t.render({'theme': theme}) 
File "/usr/local/lib/python2.7/site-packages/django/template/backends/django.py", line 66, in render return self.template.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 207, in render return self._render(context) 
File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) 
File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) 
File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) 
File "/usr/local/lib/python2.7/site-packages/django/template/defaulttags.py", line 322, in render return nodelist.render(context) 
File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) 
File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) 
File "/usr/local/lib/python2.7/site-packages/django/template/defaulttags.py", line 216, in render nodelist.append(node.render_annotated(context)) 
File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) 
File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 1040, in render output = self.filter_expression.resolve(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 708, in resolve obj = self.var.resolve(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 849, in resolve value = self._resolve_lookup(context) 
File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 890, in _resolve_lookup current = getattr(current, bit) 
File "/usr/local/lib/python2.7/site-packages/django/db/models/fields/files.py", line 69, in url self._require_file() 
File "/usr/local/lib/python2.7/site-packages/django/db/models/fields/files.py", line 46, in _require_file raise ValueError("The '%s' attribute has no file associated with it." % self.field.name) 
ValueError: The 'logo' attribute has no file associated with it.

Removing the partner from the theme, saving it and then activating worked successfully.

CC @afabiani

@afabiani afabiani self-assigned this Jun 4, 2018
@afabiani afabiani added the bug label Jun 4, 2018
@afabiani afabiani added minor A low priority issue which might affect only some users and /or not the main functionality and removed bug labels Sep 4, 2018
@afabiani afabiani closed this as completed Nov 6, 2018
@afabiani afabiani added the tested Issue has been tested on named setups label Nov 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
minor A low priority issue which might affect only some users and /or not the main functionality tested Issue has been tested on named setups
Projects
None yet
Development

No branches or pull requests

2 participants