ialima7

All that remains is to use alternatives that do not need to create an application, as RSS Graffiti or Twitterfeed.

Or use the phone number of someone else’s home or family.

Appears to be the same problem: https://www.ads-software.com/support/topic/plugin-facebook-failed-posting-to-timeline-because-the-access-token-expired?replies=17

The difference is that in the scheduled post we’re not there to see the error message. While we are not on the dashboard of WordPress unix session expires (do not know why) and gives error when it should be published on Facebook.

Your problem is not related to the plugin, but the politics of Facebook, and you even have the answer: have a personal cell phone. How do you live only with the phone of the work?

Same error… Why session is expiring?

Additionally, the item ‘Publish to fan page’ is being changed to ‘Disabled’. Someone also noted that?

I have the same problem. Thanks Matt for working on it.

@danielmattoso Usava o WordPress 3.2.2 na época.

Downgrade to previous version…

The problem was caused by another plugin ‘Redirection’. But that only happened because the campaigns are now interpreted as posts. This new mode also interferes with the plugins of autoshare on social networks. It was not cool.

I restored the database. With all the care and trouble that the situation requires.

There are many the infected files. When another infected php is executed, it infects other again. I’ve been there. Will have to do a more thorough search.

“Free Premium Themes” = site files infected.

I removed the malicious code manually. Do you stay in index.php and other important files from WordPress, themes and plugins folders.

However, it may be easier to start from scratch. Back up all files and database (I find it useful to use the Export tool). Delete everything from the server. Install WordPress, keep the default theme, import posts. So do not be left any php file infected. In any event reinstall the previous theme, find a trusted source.

I understand (I think… rsrs).

You are the expert, I’m just curious. ;D

Thanks for responding.

The siteurl is with slash (see) even so the og:url set by SFC is not with the slash.

Is there something that can be done by the htaccess to correct the errors “Redirect Path” identified by the Facebook Debugger?

In the new version is working.

Hi Michael!

For some time the plugin did not work here. Now with this new version it is working very well, but is not showing anything in History, only:

No history