joepahl

Not sure if this helps (I’m new to composer), but Pantheon support had this note:

I know when adding modules to Drupal 8 sites using composer, we can add the “--prefer-dist” flag to the composer command to avoid installing any submodules (.git folders). I wonder if he can do something similar when adding the plugin to WordPress?

• This reply was modified 7 years ago by joepahl.

The files were present when I added the plugin via the admin. Issue occurred when moving between environments after that. Pulling the changes to my local or when moving to test resulted in the missing files.

Thanks for your help with this. Hope I don’t need too much more handholding to get everything set up.

Issue seems to be coming from a couple gitignore files here: /object-sync-for-salesforce/vendor/a5hleyrich/wp-background-processing/.gitignore and here: /object-sync-for-salesforce/vendor/developerforce/force.com-toolkit-for-php/.gitignore

The version of the plugin I downloaded from WP.org had the missing files, but the version I pulled from my dev environment (added via WP admin) did not have the files. When moving the plugin from dev to test the same thing was happening.

After removing the gitignores/git directories within the vendor directories the problem went away.

Actually, I installed from the WordPress directory.

After my first message, I realized that I am able to activate the plugin in my hosting provider’s dev environment (Pantheon.io for reference). The error is occurring when I activate on, an identical, test environment.

I am reaching out to my hosting provider for additional support, but if you have thoughts I will share with them.

Same here…

https://2720cherokee.com

Can you send me a link to your site?

Hope I can help. Thanks for downloading.

hyeagz,

I don’t think it’s a conflict with the social widgets, but i could be a conflict with one of your plugins or the theme itself.

What is more likely is that your server cannot connect to the Twitter API because the rate limit has been exhausted.

A future version of the plugin will have a debugging option that will help diagnose these kinds of issues.

If you know how, ssh on to your server and type curl https://api.twitter.com/1/account/rate_limit_status.xml. This will return something like:

<hash>
<reset-time-in-seconds type="integer">1320702143</reset-time-in-seconds>
<reset-time type="datetime">2011-11-07T21:42:23+00:00</reset-time>
<remaining-hits type="integer">146</remaining-hits>
<hourly-limit type="integer">150</hourly-limit>
</hash>

If your remaining hits value is zero, you know that the rate limit is the issue. This may not be your fault. If you are on a shared server someone’s site may be responsible.

Good luck.

Not sure what the problem is, but a couple of ideas.

If you turn the other Twitter plugin off (actually deactivate it) is there still an issue? There could be a conflict between the dueling Twitter plugins.

If turning the other plugin off doesn’t fix the problem immediately, give it an hour. It’s possible that Twitter for WP is serving up a cached version, and burning through the rate limit before Twitter Wings can access it.

Hope this helps. Thanks for downloading.

Many WordPress themes use nested lists to display sidebar sections. This is slowly changing as themes incorporate HTML5 semantic markup.

Newer themes have embraced the <aside> element for sidebar sections. This is semantically more acurate than an unordered list.

In the case of a Twitter feed, I can see why an unordered list might be used, but I would argue that the <article> element is more semantic.

In addition to body content, each tweet has metadata: a dateline, an author, an avatar. Putting all of this into a list item did not make sense to me. If a Twitter feed is an unordered list, then a blog is an unordered list as well. Slippery slope…

Check out the HTML5 spec for more info:

• <article> element
• <ul> element
• <aside> element

If you need to format your feed as a list you can always edit the plugin. Change the tw-body <div> to a <ul>, and the <article> element to an <li>.

Thanks for downloading.

There are a few possible reasons for this. One is that Twitter’s API rate limit has been exhausted. The rate limit is refreshed hourly. If you are on a shared server this can be caused by someone else’s site.

Another possibility is that your Twitter account is protected. Private accounts cannot be accessed via the public API.

A future version of the plugin will include an option to register a private API key. This will prevent both of these issues.

If you have any information that may help diagnos the issue please let me know. I hope that this helps. Thanks for downloading.

It would be great if they added import functionality to the Twitter Tools plugin. I found Twitter Importer, but it doesn’t create hyperlinks or add the custom fields that I am using.

If anyone has some insight it would be extremely helpful. Really don’t want to have to edit posts by hand.

Same issue. I could swear it worked at one time.

It is possible that the js that moves the form is executing before the content of the reply title is changed. That’s my theory at least.

Hope it gets fixed.

Same issue here. Surprised more people haven’t reported it.