Forum Replies Created

Viewing 15 replies - 526 through 540 (of 975 total)
  • Could you send me an example link, and the shortcodes you’re using? I’ve never tried the arrangement you’re using now, I’d be interested to see it.

    Hi JLDV,

    Looks good for me in Firefox. (I don’t have Safari installed.)

    You were on the right track with clearing the cache. While I’m not too familiar with Safari’s cache options (for obvious reasons) be sure you’re also clearing “active logins” (as it’s called in Firefox) or “active sessions” or the like.

    Another way to troubleshoot, if possible, is to view the page in Safari on another device that you know hasn’t visited the page before. That would make it very clear when you’re having a local issue, as clearing cache is actually really a complex issue in modern browsers, which have multiple types of cache and many levels of options to do this.

    Let me know how it goes,

    Kevin

    My pleasure. Thanks for the kind remarks about the plugin.

    In hindsight, I’m sorry JTobey for misunderstanding your question. Hopefully this answer is more helpful. πŸ™‚

    Kevin

    Certainly, this behavior in GDE can be turned off.

    In GDE 2.4.x:

    GDE Settings > Advanced Options/Editor Behavior > uncheck “insert shortcode from Media Library”

    In GDE 2.5:

    If you’re using WP 3.4.x, you can check/uncheck a box in the media library itself to use the shortcode or not at the time of insertion. This does not work with the uploader changes in WP 3.5 beta yet, but the above setting still exists also:

    GDE Settings > Advanced tab > uncheck “Insert shortcode from Media Library by default”

    Hope this helps.

    Kevin

    Hi, glad to hear it’s working for you.

    99% of the problems people encounter are due to either browser cache or stale Google account login issues. So while there is no wide issue with embedding documents using Firefox, you might suggest they clear their browser cache (including “Active Logins”) and see if that resolves the issue.

    If you find you can reproduce a problem I’m happy to investigate it. The update does fix a few small known issues but is mainly a new feature release (improved settings, secure document support, etc.).

    Thanks,

    Kevin

    Brad,

    GDE is not designed to embed documents from Google Docs. I wish that I had more foresight when selecting the plugin name 2+ years ago, but it’s named after the fact that it uses Google Viewer apart from Google Docs – a solution Google has offered for translating docs that people host locally, not behind their service. Also, unfortunately, a service that (like so many Google offerings) has only been partially developed and tends to languish.

    If you want to store your docs in Google Drive then by all means follow your method, in fact as you quoted my plugin doesn’t even attempt to handle that scenario. The purpose of my plugin is to allow local hosting and to automate that tedious process to some degree. How “reliable” my plugin is depends a lot on your own environment and the settings you choose. At its base it is a straight up Google embed and it works reliably for thousands of users. No, it’s not perfect, as more than 50% of the equation isn’t even under my control as the plugin author. But it does work, and if you want help, feel free to ask. Otherwise, I’m happy to hear your suggestions for improvement.

    Kevin

    I’ve never used the peekaboo plugin myself, and it would probably be more effective to ask the author of that plugin how it works. All I can tell you is you use whatever code that plugin uses to collapse content and put the GDE shortcode inside it.

    Again, I recommend you ask the plugin author for help. I want to add a feature like this as a display option in GDE 3.0, but until that time it’s not really feasible for me to support plugins I didn’t write and haven’t used personally… I gladly give a lot of time to support the ones I did write already πŸ˜‰ Thanks for your understanding.

    I believe your answer is already in this thread – you can wrap the shortcode for GDE in the shortcode for peekaboo, or a similar plugin:

    http://wordpress.org/extend/plugins/peekaboo/

    Can you clarify what you mean about “I want to the text to be linked to the doc”?

    For pages where you don’t want the viewer, you don’t need to use the shortcode at all, but just insert the link using standard WP means. I presume this isn’t what you mean, though, so feel free to explain further.

    Thanks,

    Kevin

    Hi there,

    The plugin fails to load because it is expecting the file to end in one of the supported file extensions (in this case “.pdf”). It appears UbuntuONE is using some other kind of code to represent the true name of the document. I believe this will still work in GDE (though admittedly I have not tried it) if you turn off the plugin’s own error checking.

    To do this in GDE 2.4.x –

    GDE Settings > Advanced Options/Plugin Behavior > check “Disable internal error checking”

    To do this in GDE 2.5.x –

    GDE Settings > Advanced tab > uncheck “Check for errors before loading viewer”

    Hope this helps.

    Kevin

    Thread Starter k3davis

    (@k3davis)

    It strikes me as pretty late in the beta cycle to have to implement all these drastic changes. My situation is a bit different as my plugin doesn’t revolve around this functionality but only uses it in a rather token way; most of the action can similarly be handled via a TinyMCE plugin. I’ve had to make the unfortunate choice to remove the media uploader integration for 3.5 users for the time being, as this version of WP is near release and as far as my limited purposes, this feature is broken. I’m hopeful to restore it once I find appropriate documentation of the changes and can find a way to implement with backward compatibility intact.

    This isn’t a limitation of the plugin but the way the CSS works. You can use the class applied to the whole iframe in your CSS to make it responsive, though in that case the inline style might conflict. You could try adding !important to your own CSS styles to see if that would overrule (not sure if it does). Maybe I should have the option of not including an inline size in this event…?

    The parent frame isn’t likely to have a height set – it’s usually just loaded in the body of the page – so it just scrolls forever until the page ends. That’s why 100% height doesn’t work, and presumably why you can’t find it in firebug.

    I’m sorry, …what?

    GDE 2.5 supports reasonably private documents. While there would be potential ways to exploit it, none should be obvious to the casual observer.

    You can use the delivered “max-doc-security” profile or set any other profile to block downloads. The download is only blockable though in certain circumstances. The document isn’t blockable if you opt to show the download link (obviously). It isn’t blockable if you choose the Standard Viewer (Google’s default viewer doesn’t offer this fuction). As far as the toolbar is concerned, you must either hide the new window button or change its behavior to open in a full screen viewer instead of the Google Docs page, since that page contains a download link of its own.

    Is it just confusing or have you actually managed to bypass a document set to be blocked from download? Where is the problem you’re having?

    Thread Starter k3davis

    (@k3davis)

    This is still an issue in beta 3.

    To clarify the behavior: The initial load of the Visual editor with this filter in place works. After switching to “text” editor and back again, the tinymce editor is loaded (not the wordpress version, but the actual standard tinymce buttons). So the argument is honored on the first load and apparently ignored (or something else is going wrong) on subsequent clicks on the Visual tab.

    Hi os2mac,

    Setting the document height to 100% in CSS probably does not do what you think it does. 100% height makes the document the full height of the parent container, not of the document itself. Since the parent container has no fixed height (which is normal – you want the page to expand to fit its contents) the browser has nothing to reference. In effect the browser says “100% of what?” and gives you the minimum.

    I recommend you set the height to a fixed pixel value, or else you can wrap the viewer in a div of a fixed height (which seems a bit redundant).

    Thanks,

    Kevin

Viewing 15 replies - 526 through 540 (of 975 total)