powlo's profile - activity

I have the latest version of askbot from github in a directory called "askbot-devel". I've then run python setup.py develop and the "askbot-setup.exe" to create the site ("askbot-site") alongside the askbot-devel directory.

If I navigate to askbot-site and run

./manage.py test

or

./manage.py test askbot

It ends with

Ran 0 tests in 0.000s

Python 2.7.11, Django 1.8.13

Apologies if I'm missing the obvious.

What version of Askbot are you using? Can you provide steps to reproduce the error?

It would be good if the Askbot docs were presented as a wiki so developers could put notes against paragraphs and so on. I think Django uses something like this on their docs pages. It could be hidden from view by default to prevent viewers being hit by a barrage of comment tags.

There are several typos, style changes and more important missing functionality documentation that I'd like to put in. Askbot needs a mechanism to manage these submissions.

It looks like the documentation shown on this site comes from the git controlled source so I could just make changes and then do a git pull request. However this mechanism would lack any discussion around a documentation issue and those only interested in deploying and not coding might be locked out.

https://github.com/ASKBOT/askbot-devel/pull/160

I can't really comment on whether you should delete questions. Maybe if your database is too big?

ETA: It sounds like you need a feature to disable user created tags. Is that right?

Firstly, this command only deletes tags whose Questions have been deleted, ie removed from the database. If the Question has been marked deleted (ie not visible to users but still visible to administrators in the backend interface) then tags pointing to this question are still valid, so the tag will not be deleted.

So that's possibly why you see the "Did not find any" message.

That being said, the way the database transactions are handled could be improved. I'll submit a patch.

I was able to recreate the problem by having no tags in the db. However, it may also occur under other circumstances, eg if some exception occurs during command execution.

It has an API (https://github.com/e14n/pump.io/blob/master/API.md) but seems to have problems. The user I created was created, but I was bounced with a "Server Error" message. Only when I tried to create the account again did I get "user already exists".

Strange that removing the middleware didn't fix it. You can always try giving ASKBOT_LANGUAGE a value.

You could test the send mail by changing the EMAIL_BACKEND to a file, or console.

See here: https://docs.djangoproject.com/en/dev/topics/email/#email-backends

If i understand the problem correctly, I think it's open to debate as to whether it's a bug. Some people might want to reward their admins for essentially keeping the site clean and up-to-date. And it's also possible that admins might want to reward users for answering their own posts. Making it an option allows site maintainers to set it up how they want. Generally though, I agree, and think that most people would have these set to zero.

I noticed a question on my hosted site that the asker had posted his own (comprehensive) answer for. However, he did not mark the answer as accepted.

Having administrator privileges, I went ahead and marked the answer as accepted.

_{Whether or not it was my place to do so is another matter; for now we'll just assume it was justified for the purpose of establishing context to describe this issue (:}

When I refreshed the page, I noticed that the user had gained 15 karma for his answer being marked as accepted. However, this is not correct; because the user answered his own question, he should not have gotten a karma bonus for the accept.

Also, I noticed that I got 2 karma for accepting the answer, even though it wasn't my question.

I think there are two points here that can become feature requests:

There should be an entry under "Karma Loss and Gain" in the admin interface field which allows the admin to set the karma awarded to a user:

• for accepting their own answer.

• for accepting an answer to a question which is not their own.

@john-smith doesn't seem to work. @john smith (case insensitive) does.

You can limit the logins available through /settings/LOGIN_PROVIDERS/, eg if you only want Facebook logins or Yahoo logins, then enable those and disable all others.

However, I don't believe that Askbot offers any user moderation-before-view, only post moderation, and there is no admin controlled filter that can be applied to user registration email addresses (ie Only Allow: *@MyCompany.com, Block: *@dodgywarez.com)

Both of these things would be a feature request. (Unless someone with more knowledge proves me wrong...!)

I just tried to reproduce this and I can @refer to users that have a space in the title. The url to the users profile should convert the " " to a "-", so "John Smith" becomes http://<site>/users/<user_id>/john-smith/. The user referred to also needs to exist. There can't be a space between the @ and the first character. Comments are not processed dynamically, ie if you @refer to someone that doesn't exist, then at the user so they do exist, the original comment will not pick up that the new user exists and can be legitimately @referred to.

I'm using the latest version from github, v0.7.43. So it's possible that there has been a fix added. What version of askbot are you using?

And what are you seeing when you try to @refer to a user with a space in the user name?

Thanks for that Fitoria it fixed the problem. Is the init_postgresql documented anywhere? I couldn't see it in the online docs. Perhaps a check for postgresql, and a reminder to call the init function, should be part of the askbot automation script? The version of askbot I'm using is that latest git master. And I'm using postgresql v9.1.4.

Is the problem spambots or human spammers? Doesn't Askbot have a Captcha for certain reputation levels?

Also, perhaps you could disable url conversion for a certain reputation level.

This could be applied to both posts and profiles.

A more complex solution might be to have urls hidden in low rep posts (and profiles) pending approval from a moderator.

You can always select the "Unanswered" questions tab.