Jim,
I’m sorry for the frustration you’ve experienced. I must agree that the plugin is handy for more casual use but doesn’t serve as well in places where guaranteed performance is critical. As I have only developed a wrapper for Google’s viewer, I’m constrained by many of the bugs and issues that their viewer presents. I’ve made inroads in dealing with some of the issues (most of all IE compatibility, which the viewer as offered by Google is incapable of) but others depend on a “combination of issues” as you’ve said that I can’t predict or improve upon. This is the peril of developing a wrapper rather than a plugin from scratch; however as my first and so far only WP plugin, that task is too ambitious for me yet.
I am disappointed that Google released this code for public use and has let it rot, as it does with many projects. Had I known the strands of issues that would keep it from being more broadly useful, I probably wouldn’t have wasted my time… as it is, lack of control over bugs such as this prevent me from developing it much further.
I did have the doc embedder set up to be working fine and was really pleased with it, but suddenly I am also experiencing this problem where it requires a gmail login.
Has anyone else found a solution or can they recommend an alternative product?
Thanks
W
(@wquinn)
Has there been any solution to this?
This is a limitation of Google’s Viewer itself, perhaps by design. Unfortunately unlike some other quirks I’ve not found a workaround for my plugin, which serves mainly only as a convenient wrapper for Google’s viewer code in WordPress.
