83 Commits (5ac07bdf750977afd28d46420f6c1e78e2a0a345)

Author	SHA1	Message	Date
ulferts	1bdd2ab9ae	safe automatic fixes by rubocop (#8994)	4 years ago
luz paz	3683042c9b	Fix typos in user facing and non-user facing code ... Found via `codespell v2.1.dev0`	4 years ago
ulferts	6140f4c7e9	update copyright to 2021 (#8925) ... Updates the copyright to 2021 for all files that have a copyright. Files in our source code without the copyright header still do not receive one automatically. Additionally, backlisted files are also excluded. Previously the copyright of chiliproject which references redmine stated a copyright of redmine up to and including 2017 which is not true for the code we have in here. Because of that I changed that to 2013	4 years ago
ulferts	6cce947cbd	Chore/rename timestamps (#8765) ... * rename timestamps on time entry * add updated_at filter/order for time entries * rename on cost entries as well This will make handling in the cost query easier * adapt specs * linting * adapt project activity * update references to updated_on * remove outdated docs/code * global memberships are just memberships * rewire global membership creation/update/deletion * delete no longer required code and patches * move code to core * move specs to core * completely remove global roles in the form of a plugin * adapt specs * remove unused methods * migrate existing data * adapt membership representer to changed timestamps * global memberships available via API * implements created/update_at filters on memberships * update member on roles being added/removed * specify default value for created_at * fix project permission check and validation on members * adapt membership schema * adapt usage of sort by on members widget * support created/updated_on for api sort and filter * remove outdated model file * rename timestamps * allow specifying timestamp column for aaj * reload column information * further rename of created_on * include updated_at into journal creation * adapt document updated_at calculation * remove references to JournalVersion	4 years ago
Oliver Günther	53f2d694ff	Use AnyFixtures to generate fixtures from factories (#7230) ... Uses FactoryBot to keep and maintain specific records in a special transaction that does not get removed after each spec. They automatically are created whenever first hitting them. This makes an excellent time saver for items that are commonly used, such as an admin user account	5 years ago
Henriette Dinger	bd7f4e4814	Update copyright notice	5 years ago
Oliver Günther	0791c55870	Remove the internal setting with 500 max entries ... Instead, use the maximum allowed page size for the maximum number. This will match what the users have selected and be reasonable without adding another user-visible setting. https://community.openproject.com/wp/30103	6 years ago
Cyril Rohr	648819ce1c	Bypass the default getters and setters for installation_uuid	6 years ago
Cyril Rohr	666d038f20	Add custom getter for Setting.installation_uuid	6 years ago
Wieland Lindenthal	b1e45bc200	Allow for filtering `Setting` values when they are read. This is needed for overwriting values when EE token is not available.	6 years ago
Oliver Günther	44b93ddf04	Show consent in account/register form	7 years ago
Oliver Günther	aea0e41001	Add check box to update consent time to current time	7 years ago
Oliver Günther	9efba5d532	Correct date writing for consent_date	7 years ago
Markus Kahl	ddf0419843	added datetime setting format	7 years ago
Oliver Günther	0bc22be618	Ensure session cookie receives secure flag in https ... When users enable https in their instance, the session cookie should be `secure` by default. It currently is only when the configuration `rails_force_ssl` is set. https://community.openproject.com/wp/268331 [ci skip]	7 years ago
Oliver Günther	450b0fc13d	[27763] Ensure session cookie receives secure flag in https ... When users enable https in their instance, the session cookie should be `secure` by default. It currently is only when the configuration `rails_force_ssl` is set. https://community.openproject.com/wp/268331	7 years ago
Jens Ulferts	0875a94099	remove no longer required gems	7 years ago
Oliver Günther	6ef4211e77	Bump copyright to 2018 (#6171) ... [ci skip]	7 years ago
Oliver Günther	7cf11bb689	Update copyright notice	8 years ago
Jens Ulferts	a5ec412f3d	harmonize saving plugin settings	8 years ago
Jens Ulferts	01bbc0face	harmonize settings#value to not be AC::Params	8 years ago
Jens Ulferts	9cef3656bf	replace deprecated table_exists	8 years ago
Jens Ulferts	3ee5c4edb6	clear cache before firing the settings callback ... Otherwise, callback listeners working on the change can not get the current value	8 years ago
Oliver Günther	4353953605	Improve stored settings as a whole ... Currently, settings are cached on a per-name basis, but that cache is expired everytime *any* attribute is written. Even when a week-old attribute is still valid, its cache is expired as soon another setting is updated due to the max settings cache key. Instead of caching a single attribute, I suggest to cache the entire settings (the total number with plugins is less than 120 and 4KiB in size) and retrieve and deserialize a single value from that hash. That saves us the time to: 1. Locating a single element from database 2. Instantiate a setting object just for deserializing 3. Requesting settings several times by using RequestStore	8 years ago
Cyril Rohr	f27bce492a	Add tests for new methods to configure email settings	9 years ago
Alex Coles	57618b25ec	Replace dynamic finder usages with #find_by, etc. ... This patch replaces all dynamic finders, for the sake of consistency, although only some methods are deprecated. See: https://github.com/rails/activerecord-deprecated_finders#active-record-deprecated-finders * Revert some `User#find_by_login` usages in cuke steps accidentally removed in 74228b59. User Story # 20325 Signed-off-by: Alex Coles <alex@alexbcoles.com>	9 years ago
Alex Coles	ef4285bc0c	Kill deprecated Setting.*_cache methods ... Deprecated in version 2.4.0 (2011). See: d76fd8e4. Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Alex Coles	e0191e759c	Update year in copyright header to 2015 ... [ci skip]	10 years ago
Alex Coles	1d1ec0ef37	Prefer #map over #collect in (Rails) models ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Alex Coles	6fe9535b1f	Fix syntax (w/Rubocop) in (Rails) models ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Alex Coles	721101ed25	Use 1.9+ Hash syntax in (Rails) models ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Alex Coles	c12410a736	Fix whitespace in (Rails) models ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	11 years ago
Martin Linkhorst	1ce4d30b1b	remove openid remains	11 years ago
Martin Linkhorst	f0b1df9e07	based the settings callbacks on OP::Notifications	11 years ago
Martin Linkhorst	dda5226dff	fire callbacks only when setting was stored sucessfully	11 years ago
Alex Coles	d872d91d0d	Fix typos, spelling in model comments ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	11 years ago
Martin Linkhorst	c9effc5b6b	implements callbacks for settings	11 years ago
Johannes Wollert	8b096975fe	updates copyright headers ... updates more copyright more copyright headers	11 years ago
Michael Frister	eda857d75b	Settings: Cache whether settings table exists ... Before, ActiveRecord executed a SQL query to check whether the table exists on each settings access.	11 years ago
Stefan Frank	bcabf75ffe	Added the request-store, to make sure that thread-local variables are cleaned up after the request	11 years ago
Stefan Frank	1a9e536852	Stores the Setting.maximum(:updated_on) in a thread-local-variable ... this gets rid of numerous redundant db-calls to check with every call to a setting, if the settings have been updated. Checking this one and one time only for a request should be sufficient. let's see, if this works for the admin-specs to update settings.	11 years ago
Philipp Tessenow	a1e67dd460	new copyright header #1903	11 years ago
Philipp Tessenow	a17951d220	when there is not settings table return nil when asked for a setting	11 years ago
Philipp Tessenow	220bc5eb38	more robust settings in pre-merge phase ... when we haven't migrated yet, there is no settings table. this doesn't hinder plugins to read/write settings (when initializing the app). solution: ignore setting-writes (but give a warning) and answer an empty hash on setting-read when there is no setting-table. fixes #1830	11 years ago
Michael Frister	4ec8ebd8d9	Add exists? method to Setting	11 years ago
Sebastian Schuster	c1724649a3	Removed regexp matching delete of cache entries ... since it is not supported by memcached, instead deleted individual keys to make sure we read the latest written value in case timestamps do not change between writes	11 years ago
Jens Ulferts	21459a384f	provide every possible file with a short copyright notice ... This was done using the rake task: rake copyright:update	12 years ago
Martin Linkhorst	a860d6979a	change the way the cache gets invalidated when a setting value is changed. now deletes all cache keys containing the setting's name	12 years ago
Martin Linkhorst	02e58ee814	put possible values for available settings into a lambda block because available_settings class variable can change at runtime (was different before)	12 years ago
Martin Linkhorst	e5e2202707	do not register plugin settings at load time. this commit registers plugin settings, when they are registered.	12 years ago