Further to the above…
I continued to test and found that it was NOT caching that was the issue as other forums had suggested. It was a different type of plugin altogether, “WP to Twitter”, that was attempting to publish to Twitter. It is broken and not working. Apologies for my query as I had read so many posts blaming such issues on caching that I had not extended my testing much beyond that. This makes sense now that I think about it, because I recall that the problematic plugin that posts to Twitter does so BEFORE tags and other metadata are saved to the DB. Which would explain why the USP posts were being submitted but without the custom fields and other meta that would save AFTER the broken plugin was interfering.
And a pox upon plugin writers who write 3-word error messages like “Security check failed”. 🙂
My faith and confidence in this excellent User Submitted Posts plugin is reaffirmed.
Based on another report, I believe that this is related to posts submitted on post types that are enabled for WP to Twitter but submitted from outside the WordPress admin; can you confirm this?
Hey @thesleeper glad you got it sorted, and thanks for following up with your results. Feel free to post again with any further feedback, etc. Glad to help anytime.
@joedolson it’s not something I’m familiar with; my current test show normal functionality with custom post types.
-
This reply was modified 3 years ago by
Jeff Starr.