The HollywoodSouth Blog
Forum Replies Created
-
Forum: Plugins
In reply to: twitter tools 1.5.1a won’t authenticate at twitterDiscovered in the ‘Connections’ tab in Twitter (using web access https://www.twitter.com/username) there was an application blocking ‘spam’ etc.
I revoked access and it solved the problem.
Twitter Tools is attempting to login from our WP admin panel however, was being blocked by this application.
Just revoke the access in your Twitter.
Login>Settings>Connections
“You’ve allowed the following applications to access your account”
Revoke any spam blocking apps.
Good luck!
[sig removed]
Forum: Plugins
In reply to: [Plugin: Contact Form 7] Rollback to v1.10.1 SQL Table Not CreatedAH! That explains it! Ha!
Thanks!
We’re not crazy after all.
Great plugin.
The HollywoodSouth Blog Team
Once posted, we can’t figure out how to move this query into a plugins category.
It would be nice if there was an option.
Forum: Plugins
In reply to: [Plugin: Contact Form 7 (CF7)] Shortcode ErrorRESOLVED:
We did try other contact forms but, Contact Form 7 was certainly better and had worked within the last three weeks. Unfortunately, the other contact form plugins just didn’t give us what we needed.
After a week of troubleshooting, we posted this topic in hopes of running across someone with the same issue, though we finally figured it out late tonight.
CF7 v1.10.1 is the ONLY current version which works with WP v2.8.2, WP-United Connection v0.7.1 Beta (phpBB3) plugin and phpBB3 v3.0.5 with WP-United v0.7.1-RC1 mod.
The Atahualpa theme we discovered had no function in this plugin conflict after further testing. Using the Default WP exhibited the same issue. Therefore, we decided it wasn’t a theme issue.
It appears the CF7 authors have moved into two new versions plus a beta version in short time, where we believe there may be coding issues inadvertently generated.
We continued with the CF7 plugin upgrades, from v1.10.1 to v2.0 however, didn’t immediately discover the conflict. We believe this may have been a cache issue and once the cache was flushed during routine maintenance, we discovered the conflict.
For now, as of the date of this posting, we will stay with v1.10.1 until further testing.
Thanks for the reply samboll.
Hope this helps others.