Hi Brian,

Here is the URL the iframe preview is trying to load: https://beta.gocanvas.com/blog/missed-our-broadcast-with-the-sba-and-box-re-watch-kill-your-paperwork-save?publisher_status=draft&publisher_key=4oHWd3BZ

Here is the entry tag for the page:

{exp:channel:entries channel="blog" limit="1" disable="pagination|trackbacks" track_views="one" require_entry="yes"}

{publisher:entry_status} is not in the tag.

Thanks

Hi Brian,

My entries tag now looks like:

{exp:channel:entries channel=”blog” limit=”1” disable=”pagination|trackbacks” track_views=”one” status=”{publisher:entry_status}”}

You’ll have to apologize for my unfamiliarity with the add-on, but is there a recommended way to trigger an entry preview?

Thanks!

Thanks Brian,

So in theory, this URL should show a “draft” of that post:

https://beta.gocanvas.com/content/blog/missed-our-broadcast-with-the-sba-and-box-re-watch-kill-your-paperwork-save?publisher_status=draft

Right now it shows this:

This page contains the following errors:

error on line 6 at column 16: Extra content at the end of the document Below is a rendering of the page up to the first error.

I’m getting 2 different errors on that URL … one if I’m logged in and a different one if logged out.

Logged in: https://www.dropbox.com/s/w5051vbx1lom5j8/Screen Shot 2017-06-15 at 8.40.17 AM.png?dl=0 Logged out: https://www.dropbox.com/s/i3kg8p5f2f3f38j/Screen Shot 2017-06-15 at 8.45.37 AM.png?dl=0

Here is the trace from the logged in page: https://www.dropbox.com/s/wucan7f17ecb6xc/Screen Shot 2017-06-15 at 8.44.29 AM.png?dl=0

(tried to paste in as text but went over character limit for comments) … can send via email if needed.

Is the “This page contains the following errors:” not generated by publisher? Want to confirm as my hypothesis was that it was … if it’s xml / js related will have to dig in there. The code in the templates on this site are a mess.

Perfect. Thanks for clarifying. Let me see where I can get to on this side.

Thanks for the information here … Yes, this makes sense … I’m not sure why the client has Structure setup this way. From working on this this morning it seems the options are to remove the blog from Structure entirely (but then the client doesn’t have an easy way to manage this from the Structure panel going forward) or to rewrite the template to not include blog in the URL (which has negative SEO consequences).

As for the {publisher:entry_status} variable … does this need to be added to every template on the site? I’m a bit unclear of the purpose of this variable after reading the docs. This site (which to be clear I interited) has well over a hundred templates and they’re all only editable through the EE CP so modifying them would be a significant work around. Before I delve too far here want to get clarity on this topic.

Thanks for the ongoing help here.

If we made it an asset, though, the blog would be out of the tree and on the assets tab … not a bad idea but will have to run this by the client. Right … Assets don’t have templates associated with them so they wouldn’t try to render differently.

Thanks for clarifying on the publisher:entry_status … will get to work on those. Are there any other tags that Publisher absolutely needs in the templates (just so we don’t have to go through things multiple times if at all possible).

Of course. Thanks for clarifying. I appreciate the quick replies here.

Hi Brian,

Installing the most recent version of the software and clearing the cache fixed the issue. Thank you very much for your time in resolving this bug and the guidance you provided.

Thanks again