Odoo Help


This community is for beginners and experts willing to share their Odoo knowledge. It's not a forum to discuss ideas, but a knowledge base of questions and their answers.


Fixing server errors during theming

Bruno Matthys
on 2/27/15, 1:42 PM 892 views

I'm creating a theme but sometimes I make mistakes. This usually results in an error 500 that I can fix but not this time. I'm trying all kinds of stuff as I have no manual meaning errors are frequent.

500: Internal Server Error
Template 'web.assets_common' not found

..., line 190, in get_template raise QWebTemplateNotFound("Template %r not found" % name, template=origin_template) QWebTemplateNotFound: Template 'web.assets_common' not found

I was trying something like
<?xml version="1.0" encoding="utf-8"?>

        <!--template id="assets" name="Assets" inherit_id="web.assets_common" active="True" >
            <xpath expr="." position="replace">
                <script type="text/javascript" src="/web/static/lib/underscore/underscore.js"/>

I need some tips and tricks on how to handle problems like these. Ideally I would like to disable this theme via command line, or enable another one I know works. This is just one solution, maybe I should go into the database and fix there? I'm a bit lost as I can't access my backend anymore either.


Thanks Luke, I don't have enough karma yet to comment so I'll reply here. I requested access on the config files, my username also needs access to the database so once I get that and have tried your proposals I'll get back to you. EDIT: someone pls accept Luke's answer cheers.

Bruno Matthys
on 2/28/15, 5:53 AM

Accepted his answer for you.

on 3/2/15, 7:31 AM


No problem!

Luke Branch
on 3/3/15, 7:47 AM

Luke Branch

--Luke Branch--
| 6 7 8
Mui Wo, Lantau, Hong Kong
--Luke Branch--


Luke Branch
On 2/27/15, 10:45 PM


What I would recommend is moving the theme directory to another directory name in your local filesystem. For example if you have a module directory called website_multi_image that you're working on you could do the following:

sudo mv /opt/odoo/custom/addons/website_multi_image /opt/odoo/custom/addons/website_multi_image_BACKUP

you should then be able to restart your odoo-server from the command line (or openerp-server depending on your setup) and access your backend again. This is a workaround i've used countless times when developing odoo theme modules.

If the issue is really persistent then you could try reverting or fixing the changes you made that threw the error in the local filesystem and then upgrading the module only at the command line. This involves starting the server with the following structure (eg. using website_multi_image) for example:

./openerp-server --update=website_multi_image -c /etc/odoo-server.conf

Please comment back if you run into any issues with the above methods. I'd also recommend getting on the pre-order for this book:


I believe this will be targeting developers and it looks like it will be a great resource for theme development.

Accepted your answer since Bruno requested this. Keep up the good work Luke! :)

on 3/2/15, 7:31 AM



Luke Branch
on 3/3/15, 7:47 AM

Your Answer

Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!

About This Community

This community is for professionals and enthusiasts of our products and services. Read Guidelines

Question tools

1 follower(s)


Asked: 2/27/15, 1:42 PM
Seen: 892 times
Last updated: 3/16/15, 8:10 AM