pombreda / django-page-cms Goto Github PK

Hello,

I'm not sure If this question should appear in the Issues list, but hope
someone finds it useful (maybe). I didn't find any group for posting question.

Are you planning removing the page id from url ? (just for cleaner URL)
This might be achieved if there was unique slug for each language, which
is in your plans.

Thanks for amazing (and continuously updated!) project!

Patch creates class TinyMCE in admin/widgets.py. 
* Requires the existence of PAGES_MEDIA_URL + 'tiny_mce/tiny_mce.js'
* adds templates/admin/pages/page/widgets/tinymce.html for tinyMCE
configuration
* language should work, but not tested
* passes context variable PAGES_MEDIA_URL that is not used, but could be
useful for including other scripts.

What steps will reproduce the problem?
1. Created a page with empty slug

What is the expected output? What do you see instead?
This page should be root page. But django-page-cms shows top-most page as 
both index and slug page. So if i create page with slug "main", it will be 
available both under "/" and "/main/", that's not good.

What version of the product are you using? On what operating system?
Current SVN (r357), django 1.0.2, python 2.5, windows

Please provide any additional information below.

Django-page-cms as of Revision: 168

When I add a new page in the tree by clicking the right-down arrow, I am
getting a new page in the root added instead of new sub-page.

The project has got lots of improvements recently. This is great! Thanks!

I think that for some questions is better to have a list.
What do you think?

The order on which the translations apper in the admin is not always the
same. You can have one page traslated as en|es an the other one as es|en.

I think that there should be one more 404 raising after line 30 like this:


            current_page = pages[0]
        template_name = current_page.get_template()
    else:
        current_page = None
        raise Http404
    return template_name, locals()
details = auto_render(details)


The function returns rendered page even the variable "pages" is not
defined. I think that's not what we really want.

Hi,

It would be great if I could specify meta keywords/description for each
page (in each language).

Are you planning to include this option?

Thanks for great project!

Robert

In the previous version I have the cms runnig but It does not save the
title. It seems to me that title needs also a placeholder, could be?

1 .I've just updated to the last version and created a new database.
2. Entered in admin
3. Created languages en/en es/es

But I can't create any page.

I using Django 1.0

Sites support is a cool feature of Django, but it is optional.

Django docs says:
Django comes with an optional “sites” framework. It’s a hook for 
associating objects and functionality to particular Web sites, and it’s a 
holding place for the domain names and “verbose” names of your Django-
powered sites.

Default Django policy (url configurations, all examples in docs, etc) 
doesn't behave differently on differend sites. And this feature is good, 
but not needed for most of projects.

So it is not convinient to modify all project pages if i move to new 
domain, add alias.

More on this, it is possible in Django to disable sites at all.

It will be very good, if there will be option to disable sites support in 
django-page-cms.

Thank you.

What steps will reproduce the problem?
1. Add 'django.contrib.csrf.middleware.CsrfMiddleware' to MIDDLEWARE_CLASSES
2. In the admin interface, move a page or change its published status in
the list view

What is the expected output? What do you see instead?
Expect page to be moved or status to change, instead receive 403 Forbidden
response

What version of the product are you using? On what operating system?
Pages rev. 339, MPTT rev. 119, Opensuse 11

Please provide any additional information below.
http://docs.djangoproject.com/en/dev/ref/contrib/csrf/
Is there a way to send the CSRF token in the calls to move-page and
change-status?

Hi,

I'm currently evaluating a few Django CMSs and really like django-page-cms.
The site that I'm responsible for has a few hundred pages, which makes the
page tree quite overloaded.

Attached is a patch which implements a collapsible tree UI with the help of
some JavaScript/jQuery code. The tree remembers the state of subtrees when
collapsing and (for lack of a better word) uncollapsing. The state of the
whole tree is saved in a cookie when unloading the page and restored when
returning to it. I had to implement a method get_ancestors_list in the Page
model which returns a list of ancestors. I suspect this to be quite
query-intensive, but as the page tree is not supposed to be on a
public-facing page, I don't consider it to be a big problem.

All the JavaScript code is in media/javascript/tree_collapse.js. In there
is also a copy of the jQuery Cookie plugin.

I've got some other things like TinyMCE integration and getting rid of
site-wide slug uniqueness in favor of uniqueness between siblings, but
those aren't quite ready for a patch, yet :)

What steps will reproduce the problem?
1. Add a new page
2. Use django admin to edit that page
3. See the following traceback


Traceback:
File "/usr/lib/python2.5/site-packages/django/core/handlers/base.py" in
get_response
  82.                 response = callback(request, *callback_args,
**callback_kwargs)
File
"/usr/lib/python2.5/site-packages/django/contrib/admin/views/decorators.py"
in _checklogin
  56.             return view_func(request, *args, **kwargs)
File "/var/www/thepurldistrict/pages/utils.py" in _dec
  9.         response = func(request, *args, **kwargs)
File "/var/www/thepurldistrict/pages/admin_views.py" in modify
  124.         traduction_language = Language.objects.exclude(pk=l.id)

Exception Type: AttributeError at /admin/pages/page/1/
Exception Value: 'str' object has no attribute 'id'

See subject. If settings.PAGE_TEMPLATES is not defined, the template select
box is not rendered, which causes the javascript code on the change page to
bomb out when it tries to access it. Checking if the element exists before
accessing it solves the problem. Patch attached.

When I try to run this programin on the environment of sqlite3.

I got this error

Environment:

Request Method: GET
Request URL: http://127.0.0.1:8000/pages/
Django Version: 0.97-pre-SVN-7519
Python Version: 2.5.2
Installed Applications:
['django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.admin',
 'pages',
 'hierarchical']
Installed Middleware:
('django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.locale.LocaleMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.middleware.doc.XViewMiddleware')


Traceback:
File "/Users/ygpark/lib/django_trunk/django/core/handlers/base.py" in 
get_response
  82.                 response = callback(request, *callback_args, **callback_kwargs)
File "/Users/ygpark/lib/django-page-cms/utils.py" in _dec
  9.         response = func(request, *args, **kwargs)
File "/Users/ygpark/lib/django-page-cms/pages/views.py" in details
  12.     pages = HierarchicalNode.get_first_level_objects(Page)
File "/Users/ygpark/lib/django-page-cms/hierarchical/models.py" in 
get_first_level_objects
  98.         return [obj.object for obj in objs]
File "/Users/ygpark/lib/django_trunk/django/db/models/query.py" in _result_iter
  78.                 self._fill_cache()
File "/Users/ygpark/lib/django_trunk/django/db/models/query.py" in _fill_cache
  490.                     self._result_cache.append(self._iter.next())
File "/Users/ygpark/lib/django_trunk/django/db/models/query.py" in iterator
  162.         for row in self.query.results_iter():
File "/Users/ygpark/lib/django_trunk/django/db/models/sql/query.py" in 
results_iter
  200.         for rows in self.execute_sql(MULTI):
File "/Users/ygpark/lib/django_trunk/django/db/models/sql/query.py" in 
execute_sql
  1466.         cursor.execute(sql, params)
File "/Users/ygpark/lib/django_trunk/django/db/backends/util.py" in execute
  18.             return self.cursor.execute(sql, params)
File "/Users/ygpark/lib/django_trunk/django/db/backends/sqlite3/base.py" in 
execute
  136.         return Database.Cursor.execute(self, query, params)

Exception Type: OperationalError at /pages/
Exception Value: near "order": syntax error

Proberbly, this problem comes from sqlite's sql syntax.

Can you check that out

I'm playing a bit with show_content tag.

Perhaps I'm trying to do the wrong thing, but it was supposed to give me a
content bit from the cms

That is 


       {% show_content "test" "body" lang %} 

should give me the content named body in lang given a page whos slug is test

It fails, but I'm not sure if this is a bug or my fault.

What steps will reproduce the problem?
1. Install django-page-cms
2. Run manage.py syncdb
3. Attempt to use software

Should there be languages defined in pages_languages table?  If not, what
should I do to add them?  With an empty pages_languages table, the software
gives tracebacks for almost any action.

What steps will reproduce the problem?
------------------------------------------------
1. Clean install of Django 0.96.2 on Mac OS X
2. svn checkout http://django-page-cms.googlecode.com/svn/trunk/ django-
page-cms

3. python manage.py syncdb

What is the expected output? 
------------------------------------------------
For the sync to conclude successfully

What do you see instead?
------------------------------------------------
Traceback (most recent call last):
  File "manage.py", line 11, in <module>
    execute_manager(settings)
  File "/Library/Python/2.5/site-packages/django/core/management/
__init__.py", line 301, in execute_manager
    utility.execute()
  File "/Library/Python/2.5/site-packages/django/core/management/
__init__.py", line 248, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/Library/Python/2.5/site-packages/django/core/management/base.py", 
line 77, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/Library/Python/2.5/site-packages/django/core/management/base.py", 
line 90, in execute
    self.validate()
  File "/Library/Python/2.5/site-packages/django/core/management/base.py", 
line 117, in validate
    num_errors = get_validation_errors(s, app)
  File "/Library/Python/2.5/site-packages/django/core/management/
validation.py", line 28, in get_validation_errors
    for (app_name, error) in get_app_errors().items():
  File "/Library/Python/2.5/site-packages/django/db/models/loading.py", 
line 128, in get_app_errors
    self._populate()
  File "/Library/Python/2.5/site-packages/django/db/models/loading.py", 
line 57, in _populate
    self.load_app(app_name, True)
  File "/Library/Python/2.5/site-packages/django/db/models/loading.py", 
line 72, in load_app
    mod = __import__(app_name, {}, {}, ['models'])
  File "/Users/ucantblamem/Sites/django-page-cms/pages/models.py", line 
44, in <module>
    class Page(models.Model):
  File "/Users/ucantblamem/Sites/django-page-cms/pages/models.py", line 
59, in Page
    status = models.IntegerField(choices=STATUSES, radio_admin=True, 
default=0)
  File "/Library/Python/2.5/site-packages/django/utils/maxlength.py", line 
47, in inner
    func(self, *args, **kwargs)
  File "/Library/Python/2.5/site-packages/django/utils/maxlength.py", line 
47, in inner
    func(self, *args, **kwargs)
TypeError: __init__() got an unexpected keyword argument 'radio_admin'



What version of the product are you using? 
------------------------------------------------
Latest - Revision 39

On what operating system?
------------------------------------------------
Mac OS X Leopard - as a non-administrative user.

Please provide any additional information below.
------------------------------------------------
I tried taking the radio_admin=True option out of the IntegerField() and 
tried the syncdb again, which resulted in this error:

Creating table auth_permission
Creating table auth_group
Creating table auth_user
Creating table auth_message
Creating table django_content_type
Creating table django_session
Creating table django_admin_log
Creating table pages_language
Creating table pages_page
Creating table pages_content
Creating table hierarchical_hierarchicalnode
Creating table hierarchical_hierarchicalobject

You just installed Django's auth system, which means you don't have any 
superusers defined.
Would you like to create one now? (yes/no): yes
Username (Leave blank to use 'ucantblamem'): admin
E-mail address: [email protected]
Password: 
Password (again): 
Superuser created successfully.
Installing index for auth.Permission model
Installing index for auth.Message model
Installing index for admin.LogEntry model
Installing index for pages.Page model
Installing index for pages.Content model
Installing index for hierarchical.HierarchicalNode model
Installing index for hierarchical.HierarchicalObject model
Installing json fixture 'initial_data' from '/Users/ucantblamem/Sites/
django-page-cms/pages/fixtures'.
Problem installing fixture '/Users/ucantblamem/Sites/django-page-cms/pages/
fixtures/initial_data.json': Traceback (most recent call last):
  File "/Library/Python/2.5/site-packages/django/core/management/commands/
loaddata.py", line 112, in handle
    obj.save()
  File "/Library/Python/2.5/site-packages/django/core/serializers/
base.py", line 170, in save
    models.Model.save_base(self.object, raw=True)
  File "/Library/Python/2.5/site-packages/django/db/models/base.py", line 
320, in save_base
    manager.filter(pk=pk_val)._update(values)
  File "/Library/Python/2.5/site-packages/django/db/models/query.py", line 
420, in _update
    query.execute_sql(None)
  File "/Library/Python/2.5/site-packages/django/db/models/sql/
subqueries.py", line 112, in execute_sql
    super(UpdateQuery, self).execute_sql(result_type)
  File "/Library/Python/2.5/site-packages/django/db/models/sql/query.py", 
line 1608, in execute_sql
    cursor.execute(sql, params)
  File "/Library/Python/2.5/site-packages/django/db/backends/util.py", 
line 18, in execute
    return self.cursor.execute(sql, params)
  File "/Library/Python/2.5/site-packages/django/db/backends/sqlite3/
base.py", line 144, in execute
    return Database.Cursor.execute(self, query, params)
IntegrityError: columns app_label, model are not unique


I also tried installing the very latest version of Django from the 
repository, but I had the same issues.

Any ideas? Thanks.

What steps will reproduce the problem?

Cancel design view and try to get the data - a javascript alert appears: 
this.parent is null.

i'm using jquery 1.2.6

What steps will reproduce the problem?
1. Installation steps
2.
3.

What is the expected output? What do you see instead?

Template not found, 404s in admin interface

What version of the product are you using? On what operating system?

0.2.1

Please provide any additional information below.

Ok, you just need to finish the documentation. 

Gotta put index.html and debug.html in a template root (tsk, tsk. Use a
folder named pages)

Gotta symlink /pages/media/pages/ into your media.

What steps will reproduce the problem?
1. Follow installation steps
2. Run webserver

What is the expected output? What do you see instead?

webserver does not run. Does not find gettext_noop.

What version of the product are you using? On what operating system?

django-page-cms 0.2.1
Django 1.0.2

Please provide any additional information below.

Being a dumb american, i put in 'English' instead of gettext_noop('English')

The actuall code gives you lot of flexibillity, but for small cms
application I'd like best the previous one, where you could see the page
structure very easelly.

It could be possible to mantain both features?

As it seems to me, the django-mptt application provides the same functionality 
that the currently 
used hierarchical appication (and more). Maybe should consider refactoring to 
use django-mptt 
instead? This would mean less effort to the hierarchical stuff and more effort 
to the pages/CMS 
part. Just an idea though.

I get a strange error when trying to add a page:

Request Method:     POST
Request URL:    http://localhost:8000/admin/pages/page/add/
Exception Type:     AttributeError
Exception Value:    

'RelatedObject' object has no attribute 'unique'

Exception Location: 
/PATH/env/lib/python2.5/site-packages/django/forms/models.py in
validate_unique, line 251

Any ideas?

What steps will reproduce the problem?
1. Create a page, use "test" as a slug
2. Save
3. Modify slug

What is the expected output? What do you see instead?
"View" link now points to "test".
Expected to see new url.

What version of the product are you using? On what operating system?
Current SVN (r351), django 1.0.2, python 2.5, windows

http://code.google.com/p/django-page-cms/source/browse/trunk/pages/__init__.py

(SInce you're doing minor fixes today)

1. Download the last trunk
2. syncdb
3. runs the server

It gives:
{{
ImportError
Exception Value:    

cannot import name Language

Exception Location: 
/django-page-cms-read-only/pages/templatetags/pages_tags.py in <module>, line 4
}}}

it says

     from pages.pages_settings import *

shoud say

     from pages.settings import *

What steps will reproduce the problem?
1. Get code from svn repository
2. Run syncdb, runserver, Page already registered error
3. Comment out mptt.register() (Why do I need to do this? Is something
wrong at this step itself?) in model, then get this error

+ If I comment out admin.autodiscover() in my urls.py then things work of
course, but nothing to do in Admin then :(

What is the expected output? What do you see instead?
+ Working admin, but get this error

What version of the product are you using? On what operating system?
+ Trunk, Mac OSX, with Django 1.0.1



Please provide any additional information below.
----------------
From settings.py
----------------
sys.path.append(os.path.join(__dirname__, 'lib/rc_cms/'))
PAGE_TAGGING = True
LANGUAGES = (
    ('en', 'English'),
)
DEFAULT_PAGE_TEMPLATE = 'tivix_com/resourcecenter.html'

-------------
ERROR
-------------
Environment:

Request Method: GET
Request URL: http://localhost:8000/pages/
Django Version: 1.0.1 final
Python Version: 2.5.1
Installed Applications:
['django.contrib.auth',
 'django.contrib.humanize',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.sites',
 'django.contrib.admin',
 'registration',
 'tivix_com',
 'accounts',
 'apps.box_net',
 'apps.paypal',
 'apps.paypal',
 'apps.crm',
 'lib.rc_cms.pages']
Installed Middleware:
('django.middleware.common.CommonMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.middleware.transaction.TransactionMiddleware',
 'accounts.middleware.AssociatedAccountMiddleWare')


Traceback:
File "/Library/Python/2.5/site-packages/django/core/handlers/base.py" in
get_response
  77.                     request.path_info)
File "/Library/Python/2.5/site-packages/django/core/urlresolvers.py" in resolve
  179.             for pattern in self.urlconf_module.urlpatterns:
File "/Library/Python/2.5/site-packages/django/core/urlresolvers.py" in
_get_urlconf_module
  198.             self._urlconf_module = __import__(self.urlconf_name, {},
{}, [''])
File "/Users/chachra/Dropbox/tivix/code/dev/tivix/urls.py" in <module>
  8. admin.autodiscover()
File "/Library/Python/2.5/site-packages/django/contrib/admin/__init__.py"
in autodiscover
  40.         __import__("%s.admin" % app)
File
"/Users/chachra/Dropbox/tivix/code/dev/tivix/lib/rc_cms/pages/admin/__init__.py"
in <module>
  19. from pages.admin import widgets
File
"/Users/chachra/Dropbox/tivix/code/dev/tivix/lib/rc_cms/pages/admin/__init__.py"
in <module>
  277. admin.site.register(Page, PageAdmin)
File "/Library/Python/2.5/site-packages/django/contrib/admin/sites.py" in
register
  76.             validate(admin_class, model)
File "/Library/Python/2.5/site-packages/django/contrib/admin/validation.py"
in validate
  25.     validate_base(cls, model)
File "/Library/Python/2.5/site-packages/django/contrib/admin/validation.py"
in validate_base
  179.             check_formfield(cls, model, opts,
"fieldsets[%d][1]['fields']" % idx, field)
File "/Library/Python/2.5/site-packages/django/contrib/admin/validation.py"
in check_formfield
  254.                 "is missing from the form." % (cls.__name__, label,
field))

Exception Type: ImproperlyConfigured at /pages/
Exception Value: 'PageAdmin.fieldsets[1][1]['fields']' refers to field
'tags' that is missing from the form.

>>> Page.objects.create(author=u, parent=p, status=1, template='index.html')

raises following exception:

/home/alexander.ivanov/project/django/1.0.1-final/django/db/models/query.py
in create(self, **kwargs)
    318         obj = self.model(**kwargs)
--> 319         obj.save(force_insert=True)
    320         return obj
<type 'exceptions.TypeError'>: save() got an unexpected keyword argument
'force_insert'

You can solve it like this:
(http://docs.djangoproject.com/en/dev/topics/db/models/#topics-db-models)

    def save(self, force_insert=False, force_update=False):
        do_something()
        super(Blog, self).save(force_insert, force_update) # Call the
"real" save() method.

But I prefer following approach:

    def save(self, *args, **kwargs):
        do_something()
        super(Blog, self).save(*args, **kwargs)

So, here's the patch to fix described problem.

What steps will reproduce the problem?
1. svn checkout http://django-page-cms.googlecode.com/svn/trunk/
django-page-cms
2. cd example/
3. manage.py syncdb
4. manage.py runserver
5. Add a number of Pages, move a page to be a sub page of another
6. Try to expand/hide the sub pages - none appear

tested at time of revision 289 being the most current. In FireFox 3.0.5


What is the expected output? What do you see instead?
Seeing the sub pages for editing/moving

No sub pages seen

What version of the product are you using? On what operating system?
revision 289

What steps will reproduce the problem?
1. create two entries marked as draft
2. Move on entry into another


What is the expected output? What do you see instead?
It should nest the second entry in then first one, but the second entry
simply dissapears.

What steps will reproduce the problem?

1. Login to Django with a basic user account. One which only has
permissions to view a couple of pages.
2. Click on "Pages" under the "Pages" section
3. You get the following error text:

==================================
Request Method:     GET
Request URL:    http://localhost:8000/admin/pages/page/
Exception Type:     TemplateSyntaxError
Exception Value:    

Caught an exception while rendering: global name 'page' is not defined

Original Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/django/template/debug.py", line
71, in render_node
    result = node.render(context)
  File "/usr/lib/python2.5/site-packages/django/template/defaulttags.py",
line 148, in render
    nodelist.append(node.render(context))
  File "/usr/lib/python2.5/site-packages/django/template/__init__.py", line
915, in render
    dict = func(*args)
  File
"/home/user/Development/django-page-cms/pages/templatetags/pages_tags.py",
line 33, in show_admin_menu
  File "/home/user/Development/contentedcms/pages/models.py", line 141, in
has_page_permission
    if page.id in permission:
NameError: global name 'page' is not defined
==================================

I fixed this by modifying the function has_page_permission in models.py
(r248). Change line 167 from:
            if page.id in permission:
to:
            if self.id in permission:

In my oppinion the previous way of moving pages through the tree was more
user friendly that the actual one. Perhaps it would be nice have both and
choose with one to use as a settings parameter.

svn checkout grabbed some 3rd party apps (mptt, tagging, ..) and placed them in 
the root 
directory.  You should move them to a subfolder "external_apps" or so. (Yeah, 
maybe that's just for 
my satisfaction ;)

Instead of looking for templates index.html and debug.html at the template
root (which is bound to cause collisions with existing apps), put them in a
folder called pages. 

The third second level heading reads:

Template context processors and Middlwares

It should be "Middlewares".

Patch a SVN checkout of django-page-cms (currently - revision 39) with the
provided diff, in order to make it work with newforms and newforms-admin,
which are now part of Django's trunk (currently - revision 8194).

How to use: 
 1. You'll need 'patch' or a compatible utility, which can process unified
diffs.
 2. Checkout trunk with:

svn checkout http://django-page-cms.googlecode.com/svn/trunk/
django-page-cms-read-only

 3. Save the attached patch file and apply it like this:

gunzi < /path/to/django-page-cms/django-page-cms.newforms.patch.gz | patch -p0

 4. Go to django-page-cms-read-only/ and run:

./manage.py syncdb
./manager.py runserver

There should be no errors.
Enjoy!

Using the "legacy" installation, i.e. including the pages app and hierarchical 
app to an existing 
project), then running manage.py syncdb, will produce a database integrity 
error. The traceback 
itself is included below.

I think this problem should be solved even though this installation method is 
considered "legacy" 
for reasons unknown to me. The Django way is to reuse applications, not 
projects, so actually the 
legacy installation method should be made the primary or maybe even the only 
(documented( 
one.

Here's the traceback:

$ ./manage.py syncdb
Installing json fixture 'initial_data' from 
'/Users/erik/python-packages/django-page-
cms/pages/fixtures'.
Problem installing fixture '/Users/erik/python-packages/django-page-
cms/pages/fixtures/initial_data.json': Traceback (most recent call last):
  File "/opt/local/lib/python2.5/site-
packages/django/core/management/commands/loaddata.py", line 112, in handle
    obj.save()
  File "/opt/local/lib/python2.5/site-packages/django/core/serializers/base.py", line 168, in 
save
    models.Model.save_base(self.object, raw=True)
  File "/opt/local/lib/python2.5/site-packages/django/db/models/base.py", line 317, in 
save_base
    manager.filter(pk=pk_val)._update(values)
  File "/opt/local/lib/python2.5/site-packages/django/db/models/query.py", line 315, in 
_update
    query.execute_sql(None)
  File "/opt/local/lib/python2.5/site-packages/django/db/models/sql/subqueries.py", line 112, 
in execute_sql
    super(UpdateQuery, self).execute_sql(result_type)
  File "/opt/local/lib/python2.5/site-packages/django/db/models/sql/query.py", line 1474, in 
execute_sql
    cursor.execute(sql, params)
  File "/opt/local/lib/python2.5/site-packages/django/db/backends/util.py", line 18, in execute
    return self.cursor.execute(sql, params)
IntegrityError: duplicate key violates unique constraint 
"django_content_type_app_label_key"

[deleted issue]

What steps will reproduce the problem?
1. Don't set 'Sites' correctly
2.
3.

What is the expected output? What do you see instead?

when you go to view a page nothing shows up


What version of the product are you using? On what operating system?

r300

Please provide any additional information below.

Just add something to the FAQ, please. It took me a while to figure that out.

Request Method:     GET
Request URL:    http://localhost:8000/admin/pages/page/add/
Exception Type:     ViewDoesNotExist
Exception Value:    

Could not import pages.admin_views. Error was: cannot import name newforms

I have found that the actual syntax does not work. I atatch patch.

ProgrammingError at /admin/hierarchical/hierarchicalobject/add/
operator does not exist: integer ~~* unknown LINE 1: ...RE
("hierarchical_hierarchicalobject"."object_id" ILIKE '' A... ^ HINT: No
operator matches the given name and argument type(s). You might need to add
explicit type casts. 

The hint explains quite well what's wrong. In PostgreSQL 8.3 auto-escaping
is disabled and it seems that when adding a new node, the information is
passed into the SELECT query as strings while they clearly should be
integers. While looking at the traceback it seems that the information
passed in from the from is not converted to integers. Didn't seem to find
if this is actually django-page-cms's fault or that Django itself fails to
correctly check and convert them to int's.

'SELECT
"hierarchical_hierarchicalobject"."id","hierarchical_hierarchicalobject"."node_i
d","hierarchical_hierarchicalobject"."content_type_id","hierarchical_hierarchica
lobject"."object_id"
FROM "hierarchical_hierarchicalobject" INNER JOIN
"hierarchical_hierarchicalnode" AS "hierarchical_hierarchicalobject__node"
ON "hierarchical_hierarchicalobject"."node_id" =
"hierarchical_hierarchicalobject__node"."id" WHERE
("hierarchical_hierarchicalobject"."object_id" ILIKE \'\' AND
"hierarchical_hierarchicalobject__node"."id" ILIKE \'2\' AND
"hierarchical_hierarchicalobject"."content_type_id" = \'43\')'

Here you can clearly see object_id and node.id being strings.
Which seems to be the same as got inputted from new_data:

new_data    
<QueryDict: {u'node': [u'2'], u'csrfmiddlewaretoken':
[u'9cf9a747837d94369947209ea143d53a'], u'content_type': [u'43'],
u'object_id': [u'']}>

Hopefully we can identify where this problem lays exactly and fix it :)
As explained in the title this is PostgreSQL 8.3 (and up) specific.

Thanks for Django-page-cms !

What steps will reproduce the problem?
1. Install the app following the instructions
2. Go to /admin

What is the expected output? What do you see instead?

Get an error to the effect of 
'django.core.context_processors.auth' is required in
TEMPLATE_CONTEXT_PROCESSORS

What version of the product are you using? On what operating system?

0.2.1 download

Please provide any additional information below.

btw, please tag 0.2.1 in svn

It would be nice if a person could work on a page and then set it to go
live at a certain date/time or end at a certain date/time.  This would be
good for promotions, events, etc.

I have attached a patch to implement this functionality.  It was created by
using an svn diff from the base of the project.

thanks,

Brian Morgan

The get_absolute_url method from a Page object used for displaying URLs use
the default language and not the language wanted by the user.

I don't have the rights to edit that page.

For setting up django-page-cms in an existing project, referencing the
settings.py of the default project is helpful. But the we could be more
helpful by directly listing the required settings additions. 

Suggested text:

For settings, add django.core.context_processors.request and
pages.context_processors.media to your TEMPLATE_CONTEXT_PROCESSORS and
django.middleware.locale.LocaleMiddleware middleware to MIDDLEWARE_CLASSES. 
Set DEFAULT_PAGE_TEMPLATE to the name of your default CMS template.