Dynamic pages after 6.57.3 #767

Open
peterhaldbaek opened this Issue Jan 10, 2014 · 12 comments

Comments

Projects
None yet
7 participants
@peterhaldbaek

There seems to be a problem with dynamic pages since 6.57.3. When I type an incorrect URL and receive a 404 the (dynamic) error page sometimes does not show (sometimes it does) but any requests to static pages after that are shown without layout.

If I make the 404 page static everything behaves nicely. The latest version of DocPad where it works for me is 6.57.3.

You can recreate this by running the twitter-bootstrap-jade.docpad plugin and hit a non-existing URL.

Node 0.10.23.


Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

@michaelsbradleyjr

This comment has been minimized.

Show comment
Hide comment
@michaelsbradleyjr

michaelsbradleyjr Jan 12, 2014

I'm experiencing this problem as well.

I'm experiencing this problem as well.

@RobLoach

This comment has been minimized.

Show comment
Hide comment
@RobLoach

RobLoach Jan 12, 2014

Member

Using Clean URLs plugin?

Member

RobLoach commented Jan 12, 2014

Using Clean URLs plugin?

@michaelsbradleyjr

This comment has been minimized.

Show comment
Hide comment
@michaelsbradleyjr

michaelsbradleyjr Jan 12, 2014

I'm brand new to docpad, simply did an npm install -g ..., cloned some of the skeletons, npm install . then docpad run and began seeing the 404s and the pages being spuriously returned "without layout", as @peterhaldbaek wrote.

In other words, I'm not sure if the "Clean URLs" plugin is in play.

I'm brand new to docpad, simply did an npm install -g ..., cloned some of the skeletons, npm install . then docpad run and began seeing the 404s and the pages being spuriously returned "without layout", as @peterhaldbaek wrote.

In other words, I'm not sure if the "Clean URLs" plugin is in play.

@michaelsbradleyjr

This comment has been minimized.

Show comment
Hide comment
@michaelsbradleyjr

michaelsbradleyjr Jan 12, 2014

Okay, I just checked and two of the skeletons I cloned do use that plugin, and those are the two with which I experienced the problems described above.

Okay, I just checked and two of the skeletons I cloned do use that plugin, and those are the two with which I experienced the problems described above.

@peterhaldbaek

This comment has been minimized.

Show comment
Hide comment
@peterhaldbaek

peterhaldbaek Jan 12, 2014

I'm using the Clean URLs plugin. I removed it and I still see unexpected behavior. If I type a non-existing URL I still get the 404 but the error page is not showing. Instead it seems to render one of my layouts (the jade template itself).

I'm using the Clean URLs plugin. I removed it and I still see unexpected behavior. If I type a non-existing URL I still get the 404 but the error page is not showing. Instead it seems to render one of my layouts (the jade template itself).

@balupton

This comment has been minimized.

Show comment
Hide comment
@balupton

balupton Jan 21, 2014

Member

If anyone can submit a pull request for this, that would be amazing.

Member

balupton commented Jan 21, 2014

If anyone can submit a pull request for this, that would be amazing.

@greduan

This comment has been minimized.

Show comment
Hide comment
@greduan

greduan Jan 21, 2014

Contributor

If somebody could upload a repo with everything included that would also be nice. No gitignore stuff in the middle.

Contributor

greduan commented Jan 21, 2014

If somebody could upload a repo with everything included that would also be nice. No gitignore stuff in the middle.

@djskinner

This comment has been minimized.

Show comment
Hide comment
@djskinner

djskinner Jan 22, 2014

I'm fairly sure that #778 and #741 are essentially the same issue...

I'm fairly sure that #778 and #741 are essentially the same issue...

@balupton

This comment has been minimized.

Show comment
Hide comment
@balupton

balupton Mar 4, 2014

Member

Can confirm. This has broken the kitchensink skeleton. Needs to be fixed. Has anyone had any progress looking into this?

Member

balupton commented Mar 4, 2014

Can confirm. This has broken the kitchensink skeleton. Needs to be fixed. Has anyone had any progress looking into this?

@balupton

This comment has been minimized.

Show comment
Hide comment
@balupton

balupton Mar 4, 2014

Member

Seems that it could be an issue with the router, or a conflict with livereload, rather than an issue with DocPad's generation process per se.

Member

balupton commented Mar 4, 2014

Seems that it could be an issue with the router, or a conflict with livereload, rather than an issue with DocPad's generation process per se.

balupton added a commit to docpad/docpad-skeleton-kitchensink that referenced this issue Mar 4, 2014

balupton added a commit to docpad/documentation that referenced this issue Mar 4, 2014

@peterhaldbaek

This comment has been minimized.

Show comment
Hide comment
@peterhaldbaek

peterhaldbaek Mar 4, 2014

No, I haven't looked further into this. I actually got the impression it was fixed in some of the later releases (6.61.0 or 6.62.0 I think) since some light testing didn't reveal the issue but I never tested it thoroughly. My memory on this could be wrong though. And since my blog is running fine on 6.57.3 I haven't had an urgent need to check up on this.

No, I haven't looked further into this. I actually got the impression it was fixed in some of the later releases (6.61.0 or 6.62.0 I think) since some light testing didn't reveal the issue but I never tested it thoroughly. My memory on this could be wrong though. And since my blog is running fine on 6.57.3 I haven't had an urgent need to check up on this.

@deinhofer

This comment has been minimized.

Show comment
Hide comment
@deinhofer

deinhofer Oct 9, 2014

I would like to use the search.html.coffee of the kitchensink skeleton in another repository. But have the same problem, it does not work any more:

When running docpad run, it announces that it would regenerate it, but if I try to open the page in the browser it redirects to the main page.

Are there any plans to fix this soon?
I am using docad 6.69.1

If it is not gonna fixed soon, is it easily possible to downgrade to 6.57.3?

I would like to use the search.html.coffee of the kitchensink skeleton in another repository. But have the same problem, it does not work any more:

When running docpad run, it announces that it would regenerate it, but if I try to open the page in the browser it redirects to the main page.

Are there any plans to fix this soon?
I am using docad 6.69.1

If it is not gonna fixed soon, is it easily possible to downgrade to 6.57.3?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment