Forum Replies Created

Viewing 15 replies - 121 through 135 (of 975 total)
  • Hello,

    I’m not familiar with the Restrict Content plugin, so it would be helpful if you could include a link and/or shortcode, either here or via the support form in GDE Settings, to demonstrate the problem.

    Thanks,

    Kevin

    I tried in Firefox and Chrome and both worked fine, so I wonder how you fared with the rest of my suggestion. If you don’t want to faff with any cookies, try loading your page again using the “private” or “incognito” mode to test the point.

    I did notice something interesting when loading it in IE that might give you a path to pursue if the above fails. Your page reroutes to an HTTPS version even if you specify HTTP. However, multiple resources (especially javascript files) on the page are still hardcoded to insecure versions. There are multiple errors in the console log in all browsers, even on pages where the viewer is working. My theory, specifically, is that you may be running into a browser restriction where the mixed-content nature of the page is pushing IE (and possibly FF in some circumstances) to block the viewer on disallow-frame (X-Frame-Options header) grounds.

    If you work up an interesting extension, I’d love to see it.

    Actually, I do see the PowerPoint…

    Try clearing your cache and/or a different browser to confirm. You can also try logging out of any Google accounts, and if desired logging back in. Usually a corrupt or conflicting Google cookie is at root with this issue.

    Glad the plugin has been useful to you!

    The images are PNGs.

    Hi there,

    The first item in the plugin FAQ addresses this issue for you.

    Where can the files live?

    The file to embed must first be publicly available somewhere on the internet, in order for Google to retrieve the document for conversion. You can upload it to your WordPress site using the standard techniques, or link to a file on another site. For testing purposes, your site can run locally or on private networks, but the documents you wish to embed must be publicly accessible.

    Thus, the document being on “localhost” is not supported, even if the site itself is on localhost. The plugin works by sending the document to a Google service to perform conversion. Google can’t access your localhost, so you get no document conversion. You can store the files in some other temporary location *accessible online* if you’d like to try out the plugin locally.

    Thanks,

    Kevin

    GDE has never been tested in that environment, and I don’t really know much of anything about it, so I may not be able to offer much assistance here. Perhaps you can try creating the tables manually – if there are “tables” at all in the situation. The schema normally used when setting up the plugin under mysql can be found in libs/lib-setup.php in the gde_db_tables method if you’re inclined to try.

    Wow, that is a mess, isn’t it? πŸ™‚

    I’d be interested to know if the changes you set are indeed being saved, but not displayed properly. Try setting the default language to something you haven’t picked before (just for a clear test), hitting save, and when it looks like it’s gone back to Bahasa Indonesia, leave the settings area and come back. Did the change take effect, or not?

    Either way, that’s obviously not the way it should work, but if that were a widespread problem I’d be overrun with reports about it – this version has been stable for several months. That being the case, I’d suggest a complete removal and reinstall. If you’re familiar with the dev tools in your browser, you could have those open first and see if you can notice any errors being generated on settings save that could indicate the problem file or perhaps some other plugin that is in conflict.

    Hope this points you in the right direction. If you still come up empty please submit a support request from the support tab in GDE Settings so I can have a look at your settings/environment.

    None of those – it is on the general tab, if you’re using the default profile. Otherwise, it’s on the profile tab. See this screenshot from wordpress.org:

    http://s.w.org/plugins/google-document-embedder/screenshot-4.png?r=883831

    The “remove toolbar” option is the first option under “enhanced viewer settings” which appears as soon as you select “enhanced viewer” in the first box labeled “viewer mode”.

    To be honest I’m not sure how this autoformatting works with Google Viewer, but I downloaded the original document and then highlighted the first column and explicitly set the date format of those cells to English-UK format and it appears to render in the way you’re expecting for me:

    https://docs.google.com/viewer?url=http://www.davistribe.org/temp/WC-Rota.xls

    I did have to convert it to XLS format from XLSX, but that is probably not related. Another solution to consider is to save your document in PDF format, since it is being rendered as a flat file anyway. That will help ensure it is being displayed as you intend.

    Hope this helps.

    Kevin

    I can’t give you specific step by step instructions, because they would vary too much depending on your environment, but the general idea is to use the secure documents feature to prevent people from knowing the real location of your files. That feature is described here.

    I would suggest these instructions, though whether you’re on windows or linux as a host has something to say about it:

    1) Store your embedded documents in a folder on your web site that isn’t linked to from anywhere, and known only to you. Do not password protect this folder, or GDE won’t work.

    2) Use the secure documents feature (by default profile="2" in your shortcode) eo embed the documents in a way where they can’t be downloaded and their true location is hidden.

    3) Optionally add that folder to your robots.txt file to prevent any search engine from locating the files or indexing them if they are found. (not applicable to windows/IIS)

    Arkull,

    Go to GDE Settings and switch to Enhanced Viewer. You’ll see a checkbox there to remove the toolbar.

    Kevin

    Hi Cass,

    The size limitation is only one suggestion for this issue, which likely doesn’t apply in your case given the relatively small file size. More often this is caused by servers that are slow to respond to the response from Google (USA) due to distance, intermittent network issues somewhere along the way, or too many shared hosts on the same server draining resources, etc.

    If your web host is physically located within the US, then you may just be on an overloaded server and can ask your web host to move to a server that’s less sluggish to respond. If not, you might consider hosting your documents on a service like Dropbox instead, if that’s appropriate for your content.

    For what it’s worth, I loaded the URL you provided and it worked just fine on my end – no apparent issues. So it may have just been a momentary hiccup in internet speed somewhere along the way.

    Hope this helps,

    Kevin

    Answered in your other thread

    Thanks, I’m aware of that and have a fix ready. Just trying to role it into a wider update. If you need both WP 3.9 now and GDE, remove this line from the top of js/editor_plugin.js:

    tinymce.PluginManager.requireLangPack('gde');

Viewing 15 replies - 121 through 135 (of 975 total)