Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

custom.css not found and strange styling

See original GitHub issue

Describe the bug The error shows up in the error log and the UI looks a bit strange. I think this code block is the cause. It immediately throws an IOException on FileLocator.resolve.

To Reproduce Steps to reproduce the behavior: Just open Portfolio Performance 0.53.3.

Expected behavior Nothing like that 😉

Screenshots

Desktop (please complete the following information):

OS: Windows 10
Version 0.53.3

Logfile:

Mon Jun 28 09:21:07 CEST 2021
C:\Users\sbaumhekel\AppData\Local\PortfolioPerformance\workspace\.metadata\.plugins\name.abuchen.portfolio.ui\custom.css (Das System kann den angegebenen Pfad nicht finden)
java.io.FileNotFoundException: C:\Users\sbaumhekel\AppData\Local\PortfolioPerformance\workspace\.metadata\.plugins\name.abuchen.portfolio.ui\custom.css (Das System kann den angegebenen Pfad nicht finden)
	at java.base/java.io.FileInputStream.open(FileInputStream.java:219)
	at java.base/java.io.FileInputStream.<init>(FileInputStream.java:157)
	at java.base/java.io.FileInputStream.<init>(FileInputStream.java:112)
	at java.base/sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:86)
	at java.base/sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:184)
	at java.base/java.net.URL.openStream(URL.java:1140)
	at org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.parseStyleSheet(AbstractCSSEngine.java:224)
	at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.setTheme(ThemeEngine.java:473)
	at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.setTheme(ThemeEngine.java:434)
	at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.setTheme(ThemeEngine.java:426)
	at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.restore(ThemeEngine.java:622)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.setCSSTheme(PartRenderingEngine.java:1419)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.initializeStyling(PartRenderingEngine.java:1326)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1050)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.start(E4Application.java:166)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1461)

Issue Analytics

State:
Created 2 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

zr40commented, Jun 28, 2021

Creating the directory .../workspace/.metadata/.plugins/name.abuchen.portfolio.ui solved the problem for me.

0reactions

sebasbaumhcommented, Jul 19, 2021

Yes, I can confirm with 0.54.0 the bug with the missing folder for custom.css is still there. It can be solved by manually creating it, but it would be better if Portfolio Performance could do that on startup. I use only the light mode and the other errors in the UI I saw before 0.54.0 have not shown up on the new version.

Top Results From Across the Web

Custom CSS not working - WordPress.org

Custom CSS not working ... Very strange indeed. ... The Custom CSS is added to the page as <style> , so a URL...

Custom stylesheet not found ASP.NET Core - css

I am in the process of trying to add some styles to a ASP.Net web app. The issue I am having is related...

CSS not being applied in pages :/ · Discussion #22495 - GitHub

Looking at your page, it appears the issue is the “/” at the beginning of your stylesheet's source. Change “/css/main.css” to “css/main.css” (on ......

style-m.css not found error for custom theme in magento 2

It looks like some of the variables that are being requested in the style-m.less file have not be created in the "blank" theme....

Changes made in custom.css are not reflected in store

You may try to add !important directive for the styles which aren't working. Thanks.