Date: 2016-01-20 01:37 am (UTC)
marahmarie: (M In M Forever) (0)
From: [personal profile] marahmarie
No, it's not the CSS at fault. It's something with the s1 itself (s1/s2 are LJ's names for their own versions of Perl, a specific backend coding language widely used across the web). The Perl/s1 itself does not work with Core1. There's a tiny bit more info on that here:

http://www.dreamwidth.org/support/faqbrowse?faqid=129

The upside is, if you can somehow make your CSS work on a Core1 layer (which runs LJ's old s2) or Core2 (which runs DW's newer s2) you'll get more features than LJ's s1 had (with Core2 being the most feature-rich by far).

ETA: I just realized [personal profile] momijizukamori's replies show the reason the layer compiled correctly is it was LJ's old s2 that got converted from s1. I was wondering how it could've possibly compiled myself, so that answers that question!

If it's already working as a Core1 style then it's really just a matter of getting the CSS to work with the s2 (which might require a major rewriting to match the differing HTML elements and account for any missing or extra).

Core2 would still be more feature-rich (and easier to use once up and running, because it has all the modern features that Core1's s2 lacks) so if you're going to rewrite the CSS anyway, I'd go with that.

I don't really know how to convert your layout to from Core1 or Core2, though, sorry (it's cute, though! I can see why you'd like to use it here).
This account has disabled anonymous posting.
If you don't have an account you can create one now.
HTML doesn't work in the subject.
More info about formatting

Profile

Dreamwidth style system discussion

June 2025

S M T W T F S
12345 67
891011121314
15161718192021
22232425262728
2930     

Style Credit

Expand Cut Tags

No cut tags
Page generated Jun. 6th, 2025 11:19 pm
Powered by Dreamwidth Studios