jabber-at / hp Goto Github PK

Hi, unless you want to offer support for all deployments of this software I suggest you make the support MUC in the contact view configurable via localsettings.py ;)

https://jabber.at/clients/ shows "View this page in: Englisch".

Hi,
although localsettings.py.examples contains the block

################
# Social media #
################
# Various social media accounts
#FACEBOOK_PAGE = 'example.com'
#TWITTER_HANDLE = 'example_com'

these settings seem to have no effect, at least the links in the sidebar are hardcoded.

Hi,
I have set "REQUIRE_UNIQUE_EMAIL = True", which works for registration, but it can be circumvented by first creating an account with a different address and then using the "change email" function in the account app.

autostart is not possible in jessie otherwise, see systemd/systemd#1836 argh

I need to restrict users to 1 account per email address, i.e. the email address used for registration must be unique / not registered yet.

Obviously that restriction must also apply to the "Set new email address" feature.

Just noticed after reading "Passwords must be at least six characters." that apparently this is hard-coded and cannot be configured.

Just a reminder to add info about the filesize-limit currently in place.

I would like the ability to change a blogpost's creation date through /admin/ because it is displayed above the blogpost on the website.

When trying to use an invalid/expired auth token,
I get "server error (500)" and an e-mail with the full stack trace to the configured admins.

It would be nice to catch that error.

ejabberd doesn't know about different types of users and treats them the same, i.e. deleting them after 1 year if you have such a cronjob in place.

celery triggers a daily job that removes accounts from the hp that have been deleted from ejabberd. While it could in theory differentiate between normal and superuser accounts, it currently does not.

Removing superusers automatically is dangeours because all core content they created will be removed as well.

I recommend

• either to differentiate between normal users and superusers and only remove normal accounts automatically
• or make core content independent from their creating superusers
  or both.

When I try to (un)publish 1 or more blogposts via the checkboxes on /admin/core/blogpost/ it fails with:

Internal Server Error: /admin/core/blogpost/

TypeError at /admin/core/blogpost/
make_unpublish() takes 3 positional arguments but 4 were given

It works fine via /admin/core/blogpost/$ID/change/ though.

It would be nice if the string "© 2010-2016, jabber.at." in core/templates/base.html would be configurable through localsettings.py as it adresses the content.

Hi, looking at hp/account/locale/de/LC_MESSAGES/django.po I noticed that jabber.at is hardcoded on
templates/account/user_register.html:27

Please use DEFAULT_XMPP_HOST instead.

• Add confirmation keys to admin.
• One key I received couldn't be opened - why?
  Tried this while being logged in with the wrong user - maybe that is the issue?
• Password reset doesn't work: https://twitter.com/hatschew/status/772732106405478400
• When the user wasn't yet created in the backend (didn't confirm email), set password yields a server-error. Set email works, but doesn't create the user either.

Contact form

• DnsBl, Blocklist
• Rate limit
• Filter any URLs. Also HTML etc...
• Minimum Length

I need to restrict the allowed email domains for registration to a specific set.

A whitelist with support for regular expressions would be awesome!

For example
".*foo.net"
".*bar.org"

which would allow all email addresses ending with foo.net or bar.org, including subdomains of foo.net and bar.org

Obviously that restriction must also apply to the "Set new email address" feature.

Help

In localsettings.py I have set TIME_ZONE = 'Europe/Berlin', which removes the warning about being ahead of server time when editing blog posts.

However, a blog post with the current (local) time as publishing time still won't show up until an hour later (when UTC has reached the publishing time),
so it seems that time zone support is missing from the blogpost view or the setting is not imported.

• Fix admin form for users.
• Validate BANNED_EMAIL_DOMAINS properly

Hi,
according to account/formfields.py line 70, DomainWidget should be disabled if only 1 domain is available, but that doesn't work.

I'm currently using the attached workaround to hardcode that setting in account/widgets.py:
widgets.py.patch.txt

Hey,
Firefox stopped requiring disabling controls five years ago [1]. So you are now able to remove your last usages of document.execCommand for things like "enableInlineTableEditing" or "enableObjectResizing".

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1490641