Leevi,
I finally got this working. My fault originally. I overlooked the fact that I needed status=”not closed” in the weblog:entries opening tag. Makes sense after I read your tutorial on Newism for the fifth time. Don’t know how I overlooked it the first four times, but anyway, here’s two more bugs that I’ve ran into (or I assume they are bugs). Could be something I’m doing (again).
So, first, as soon as I go to publish a new entry everything looks normal and I have the message “Save this entry to enable Live Look.” So, I fill in all of my fields and then click quick save so that I can view the live look preview. Upon clicking quick save, I get this error:
MySQL ERROR:
Error Number: 1064
Description: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 1' at line 1
Query: SELECT * FROM `exp_weblog_titles` WHERE entry_id = LIMIT 1
Aside from getting the error, everything seems to be fine. By that I mean that all I have to do is click the browser back button which takes me back to the entry and then if I click the “edit” tab in the CP, the new entry is there and all I have to do is click on it and I can go back in and view the live look preview and everything works fine from that point on (even the quick save). It’s just that first initial time if I click quick save.
EDIT: Disregard the above. I obviously need to read the WHOLE thread before posting.
The second thing I’ve encountered is because of another extension but I figured I’d mention it to you regardless. Maybe it’s an easy tweak? On our company site, I’ve installed the tab forward extension so that I can select the “show all” tab by default. That way, our users don’t accidentally miss a setting when publishing an entry. When I save the entry and then go back into the entry to view the live look preview, the “show all” tab is selected as normal. The live look preview area is there but it’s just a white box and it does not show the preview until I actually click on the “live look” tab. Not a huge deal, but figured I’d mention it.
Thanks for this extension. It will prove wonderful for our users. I’ve been asked many times over why when they click the “preview” button inside the publish page why it doesn’t look like the live site, so this will be fantastic.
I’ll add support for this in the next version. Basically if an entry is a page I’ll just use the {page_url} as the Live Look tab value.
That is great. Sorry about my wrong comments. Though I tried the pages module once we never really use it. I was misinformed.
So far the extension is working great on our production server. Everyone is happy with it.
I haven’t been able to get any of the errors others have posted. I may just be luck 😉
Love this extension!
Instead of making a new status, I just setup a separate template that has status=”closed|open” so that users don’t have to change status to preview it. Also in this separate template, I am previewing what the exceprt looks like on the homepage, and I added warnings at the top in red if an article is not categorized or tagged. Showing them what they haven’t done correctly so easily on the publish page is key. It works like a charm and as really helped my users shape up with their inputs. Thank you Levi!
Love this extension! Instead of making a new status, I just setup a separate template that has status=”closed|open” so that users don’t have to change status to preview it. Also in this separate template, I am previewing what the exceprt looks like on the homepage, and I added warnings at the top in red if an article is not categorized or tagged. Showing them what they haven’t done correctly so easily on the publish page is key. It works like a charm and as really helped my users shape up with their inputs. Thank you Levi!
Nice idea, If your willing to make an extra template you can do lots and lots of things. Personally I still prefer the single template option. You could use a single template and still display the warnings using conditional template logic:
Firstly, Leevi, what a wonderful little example of EE magic you’ve pulled off here. Thanks very much for writing it.
Re:
MySQL ERROR:
Error Number: 1064
I have a client who still very much likes to use the built-in CP preview as well as the Live Look, but they run into the error above without fully saving.
Can you estimate when you might find a work around for the need to do a full save?
Keep up the great work, LG. Impressive stuff.
Thanks so much for this fantastic extension, in addition to the rest of your great work Leevi. We really appreciate it!
I get the following error when LiveLook is enabled on a weblog. It occurs when I’m starting a new entry and try to quick save it. It will still save the entry, but it will kick back a blank page with this error.
MySQL ERROR:
Error Number: 1064
Description: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 1' at line 1
Query: SELECT * FROM `exp_weblog_titles` WHERE entry_id = LIMIT 1
This does not occur when clicking “submit” on a new entry or clicking “quick save” or “update” on an existing entry.
I’m getting a conflict with Live Look and Solspace Tags Module (v2.5). It causes the iframe to not load. If I disable Tags, it’s fine.
Here’s the error:
$iframe is not defined enlarge_iframe()index.ph…e3Q== (line 2102) onclick(click clientX=1361, clientY=177)index.ph…q6g== (line 2) [Break on this error] undefined
If I click on the Live Look tab, I get nothing. If I click on the “enlarge” button I get this error.
I’m having trouble getting this to work.
Everything works fine, except the preview tab is coming up blank. There are no jquery errors coming up in firebug and no error messages are visible. I’ve tried it on a development server and a live server. I’m using EE version 1.6.3.
It looks like a great extension and it will definitely go down very well with my clients!
Thanks,
Antony
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.