Fabien Meghazi's profile - activity

In an askbot customization, I ensured that the real_name field is always filled in, the username field contains the email address and is used as login.

Is there a way to use the real_name field instead of username in the screens ?

If possible I'd prefer not to change the templates because I manage to do all my customization in the askbot instance without touching to the templates.

Replying to myself, I could trace the id of the thread causing problem at File "/usr/local/lib/python2.7/dist-packages/askbot/models/question.py", line 586, I used the admin in order to delete the thread and now the user pages are ok. So it was a relation missing. Not sure how it could happen as they are foreign key checks in postgres, ...

On an askbot running pip version 0.7.48, I've got an exception on the profile page of 3 users. I don't get the relation between those three user, I guess they have a broken relation or something but I don't know how to trace it.

Here's the traceback:

  File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 111, in get_response
    response = callback(request, *callback_args, **callback_kwargs)

  File "/usr/local/lib/python2.7/dist-packages/askbot/views/users.py", line 1123, in user
    return user_view_func(request, profile_owner, context)

  File "/usr/local/lib/python2.7/dist-packages/askbot/views/users.py", line 531, in user_stats
    return render(request, 'user_profile/user_stats.html', context)

  File "/usr/local/lib/python2.7/dist-packages/django/shortcuts/__init__.py", line 44, in render
    return HttpResponse(loader.render_to_string(*args, **kwargs),

  File "/usr/local/lib/python2.7/dist-packages/django/template/loader.py", line 176, in render_to_string
    return t.render(context_instance)

  File "/usr/local/lib/python2.7/dist-packages/coffin/template/__init__.py", line 55, in render
    return super(Template, self).render(**context)

  File "/usr/local/lib/python2.7/dist-packages/jinja2/environment.py", line 894, in render
    return self.environment.handle_exception(exc_info, True)

  File "/usr/local/lib/python2.7/dist-packages/askbot/templates/user_profile/user_stats.html", line 3, in top-level template code
    {% import "user_profile/macros.html" as user_profile_macros %}

  File "/usr/local/lib/python2.7/dist-packages/askbot/templates/user_profile/user.html", line 1, in top-level template code
    {% extends "one_column_body.html" %}

  File "/usr/local/lib/python2.7/dist-packages/askbot/templates/one_column_body.html", line 1, in top-level template code
    {% extends "base.html" %}

  File "/usr/local/lib/python2.7/dist-packages/askbot/templates/base.html", line 53, in top-level template code
    {% block body %}

  File "/usr/local/lib/python2.7/dist-packages/askbot/templates/one_column_body.html", line 5, in block "body"
    {% block content%}

  File "/usr/local/lib/python2.7/dist-packages/askbot/templates/user_profile/user.html", line 17, in block "content"
    {% block usercontent %}

  File "/usr/local/lib/python2.7/dist-packages/askbot/templates/user_profile/user_stats.html", line 131, in block "usercontent"
    href="{{ award.content_object.get_absolute_url() }}"

  File "/usr/local/lib/python2.7/dist-packages/django/utils/functional.py", line 11, in _curried
    return _curried_func(*(args+moreargs), **dict(kwargs, **morekwargs))

  File "/usr/local/lib/python2.7/dist-packages/django/db/models/base.py", line 883, in get_absolute_url
    return settings.ABSOLUTE_URL_OVERRIDES.get('%s.%s' % (opts.app_label, opts.module_name), func)(self, *args, **kwargs)

  File "/usr/local/lib/python2.7/dist-packages/askbot/models/post.py", line 759, in get_absolute_url
    question_post = self.thread._question_post()

  File "/usr/local/lib/python2.7/dist-packages/askbot/models/question.py", line 586, in _question_post
    self._question_cache = Post.objects.get(post_type='question', thread=self)

  File "/usr/local/lib/python2.7/dist-packages/django/db/models/manager.py", line 131, in get
    return self.get_query_set().get(*args, **kwargs)

  File "/usr/local/lib/python2.7/dist-packages/django/db/models/query.py", line 367, in get
    % self.model._meta.object_name)

DoesNotExist: Post matching query does not exist.

Yes, I confirm. I migrated to 0.7.48 and the problem has gone. Thanks !

At the time of writing, askbot 0.7.48 is available on pypi but it is not mentioned in the changelog [1]. I checked the diff between 0.7.47 and 0.7.48 and saw javascript debugger statements in the code [2].

I am currently testing 0.7.47 and I'm experiencing some troubles that doesn't seem to be fixed in 0.7.48 but I can't be 100% sure without migrating.

Is 0.7.48 supposed to be stable besides those debugger leftovers ?

[1] http://askbot.org/doc/changelog.html

[2] https://github.com/ASKBOT/askbot-devel/compare/0.7.47...0.7.48#L45R2079

Using askbot 0.7.47 installed from pip.

Whenever someone tries to retag a question, a "Sorry, something is not right here" overlay appears and I can notice this traceback on the server :

/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py TIME: 2013-01-31 16:57:53,083 MSG: base.py:handle_uncaught_exception:215 Internal Server Error: /questions/64/retag/
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 111, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
  File "/usr/local/lib/python2.7/dist-packages/django/contrib/auth/decorators.py", line 20, in _wrapped_view
    return view_func(request, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/django/views/decorators/csrf.py", line 77, in wrapped_view
    return view_func(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/askbot/views/writers.py", line 326, in retag_question
    if request.user.message_set.count() > 0:
AttributeError: 'RelatedObjectSimulator' object has no attribute 'count'

Is this a known problem ? If true, is there a way to solve it ?

Ok, what I was searching for was not backend specific at all. I found the answer here : http://stackoverflow.com/questions/2787650/manually-logging-in-a-user-without-password

Ok, what I was searching for was not backend specific at all. I found the answer here : http://stackoverflow.com/questions/2787650/manually-logging-in-a-user-without-password

In fact, all the code I need is in the openid backend included in askbot. I just need to figure out how to call some parts from my view directly plugged in url.py. No, I don't come from rails.

Is it possible to add a custom web controller in an askbot instance in order to respond to an url and login users using a custom login scheme.

I'm currently trying to add the code in url.py, is there a better place to put the controller's code ?

Also, how can I programmatically create a user and/or authenticate users from a custom controller ?

You're right. I forgot about running in strandalone in order to have helpful debug information. This topic helped me too : http://askbot.org/en/question/7499/askbot_extra_skins_dir-settings-stalls-model/

Sorry about my previous message, it is incomplete. Running the group_messaging migration command actually solved the first error (relation does not exists). Thanks ! I still experience the second problem when updating a user (Key (id)=(xxx) is still referenced from table "askbot_groupmembership").

I ran manage.py migrate [...] with the following listed commands : group_messaging, longerusername, robots. Those were the missing migrations according to migrate --list. According to the message I guess only group_messaging was relevant. Anyway, I restarted the server and I still have the exact same errors. Running python manage.py migrate --all --fake reports nothing to migrate for all targets. Any idea ?

How can I add an oauth2 custom login provider to askbot ?

I grepped askbot code and it seems that it supports oauth2, right ?

askbot/deps/django_authopenid/util.py:import oauth2 as oauth

Previous comment is true. I had the same traceback and when enabling the debug mode in settings.py it revealed another problem. See http://askbot.org/en/question/9815/database-integrityerror-in-admin/

Previous comment is true. I had the same traceback and when enabling the debug mode in settings.py it revealed another problem. See http://askbot.org/en/question/9815/database-integrityerror-in-admin/

I have exactly the very same traceback when saving or deleting a user from the admin panel. I enabled the debug mode in settings.py and it revealed a completely different problem when doing the same operation (updating/deleting users). See http://askbot.org/en/question/9815/database-integrityerror-in-admin/