Ben Balter

Great. Will push an update momentarily. Thank you for taking the time to test and report back. I’m sure many users are grateful.

Closing here in favor of duplicate issue https://www.ads-software.com/support/topic/completely-broken-due-to-twitter-api-update?replies=9. Please follow that thread for updates.

I believe version v1.5.5. RC2 of the plugin should resolve the problem. If anyone can test and confirm that that is the case by downloading and uploading the linked .zip file, we can update the plugin here. Thanks everyone for their help getting this release polished.

Is anyone able to test a quick update which adds support for Twitter API v1.1?

https://github.com/benbalter/Twitter-Mentions-as-Comments/releases/v1.5.5-rc1

(background: https://github.com/benbalter/Twitter-Mentions-as-Comments/pull/30)

Hoping to get it updated here and working very soon.

Are you able to give the development version a try? If that version resolves the issue I can update the plugin in the repository.

Are you able to give the development version a try? If that version resolves the issue I can update the plugin in the repository.

Assuming you are not passing any conditions to the shortcode, all the shortcode does is fire get_documents() which is itself, a wrapper for WordPress’s native get_posts() function.

It could be that the revisions aren’t properly saving, which could cause a problem further down the pipeline, but other than that it shouldn’t touch WordPress’s core functionality.

I’d recommend updating to the latest version of the plugin and WordPress if you haven’y already, and disabling all other plugins. If the problem persists, and you’re a bit familiar with code, you can try to recreate the problem either in WP Debug Bar’s console, or by adding commands to output documents in the shortcode function, as well as get_documents.

Awesome stuff. Don’t hesitate to let me know if there’s any way I can be helpful.

Two quick things:

1) May make more sense for the counter to hook into serve_document rather than template_redirect which will better account for 404s, private documents or password protected documents, etc.

https://github.com/benbalter/WP-Document-Revisions/blob/master/wp-document-revisions.php#L718

2) Feel free to give yourself a shout out, etc. in the FAQ. So people looking for download counters, widgets, etc. can find your plugin if you want — https://github.com/benbalter/WP-Document-Revisions/wiki/Frequently-Asked-Questions

If there’s any way document revisions can make your plugin easier (or if you want to contribute), always more than glad to accept a pull request! ??

Not sure why this is happening, and having trouble recreating it. I’ve opened an issue on GitHub.

if you have the ability to troubleshoot, any information (or a pull request) would be awesome.

Not sure why this is happening, and having trouble recreating it. I’ve opened an issue on GitHub.

if you have the ability to troubleshoot, any information (or a pull request) would be awesome.

You need to increase your PHP Memory Limit:

https://www.dailyblogging.org/wordpress/increase-wordpress-memory-limit/

You can do that via your theme’s style.css

The page should contain the position title and description. If not, it would most likely be a templating issue, which you could make a template specifically for the position post type.

Can you give me some more information on your setup? WordPress / plugin version? Also, what is your username by chance? does it have a non-alphanumeric character?

Good find. If you could package this into a pull request on GitHub, would love to include this in the plugin.