k3davis

Dan,

I’m very interested to see what you accomplish in integrating this plugin with your theme. Fortunately/unfortunately, I have mixed news to report on your request.

In the first place, while I’ve never tried it, I expect it’s possible to control the page changing from outside the viewer frame. Jumping to a specific page is handled by Javascript after that portion of the viewer has loaded. Skipping to page 2, for example, is accomplished by added this onload event to the iframe itself:

onload="javascript:this.contentWindow.location.hash=':0.page.1';"

(Note that the pages are indexed from 0, so to get to page 6, you’ll have to put page.5 on the end, etc.) You would have to try to fire this behavior using some external link or button instead of the onload event – again I’ve never tried this but it’s somewhat hopeful. 😉

As far as counting the number of pages, this is much more difficult, only because the viewer loads the pages one at a time to decrease time to actually display the first page. I’ve written some functions that do provide a page count, but they are costly in that they have to essentially load the entire document first and then count the pages. This can have pretty severe performance disadvantages, especially for longer or larger docs. I would consider this probably not useful at present.

Let me know if you have other ideas/questions, and thanks so much for your positive feedback about the plugin! Looking forward to developing it further. 2.5 was a monumental release so I expect I’ll need a couple maintenance releases to make it rock solid like 2.4.6 was, before starting to add significant new features again.

Kevin

Sorry for the trouble. There seems to be some problem with the upgrade routine that converts 2.4.x settings to the new 2.5 format, but I don’t see the problem on my end so it’s hard to track down. I’m hoping someone who has experienced this problem will be able to send me an error log with the details, or give me access to a test site where it’s occurring to test it out.

I know not everyone has the time or access to invest in that, though. I’m glad the clean install worked for you. 🙂

Note there are a few issues some have seen with WP 3.5 (which this thread says you’re running). I’m currently investigating these. If you run into any more snags, please let me know.

2.5 was a major undertaking, so I’m not surprised that some issues slipped past beta testing… thanks for your patience. Let me know what you find out or if you need any more help.

Chad,

Thanks for your note. A few others have had that issue as well, though I’ve not been able to reproduce it myself. For some reason the upgrade routine wasn’t able to create the necessary database tables.

I’m glad the issue resolved itself, but if you care to reproduce it and provide a log of the problem, I may be able to improve it in a future version. Thanks.

Kevin

Thanks Clifford, I added this note to the FAQ.

Yes, the GDE site is temporarily down while I update all the documentation. Sorry for that inconvenience.

I have planned to support the title attribute in the next version after 2.5. The changes in 2.5 are extensive and I am hesitant to add anything else at this point that would extend the beta cycle. But be assured this is already on my list. 🙂 Thanks.

Kevin

It’s fine and normal to host your files on the same server as WordPress. So that’s not an issue.

“Took too long” could be the result of several things – the server you’re hosting on is slow, underpowered, or over-shared, making Google’s request for the document laggy. A network issue (perhaps temporary) has caused a delay between your server and Google. Or, your source document is too large/not web optimized.

Hope this helps.

Kevin