k3davis

Hi there, and thanks for reading the documentation before reaching out for help… a small act of relief for one-person volunteer dev teams. 🙂

So long as the files exist on a public network (ie., I would be able to reach them from anywhere if I knew the URL, not stored on a private or protected space) you can use GDE even on a localhost or private install of WordPress.

In GDE 2.5.x the setting is “Check for errors before loading viewer”. Turning this off has other consequences, such as the plugin won’t be able to report the file download size in the download link. But so long as the file is indeed public (even if the site isn’t), it should work with this setting turned off.

Hi Geert,

I’m sorry you’re having trouble, but if it wasn’t working on my site I would have noticed (meaning, it’s working fine on my end)… check your browser cache or give me a specific URL where you’re seeing a failure.

Thanks!

The code there is straight out of the Codex so I don’t know why you’re getting a fatal error from it.

To bypass this portion of code, though, you can find this line near the top of lib-setup.php (currently on line #17:

$env['apikey'] = gde_get_api_key( $env['pdata']['Version'] );

and change it to something like

$env['apikey'] = '123456abcdefg';

Doesn’t explain why you’re having the issue, though.

I try to clean these messages out but may have missed that one in your case. You might find though that deactivating and reactivating clears that, if it’s annoying you.

In any event this is a notice message and not an error, most likely the result of having WP_DEBUG enabled in your wp-config file, which isn’t normally a production value in WordPress.

Unfortunately that’s a symptom of the same problem. GDE can’t access the document normally to either show it or get its file size because of the 403 header being sent. Turning off that setting tells GDE not to bother checking for either of those things, which in your case helps the document to display anyway but makes checking the file size impossible.

You may want to check the permissions on that folder (or refer to your web host) and investigate why its returning an HTTP 403 response. Then you can turn that setting back on and get the document size.

Hello,

Your document is clearly accessible without authentication, so I’m not sure why the server you’re on is returning an HTTP 403 response. However this can be quickly bypassed by going to the Advanced tab in GDE Settings and unchecking the option “Check for errors before loading viewer”.

Hope this helps.

In the next day or two… just testing it as much as possible first.

I haven’t had the experience often that it “completely fails” – though yes, there is a marked impact on performance with the enhanced viewer in some cases.

I’m interested in hearing more about your idea, and I’m open to collaboration of course. The immediate problem I see with the proposal is that caching images – unless we cache them at their largest possible size – would defeat the zoom capability. Caching the XML is easy enough, but the images could be burdensome even on a few long documents, let alone a library of them at full res. Nonetheless, it’s worth some thought. Feel free to get in touch directly (my email address is in gviewer.php in the GPL statement).