MediumFox icon indicating copy to clipboard operation
MediumFox copied to clipboard

Why my posts did not show in the homepage?

Open yj14n9xyz opened this issue 11 years ago • 14 comments

Why my posts did not show in the homepage? I used rake new_post['hello world'] and the new post showed up in "all post" after I clicked it, but it was not showing up on the homepage. Any help would be greatly appreciated.

yj14n9xyz avatar Oct 17 '14 11:10 yj14n9xyz

Can confirm, I'm playing around with octopress and have the same issue with a fresh install of this theme.

I've copied a _posts directory from another project with the same theme and all posts show up within all posts. Other project is fine (but hasn't been updated in a while).

chrisRidgers avatar Oct 17 '14 23:10 chrisRidgers

I've just tried another fresh install of octopress and medium fox. Problem continues.

As an update, if you run rake install (to reinstall the default theme) the problem persists. However the initial clean install of Octopress displayed posts correctly.

chrisRidgers avatar Oct 18 '14 01:10 chrisRidgers

Another update. Problem appears to lie within the paginator.posts variable in source/index.html.

I tried inserting a bog standard

tag within the loop to test if it was at least looping but there was no output. Inserting the tag prior to the loop worked as expected.

I've also run git diff against the working fresh install of octopress and the project after installing the medium fox theme, but I haven't spotted anything obvious. I can post the output if you like although I'm not sure where would be the best place to do so?

chrisRidgers avatar Oct 18 '14 17:10 chrisRidgers

Although the code itself is near identical to my working older version; perhaps there is a problem/ change within the Octopress/ Jekyll release? screen shot 2014-10-18 at 18 58 42

chrisRidgers avatar Oct 18 '14 18:10 chrisRidgers

Victory fish.

Following advice found here I modified my paginate_path within _config.yml from "posts/:num" to "blog/posts/:num".

I'm not sure why this worked (or if it will for you), however comments on the link seem to indicate an awareness of some undocumented change within either Jekyll or Octopress. I guess the answer here is to report it to the devs of both just in case.

@sevenadrian in the mean time you may want to consider including this in the readme (unless you have a better idea) in case someone runs into the same issue in the future.

chrisRidgers avatar Oct 18 '14 18:10 chrisRidgers

Hi Chris,

It did work for me. Thanks for your efforts~

yj14n9xyz avatar Oct 22 '14 23:10 yj14n9xyz

@chrisRidgers, awesome work. This was exactly the fix I was looking for.

cnorm35 avatar Nov 30 '14 03:11 cnorm35

Thanks @chrisRidgers, I've had the same issue and couldn't find the fix myself (your suggestion fixed it for me).

alexeyza avatar Dec 08 '14 19:12 alexeyza

@chrisRidgers Thanks for tracking this down so that I didn't have to

nrmitchi avatar Jan 04 '15 06:01 nrmitchi

@chrisRidgers, The fix works, you saved my life, thanks a ton

V01dZer0 avatar Feb 13 '15 08:02 V01dZer0

Can confirm the behavior, and the fix. Thanks, everyone! @sevenadrian, please fix or close the issue.

Zettt avatar Mar 16 '15 06:03 Zettt

The change didn't work for me, but I enforced posts by changing {% for post in paginator.posts %} in {% for post in site.posts %} in index.html.

cristina2689 avatar Jun 22 '15 20:06 cristina2689

changing: {% for post in paginator.posts %} to {% for post in site.posts %} in index.html worked for me. Thanks

durrellchamorro avatar Oct 07 '15 06:10 durrellchamorro

@chrisRidgers it works for me Fantageek, too. So MediumFox must have modified the config :|

onmyway133 avatar Nov 01 '15 17:11 onmyway133