Flavio Martins

This should be fixed in the latest version of the plugin.

Can you try and install it again and let me know if you still see the issue on your site?

You will need to deactivate your Twitter account in the plugin, then add it again.

Thanks!

This should be fixed in the latest version of the plugin.

Can you try and install it again and let me know if you still see the issue on your site?

Thanks!

This should be fixed in the latest version of the plugin.

Can you try and install it again and let me know if you still see the issue on your site?

Thanks!

On the Tweetily settings page, there is a check box that you can check to save to a log file.

To access the log, you need to go to the plugin editor.

Dashboard > Plugins > Editor > select Tweetily > select log.txt file.

You can email me the log file: flavio[at]winthecustomer[d | o | t ]com.

Thanks!

I’ll install the 404 Customize plugin on my test site and see what’s causing the problem. That’s one of the fun games of WordPress plugin development, you always run into issues with other people’s plugins.

LOL.

I’ve updated the code for the plugin recently. Can you try deleting it and installing it again fresh? It should fix these bugs.

Did you have the Tweet Old Post plugin enabled at the same time? The two can’t be working at the same time since they’re doing the same thing, so it needs to be one or the other.

Multiple accounts is pretty difficult to do so for now I’m going to wait on adding this.

I may go back in the future and add this option. But it won’t be for a little while. In the mean time, I have a number of extra features that have been requested that I’m working on.

I’ve checked into this and it’s a bit complicated for me to do, so I’ll have to leave it out for now, sorry.

Looks like this is a duplicate suggestion. I’m adding that feature on this next update.

Thanks Jenn.

I’ll add this to my list of suggestions and add it to my update I’m working on at the end of the year.

I’ve just updated the plugin to version 3.2. It should be available for you to update and then re-install. That should take care of some of the issues that you’re seeing.

If not, let me know. I may have to log in and see what your WordPress site is doing behind the scenes to see why it’s not working.

Any update on a workaround for this?

I have a separate plugin that tweets out a blog post then updates a field in the DB. I know it works find for everyone who is NOT using W3TC as they don’t have object caching in place.

But it looks like if you do, the field is never updated in the DB and causes a big error with the plugin.

Same here. I’m getting several users of my plugin reporting that queries being made are cached since they’re running W3TC.

I’ll add that to my list of items to add in the next update.