5:58 pm
-
- -3
- +11
-
- -3
- +14
|
|
Saturday 28 Dec 2024
5:58 pm
Fixed 2 bugs: with remote code repository- fixed repository URL when trying to "install-from-repositry" on a checkout from the HEAD channel. The code tried to fetch from a channel "6-0", which does not exist.- determine the exact repository tag for repository channels
4:49 pm
unset temporary variables which would be kept in the in the ::xowiki namespace
4:46 pm
streamline spelling
4:46 pm
fixed typo
4:45 pm
Bumped upstream version of highcharts to 12.1.2
4:43 pm
bumped version of fa icons to 6.7.2
4:39 pm
Ported essential post-release fixes from oacs-5-10 branch
4:37 pm
improved comments
Friday 27 Dec 2024
8:00 pm
backport from oacs-head, otherwise the cache viewer is unusuable
7:56 pm
fixed page contract for cache viewer
7:28 pm
Bumped version number of acs-tcl to 5.10.2d2
7:25 pm
Fixed bug in install-from-repository (issue #3472)Install from repository (e.g., of /dotlrn) was horribly broken, see,e.g., issue #3472. Furthermore, this bug was hard to debug, since itshowed up just during a complex installation attempts involvinginstall.xml, and it requires fetching from the repository. Therefore,the debug rounds were quite time-consuming.There were several problems involved: 1) dotlrn/install.xml was trying to set the theme to the dotlrn-bootstrap3-theme, which was not loaded from the repository 2) The loading order was not correct, since the theme requires an existing dotlrn instance to register the theme templates there. 3) The tests in install::xml::action::mount checking, if the package was already mounted were incorrect, probably since many years. It looks to me as some refactorings of the "get_node_id" semantics (many years ago) were not reflected in this code. This bug let the code assume, that the package was already mounted. Therefore, the package was never mounted, causing a long tail of subsequent issues. 4) the site_node::instantiate_and_mount call in install::xml::action::mount was called with incorrect parameters, causing overwriting of the site root node, leaving the site completely unusable.Bumped version number of acs-tcl to 5.10.2d1
6:31 pm
fixed overquoting in "ad_progress_base_end"
6:13 pm
dirty editor buffer
6:05 pm
switch responsibilities for theme setting
5:45 pm
One more attempt to install bootstrap3 theme automatically
1:32 pm
fixed cut&paste problem
1:09 pm
reset to released version to keep differences little
12:19 pm
deactivate automated theme setting for now
10:50 am
keep theme-stetting for dotlrn themes in dotlrn, since it requires a dotlrn instancebut when the dotlrn is installed, it requires the dotlrn-theme package to be installed
10:22 am
Continue working on the install.xml issue.
10:01 am
added more debugging info
9:29 am
undo one more recent change
9:15 am
undo recent change. This was not the problem
9:00 am
added debug statement
Thursday 26 Dec 2024
7:25 pm
try to get a non-empty context id
6:56 pm
added debugging line
6:32 pm
Fixed incorrect result handling from ::acs::site_node get_node_idWhen ::acs::site_node get_node_id -url /$mount_pointis executed with a non-existing mount point, the node info of theparent_id is returned. The code assumed that for such cases, theresulting "object_id" member is empty. Since this affects only thetwo action procs install::xml::action::mount install::xml::action::mount-existingi have adjusted the behavior there.Furthermore, some tests are now less mind-twisted.
12:10 pm
strangely, parameter CommDefaultSiteTemplate_p was set on wrong package_idBefore this change, the install from repo on dotlrn led to error below.this change makes sure, that the used "package_id" is the package_id from dotlrn.: ERROR: -20000: The specified package 702 AND/OR parameter CommDefaultSiteTemplate_p do not exist in the system: CONTEXT: PL/pgSQL function apm__id_for_name(integer,character varying) line 13 at RAISE: PL/pgSQL function apm__set_value(integer,character varying,character varying) line 6 at assignmentoacs-5-10=# select * from apm_packages where package_key like '%dotlrn%'; package_id | package_key | instance_name | default_locale------------+-------------------------+----------------------------+---------------- 1843 | dotlrn-bm | dotLRN Bulk Mail Applet | 1850 | dotlrn-faq | dotLRN FAQ Applet | 1868 | dotlrn-forums | dotLRN Forums Applet | 1886 | dotlrn-fs | dotLRN File Storage Applet | 1933 | dotlrn-news | dotLRN News Applet | 1981 | dotlrn-portlet | dotLRN Portlet | 1998 | dotlrn-assessment | dotLRN Assessment Applet | 2040 | dotlrn-bootstrap3-theme | dotLRN Bootstrap 3 Theme |oacs-5-10=# select * from apm_packages where package_id = 702; package_id | package_key | instance_name | default_locale------------+-------------+------------------------+---------------- 702 | acs-subsite | #acs-kernel.Main_Site# |
11:15 am
moved theme setting to theme package (dotlrn-bootstrap3-theme)This make sure that in the loading sequence, the theme is available when onetries to switch to it.
Problem fetching more activity
|
Got a suggestion or an issue?
Discuss it on the Atlassian Community or
visit Atlassian Support for other options.