Support community for TTG plugins and products.
NOTICE
The Turning Gate's Community has moved to a new home, at https://discourse.theturninggate.net.
This forum is now closed, and exists here as a read-only archive.
You are not logged in.
Using CSS lint, I get these error messages:
line column title description
error 40 1 Parsing Errors Expected LBRACE at line 40, col 1.
.contact-form {
warning 27 5 Require use of known properties Unknown property 'text-colour'.
text-color: #DCDCDC;
warning 36 3 Require use of known properties Unknown property 'text-colour'.
text-color: white;
What's that Left Brace on line 40? And why are the colours not "known"?
Last edited by pideja (2019-10-05 01:04:16)
Offline
just realized this is Okapi.
text color changes are made in the template under Main Copy > Copy Color
your css wouldn't work anyway; there is no text-color property. And you're applying it to the input field, not the label.
Rod
Just a user with way too much time on his hands.
www.rodbarbee.com
ttg-tips.com, Backlight 2/3 test site
Offline
Thank you again, Rod.
The confusion (on my part) arose when I saw that I had an Okapi and a Pangolin page in the Templates>Page Template section. The Pangolin was the default but setting the Okapi as default fixed the problem.
Now, if I want to "upgrade" to Pangolin thru-out, can I do this in a straightforward way?
Offline
I found some great tools to correct mistakes in the writing of the CSS code:
https://html-cleaner.com/css/
https://codebeautify.org/cssvalidate
My CSS now reads:
.thumbnail {
position:relative;
width:100px;
height:200px;
overflow:hidden;
}
ul.breadcrumbs li {
font-size:1.2rem;
}
.breadcrumbs a {
font-weight:700;
font-size:1.15rem;
color:#D3D3D3;
}
.breadcrumbs li a:hover {
color:#FFF;
}
.gallery figcaption {
text-align:center;
color:#D3D3D3;
}
.contact-form input {
max-width:50%;
color:red;
}
.copyright p {
font-style:italic;
text-align:center;
}
.the__copy>.content,.contact-form p {
text-align:center;
}Works great! All that's left is to figure out why the album page doesn't conform to the styling I designed. But that's another post...
Last edited by pideja (2019-10-06 02:10:18)
Offline
Thank you again, Rod.
The confusion (on my part) arose when I saw that I had an Okapi and a Pangolin page in the Templates>Page Template section. The Pangolin was the default but setting the Okapi as default fixed the problem.
Now, if I want to "upgrade" to Pangolin thru-out, can I do this in a straightforward way?
You’ve converted sites before, haven’t you?
Going from Okapi templates to Pangolin templates requires starting over with design. Phplugins is also different. And some css selectors may be different.
Rod
Just a user with way too much time on his hands.
www.rodbarbee.com
ttg-tips.com, Backlight 2/3 test site
Offline
So, I guess that I'll stay at Okapi for the time being...unless there are overwhelming reasons to upgrade. I can't afford to go through that again at least for this project. The site is used almost daily by the dance company. So, until next summer (off-season) it's going to stay like this.
Thanks Rod.
Offline