1.3. This means you will have to make sure you serve static files as well as media files on your server. Features deprecated in 2.2 django-dbgettext support The django-dbgettext support has been fully manage.py syncdb python manage.py migrate Up and running! That should be it. Restart your development server using python manage.py runserver and point a web browser to 127.0.0.1:8000 :you should get the django Creating your first CMS Page! That’s it, now the best part: you can start using the CMS! Run your server with python manage.py runserver, then point a web browser to 127.0.0.1:8000/admin/ , and log in using

1.3. This means you will have to make sure you serve static files as well as media files on your server. 2.1.1.3. Features deprecated in 2.2 2.1.1.3.1. django-dbgettext support index modules | next syncdb python manage.py migrate 3.3.3. Up and running! That should be it. Restart your development server using python manage.py runserver and point a web browser to 127.0.0.1:8000 [http://127.0.0.1:8000] Creating your first CMS Page! That’s it, now the best part: you can start using the CMS! Run your server with python manage.py runserver, then point a web browser to 127.0.0.1:8000/admin/ [http://127.0

1.3. This means you will have to make sure you serve static files as well as media files on your server. Warning: If you use Django 1.2.x you will not have a django.contrib.staticfiles app. Instead you manage.py syncdb python manage.py migrate Up and running! That should be it. Restart your development server using python manage.py runserver and point a web browser to 127.0.0.1:8000 :you should get the django Creating your first CMS Page! That’s it. Now the best part: you can start using the CMS! Run your server with python manage.py runserver, then point a web browser to 127.0.0.1:8000/admin/ , and log in using

application is now available directly from the new django CMS page. (Apphooks won’t take effect until the server has restarted, though this is not generally an issue on the runserver, which can handle this automatically 1. Tutorials 17 django cms Documentation, Release 3.0.19.dev1 python manage.py migrate Start the server again. The blog application comes with a django CMS apphook, so add a new django CMS page, and add blog application to it as you did for Polls in the previous tutorial. You may need to restart your server at this point. Publish the new page, and you should find the blog application at work there. You

manage.py syncdb python manage.py migrate Up and running! That should be it. Restart your development server using python manage.py runserver and point a web browser to 127.0.0.1:8000 :you should get the Django Creating your first CMS page! That’s it, now the best part: you can start using the CMS! Run your server with python manage.py runserver, then point a web browser to 127.0.0.1:8000/admin/ , and log in using /1/edit-plugin/2/. Domains, protocols and ports must match. This error is due to the Django test server running on a different port and URL than the main webserver. In your test environment, you can overcome

1.3. This means you will have to make sure you serve static files as well as media files on your server. Warning: If you use Django 1.2.x you will not have a django.contrib.staticfiles app. Instead you correctly: python manage.py cms check Up and running! That should be it. Restart your development server using python manage.py runserver and point a web browser to 127.0.0.1:8000 :you should get the django Creating your first CMS Page! That’s it. Now the best part: you can start using the CMS! Run your server with python manage.py runserver, then point a web browser to 127.0.0.1:8000/admin/ , and log in using

syncdb python manage.py migrate 2.1.4. Up and running! That should be it. Restart your development server using python manage.py runserver and point a web browser to 127.0.0.1:8000 [http://127.0.0.1:8000] Creating your first CMS page! That’s it, now the best part: you can start using the CMS! Run your server with python manage.py runserver, then point a web browser to 127.0.0.1:8000/admin/ [http://127.0 1/edit- plugin/2/. Domains, protocols and ports must match. This error is due to the Django test server running on a different port and URL than the main webserver. In your test environment, you can overcome

1.3. This means you will have to make sure you serve static files as well as media files on your server. Warning If you use Django 1.2.x you will not have a django.contrib.staticfiles app. Instead you correctly: python manage.py cms check 1.3.4. Up and running! That should be it. Restart your development server using python manage.py runserver and point a web browser to 127.0.0.1:8000 [http://127.0.0.1:8000] Creating your first CMS Page! That’s it. Now the best part: you can start using the CMS! Run your server with python manage.py runserver, then point a web browser to 127.0.0.1:8000/admin/ [http://127.0

application is now available directly from the new django CMS page. (Apphooks won’t take effect until the server has restarted, though this is not generally an issue on the runserver, which can handle this automatically Tutorials 17 django cms Documentation, Release 3.1.8.dev1 python manage.py migrate Start the server again. The newsblog application comes with a django CMS apphook, so add a new django CMS page (let’s the new page, and you should find the blog application at work there. You may need to restart your server at this point. You can add new blog posts using the admin, but also have a look at the toolbar.

necessary because we have created a new file containing Python code that won’t be loaded until the server restarts. You only have to do this the first time the new file has been created. Apply the apphook We’ve added a new application so we need to update our database: python manage.py migrate Start the server again. Create a new apphooked page The News & Blog application comes with a django CMS apphook creation Using an apphook Apphook management Apphook menus Apphook permissions Automatically restart server on apphook changes Apphooks and placeholder template tags Complex apphook configuration Attaching