mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #65257
[Bug 1963608] [NEW] Allow Comments by Default default value is not saved to the database on upgrade
Public bug reported:
Mahara: 21.10
OS: Linux
DB: Postgres
Browser: N/A
When upgrading from 20.10 to 21.10, the new site wide default setting
for 'Allow page comments by default' is not set to the default of 'true'
during the upgrade script.
It is a new field that was introduced in bug 1922624. So it only affects
21.10 sites that get upgraded from previous versions.
Searching for the data in the DB:
select * from config c where c.field = 'allowcommentsbydefault';
results in an empty record.
A work-around is to:
* From the site admin > site settings: unset "Allow page comments by default" and save
* Then, set the field to true and save
The database field is then saved.
** Affects: mahara
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: mahara-contributors
https://bugs.launchpad.net/bugs/1963608
Title:
Allow Comments by Default default value is not saved to the database
on upgrade
Status in Mahara:
New
Bug description:
Mahara: 21.10
OS: Linux
DB: Postgres
Browser: N/A
When upgrading from 20.10 to 21.10, the new site wide default setting
for 'Allow page comments by default' is not set to the default of
'true' during the upgrade script.
It is a new field that was introduced in bug 1922624. So it only
affects 21.10 sites that get upgraded from previous versions.
Searching for the data in the DB:
select * from config c where c.field = 'allowcommentsbydefault';
results in an empty record.
A work-around is to:
* From the site admin > site settings: unset "Allow page comments by default" and save
* Then, set the field to true and save
The database field is then saved.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1963608/+subscriptions
Follow ups
-
[Bug 1963608] Re: Allow Comments by Default default value is not saved to the database on upgrade
From: Gold, 2022-04-27
-
[Bug 1963608] Re: Allow Comments by Default default value is not saved to the database on upgrade
From: Dianne Tennent, 2022-04-27
-
[Bug 1963608] Re: Allow Comments by Default default value is not saved to the database on upgrade
From: Doris Tam, 2022-04-27
-
[Bug 1963608] A change has been merged
From: Mahara Bot, 2022-03-07
-
[Bug 1963608] A change has been merged
From: Mahara Bot, 2022-03-07
-
[Bug 1963608] Re: Allow Comments by Default default value is not saved to the database on upgrade
From: Robert Lyon, 2022-03-07
-
[Bug 1963608] A patch has been submitted for review
From: Mahara Bot, 2022-03-06
-
[Bug 1963608] A patch has been submitted for review
From: Mahara Bot, 2022-03-06
-
[Bug 1963608] A change has been merged
From: Mahara Bot, 2022-03-06
-
[Bug 1963608] Re: Allow Comments by Default default value is not saved to the database on upgrade
From: Robert Lyon, 2022-03-06
-
[Bug 1963608] Re: Allow Comments by Default default value is not saved to the database on upgrade
From: Robert Lyon, 2022-03-04
-
[Bug 1963608] Re: Allow Comments by Default default value is not saved to the database on upgrade
From: Robert Lyon, 2022-03-04
-
[Bug 1963608] A patch has been submitted for review
From: Mahara Bot, 2022-03-04
-
[Bug 1963608] Re: Allow Comments by Default default value is not saved to the database on upgrade
From: Robert Lyon, 2022-03-04