Evgeny's profile - activity

@dccarson, this will be fixed, thank you!

Sorry, what do you mean by self-building (do you mean self-hosting)? What version of Askbot are you using and how did yo

Sorry, what do you mean by self-building? What version of Askbot are you using and how did you download it?

Of course the accounts from askbot.org are not used on your site, there must be something else.

In a way it's possible: deploy Askbot on your server perhaps "mounted" at some sub-url example.com/qa. If necessary it

I am working with AskBot since 6-months and I have tested the AskBot with Different Linux distro including Ubuntu 16.04, Debian 8, CentOS 7, RHEL 7.

The Askbot have different branches including different Django versions the Askbot branches looks like

0.7.x, 0.8.x, 0.9.x, 0.10.x

Instead of different branches Why not it must be at one that is major versions like ASKBOT 1.0 must be dependent on Latest Django version.

Please merge all AskBot subversion 0.7.x, 0.8.x, 0.9.x, 0.10.x to AskBot major version 1.0.x

If it has major versions updates are going to be maintained easily.That is recommended step for future development and releases under Latest stable Django environment.

From what I gather in the suggestion - would be nice to support the latest version of Django - of course it makes sense. Regarding branching of versions - it has become required since at some point versions of Django became mutually incompatible. Perhaps this will stop being the case at some point.

Regarding how to name the versions - I think it's not that important as long as the scheme is understandable.

At this point it is not hard to maintain sub-versions 0.7 - 0.10, so older version still continue to receive updates and their templates and internationalization strings are almost fully compatible.

No, Askbot (as of v0.10.2/ March 2017) does not support Pyton 3, please install latest Python 2.7 and try again.

I am installing for the first time on a Windows machine. I first installed Python 3.6 and verified PIP is working fine. However, in following the instructions to install using PIP, I get the following error:

C:\Askbot>pip install askbot Collecting askbot Downloading askbot-0.10.2.tar.gz (8.1MB) 100% |████████████████████████████████| 8.1MB 156kB/s Complete output from command python setup.py egg_info: Traceback (most recent call last): File "<string>", line 1, in <module> File "C:\Users\MyUser\AppData\Local\Temp\pip-build-eukbfsgi\askbot\setup.py", line 135 ********************""" ^ SyntaxError: Missing parentheses in call to 'print'

---------------------------------------- Command "python setup.py egg_info"

failed with error code 1 in C:\Users\MyUser\AppData\Local\Temp\pip-build-eukbfsgi\askbot\

I have been trying to follow the instructions from the upgrade page on askbot website.

Everything worked fine until the last step. When I upgraded from 0.8.1 to the next version. pip install askbot<1.0 installed version 0.10.1 and Django 1.8.17. But my database wasn't ready for Django 1.8. It was giving me the following error:

System check identified 2 issues (0 silenced).
There is no South database module 'south.db.postgresql_psycopg2' for your database. Please either choose a supported database, check for SOUTH_DATABASE_ADAPTER[S] settings, or remove South from INSTALLED_APPS.

I tried to downgrade askbot to 0.9 and Django to 1.7. Then the problem was pytz2013b0 was installed and the self check test says pytz2013b was required. But I couldn't install pytz2013b.

Any suggestions how to move forward?

Thanks.

@AaronHuang what was the solution?

Deleting as duplicate of http://askbot.org/en/question/15003/upgrade-from-075-to-010/

This issue is resolved in the latest releases and in the github repository.

It was caused by a dependency used by another dependency library (Lamson - used for processing of incoming email), where a version of the dependency library was not specified with sufficient detail. From now on these libraries will need to be installed manually by those people who want to support posting responses by email. This feature is not enabled by default.

Before the solution was to run pip install Lamson or pip install django-lamson (the latter is better as it satisfies all dependencies for the "reply by email" feature.

You're welcome!

migrate "robots" with --fake, then run `python manage.py migrate` without options. Then don't forget to copy the uploaded media files to the same directory that is specified by the `MEDIA_ROOT` in settings.py

Maybe you've applied migrate --fake to some other apps? If it says "nothing to migrate", it is thinking that migrations were applied, but it can't be the case if some database tables are missing... What was your site domain name? I can try migrating your data dump myself.

Just run "migrate", without specifying the app name, that will migrate all apps.

Looks like you have installed on top of later development version from github. File 0013_auto_2017 is not even on the master branch. Better start over with a brand new directory.

Lamson dependency will be removed in the upcoming release.

I have changed the title of your question to make specific.

(Assuming that you are migrating from some version whose number starts with 0.7) Start with the latest version 0.7.x, i.e. pip install 'askbot<0.8'. Put your dump into an empty database then migrate the database that you've downloaded and imported with the newer version of Askbot. The issue is that you've started with the some sub-version of 0.10, which is incompatible with your database out of the box.

This answer does not answer the question fully and will be updated, I need to run a test migration to higher versions to confirm the steps. Later versions (>0.7.x) support other versions of Django with incompatible database migrations methods, so to migrate to the Latest version, some intermediate steps will be required.

The process is documented here: https://github.com/ASKBOT/askbot-deve...

The documentation is tested with versions 0.7.58, 0.8.2, 0.9.3, 0.10.2 (released on March 1, 2017).

Because in production it's a lot more efficient to serve static files by a web-server such as nginx, rather than by a Python program. The `runserver` is meant only for the development and testing, so it should be serving from the media directories. The /m/ `STATIC_URL prefix can be replaced with anything else. Short url saves on bandwidth, even though a tiny bit.

You are confusing django-rosetta with makemessages. The makemessages is a django's built-in command and it must be run from within an app for which you are trying to build the internationalization file.

Change the current directory to the app, then run the command.

cd <path-to-some-app>
python <path-to-manage.py file> makemessages

Notice that Django's makemessages will extract files from django templates, but won't work with Jinja2 templates. For example Askbot (which uses Jinja2 templates) relies on it's own jinja2_makemessages command.

In my development setup I mostly have the askbot app installed in the root of the Django project, so my manage.py file is one level up from askbot directory, therefore I jump into askbot and run

python ../manage.py jinja2-makemessages -l en -e html,py,txt #for .py files and templates.
python ../manage.py makemessages -d djangojs -l en -e js #this time extract strings from .js files

I have installed django-rosetta successfully.

But when I was running django-admin makemessages -l de.

I got only two records from django.po:

 #: settings.py:225
msgid "account/"
msgstr ""

#: settings.py:225
msgid "signin/"
msgstr ""

is that anything wrong I did?

This means that askbot as well as probably other modules are not on Python path. If you are using virtualenv - virtual environment, then you must activate it first:

source /path/to/env/bin/activate

In the case above the /path/to/ is the directory where the virtual environment was built, by command:

cd /path/to
virtualenv env --no-site-packages

Then, it is assumed that you've installed your modules into that environment. For example installed askbot there:

cd /path/to
source env/bin/activate
pip install askbot #as an example here used basic pip install method

If you've followed the above through with the deployment of the Django project (it is described in the documentation), python manage.py collectstatic would work without errors.

For example, when I run "python manage.py collectstatic" command for my Django project, the error is raised.

Import Error: No module named askbot

Configure your web server to serve static files. For example, in nginx:

location /m/ { # url should be the same as STATIC_URL in settings.py in this case it's /m/
    alias /path/to/static/files/; #path should be the same as STATIC_ROOT in settings.py
    autoindex off;
    expires 30d;
}

Hello,

is it possible to have mutliple instance of askbot in differents directories on the same virtual host ?

ex: https://www.example.org/askbot1 and https://www.example.org/askbot2

They will not share the database, nor the users.

And if it's possible, what is the best way to do it : follow the install procedure from de begining to the end two times in the separates directories, or we can share some parts of the code or something ?

Thank you in advance for your help.

Vincent

Ok, thanks, I'll work on making this more clear and add 'save tags' button.