Posts tagged with “Chyrp”
any colour you like
I wanted different colors and fonts for the stardust theme in chyrp.
Plan A
I edited /themes/stardust/stylesheets/screen.css. This worked but screen.css ended up a bit of a mess and I had trouble tracking some elements down.
Plan B
I put my edits in a new file /themes/stardust/stylesheets/screen.neilt.css. I used the excellent Inspect Element facility in Safari to find out the styles for elements. I then put the styles for just those elements that I wanted to change in screen.neilt.css. This works because chyrp loads all the style sheets it finds in the stylesheets folder. Chyrp must of course load them in the correct order for my styles take priority over previous styles. I am not sure of the rules that govern the load order but alphabetic seems to work for this situation.
chyrp modules work after all
I asked a question about my chyrp module problem on the chyrp community forum and got some prompt and helpful replies.
Turning off Javascript is a quick and easy way to expose a link to enable or disable modules and feathers. The issue with dragging modules from disable to enable is a work in progress.
12:36 PM | Tags: Chyrpmany rivers to cross
I might have titled this the long and winding road: to this weblog and the first revision to my website for some years.
Chyrp seems light enough for my means. I can't get the modules to work for now following the instructions: except that i can if i hand edit the ./includes/config.yaml.php file.
enabled_modules:
- textilize
enabled_feathers:
- text
I added - textilize to get textilize to work.
I have changed the screen.css flie to reflect my idea of taste: still a work in progress.
I have reworked neilt.org using a very differnt style and in PHP. I used my own perl template scripts to build the last version (and m4 before that).
Somewhere along the line I must have used an editor that saved the Byte Order Mark (BOM) of the Unicode Standard. My pages would not validate as XHTML 1.0 Strict! Doh! The answer came from some Googling: Joomla Forum provided the best information.
I used grep -rl $'\xEF\xBB\xBF' * from the top folder of my site to track down the files with the evil BOM. The -r recursivly checks files in sub-folders and -l prints FILE names containing matches. I either used nano e.g. nano technical/technical.php in terminal to strip out the BOM or resaved the files from TextWrangler. My pages now validate to XHTML 1.0 Strict.