Hello,

Sorry i've never submitted an issue before so i hope this is correct and the information is sufficient.

We have installed your Page Preview module on both a dev and live site. It works brilliantly on the dev site but when the module is enabled on the live site we unfortunately come up against an issue. The preview will generate however the content typed into the editor does not display. Instead we receive a message:

"Page Not Found - The requested page could not be found".

Could you advise if this is related to the Page Preview module or is it something else entirely?

CommentFileSizeAuthor
page_preview.png58.47 KBmichael.simpson

Comments

FreddieK’s picture

I'm experiencing the same problem when anonymous users are allowed to create and preview a node type. It looks like it might be related to pathauto module permissions.

krolpl’s picture

Same issue here

les lim’s picture

Status: Active » Fixed

This is probably because of problems with token generation. We don't really need to use the form token to identify the preview; we can generate our own ids.

Should be fixed in the next dev release.

Status: Fixed » Closed (fixed)

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

alanom’s picture

Status: Closed (fixed) » Needs work

Sorry but I'm seeing the same in the latest dev version.

Any pointers on what changes were made, what possible causes there are?

My case: page manager pages, anonymous users can't create or preview. Nothing in logs (other than the 404 error)

EDIT - It seems to be a timing thing in my case. If I refresh the page, or copy the URL into another tab, it appears fine. I'm using the background process module - could that have something to do with it? Maybe it's happening asynchronously with Background Process installed when it shouldn't?

alanom’s picture

False alarm! This happened on the first attempt but has worked fine since then. No idea why, but all seems to be working okay now.

nicholasthompson’s picture

Issue summary: View changes

This happened to me until I ran a cache clear all (the menu hadn't rebuilt after enabling the module). I was also using memcache_storage...