When you view the blog index page, the formatting of the text in the post previews does not match the formatting in a post when viewed as a permalink.

Index page:

Individual/permalink post:

I'm seeing this in firefox, but not safari or chrome.

Where's the demo link?

ERROR [2017-10-29 18:58:13] "POST /ghost/api/v0.1/themes/upload/" 422 276ms NAME: ThemeValidationError MESSAGE: Theme is not compatible or contains errors. level:normal [object Object] ERROR DETAILS: fatal: true level: error rule: Replace <code>{{pageUrl}}</code> with <code>{{page_url}}</code> details: The helper <code>{{pageUrl}}</code> was replaced with <code>{{page_url}}</code>.<br>Find more information about the <code>{{page_url}}</code> helper <a href="https://themes.ghost.org/docs/page_url" target=_blank>here</a>. failures: - ref: partials/pagination.hbs message: Please remove or replace {{pageUrl}} from this template code: GS001-DEPR-PURL ThemeValidationError: Theme is not compatible or contains errors. at ThemeValidationError.GhostError (/var/lib/ghost/versions/1.16.0/core/server/errors.js:9:26) at new ThemeValidationError (/var/lib/ghost/versions/1.16.0/core/server/errors.js:52:20) at resultHandler (/var/lib/ghost/versions/1.16.0/core/server/themes/validate.js:32:31) at tryCatcher (/var/lib/ghost/versions/1.16.0/node_modules/gscan/node_modules/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/var/lib/ghost/versions/1.16.0/node_modules/gscan/node_modules/bluebird/js/release/promise.js:510:31) at Promise._settlePromise (/var/lib/ghost/versions/1.16.0/node_modules/gscan/node_modules/bluebird/js/release/promise.js:567:18) at Promise._settlePromise0 (/var/lib/ghost/versions/1.16.0/node_modules/gscan/node_modules/bluebird/js/release/promise.js:612:10) at Promise._settlePromises (/var/lib/ghost/versions/1.16.0/node_modules/gscan/node_modules/bluebird/js/release/promise.js:691:18) at Async._drainQueue (/var/lib/ghost/versions/1.16.0/node_modules/gscan/node_modules/bluebird/js/release/async.js:138:16) at Async._drainQueues (/var/lib/ghost/versions/1.16.0/node_modules/gscan/node_modules/bluebird/js/release/async.js:148:10) at Immediate.Async.drainQueues (/var/lib/ghost/versions/1.16.0/node_modules/gscan/node_modules/bluebird/js/release/async.js:17:14) at runCallback (timers.js:672:20) at tryOnImmediate (timers.js:645:5) at processImmediate [as _immediateCallback] (timers.js:617:5)

It seems Ghost 0.5 has been ready for production. Would you plan to upgrade Vapor to ghost 0.5? Or is it now already compatible with 0.5?
Thanks.

When you type an HTML table into the ghost editor you see the table show up as a nice "zebra" table in the preview. However, once you make an actual post the style you see in the preview goes away and instead you see a narrow table that is unstyled. It would be nice if there was a Vapor specific styling consistent with the style in the preview pane.

Hi, as a normal user who's actually comparing themes of the community is always nice to have screenshots of the final theme to help users decide if they want to use this theme

What do you think?

Just thought I'd drop in and post a link to theme developer guide to what changed in Ghost 0.4.

I'm trying to encourage as many theme devs as possible to upgrade to use the {{asset}} helper in particular. Without this change, your theme won't work when Ghost is installed in a subdirectory, and users may encounter caching problems.

Thanks 👍

Replace current Disqus implementation with a commented section or file with multiple comment options including Disqus, Google+, and maybe Facebook.

It looks like my hosted blog (cjremus.ghost.io) at ghost.org was just updated to the 0.4.2 Maintenance Release and that new release may have broken the Vapor theme. Could it be that the Vapor theme's not compatible w/the 0.4.2 release? Nothing else that I'm aware of has changed on my installation. Please let me know if you need any additional info to troubleshoot, happy to help out where I can. Thanks..Chris

It is a great theme, but doesn't show the links to the static pages anywhere.
Would be brilliant if that could be supported.

With the last major revision of this repo being launched over a year ago, I have to ask if this is still an actively supported project, If it is, can we expect an update soon? I'm seeing deprecation notices when I test the theme on my local development version, asking that pageUrl be updated to page_url. Ghost stopped supporting this call syntax in version 0.6, and the production version of Ghost is now up to 0.7.

I think it might be silly 😅, but I think it would be nice to put the steps to start using it in the README, I think it can help more people use it.
If you think it's a good option I can try to make it the best I can

Is anyone else seeing a change in the font used to display the content? I checked my blog randomly this morning and found that the font-face had changed to what looks like Open Sans? Did something happen with the primary Merriweather font in the CSS?

h1,
h2,
h3,
h4,
p,
li,
dt,
dd {
  font-family: "Merriweather", "Open Sans", "Helvetica Neue", Helvetica, Arial, "Nimbus L", sans-serif;
}

It seems that when you click on the author name it takes you to a 404 page. I looked at the address and it has the email address of the blog as the destination page. Is there a variable that I am supposed to set for this?

Love the theme, thank you for your time.

you should give #blog-logo text-align: center as a blog logo smaller than 100px will be aligned to the left.

Example:
http://kaumgeschlafen.ghost.io/

I tried to add Disqus comments to posts today, following these instructions -

http://blog.christophvoigt.com/enable-comments-on-ghost-with-disqus/

When I went to add my Disqus "universal code" to the post.hbs file, I saw that the code was already in the post.hbs file. I compared the "universal code" provided by Disqus to the code in the post.hbs file and it looked like all I had to do was change the disqus_shortname variable, which I did.

Here's what it looks like -

I uploaded a new .zip file theme to my blog that includes the updated post.hbs file. However, Disqus is unable to verify the install and the comments aren't showing as a result.

Any help on what's wrong here would be appreciated, thanks!

Description text isn't centered on an iPhone (small screen) like it is on an iPad or Desktop.

Is there anyway I can show view count of post?

Great theme...just uploaded it yesterday and like it a lot!

Right now the link to the author name is a combination of -

• path to the most recent post

and

• the URL that I add in my Ghost user profile

http://cjremus.ghost.io/rolling-with-this-first-thing/cjrcycl.es

Any chance to make the link point to a user-defined page, i.e. twitter account, other contact or profile info? If not, how about just pointing it back to the blogs home page for now? Right now the above link is sending readers to a broken link.

Thanks!

When I first started with Vapor I enhanced it with Tapirius, which is a really cool search bar using .js. I'm thinking since Vapor has no native search capability, it might borrow from Tapirius, similar to plans to incorporate Prism.js for v1.5.

You can test it on my blog, the classic yuppie, and enter "Mavericks" in the search bar.

According to the local version of Ghost I have running for testing purposes, Vapor does not have a package.json file. According to the error, while not required now, it will be in the future, and I'd rather not have my Ghost blog borked by an omission. The exact warning message is:

Warning: Found a theme with no package.json file 
 Theme name: Vapor-master 
 This will be required in future. Please see http://docs.ghost.org/themes/

According to the developer documentation on Ghost.org, package.json will be required as of Ghost 0.6. I know it's a bit of a ways off from 0.6, but are there any plans to implement package.json prior to that Ghost release?

Hi,

Just a suggestion. Maybe you could include instructions, or a direct link to explaining how to install the theme in the readme.md.

Ghost 2.0 was released today (https://blog.ghost.org/2-0/) and Vapor 1.5 is no longer compatible. According to Gscan, here's what we need to fix:

Must Fix:

• The {{#if author.*}} block helper should be replaced with {{#if primary_author.*}} or {{#if authors.[#].*}}
• Replace the {{author.name}} helper with {{primary_author.name}} or {{authors.[#].name}}
• Replace the {{author.bio}} helper with {{primary_author.bio}} or {{authors.[#].bio}}
• Replace the {{author.website}} helper with {{primary_author.website}} or {{authors.[#].website}}
• Replace the {{author.profile_image}} helper with {{primary_author.profile_image}} or {{authors.[#].profile_image}}
• The .kg-width-wide CSS class is required to use your theme with 2.0
• The .kg-width-full CSS class is required to use your theme with 2.0

Should Fix:

• package.json property keywords should contain ghost-theme

I'm going to give this a shot sometime tonight or tomorrow when I get a chance, but figured I'd open an issue for it in case anyone wants to get ahead and submit a PR before I do.

In the section of Thanks in line:
Thanks to @JohnONolan for suggesting this project, the to suggesting this project is broken.
I've tried to find the link to correct it, but I can't find it.

If I enable the menu in the default.hbs file, I see some static menu instead that the theme uses the Ghost navigation settings...

The white space between menu items is not equal. Instead the space between the last item and the second last is always less, whereas the other spaces are equal. It is independent of the number of menu items. I have used the most recent version of Vapor.

The error seems to be caused by the .last-child qualifier in the css. If I remove that, it looks a lot better.

If the image of the author is not in a square format, it will be disorted in the author block in the post view.

Possible (certainly not the best) solution:

Switch from an img tag to a div with an background-image:

posts.hbs line 45

<div class="userimage" style="background: url({{author.image}})"></div>

screen.css line 242

div.userimage {
  width: 70px;
  height: 70px;
  border-radius: 50%;
  background-size: cover !important;
  background-position: center center !important;
  margin-right: 10px;
  float: left;
}

Thanks for the great work you've put so far into this project! :)