- Newer version of owncloud package enable the Apache2 owncloud configuration
by default. This happens eventhough database configuraiton is not available.
Plinth only checks for Apache2 owncloud configuration as enabled to determine
if owncloud is enabled and hence falsely shows the owncloud is enabled.
- Newer version of owncloud also create a /etc/owncloud/config.php with simple
instance identifier set. So merely checking if the files exists is not of
much use.
- This patch checks if the dbtype variable is configured in config.php or
autoconfig.php along with Apache2 owncloud configuration to determine if
owncloud is enabled.
- The same logic is used to determine if autoconfig.php must be generated.
- We must assume that apart from Plinth there will be user or user-agent
changes to the configuration files. In this case the value may be set
something other than '1' day.
- Remove emacs mode line as emacs automatically detect Python files
based on the #! line.
- End comments with a '.'.
- Use single quotes instead of double quotes for string for consistensy.
- Update message to say that it take more than a minute to finish
upgrades. Some times it takes a lot more than that.
Restarting Apache breaks existing connections. This includes the connection
on which the Plinth's user has made the ownCloud enable/disable request. This
leads to an almost certain 'Connection Interupted' message to the client when
changes to ownCloud are submitted.
On the other hand, 'reload' is sufficient and 'restart' is not required. It is
also faster and recommended by 'a2enconf' and 'a2disconf' commands.
* Add unit tests for cfg.py, context_processors.py, and menu.py
* Add new plinth/tests/data directory for miscellaneous test data
* In cfg.py, add an explicit check to verify the existence of the secondary
(non-default) plinth.config file
* In cfg.py, replace deprecated configparser.SafeConfigParser with
configparser.ConfigParser
* Add a detailed console report to the 'test_coverage' command output
* Expand the precision of all coverage percentages to two decimal places
* Print the location of the HTML coverage report at the end of the console report
When modules were removed, Debian packaging also had to remove them to
avoid errors. When Debian guidelines are following and correspoding deb
helper is used, it creates .dpkg-* files in the module configuration
directory. Plinth tries to load these which causes problems. We should
consider loading files with a known extension in future.
Since the links to javascript libraries have been removed in favor of
using javscript-common, it is no longer possible to run Plinth stand
alone without a reverse proxy that also serves /javscript. This patch
fixes that. Now /javascirpt is also available when Plinth is running
stand alone.
- If during an action, user does not exist ignore.
- If during an action, return a non-zero exist status.
- Catch an errors during actions as exceptions.
- Display a message that corresponding POSIX operation failed.
These cause lintain warning during Debian package building. They
currently don't serve any purpose as they are empty. They can be
re-added when they have some content.
Documentation shown inside Plinth is not effected by this as it includes
its own styling. Documentation that is opened by user directly from
/usr/share/doc/plinth is effected.
We manually have to call the form.save() method in form_valid().
Plus tiny cleanups like using SetPasswordForm instead of
AdminPasswordChangeForm.
Note: this allows any logged-in user to change all other user passwords.
