Hi,
ProcessMaker seems to default to the to the root folder for the location of the custom background image even though I have updated the path in my custom skin loginStyle.css file.
body.login {
background-color: #444;
background: url('../../shared/skins/myskinfolder/images/mybackgroundimage.jpg');
background-size: cover;
}
This change causes the background not to display even though the file is located in the custom skin image folder. However, when I have the custom image in the root public_html/images folder and use background: url('/images/mybackgroundimage.jpg'), it displays the custom background image properly.
Note, the same thing happens when trying to load a custom logo image in the custom skin layout.html file.
Am I missing something?Hi,
ProcessMaker seems to default to the to the root folder for the location of the custom background image even though I have updated the path in my custom skin loginStyle.css file.
body.login {
background-color: #444;
background: url('../../shared/skins/myskinfolder/images/mybackgroundimage.jpg');
background-size: cover;
}
This change causes the background not to display even though the file is located in the custom skin image folder. However, when I have the custom image in the root public_html/images folder and use background: url('/images/mybackgroundimage.jpg'), it displays the custom background image properly.
Note, the same thing happens when trying to load a custom logo image in the custom skin layout.html file.
- It is possible to create a skin based on Classic (this will copy all necessary/updated files from classic skin) or based on any other skin. How to switch skins? The first way is by changing in the URL “classic” by the name of desired skin. The second way is by double click in the name of the skin in the list.
- Download common business process templates and automate your workflow today. Browse the available processes. Click 'download' to get the.pm file. You can then 'upload' the.pm file to your ProcessMaker environment through the Import option in the Processes tab. Automating your workflow has never been easier.
- Download Latest Version processmaker-3.5.4-community.tar.gz (155.5 MB) Get Updates. Skins 2.0 (Promoted to stable version) Finally this release comes with a fully functional Skins administration that helps any administrator to create, delete, import and export (.tar format) skins.
ProcessMaker seems to default to the to the root folder for the location of the custom background image even though I have updated the path in my custom skin loginStyle.css file.
180,105 phpvms skins download jobs found. Fortnite custom skins download, processmaker skins download Need to hire a freelancer for a job? It's free to sign up.
body.login {
background-color: #444;
Skins Episode Download
background: url('../../shared/skins/myskinfolder/images/mybackgroundimage.jpg');
background-size: cover;
}
This change causes the background not to display even though the file is located in the custom skin image folder. However, when I have the custom image in the root public_html/images folder and use background: url('/images/mybackgroundimage.jpg'), it displays the custom background image properly.
Note, the same thing happens when trying to load a custom logo image in the custom skin layout.html file.
Am I missing something?Hi,
ProcessMaker seems to default to the to the root folder for the location of the custom background image even though I have updated the path in my custom skin loginStyle.css file.
body.login {
background-color: #444;
background: url('../../shared/skins/myskinfolder/images/mybackgroundimage.jpg');
background-size: cover;
}
Processmaker Bpm
![Windows media player skins download Windows media player skins download](/uploads/1/1/8/5/118503843/817649155.png)
Note, the same thing happens when trying to load a custom logo image in the custom skin layout.html file.