NoahY's profile - activity

It looks like if your karma is over 1000, and you've got lots of badges, the karma appears beside the username in your answers. Just adding a
before the karma tag fixes this. I'm adding it to my server, and my git fork.

Edit: Ah, sorry, I see... it's the website that's the problem... it looks like an improper if statement in askbot/skins/default/templates/macros.html:

{% if not user.website %}<br/>{% endif %}

this seems useless, since the website comes below anyway... just leaving the <br/> works fine.

When I enter characters with diacritics, like ā in a question on my AskBot installation, they are converted to question marks. Why would that be?

I'm pretty new to Python, and Django is even more unfamiliar, but I was trying to find a simple hack that would process a text-based askbot setting using the Django Template() function, specifically here:

http://askbot.org/en/question/519/faq-to-settings

Where what I would like to do something remotely like:

if getattr(askbot_settings, 'FORUM_FAQ',''):
    faq = Template(FORUM_FAQ)
    return render_into_skin(faq, data, request)

which of course doesn't work for various reasons. My question is, what exactly are the intermediate steps to get something like this to work, so that FORUM_FAQ can contain template tags like {{settings.MIN_REP_TO_VOTE_UP}}, be processed to replace these tags, then fed into an HTTP request like faq.htm?

It seems like it should be pretty easy, but again, I don't know either python or django (or askbot) well enough to figure it out.

I've been wondering why my Askbot site didn't have a facebook sign-in button, so I looked through the source and found that in the file:

deps/django_authopenid/util.py

The facebook entry is commented out. Removing the comments restores the button. Am I missing something? Why is it commented out in the code?

Maybe there is a way to improve the widget to make it use space more efficiently? How about allowing site owners select which sharing tools to enable?

The problem if you move the buttons elsewhere they will be used less often, the spot on the left top is the best and a tenth of a square inch for those buttons is a good use of space.

yeah, I agree. problem is there are really so many sharing sites available :) I ended up doing what you suggest by changing the "enable social sharing" to providing an option to enable each individually.

I created a new branch with sidebar settings for each of:

• main page
• question page
• profile page

There's only a header and footer for the profile page, but more can be added in the future. What I'd like to try next, but am not sure how to go about it, is allowing the widgets to be rearranged. Any ideas?

I just added a linkedin button below the twitter/facebook buttons. Combined with the g+ button, it's starting to clutter - maybe it would be better to move the buttons to a different place? Or have them show on demand?

It works fine on my test site - both kinds of vote trigger a notice if karma is not enough.

note: google+ doesn't seem to have such a link available: http://stackoverflow.com/questions/6676658/share-link-on-google

note that it is incorrect to say that 'every question has a footer'... on stackexchange, only those questions _without answers_ have this footer, hence the "else" tag in the example below.

Not sure if it's kosher to just copy the code verbatim, but this seems to work:

    {% if answers %}

    ...

    {% else %}
        <h2 class="share-question">{% trans url=settings.APP_URL+question.get_absolute_url()|iriencode, name=settings.APP_SHORT_NAME|iriencode %}Know someone who can answer?  Share a <a href="{{ url }}">link</a> to this question via 
            <a href="mailto:?subject={{ name }}&amp;body={{ url }}">email</a>, 
            <a href="http://twitter.com/share?url={{ url }}">Twitter</a>, 
            <a href="http://www.facebook.com/sharer.php?u={{ url }}">Facebook</a>, or
            <a href="http://www.linkedin.com/shareArticle?mini=true&amp;url={{ url }}&amp;source={{ name }}">Linkedin</a>.{% endtrans %}
        </h2>
    {% endif %}

great! let me know if there's anything else I can do.

great. I'm still not a pro with git... it seems to want to merge my branches automatically when I switch back and forth... have to read up on it.

But the tags are fully customizable right now too - just override the existing css rules. The tags are rendered fully via css.

There is one specific need answered by the current tag HTML - support "sliding doors" technique to use with the background images as some people will sure want to use background images.

Also, in some web-browsers rounded css corners are not supported.

I've added a 'print' branch to my repository... @Evgeny - maybe you can let me know what you think?

I've worked out CSS code for the tags:

<div style="float: left; display: inline-block; height:16px;background-color:#FAFAFA;border-radius:8px 0 0 8px; position:relative; padding-right:6px; border-right: 1px #CCCCCC solid; border-bottom: 1px #CCCCCC solid; border-top: 1px #EEEEEE solid; border-left: 1px #EEEEEE solid; ">
    <div style="border: 1px #CCCCCC solid; border-radius:6px;margin:5px;position:absolute; width:5px;height:5px; background-color:white"></div>
    <span style="font-size: 11px;margin-left:16px; vertical-align:center;white-space: nowrap;line-height: 18px; color:#333333">test tag</span>
</div>

that gives an output almost exactly like the tags as they are, only it is now fully customizable via custom css.

re: tests - thanks, I'll do that from now on.

Oh, I'm sorry, again I changed something on the production server but forgot to go back and edit the dev code. setting.SITE_FAVICON should be settings.SITE_FAVICON Fixed now.

ah, this is new to me... I don't quite understand test cases, but I can run that command before committing, sure.

try my github fork... it should work.

custom header and footer for the sidebar is now up as well. One day maybe wordpress widgets :)

I think custom favicon is broken, or at least I can't figure out what I'm doing wrong... I've fixed it on my github, by changing base.html as follows:

    {% if settings.SITE_FAVICON %}
        <link rel="shortcut icon" href="{{ settings.SITE_FAVICON|media }}" />
    {% else %}
        <link rel="shortcut icon" href="{{ '/m/default/media/images/favicon.gif'|media }}" />
    {% endif %}

I also changed the default for settings.SITE_FAVICON to reflect what was in this file originally (/m/default/media/images/favicon.gif). I think /images/favicon.gif does not exist. If it works as I think it should, there is really no need for the if/else in the above code; simply:

<link rel="shortcut icon" href="{{ settings.SITE_FAVICON|media }}" />

should capture the default if set correctly. I can't test this, though, since there seems to be no way to reset the defaults... guess I could hack the database...

Okay, done... I added a new config section, SIDEBAR_SETTINGS, because I think there is room for development in this area... no need to clutter up another settings page, and we can also configure sidebars for questions here as well. Somehow it would be nice to have an html header and footer for the sidebar too... I'll add that to my git, Evgeny can decide what to do with it all :) The three sidebar options are already on my github fork.

actually, this feature is a trivial thing to implement, but I wonder how to do the settings... maybe I'll go ahead and add some settings to Skin and User... can always move them later.