Inline code tag not working in Markdown on Ghost blog

Posted March 15, 2017 4.1k views

In Ghost’s preview the inlinecode looks fine but when I publish the blog post and load in Safari or Chrome, it shows up as plain text. Here’s the post:

Adding new users

While you can use vipw to edit the user configuration files, it is better to run useradd.

vim /etc/default/useradd

The output should look similar to this:


Useradd examples

  • useradd -c "Comment here" sarah -s /bin/bash sets a comment (-c) and defines the default shell (-s)
  • useradd bob -s /usr/sbin/nologin sets nologin as the users’s default shell because many users don’t need shell access
  • useradd -m -u 1201 -G ops,dev linda adds user, adds home directory (-m), adds user to groups ops and dev (-G), assigns _UID 1201+ (-u)
  • useradd creates a locked account until you run passwd user

The login configuration file

The /etc/login.defs file sets the configuration for the for the Shadow Password Suite. The following are some of its most significant attributes:

  • MOTD_FILE: Defines the file that is used as message of the day file. In this file, you can include messages to be displayed after the user has successfully logged into the server.

  • ENV_PATH: Defines the $PATH variable, a list of directories that should be searched for executable files after logging in.

  • PASS_MAX_DAYS, PASS_MIN_DAYS, and PASS_WARN_AGE: Define the default password expiration properties when creating new users.

  • UID_MIN: The first UID to use when creating new users.

  • CREATE_HOME: Indicates whether or not to create a home directory for new users.

  • USERGROUPS_ENAB: Set to yes to create a private group for all new users. That means that a new user has a group with the same name as the user as its default group. If set to no, all users are made a member of the group users. [^n]

System-wide Bash shell startup files

  • /etc/profile runs system-wide environment variables and startup scripts
  • /etc/bashrc contains system-wide aliases and functions [^n]

Bash shell personal startup files

While creating a user, useradd copies the /etc/skel user environment configuration files to the new user’s home directory. The following are the default configuration files:

  • ~/.bash_profile contains personal environment variables and startup scripts
  • ~/.bashrc contains personal aliases and functions
  • ~/.bash_logout contains personal scripts to run on logout[^n]

Using usermod to modify users

These are a couple common use cases for usermod:

  • usermod -g sales mike adds mike to sales as primary group
  • usermod -aG ops lisa adds lisa to ops as a secondary group

Managing password properties

Here are some example use cases for passwd and chage:

  • chage -E 2018-12-31 bob sets Bob’s account to expire on a specific date
  • chage -l linda lists account aging information
  • passwd -n 30 -x 90 lori -w 3 sets minimum password age of 30 days, a maximum password age of 90 days (-w), and starts warning the user 3-days before the password expires (-w)

Linux group management

The useradd command creates a default primary group with the same name as the user.

When a user creates a file, the group owner will be set to that user’s primary group. Users have access to files owned by their secondary groups.

Use the id command to list a user’s group memberships:

id linda

The output should look something like this:

uid=1002(linda) gid=1003(account) groups=1003(account),1001(sales)

A common use case for secondary groups is to share documents between departments with a file server.

Creating groups

To create a new group, you can use the vigr command to directly modify the /etc/group file or you can run the groupadd command.

  • groupadd devs adds a group called dev
  • groupadd -g 404 devproject adds a group called devproject with Group ID (GUID) 404
  • grep devproject /etc/group to confirm that you successfully added a group

Modifying group membership

  • usermod -g 1003 frank changes frank’s primary group to account, assigning GUID of 1003
  • usermod -aG dev lori adds account as a secondary group for lori
  • usermod -g sales anouk changes anouk’s primary group to sales

[^n]: Excerpt from Sander van Vugt’s Red Hat® RHCSA™/RHCE® 7 Cert Guide Premium Edition

[^n]: Derived from Linux From Scratch

[^n]: Derived from Linux From Scratch

  • @marmot7
    I don’t understand the problem. The website looks similar to what you posted here.

  • @hansen The issue is the inline code in particular looks like plain text. It’s not showing up as inlinecode. So multi-line blocks of code look fine. The inline does not. For example, useradd neil is inline.

  • Okay, i just switch themes and it worked perfectly. Thank you!

    I may try to customize the css later but the immediate goal was to get this looking reasonable as these are notes for a class I’m taking an online RHCSA course, and other students expressed interest in my class notes so I’m going to clean them up and publish as a series of blog posts as the class progresses.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer

So for example, the section called “Useradd examples”, the first line has a <code>-block with the following useradd -c "Comment here" sarah -s /bin/bash, but there’s just not any CSS making the background gray.
If that’s what you’re talking about, then just add this to your CSS:

code, kbd, pre, samp {
  background: #F1F0EA;
  border: 1px solid #DDDBCC;
  border-radius: 3px;
  padding: 2px;
  • Thank you. I’ll give that a go or possibly switch back to the them that worked. It occurs to me that I switched themes between the last post that made use of inline code. I went back to look at that post and, sure enough, it’s no longer working there either.

    This is making more sense now as Ghost’s preview does not use the theme’s css, explaining why it works there but not in the web version.

  • @hansen

    That’s what I was about to say as well.


    When you look at the source code, the text that is wrapped and has a background is within:

    <pre><code class="language-  ">

    While the non-highlighted is just wrapped in:


    That’s the main difference. The extra class="language- " is what’s adding the styling. So to get the same effect, you’d need to add your own custom styling to the stylesheet.

    • @jtittle Seems like you need to change your ballroom shoes - they’re slowing you down :::)))

      • @hansen

        heh – there’s also some heavy caching going on over on my end it seems. I’ve put in a ticket about it, but it seems that even when I hard refresh or log out/in, the cache does not clear so I often don’t see a response before I post mine.