So, when I use the master build (in this case from Oct 10, 2024 Master 3556) I find that the reports are not formatted as usual. (see attachment) I imagine this is because such a small detail is not important at this stage of development? Other than that, I take it they are ok to use (and yes, I do backup my data religiously!)
Using a version from about two weeks ago, my report is formatted just fine, so itās certainly not intentional or even a known problem.
Those first three lines look like css that should be interpreted, not displayed. That suggests that the css was edited, and some syntax error was introduced, such as a misformed comment. Look in ~/.config/kmymoney/html for one or two .css files.
Hold that thought. I just launched my own compiled version, and it shows those same first lines on the Home View - so Iāve got to dig into whether there might actually be a problem in the css as shipped.
1 Like
Thanks, Jack. I have not edited that css in a long time. So, I renamed the kmymoney.css and let the program generate a new one. Same problem.
That file was edited a few weeks ago - but those changes look OK to me. Try renaming ~/.config/kmymoney/html/kmymoney.css. It will get recreated when you run kmymoney, and the problem seems to go away, although Iām still not sure what the exact problem is.
Thanks again, but see my previous commentā¦
A
Curiouser and curiouser. I just downloaded the 3556 version and it works fine for me, even after deleting the file under ~/.config. Iām not sure where else a copy might be cached.
1 Like
So, it has been years since I edited the kmymoney.css file and I pointed the program at my edited copy in another directory. I guess I thought since the program regenerated a new css file when it starts up, that that was the one it would use. Silly me. 
Also, when I run the May 5th stable version, all reports are fine. So, looking at my edited css file, there must be a missing semicolon or ending parenthesis ā but for the life of me, I donāt see it. Here is the section of the code that prints out instead of being executed:
.summaryheader { /section labels over each table in the financial summary/
background: #3daee9 url(/usr/share/kmymoney//html/images/currencyflourish.png) no-repeat bottom right;
color:#232627; /* Atheist change bkg from #3daee9 and color from #232627 */
Font-size:1.2em;
font-weight:bold;
padding:5px 10px;
}
.summarytable { /*the tables in the financial summary */
padding:5px;
}
.summarytable td { /*style in the tables in the financial summary */
padding:5px 10px;
border-left: medium solid #eff0f1;
border-right: medium solid #eff0f1;
color:#232627;
}
.itemtitle { / -additional label for table headers. example āAssetsā and āLiabilitiesā/
color:#232627; /* Atheist changed from 3daee9 */
Font-weight:bold;
}
.itemtitle td { / table data cells related to .itemtitle/
padding:0px 10px 0px 10px;
border-left: 0px;
border-right: 0px;
font-size:2.0em; /* Changed from 1.2em */
}
.item { /* -item labels (table headers) for sections in the financial summary /
font-weight:bold;
color:#232627; / Atheist changed from #232627 */
}
.item td { / table data cells related to .item/
border-left: 0px;
border-right: 0px;
border-bottom:3px solid #232627; /* Atheist changed from 232627 */
}
.warningtitle { / -set warning background color -overdue payments -items of this class also belong to the class called āitemtitleā/
color:red;/set programatically, not by css/
background-color: #3daee9;
[I sent this by email, but Iām assuming I sent it from the wrong address, since it still hasnāt shown up here.]
My css knowledge is a bit short and a bit rusty, but I can think of things other than missing semicolon or close paren. Missing right curly brace for one, or missing comment close. Also, at least in my case, the parts that showed up in the report or home view started just after a ātdā (with the single quotes) although I couldnāt find any mismatched quotes. The other possibility is something in the way that css gets embedded in the page might be broken. I think the next step might be to take the whole page (possibly try saving the report as HTML) and run it through some html/css checker.
Also - since you didnāt change your copy recently, Iām more inclined to look for how that css gets used, not the css itself. Iāll have to see if I can get the error back - but I may have deleted the version of kmymomney.css that triggered it.
If I can help, please ask. Meanwhile, I have replaced my edited .css file with the one that is auto-generated. All seems normal (albeit with smaller fonts than I like! ) A