FieldError at /
Hello.
After installing (following the docs), and running ther server I've got the following error
FieldError at /
Unknown field(s) (a, l, _) specified for Rule
Can you help me with it ?
Hello.
After installing (following the docs), and running ther server I've got the following error
FieldError at /
Unknown field(s) (a, l, _) specified for Rule
Can you help me with it ?
This is because django-robots app was updated and Askbot did not have fixed version requirement. Added that in the repository. A release will follow shortly.
The Django version is the problem. This post:
stackoverflow.com/questions/17990704/django-forms-field-error-unknown-fields-a-l-specified-for-tablenam
For fix it, You can edit the file:
askbot/lib/python2.7/site-packages/robots/forms.py
class RuleAdminForm(forms.ModelForm):
class Meta:
model = Rule
#fields = "__all__" ---> Comment this line.
Btw, Why should I need more Karma to post a Link? That doesn't have any sense!!!
Karma limit to post links is there because of the spammers.
I have the same problem.
Try with:
pip install django-robot==1.0
and after restart your server.
This doesn't work, I get an error: Could not find any downloads that satisfy the requirement django-robot==1.0
It should say pip install django-robots==1.0 i.e. django-robots not django-robot. Works for us. Restart wasn't required.
I have met the same problem, It takes me all day long to reinstall and uninstall them. I think I make some mistakes when I install askbot, after I analysis the traceback infomation, I found it is beacuse the Django form part has a query using get method, but django 1.5 didn't support it. Hope someone can fix it.
Now, you can download the newest source code from git, they have fix the problem. :) have a good day!
To enter a block of code:
Comments
i am experiencing the same issue, here. maybe a problem with the required Django version?
Then please upvote :P
Where did the Askbot code come from, what Django version do you have?
Github master , I think Django is the one in requirements. 1.5.4
I have the same problem on OpenShift. I thought it was related to the environment.