vikas.gulati's profile - activity

Regarding mobile detection without the request object. That would be easily handled with the get_flavous() function provided by django_mobile (as it sets the flavour in middleware itself.)

But I would need to keep my newly created loader (by subclassing askbot.skins.loaders.Loader) at the beginning of the TEMPLATE_LOADERS property and askbot won't allow any loader before the askbot.skins.loaders.Loader. Also there seems to be no way to turn off the startup tests and hence I won't be able to use my custom loader.

I'm trying to integrate django_mobile with my askbot app. But I'm unable to integrate it because django_mobile's custom template_loader is not identified by coffin and is ignored.

It throws this warning UserWarning:

Cannot translate loader: django_mobile.loader.Loader

My TEMPLATE_LOADERS setting is something like this:

TEMPLATE_LOADERS = (
    'askbot.skins.loaders.Loader',
    'django_mobile.loader.Loader',
    'django.template.loaders.filesystem.Loader',
    'django.template.loaders.app_directories.Loader'
)

I have tried tracing it down and fixing it but haven't yet hit a solution. What I could workout so far is this.

Coffin translates each of the template loader into a corresponding Jinja loader and warns if it can't be translated. This is where the translation is done. Now coffin can't find a suitable translation for 'django_mobile.loader.Loader' as it only translates some specific loaders with jinja_loader_from_django_loader.

What could be done to solve this?

whats the fix for this? your link returns 404!

what i did was to override the process_vote method and change the line which says:

score_delta = vote.cancel()
response_data['count'] = post.score + score_delta
response_data['status'] = 1 #this means "cancel"

to this:

before_vote = vote.vote

if (before_vote<0 and vote_direction == 'up') or (before_vote>0 and vote_direction == 'down'):
    score_delta = vote.cancel()
    response_data['count'] = post.score + score_delta
    response_data['status'] = 1 #this means "cancel"

desired behavior should be that previous vote shall only be cancelled if my current vote and old vote are opposites otherwise it shouldn't.

to tackle this situation i had to override the process_vote method and added a check before vote.cancel() as mentioned below in my answer.

when i try to upvote a post that i have upvoted previously the previous vote gets cancelled and score gets reduced.

same problem occurs when i try to downvote a post that i have previously downvoted. Is this the desired behavior?