Menu
▾
▴
tikiwiki-devel — Tiki developers (the main decision/communication channel)
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(10) |
Nov
(94) |
Dec
(308) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(272) |
Feb
(246) |
Mar
(353) |
Apr
(651) |
May
(1017) |
Jun
(569) |
Jul
(1165) |
Aug
(542) |
Sep
(340) |
Oct
(665) |
Nov
(325) |
Dec
(229) |
| 2004 |
Jan
(317) |
Feb
(267) |
Mar
(136) |
Apr
(88) |
May
(77) |
Jun
(134) |
Jul
(32) |
Aug
(57) |
Sep
(79) |
Oct
(121) |
Nov
(24) |
Dec
(44) |
| 2005 |
Jan
(83) |
Feb
(64) |
Mar
(123) |
Apr
(101) |
May
(141) |
Jun
(108) |
Jul
(97) |
Aug
(57) |
Sep
(70) |
Oct
(83) |
Nov
(37) |
Dec
(96) |
| 2006 |
Jan
(80) |
Feb
(106) |
Mar
(150) |
Apr
(53) |
May
(11) |
Jun
(48) |
Jul
(115) |
Aug
(112) |
Sep
(101) |
Oct
(35) |
Nov
(71) |
Dec
(128) |
| 2007 |
Jan
(55) |
Feb
(32) |
Mar
(43) |
Apr
(53) |
May
(90) |
Jun
(62) |
Jul
(113) |
Aug
(82) |
Sep
(38) |
Oct
(82) |
Nov
(116) |
Dec
(160) |
| 2008 |
Jan
(86) |
Feb
(68) |
Mar
(166) |
Apr
(189) |
May
(60) |
Jun
(81) |
Jul
(137) |
Aug
(242) |
Sep
(103) |
Oct
(201) |
Nov
(168) |
Dec
(122) |
| 2009 |
Jan
(115) |
Feb
(427) |
Mar
(416) |
Apr
(377) |
May
(420) |
Jun
(351) |
Jul
(368) |
Aug
(283) |
Sep
(356) |
Oct
(359) |
Nov
(494) |
Dec
(312) |
| 2010 |
Jan
(368) |
Feb
(391) |
Mar
(285) |
Apr
(236) |
May
(437) |
Jun
(424) |
Jul
(267) |
Aug
(272) |
Sep
(377) |
Oct
(384) |
Nov
(457) |
Dec
(337) |
| 2011 |
Jan
(389) |
Feb
(415) |
Mar
(445) |
Apr
(412) |
May
(552) |
Jun
(537) |
Jul
(408) |
Aug
(422) |
Sep
(631) |
Oct
(592) |
Nov
(280) |
Dec
(242) |
| 2012 |
Jan
(296) |
Feb
(296) |
Mar
(517) |
Apr
(668) |
May
(426) |
Jun
(398) |
Jul
(273) |
Aug
(184) |
Sep
(281) |
Oct
(535) |
Nov
(637) |
Dec
(315) |
| 2013 |
Jan
(148) |
Feb
(326) |
Mar
(425) |
Apr
(292) |
May
(359) |
Jun
(238) |
Jul
(461) |
Aug
(324) |
Sep
(356) |
Oct
(386) |
Nov
(405) |
Dec
(253) |
| 2014 |
Jan
(139) |
Feb
(172) |
Mar
(115) |
Apr
(292) |
May
(160) |
Jun
(82) |
Jul
(265) |
Aug
(209) |
Sep
(233) |
Oct
(172) |
Nov
(124) |
Dec
(126) |
| 2015 |
Jan
(188) |
Feb
(247) |
Mar
(353) |
Apr
(373) |
May
(202) |
Jun
(101) |
Jul
(66) |
Aug
(163) |
Sep
(102) |
Oct
(98) |
Nov
(145) |
Dec
(129) |
| 2016 |
Jan
(194) |
Feb
(231) |
Mar
(315) |
Apr
(257) |
May
(179) |
Jun
(186) |
Jul
(260) |
Aug
(346) |
Sep
(289) |
Oct
(237) |
Nov
(396) |
Dec
(233) |
| 2017 |
Jan
(362) |
Feb
(222) |
Mar
(236) |
Apr
(309) |
May
(169) |
Jun
(183) |
Jul
(295) |
Aug
(339) |
Sep
(186) |
Oct
(187) |
Nov
(278) |
Dec
(320) |
| 2018 |
Jan
(203) |
Feb
(190) |
Mar
(313) |
Apr
(163) |
May
(147) |
Jun
(340) |
Jul
(171) |
Aug
(123) |
Sep
(194) |
Oct
(392) |
Nov
(204) |
Dec
(124) |
| 2019 |
Jan
(81) |
Feb
(139) |
Mar
(105) |
Apr
(148) |
May
(173) |
Jun
(98) |
Jul
(185) |
Aug
(176) |
Sep
(216) |
Oct
(162) |
Nov
(166) |
Dec
(131) |
| 2020 |
Jan
(166) |
Feb
(142) |
Mar
(296) |
Apr
(212) |
May
(195) |
Jun
(156) |
Jul
(83) |
Aug
(123) |
Sep
(147) |
Oct
(147) |
Nov
(154) |
Dec
(94) |
| 2021 |
Jan
(183) |
Feb
(156) |
Mar
(82) |
Apr
(115) |
May
(96) |
Jun
(95) |
Jul
(146) |
Aug
(77) |
Sep
(58) |
Oct
(105) |
Nov
(110) |
Dec
(79) |
| 2022 |
Jan
(54) |
Feb
(39) |
Mar
(24) |
Apr
(33) |
May
(35) |
Jun
(7) |
Jul
(21) |
Aug
(47) |
Sep
(25) |
Oct
(32) |
Nov
(43) |
Dec
(27) |
| 2023 |
Jan
(48) |
Feb
(30) |
Mar
(9) |
Apr
(39) |
May
(34) |
Jun
(33) |
Jul
(37) |
Aug
(13) |
Sep
(6) |
Oct
(39) |
Nov
(25) |
Dec
|
| 2024 |
Jan
(6) |
Feb
(4) |
Mar
(10) |
Apr
(8) |
May
(13) |
Jun
(7) |
Jul
(13) |
Aug
|
Sep
(7) |
Oct
(23) |
Nov
(22) |
Dec
(15) |
| 2025 |
Jan
(4) |
Feb
(3) |
Mar
(14) |
Apr
(9) |
May
(9) |
Jun
(11) |
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Rodriguez N. <rod...@gm...> - 2025-07-29 14:50:59
|
Dear Devs, We're releasing Tiki 29.0-alpha right now. Please don't commit/merge to branch 29.x until we are done. Thanks, Rodriguez Nyiringabo & Bienvenu Ushindi |
|
From: Jonny B. <jo...@ti...> - 2025-07-24 08:59:00
|
Many thanks guys, looking forward to my workload reducing soon so i can play with this one and contribute! jonny > On 23 Jul 2025, at 21:09, Rodriguez Nyiringabo <rod...@gm...> wrote: > > Dear Devs, > > We've branched Tiki 29.x. > > Best Regards, > Rodriguez Nyiringabo & Bienvenu Ushindi > > Le mer. 23 juil. 2025 à 20:28, Rodriguez Nyiringabo <rod...@gm...> a écrit : >> Dear Devs, >> >> We're going to create Tiki branch 29.x in a few moments. >> >> Thanks! >> Rodriguez Nyiringabo & Bienvenu Ushindi > > _______________________________________________ > TikiWiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
From: Rodriguez N. <rod...@gm...> - 2025-07-23 20:09:57
|
Dear Devs, We've branched Tiki 29.x. Best Regards, Rodriguez Nyiringabo & Bienvenu Ushindi Le mer. 23 juil. 2025 à 20:28, Rodriguez Nyiringabo < rod...@gm...> a écrit : > Dear Devs, > > We're going to create Tiki branch 29.x in a few moments. > > Thanks! > Rodriguez Nyiringabo & Bienvenu Ushindi > |
|
From: Rodriguez N. <rod...@gm...> - 2025-07-23 19:29:00
|
Dear Devs, We're going to create Tiki branch 29.x in a few moments. Thanks! Rodriguez Nyiringabo & Bienvenu Ushindi |
|
From: Rodriguez N. <rod...@gm...> - 2025-07-21 22:19:36
|
Hello Dear Devs, We should have branched Tiki-29x today but due to the work not yet finished on headerlib, we postponed the branching to after tomorrow (2025-07-23). As for each new Tiki major version a star name is needed, before branching or at the latest before the alpha release, we need to make sure the star name is already chosen. So, If you have a star name to propose for Tiki-29x, please share it with us and we will decide together which one to pick from all the propositions. Thanks, Rodriguez Nyiringabo |
|
From: Karsten W. <kw...@gm...> - 2025-07-01 13:05:26
|
Hi, I have noticed a strange behavior in Tiki27.3: A wiki page has an alias entry (e.g. Support). When I enter "support" in the search field of search-plugin, I get a red link for a non-existent page in the suggestions. This was not the case in Tiki21. There, alias pages were not found at all (which is better than a red link). How can I fix this or even better: How can an alias entry be found by the search in the same way as a page title? Thanks in advance. Best regards Karsten |
|
From: Rodriguez N. <rod...@gm...> - 2025-06-19 19:53:19
|
Dear Devs, New security updates are available: https://tiki.org/article520-New-Security-Updates-Released-for-Tiki-28-x-27-x-LTS-and-24-x-LTS-and-Upgrade-is-Strongly-Recommended Please download the new Tiki versions following the links given in the article. Best regards, Rodriguez Nyiringabo & Bienvenue Ushindi |
|
From: Karsten W. <kw...@gm...> - 2025-06-18 08:15:21
|
Hi, I have two problems with the display of “backlinks” in Tiki 27.2. The first concerns orphaned links to deleted pages that are displayed in red. Where do these come from? The pages in question no longer exist and yet they are displayed as backlinks. A search correctly no longer finds the pages. The second problem concerns the display of namespaces in the backlinks. In Tiki 21 I had pages with the same title and different namespace, separator is ~. For example, “4.0~page 1” and “3.1~page 1” or “page 1”. In Tiki 21 the complete name was displayed. In Tiki 27 I see three titles with the same name in the backlinks (with the correct links). Are these known problems? How can I investigate this further? Where are the backlinks compiled? Thanks in advance! Best regards Karsten |
|
From: Benoit G. <be...@co...> - 2025-06-06 17:40:24
|
On vendredi 6 juin 2025 13 h 02 min 09 s heure avancée de l’Est Karsten Wemheuer
wrote:
> Hi,
>
> thanks for the pointer. I finally found the error. That weird path with
> the missing / is produced in tiki-tc.php, line 57.
>
> original:
> $headerlib->add_cssfile("{$tc_theme_path}css/{$tc_theme_option}.css");
>
> fixed:
> $headerlib->add_cssfile("{$tc_theme_path}/css/{$tc_theme_option}.css");
>
> I have included a patch. The solution works for me. But I don't know if
> it has unintended side effects.
>
> I compared the file from tiki 27.2 with tiki 28.3. As they are
> identical, I assume the patch works for Tiki 27 and Tiki 28.
>
> Best regards
>
> Karsten
Thanks!
https://gitlab.com/tikiwiki/tiki/-/merge_requests/7708[1]
--
Benoit Grégoire
--------
[1] https://gitlab.com/tikiwiki/tiki/-/merge_requests/7708
|
|
From: Karsten W. <kw...@gm...> - 2025-06-06 17:02:18
|
Hi,
thanks for the pointer. I finally found the error. That weird path with
the missing / is produced in tiki-tc.php, line 57.
original:
$headerlib->add_cssfile("{$tc_theme_path}css/{$tc_theme_option}.css");
fixed:
$headerlib->add_cssfile("{$tc_theme_path}/css/{$tc_theme_option}.css");
I have included a patch. The solution works for me. But I don't know if
it has unintended side effects.
I compared the file from tiki 27.2 with tiki 28.3. As they are
identical, I assume the patch works for Tiki 27 and Tiki 28.
Best regards
Karsten
Am Donnerstag, dem 05.06.2025 um 17:54 -0400 schrieb Benoit Grégoire:
> On mardi 3 juin 2025 18 h 02 min 29 s heure avancée de l’Est Karsten
> Wemheuer via TikiWiki-devel wrote:
> > the generated file is correctly located as You mentioned. Where
> > should
> > I look for a bug in the code? Where is the url generated?
>
> In themelibl.php, getThemeCssFilePath() or getThemePath()
>
>
> --
> Benoit Grégoire
|
|
From: Benoit G. <be...@co...> - 2025-06-05 22:05:59
|
On mardi 3 juin 2025 18 h 02 min 29 s heure avancée de l’Est Karsten Wemheuer via TikiWiki-devel wrote: > the generated file is correctly located as You mentioned. Where should > I look for a bug in the code? Where is the url generated? In themelibl.php, getThemeCssFilePath() or getThemePath() -- Benoit Grégoire |
|
From: Karsten W. <kw...@gm...> - 2025-06-04 15:16:54
|
Hi, can someone tell me, wehre the url for the option css file is generated? The file is generated in: public/generated/_custom/shared/themes/mytheme/options/home/css/home.cs s But the URL would like to load /public/generated/_custom/shared/themes/mytheme/options/homecss/home.cs s This leads to an error. It looks as if “home/css” is being converted to “homecss” at the end of the path. Any ideas? Thanks in advance. Best regards Karsten Am Dienstag, dem 03.06.2025 um 19:29 +0200 schrieb Karsten Wemheuer via TikiWiki-devel: > Hi, > > I was now successful in creating my custom theme in the new _custom > folder structure. > > My original theme from tiki21 has two options. I tried creating > > _custom/shared/themes/mytheme/options/opt1/css > > directory and put the file opt1.css inside. > > After cleaning caches and accessing the site, I get errors in the log > > No route found - > full:/public/generated/_custom/shared/themes/mytheme/options/opt1css/ > op > t1.css > > What am I doing wrong? How should the directory structure below > "options" look like? > > Thanks in advance. > > Best regards > Karsten > > > _______________________________________________ > TikiWiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
From: Karsten W. <kw...@gm...> - 2025-06-03 22:02:37
|
Hi, Am Dienstag, dem 03.06.2025 um 17:10 -0400 schrieb Benoit Grégoire: > On mardi 3 juin 2025 13 h 29 min 43 s heure avancée de l’Est Karsten > Wemheuer via TikiWiki-devel wrote: > > Hi, > > > > I was now successful in creating my custom theme in the new _custom > > folder structure. > > > > My original theme from tiki21 has two options. I tried creating > > > > _custom/shared/themes/mytheme/options/opt1/css > > > > directory and put the file opt1.css inside. > > > > After cleaning caches and accessing the site, I get errors in the > > log > > > > No route found - > > full:/public/generated/_custom/shared/themes/mytheme/options/opt1cs > > s/op > > t1.css > > > > What am I doing wrong? How should the directory structure below > > "options" look like? > > It should look exactly like that. > > There may be a code bug. The path should be > /public/generated/_custom/shared/themes/mytheme/options/opt1/css/opt1 > .css Is there really a missing slash between opt1 and css in the > error message? Is the file actually copied at > /public/generated/_custom/shared/themes/mytheme/options/opt1/css/opt1 > .css after a build? the generated file is correctly located as You mentioned. Where should I look for a bug in the code? Where is the url generated? Perhaps I still have a misunderstanding. The source code for the theme is a .scss file in the directory _custom/shared/themes/mytheme/css/mytheme.scss (as described in the docs). The last directory is css, not scss. The other scss-files like _variables.scss are located in scss-directory. What about the file structure beyond options? As far as I understood die directory is 'css'. The file there is a scss-file with extension .scss? > > I just re-tested that scenario locally in master and it seems to work > fine. I can select the theme option and the css is properly > included. unfortunately I am locked to an LTS release. Best regards Karsten |
|
From: Benoit G. <be...@co...> - 2025-06-03 21:28:27
|
On mardi 3 juin 2025 13 h 29 min 43 s heure avancée de l’Est Karsten Wemheuer via TikiWiki-devel wrote: > Hi, > > I was now successful in creating my custom theme in the new _custom > folder structure. > > My original theme from tiki21 has two options. I tried creating > > _custom/shared/themes/mytheme/options/opt1/css > > directory and put the file opt1.css inside. > > After cleaning caches and accessing the site, I get errors in the log > > No route found - > full:/public/generated/_custom/shared/themes/mytheme/options/opt1css/op > t1.css > > What am I doing wrong? How should the directory structure below > "options" look like? It should look exactly like that. There may be a code bug. The path should be /public/generated/_custom/shared/ themes/mytheme/options/opt1/css/opt1.css Is there really a missing slash between opt1 and css in the error message? Is the file actually copied at /public/generated/_custom/ shared/themes/mytheme/options/opt1/css/opt1.css after a build? I just re-tested that scenario locally in master and it seems to work fine. I can select the theme option and the css is properly included. -- Benoit Grégoire |
|
From: Karsten W. <kw...@gm...> - 2025-06-03 17:29:56
|
Hi, I was now successful in creating my custom theme in the new _custom folder structure. My original theme from tiki21 has two options. I tried creating _custom/shared/themes/mytheme/options/opt1/css directory and put the file opt1.css inside. After cleaning caches and accessing the site, I get errors in the log No route found - full:/public/generated/_custom/shared/themes/mytheme/options/opt1css/op t1.css What am I doing wrong? How should the directory structure below "options" look like? Thanks in advance. Best regards Karsten |
|
From: Karsten W. <kw...@gm...> - 2025-06-02 07:53:58
|
Hi Gary, yes, the path is as You described it. I found some garbage in the tree. After cleaning up, triggering "npm run watch" and clearing the cache it seems to work now. I now continue upgrading the theme. Many thanks! Have a nice day. Karsten Am Montag, dem 02.06.2025 um 04:06 +0900 schrieb Gary Cunningham-Lee: > Hi, > > Is your _custom/ path to mytheme.scss like this: > _custom/shared/themes/mytheme/css/mytheme.scss ? > > -- Gary > > On 5/31/2025 2:13 AM, Karsten Wemheuer via TikiWiki-devel wrote: > > Hi, > > > > I noticed something strange. The URL for the CSS file is in the > > Firefox > > Console: > > > > /public/generated/_custom/shared/themes/mythemecss/mytheme.css > > > > That leads to an 404, and the CSS is not loaded. The attached "css" > > in > > the path seems to be wrong. > > > > Where is my mistake? > > > > Thanks in advance > > > > Best regards > > > > Karsten > > > > Am Freitag, dem 30.05.2025 um 18:02 +0200 schrieb Karsten Wemheuer > > via > > TikiWiki-devel: > > > Hi, > > > > > > thanks for answering. > > > > > > I now put my mytheme.scss file in the > > > _custom/shared/themes/mytheme/css/ directory. But this does not > > > change > > > the generation process: running the "npm run watch" the file > > > mytheme.scss is compiled to mytheme.css only in public directory. > > > Is > > > this correct? > > > > > > Wht to do if going to production: Should I take the public > > > directory > > > tree or the _custom or both? > > > > > > Still a little bit confused... > > > > > > -- Karsten > > > > > > > > > Am Freitag, dem 30.05.2025 um 20:44 +0900 schrieb Gary > > > Cunningham- > > > Lee: > > > > Hi, > > > > > > > > Copying the CSS file to the css directory shouldn't be > > > > necessary. > > > > Just > > > > to be sure, is your mytheme.scss in mytheme/scss/ or in > > > > mytheme/css? > > > > In > > > > the new build system, this file should be in the mytheme/css > > > > directory. > > > > > > > > I see now that the themes.tiki.org page shows that the custom > > > > theme > > > > has > > > > a templates directory, but I think this might not be correct. > > > > Custom > > > > template files should be in _custom/shared/templates. I don't > > > > think > > > > theme-specific template files are supported. > > > > > > > > -- Gary > > > > > > > > On 5/30/2025 6:54 PM, Karsten Wemheuer via TikiWiki-devel > > > > wrote: > > > > > Hi, > > > > > I want to create a custom theme in the new directory > > > > > structure > > > > > for > > > > > a > > > > > tiki 27 installation. > > > > > > > > > > I created the structure unter _custom as described on > > > > > https://themes.tiki.org/Making+or+Updating+a+Theme+for+Tiki+27+and+Newer+Versions > > > > > > > > > > I created a sccs-file an the npm run watch compiled it to the > > > > > directory > > > > > public/generated/_custom/shared/themes/mytheme/scss/mytheme.c > > > > > ss > > > > > > > > > > On the Look&Feel page the new theme doesn't show up. I have > > > > > to > > > > > manually > > > > > copy the created css file to > > > > > _custom/shared/themes/mytheme/css. > > > > > Is > > > > > this > > > > > the correct way to work? > > > > > > > > > > Another question regards the layout files like > > > > > layout_view.tpl. > > > > > Where > > > > > should I place this file? > > > > > > > > > > Thanks in advance! > > > > > > > > > > Best regards > > > > > > > > > > Karsten > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > TikiWiki-devel mailing list > > > > > Tik...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > > > > > > _______________________________________________ > > > > TikiWiki-devel mailing list > > > > Tik...@li... > > > > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > > > > > > > _______________________________________________ > > > TikiWiki-devel mailing list > > > Tik...@li... > > > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > > > > _______________________________________________ > > TikiWiki-devel mailing list > > Tik...@li... > > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > _______________________________________________ > TikiWiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
From: Gary Cunningham-L. <ga...@cu...> - 2025-06-01 20:26:26
|
Hi, Is your _custom/ path to mytheme.scss like this: _custom/shared/themes/mytheme/css/mytheme.scss ? -- Gary On 5/31/2025 2:13 AM, Karsten Wemheuer via TikiWiki-devel wrote: > Hi, > > I noticed something strange. The URL for the CSS file is in the Firefox > Console: > > /public/generated/_custom/shared/themes/mythemecss/mytheme.css > > That leads to an 404, and the CSS is not loaded. The attached "css" in > the path seems to be wrong. > > Where is my mistake? > > Thanks in advance > > Best regards > > Karsten > > Am Freitag, dem 30.05.2025 um 18:02 +0200 schrieb Karsten Wemheuer via > TikiWiki-devel: >> Hi, >> >> thanks for answering. >> >> I now put my mytheme.scss file in the >> _custom/shared/themes/mytheme/css/ directory. But this does not >> change >> the generation process: running the "npm run watch" the file >> mytheme.scss is compiled to mytheme.css only in public directory. Is >> this correct? >> >> Wht to do if going to production: Should I take the public directory >> tree or the _custom or both? >> >> Still a little bit confused... >> >> -- Karsten >> >> >> Am Freitag, dem 30.05.2025 um 20:44 +0900 schrieb Gary Cunningham- >> Lee: >>> Hi, >>> >>> Copying the CSS file to the css directory shouldn't be necessary. >>> Just >>> to be sure, is your mytheme.scss in mytheme/scss/ or in >>> mytheme/css? >>> In >>> the new build system, this file should be in the mytheme/css >>> directory. >>> >>> I see now that the themes.tiki.org page shows that the custom theme >>> has >>> a templates directory, but I think this might not be correct. >>> Custom >>> template files should be in _custom/shared/templates. I don't think >>> theme-specific template files are supported. >>> >>> -- Gary >>> >>> On 5/30/2025 6:54 PM, Karsten Wemheuer via TikiWiki-devel wrote: >>>> Hi, >>>> I want to create a custom theme in the new directory structure >>>> for >>>> a >>>> tiki 27 installation. >>>> >>>> I created the structure unter _custom as described on >>>> https://themes.tiki.org/Making+or+Updating+a+Theme+for+Tiki+27+and+Newer+Versions >>>> >>>> I created a sccs-file an the npm run watch compiled it to the >>>> directory >>>> public/generated/_custom/shared/themes/mytheme/scss/mytheme.css >>>> >>>> On the Look&Feel page the new theme doesn't show up. I have to >>>> manually >>>> copy the created css file to _custom/shared/themes/mytheme/css. >>>> Is >>>> this >>>> the correct way to work? >>>> >>>> Another question regards the layout files like layout_view.tpl. >>>> Where >>>> should I place this file? >>>> >>>> Thanks in advance! >>>> >>>> Best regards >>>> >>>> Karsten >>>> >>>> >>>> >>>> _______________________________________________ >>>> TikiWiki-devel mailing list >>>> Tik...@li... >>>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >>> >>> _______________________________________________ >>> TikiWiki-devel mailing list >>> Tik...@li... >>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >> >> >> _______________________________________________ >> TikiWiki-devel mailing list >> Tik...@li... >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > _______________________________________________ > TikiWiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
From: Karsten W. <kw...@gm...> - 2025-05-30 17:22:12
|
Hi Jean-Marc, thanks for the hint. I can confirm that templates are fetched from both locations __custom/shared/themes/mythemes/templates and __custom/shared/templates Thanks for clarifying the order of overriding the values. Cheers, Karsten Am Freitag, dem 30.05.2025 um 18:08 +0200 schrieb Jean-Marc Libs: > Hi ! > > I trust Gary on CSS/SCSS matters but I can tell theme-specific > template files are supported and so should theme option template > files. > Plus, theme-specific template files override the templates in > _custom/shared/templates which themselves override the templates in > templates. > > Cheers, > J-M > > On Fri, May 30, 2025 at 5:20 PM Gary Cunningham-Lee > <ga...@cu...> wrote: > > Hi, > > > > Copying the CSS file to the css directory shouldn't be necessary. > > Just > > to be sure, is your mytheme.scss in mytheme/scss/ or in > > mytheme/css? In > > the new build system, this file should be in the mytheme/css > > directory. > > > > I see now that the themes.tiki.org page shows that the custom theme > > has > > a templates directory, but I think this might not be correct. > > Custom > > template files should be in _custom/shared/templates. I don't think > > theme-specific template files are supported. > > > > -- Gary > > > > On 5/30/2025 6:54 PM, Karsten Wemheuer via TikiWiki-devel wrote: > > > Hi, > > > I want to create a custom theme in the new directory structure > > > for a > > > tiki 27 installation. > > > > > > I created the structure unter _custom as described on > > > https://themes.tiki.org/Making+or+Updating+a+Theme+for+Tiki+27+and+Newer+Versions > > > > > > I created a sccs-file an the npm run watch compiled it to the > > > directory > > > public/generated/_custom/shared/themes/mytheme/scss/mytheme.css > > > > > > On the Look&Feel page the new theme doesn't show up. I have to > > > manually > > > copy the created css file to _custom/shared/themes/mytheme/css. > > > Is this > > > the correct way to work? > > > > > > Another question regards the layout files like layout_view.tpl. > > > Where > > > should I place this file? > > > > > > Thanks in advance! > > > > > > Best regards > > > > > > Karsten > > > > > > > > > > > > _______________________________________________ > > > TikiWiki-devel mailing list > > > Tik...@li... > > > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > > > > _______________________________________________ > > TikiWiki-devel mailing list > > Tik...@li... > > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > _______________________________________________ > TikiWiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
From: Karsten W. <kw...@gm...> - 2025-05-30 17:13:38
|
Hi, I noticed something strange. The URL for the CSS file is in the Firefox Console: /public/generated/_custom/shared/themes/mythemecss/mytheme.css That leads to an 404, and the CSS is not loaded. The attached "css" in the path seems to be wrong. Where is my mistake? Thanks in advance Best regards Karsten Am Freitag, dem 30.05.2025 um 18:02 +0200 schrieb Karsten Wemheuer via TikiWiki-devel: > Hi, > > thanks for answering. > > I now put my mytheme.scss file in the > _custom/shared/themes/mytheme/css/ directory. But this does not > change > the generation process: running the "npm run watch" the file > mytheme.scss is compiled to mytheme.css only in public directory. Is > this correct? > > Wht to do if going to production: Should I take the public directory > tree or the _custom or both? > > Still a little bit confused... > > -- Karsten > > > Am Freitag, dem 30.05.2025 um 20:44 +0900 schrieb Gary Cunningham- > Lee: > > Hi, > > > > Copying the CSS file to the css directory shouldn't be necessary. > > Just > > to be sure, is your mytheme.scss in mytheme/scss/ or in > > mytheme/css? > > In > > the new build system, this file should be in the mytheme/css > > directory. > > > > I see now that the themes.tiki.org page shows that the custom theme > > has > > a templates directory, but I think this might not be correct. > > Custom > > template files should be in _custom/shared/templates. I don't think > > theme-specific template files are supported. > > > > -- Gary > > > > On 5/30/2025 6:54 PM, Karsten Wemheuer via TikiWiki-devel wrote: > > > Hi, > > > I want to create a custom theme in the new directory structure > > > for > > > a > > > tiki 27 installation. > > > > > > I created the structure unter _custom as described on > > > https://themes.tiki.org/Making+or+Updating+a+Theme+for+Tiki+27+and+Newer+Versions > > > > > > I created a sccs-file an the npm run watch compiled it to the > > > directory > > > public/generated/_custom/shared/themes/mytheme/scss/mytheme.css > > > > > > On the Look&Feel page the new theme doesn't show up. I have to > > > manually > > > copy the created css file to _custom/shared/themes/mytheme/css. > > > Is > > > this > > > the correct way to work? > > > > > > Another question regards the layout files like layout_view.tpl. > > > Where > > > should I place this file? > > > > > > Thanks in advance! > > > > > > Best regards > > > > > > Karsten > > > > > > > > > > > > _______________________________________________ > > > TikiWiki-devel mailing list > > > Tik...@li... > > > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > > > > _______________________________________________ > > TikiWiki-devel mailing list > > Tik...@li... > > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > > _______________________________________________ > TikiWiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
From: Jean-Marc L. <jea...@gm...> - 2025-05-30 16:09:20
|
Hi ! I trust Gary on CSS/SCSS matters but I can tell theme-specific template files are supported and so should theme option template files. Plus, theme-specific template files override the templates in _custom/shared/templates which themselves override the templates in templates. Cheers, J-M On Fri, May 30, 2025 at 5:20 PM Gary Cunningham-Lee < ga...@cu...> wrote: > Hi, > > Copying the CSS file to the css directory shouldn't be necessary. Just > to be sure, is your mytheme.scss in mytheme/scss/ or in mytheme/css? In > the new build system, this file should be in the mytheme/css directory. > > I see now that the themes.tiki.org page shows that the custom theme has > a templates directory, but I think this might not be correct. Custom > template files should be in _custom/shared/templates. I don't think > theme-specific template files are supported. > > -- Gary > > On 5/30/2025 6:54 PM, Karsten Wemheuer via TikiWiki-devel wrote: > > Hi, > > I want to create a custom theme in the new directory structure for a > > tiki 27 installation. > > > > I created the structure unter _custom as described on > > > https://themes.tiki.org/Making+or+Updating+a+Theme+for+Tiki+27+and+Newer+Versions > > > > I created a sccs-file an the npm run watch compiled it to the directory > > public/generated/_custom/shared/themes/mytheme/scss/mytheme.css > > > > On the Look&Feel page the new theme doesn't show up. I have to manually > > copy the created css file to _custom/shared/themes/mytheme/css. Is this > > the correct way to work? > > > > Another question regards the layout files like layout_view.tpl. Where > > should I place this file? > > > > Thanks in advance! > > > > Best regards > > > > Karsten > > > > > > > > _______________________________________________ > > TikiWiki-devel mailing list > > Tik...@li... > > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > _______________________________________________ > TikiWiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > |
|
From: Karsten W. <kw...@gm...> - 2025-05-30 16:02:54
|
Hi, thanks for answering. I now put my mytheme.scss file in the _custom/shared/themes/mytheme/css/ directory. But this does not change the generation process: running the "npm run watch" the file mytheme.scss is compiled to mytheme.css only in public directory. Is this correct? Wht to do if going to production: Should I take the public directory tree or the _custom or both? Still a little bit confused... -- Karsten Am Freitag, dem 30.05.2025 um 20:44 +0900 schrieb Gary Cunningham-Lee: > Hi, > > Copying the CSS file to the css directory shouldn't be necessary. > Just > to be sure, is your mytheme.scss in mytheme/scss/ or in mytheme/css? > In > the new build system, this file should be in the mytheme/css > directory. > > I see now that the themes.tiki.org page shows that the custom theme > has > a templates directory, but I think this might not be correct. Custom > template files should be in _custom/shared/templates. I don't think > theme-specific template files are supported. > > -- Gary > > On 5/30/2025 6:54 PM, Karsten Wemheuer via TikiWiki-devel wrote: > > Hi, > > I want to create a custom theme in the new directory structure for > > a > > tiki 27 installation. > > > > I created the structure unter _custom as described on > > https://themes.tiki.org/Making+or+Updating+a+Theme+for+Tiki+27+and+Newer+Versions > > > > I created a sccs-file an the npm run watch compiled it to the > > directory > > public/generated/_custom/shared/themes/mytheme/scss/mytheme.css > > > > On the Look&Feel page the new theme doesn't show up. I have to > > manually > > copy the created css file to _custom/shared/themes/mytheme/css. Is > > this > > the correct way to work? > > > > Another question regards the layout files like layout_view.tpl. > > Where > > should I place this file? > > > > Thanks in advance! > > > > Best regards > > > > Karsten > > > > > > > > _______________________________________________ > > TikiWiki-devel mailing list > > Tik...@li... > > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > _______________________________________________ > TikiWiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
From: Gary Cunningham-L. <ga...@cu...> - 2025-05-30 15:20:14
|
Hi, Copying the CSS file to the css directory shouldn't be necessary. Just to be sure, is your mytheme.scss in mytheme/scss/ or in mytheme/css? In the new build system, this file should be in the mytheme/css directory. I see now that the themes.tiki.org page shows that the custom theme has a templates directory, but I think this might not be correct. Custom template files should be in _custom/shared/templates. I don't think theme-specific template files are supported. -- Gary On 5/30/2025 6:54 PM, Karsten Wemheuer via TikiWiki-devel wrote: > Hi, > I want to create a custom theme in the new directory structure for a > tiki 27 installation. > > I created the structure unter _custom as described on > https://themes.tiki.org/Making+or+Updating+a+Theme+for+Tiki+27+and+Newer+Versions > > I created a sccs-file an the npm run watch compiled it to the directory > public/generated/_custom/shared/themes/mytheme/scss/mytheme.css > > On the Look&Feel page the new theme doesn't show up. I have to manually > copy the created css file to _custom/shared/themes/mytheme/css. Is this > the correct way to work? > > Another question regards the layout files like layout_view.tpl. Where > should I place this file? > > Thanks in advance! > > Best regards > > Karsten > > > > _______________________________________________ > TikiWiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
From: Karsten W. <kw...@gm...> - 2025-05-30 09:54:44
|
Hi, I want to create a custom theme in the new directory structure for a tiki 27 installation. I created the structure unter _custom as described on https://themes.tiki.org/Making+or+Updating+a+Theme+for+Tiki+27+and+Newer+Versions I created a sccs-file an the npm run watch compiled it to the directory public/generated/_custom/shared/themes/mytheme/scss/mytheme.css On the Look&Feel page the new theme doesn't show up. I have to manually copy the created css file to _custom/shared/themes/mytheme/css. Is this the correct way to work? Another question regards the layout files like layout_view.tpl. Where should I place this file? Thanks in advance! Best regards Karsten |
|
From: Karsten W. <kw...@gm...> - 2025-05-28 17:36:48
|
Hi Jonny, thanks a lot. I'll fix it as You described. Best regards Karsten Am Mittwoch, dem 28.05.2025 um 17:35 +0100 schrieb Jonny Bradley: > Hi Karsten > > Looks like that has been fixed (i.e. removed) since 27.2 was released > but no new version has been released yet sadly. > > https://gitlab.com/tikiwiki/tiki/-/commit/406bea4f > > So for now just put it back to how is was in 27.1 or indeed how it is > now in get, here: > > > https://gitlab.com/tikiwiki/tiki/-/blob/27.x/lib/wiki-plugins/wikiplugin_includetpl.php?ref_type=heads > > Sorry about that, hope this gets you going again! > > jonny > > > > > On 28 May 2025, at 16:50, Karsten Wemheuer via TikiWiki-devel > > <tik...@li...> wrote: > > > > Hi, > > > > I just do a fresh install of Tiki 27.2 LTS. > > > > I got this error message > > Call to undefined method TikiLib::sanitizeEvalExpression() > > > > > > As I understand it, line 56 in file lib/wiki- > > plugins/wikiplugin_includetpl.php is the cause. > > > > I checked the previous version and see this diff between 27.1 and > > 27.2. > > > > --- tiki-27.1/lib/wiki-plugins/wikiplugin_includetpl.php > > +++ tiki-27.2/lib/wiki-plugins/wikiplugin_includetpl.php > > @@ -53,5 +53,5 @@ > > } > > > > $smarty->assign('values', $defvalues); > > - return $smarty->fetch($params["filename"]); > > + return $smarty- > > > fetch(TikiLib::sanitizeEvalExpression($params["filename"])); > > } > > > > I can not find the method TikiLib::sanitizeEvalExpression in the > > tar > > ball of 27.2. How can I to fix this? > > > > Thank you for any advice! > > > > Best regards > > Karsten > > > > > > > > _______________________________________________ > > TikiWiki-devel mailing list > > Tik...@li... > > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > |
|
From: Jonny B. <jo...@ti...> - 2025-05-28 16:48:55
|
Hi Karsten Looks like that has been fixed (i.e. removed) since 27.2 was released but no new version has been released yet sadly. https://gitlab.com/tikiwiki/tiki/-/commit/406bea4f So for now just put it back to how is was in 27.1 or indeed how it is now in get, here: https://gitlab.com/tikiwiki/tiki/-/blob/27.x/lib/wiki-plugins/wikiplugin_includetpl.php?ref_type=heads Sorry about that, hope this gets you going again! jonny > On 28 May 2025, at 16:50, Karsten Wemheuer via TikiWiki-devel <tik...@li...> wrote: > > Hi, > > I just do a fresh install of Tiki 27.2 LTS. > > I got this error message > Call to undefined method TikiLib::sanitizeEvalExpression() > > > As I understand it, line 56 in file lib/wiki- > plugins/wikiplugin_includetpl.php is the cause. > > I checked the previous version and see this diff between 27.1 and 27.2. > > --- tiki-27.1/lib/wiki-plugins/wikiplugin_includetpl.php > +++ tiki-27.2/lib/wiki-plugins/wikiplugin_includetpl.php > @@ -53,5 +53,5 @@ > } > > $smarty->assign('values', $defvalues); > - return $smarty->fetch($params["filename"]); > + return $smarty- >> fetch(TikiLib::sanitizeEvalExpression($params["filename"])); > } > > I can not find the method TikiLib::sanitizeEvalExpression in the tar > ball of 27.2. How can I to fix this? > > Thank you for any advice! > > Best regards > Karsten > > > > _______________________________________________ > TikiWiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
361 messages has been excluded from this view by a project administrator.
