Sunil Mohan Adapa 74214c18ae
*: Use Django gettext functions instead of ugettext
- ugettext functions will be removed in Django 4.0. Each use emits a warning
when running with Django 3.2. Since we have warnings enabled in developer mode,
we see quite a few messages because of this.

- ugettext is already a simple alias of gettext. So, no regressions are
expected.

Tests:

- Accessing an affected app in UI with Django 3.2 and Django 2.2 works fine.

- Using Django 3.2 there are no warnings related to removal of ugettext
functions.

- Ran regular unit tests.

Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
2021-09-20 16:50:16 -04:00

40 lines
1.1 KiB
Python

# SPDX-License-Identifier: AGPL-3.0-or-later
"""
FreedomBox app for configuring WordPress.
"""
import pathlib
from django.contrib import messages
from django.utils.translation import gettext as _
from plinth import actions, views
from . import PUBLIC_ACCESS_FILE
from .forms import WordPressForm
class WordPressAppView(views.AppView):
"""Serve configuration page."""
form_class = WordPressForm
app_id = 'wordpress'
def get_initial(self):
"""Get the current WordPress settings."""
status = super().get_initial()
status['is_public'] = pathlib.Path(PUBLIC_ACCESS_FILE).exists()
return status
def form_valid(self, form):
"""Apply the changes submitted in the form."""
old_status = form.initial
new_status = form.cleaned_data
if old_status['is_public'] != new_status['is_public']:
actions.superuser_run(
'wordpress',
['set-public', '--enable',
str(new_status['is_public'])])
messages.success(self.request, _('Configuration updated'))
return super().form_valid(form)