mcg's profile - activity

I know this isn't an answer but a comment alone doesn't seem to give it an activity bump. I'd like to acknowledge that this is problem recently occurred for me during a migration from 0.7.43 to 0.7.50. Instead of seeing answers disappearing, I'm only seeing the summary. The full answer cannot be revealed.

However, if I edit a question or answer, the full question now appears on the page.

If you want to see the difference, here is a question on my original site: http://ask.cvxr.com/question/3072/computing-or-bounding-a-modified-ky-fan-norm/

And here is the same question on my test site: http://ask2.cvxr.com/question/3072/computing-or-bounding-a-modified-ky-fan-norm/

(The theme on the new site is a work in progress, so ignore that, please.)

I just encountered this problem myself. Thanks for offering up a solution here. I do agree that a migration fix is in order.

Here's how I managed to get past this error:

• Run python manage.py migrate --fake to see which migrations need to take place.
• For each migration, run python manage.py migrate appname .

That seemed to fix things; I can now do full migrations without incident.

I created a patch for the markdown2.py module that does a better job of isolating MathJax equations from the Markdown processing. Basically, it just replaces all instances of $...$ and $$...$$ patterns from the text, performs the standard markdown processing, and inserts them back in. It works surprisingly well. You can download the context diff from this link (this is just a text file).

The only downside that I can see is that you need to backslash all regular dollar signs that you use in text---but if you run a math-heavy web site like I do, that's no big deal.

Anyway, the Javascript module needs a similar update so that the functionality matches. I've worked on that already, and once I'm satisfied I'll share it here, too. EDIT: OK, I'm satisfied with that patch; you can grab it from this link.

I added it right into the skin's CSS file. Make sure to use the CSS inspector to see if it is not being overridden by other style entries.

Granted, I have not made the attempt. But everything about my single-site experience suggests that multiple sites will be no problem.

First of all, I installed Askbot via pip directly into my central site-packages repository. So that would be accessible from every separate site that you install.

Secondly, when I ran the Askbot setup script to create a new site, it asks where you want to put the installation---and then it creates a copy of the template files, uwsgi initialization script, and configuration settings, but not the main Askbot code. This suggests to me that multiple uwsgi servers could run off the same code base. Editing the templates for one site won't change the look of another site.

Of course, you will need to create a separate database for each site, and manage a separate uwsgi server. But there's nothing I saw that suggests this is not possible.

This worked for me, thanks!

Nevermind, I misread the answer above, and now I have done so via the Django panel.

Do you intend to switch to PageDown on the WMD side of things? I intend to stick with Markdown over TinyMCE myself. (And how about the latest StackExchange editor with its expanding help toolbar? Wow! Gotta find a way to snag that.)

Sure, but please be gentle. I am still working on it heavily. http://ask.cvxr.com

I was able to enable it by editing the following files:

• skins/default/templates/question/content.html
• skins/default/templates/question/new_answer_form.html

In the first, change

{% if question.closed == False and request.user == question.author %}{# this is outside the form on purpose #}

to this:

{% if question.closed == False %}{# this is outside the form on purpose #}

And in the second file, remove this line:

{% if user == question.author %}style="display:none"{% endif %}

This is a well-known problem with iOS devices: they tend to override the defaults for all sorts of form elements, including buttons, checkboxes, radio buttons, etc. To fix this particular problem, try adding this custom CSS:

input[type="text"] {
    -webkit-appearance: none;
}

That's worked for me. I'm putting together a highly hacked theme for Askbot for my site and this problem was vexing me.

Until this feature is implemented, is it possible to do this from the shell?

I'd definitely like an update to this question... I'm having the exact same problem.

I just cleared my cookies, and that seemed to clear things up. My guess is that it has to do with a conflict between the cookies generated when running the test server on port 8888, and the cookies generated on the production server.

This would explain why we administrators would have the problem but not other users we send to our site to check things out.

EDIT: Sorry folks, that didn't fix it after all---or at least, it is also related to Facebook logins. I tried to add Facebook logins back, and once I added that key to my login set, the reloading started again.