Clean install, happened with ns1 and ns2 alpha too:

- I create a new article
- set it to published
- add some media, fact boxes, polls
- assign to to one or more categories, of which 'frontpage'
- submit
- article doesn't appear, neither on the frontpage or the corresponding categories

Double checked moderations status: it's published.

Is this a caching thing?

Comments

mixhael’s picture

mixhael commented

I've added two articles now, none show up

mixhael’s picture

mixhael commented

I see what is going wrong: the automatically created web-promo is not linked to the article: when I edit this web-promo the article field is empty. When I link the web-promo to the right article it appears.

Any clue why this is happening?

fabsor’s picture

fabsor commented
Category: support » bug

This is a bug, probably related to this: #1508060: Promos don't get a reference to it's article when created through crossclone

We are working on it!

fabsor’s picture

fabsor commented

This is what's currently blocking NodeStream alpha 11 btw =)

mixhael’s picture

mixhael commented

Ok, tnx. Is there a quick patch to fix it now myself?

fabsor’s picture

fabsor commented

I pushed a fix to dev, so the problem shouldn't occur if you download the latest dev.

mixhael’s picture

mixhael commented

I just updated to the latest dev, but the problem remains exactly the same....

fabsor’s picture

fabsor commented

Did you try adding new articles after you updated? The old articles are unfortunately already "Misconfigured" and you have to add the article to the promo manually, but new ones should work.

mixhael’s picture

mixhael commented

Yes I tried it with a new one.... exactly the same problem

My update process btw was:

- downloading the latest dev-tarball via ssh
- extracting it
- replacing the old 'nodestream' installation profile folder with the new one

mixhael’s picture

mixhael commented

fyi, the new dev version fixed it!

fabsor’s picture

fabsor commented
Status: Active » Fixed

Good to see that it worked out! Closing.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.