vich11

Ah, gotcha, thanks very much. Will try that ASAP.

Where is that done? BTW, the link you provided for the fix does not mention (that I can find), changing WP-Cron settings:

Solution
To avoid multiple instances of WP-Cron running on your server and making duplicate posts, you can try to use the default way of setting up cron jobs on a Linux server.
Please make sure that your web host allows you to setup Linux cron jobs. The way this is setup would be different based on the control panel offered by your host.
There are two steps involeved:
1. Disable internal WP-Cron execution on page load.
2. Setup a real cron job function that makes a request to the wp-cron.php file at regular intervals based on your preference.
NOTE: Before you follow this method, please note that disabling internal WP-Cron can also result in the website not running properly based on your setup or the plugins used.

I can’t disable wp-cron because other plugins use it. Since I have the paid version of this plugin, it would be nice to get a resolution to this. Here’s the latest, again 5 in a row for some reason:

https://screencast.com/t/ppzlEMbP

I wish I knew why some are only posting once and others multiple times.

Wow. Awesome support on this.

BTW, the issue here is that SNAP is not flagging duplicates as duplicates and not posting. I looked through the log and saw instances where there was a duplicate post attempt but the plugin blocked it. Here, it’s just letting them all through.

Log results for one post:

[2013-06-24 16:18:58] – [Posted] [Tumblr – Tumblr] – OK – Message Posted | PostID: 327486 – ‘World War Z’ Original Ending Revealed; Sequel to Begin Development |im
[2013-06-24 16:18:58] – [Posted] [Tumblr – Tumblr] – OK – Message Posted | PostID: 327486 – ‘World War Z’ Original Ending Revealed; Sequel to Begin Development |im
[2013-06-24 15:19:31] – [Posted] [Twitter – Twitter] – OK – Message Posted
[2013-06-24 15:19:30] – [Posted] [Pinterest – Pinterest] – OK – Message Posted | PostID: 327486 – ‘World War Z’ Original Ending Revealed; Sequel to Begin Development
[2013-06-24 15:19:24] – [Posted] [Google+ – Google+] – OK – Message Posted | PostID: 327486 – ‘World War Z’ Original Ending Revealed; Sequel to Begin Development
[2013-06-24 15:18:55] – [Scheduled] [Twitter (Twitter)] – for 1372087155(2013-06-24 15:19:15) | PostID:(327486)
[2013-06-24 15:18:55] – [Scheduled] [Tumblr (Tumblr)] – for 1372090735(2013-06-24 16:18:55) | PostID:(327486)
[2013-06-24 15:18:55] – [Delayed] [Tumblr (Tumblr)] – Post has been delayed for 3600 Seconds (1 Hours )
[2013-06-24 15:18:55] – [Scheduled] [Pinterest (Pinterest)] – for 1372087146(2013-06-24 15:19:06) | PostID:(327486)
[2013-06-24 15:18:55] – [Scheduled] [Google+ (Google+)] – for 1372087145(2013-06-24 15:19:05) | PostID:(327486)
[2013-06-24 15:18:55] – [Start =- ]- ——=========#### NEW AUTO-POST REQUEST PostID:(327486) Scheduled +4 ####=========——

I have a lot of plugins, some of them might use wp cron. I don’t get why twitter and G+ don’t have this issue but tumblr does.

Hello?

Can I get some help here?

Another thing would be a list of existing media tags appearing when a new image is uploaded.

I have a LOT of plugins on my site. My developer ended up being able to get the plugin installed by deactivating all other plugins and reactivating them. However I still have a problem where they /media-tags/slug/ URLs are very twitchy. Today I tried to change media-tags to galleries and ended up with the 404 error once again.

I really LOVE the functionality of this plugin, but I’m very concerned with having something so seemingly delicate driving what I hope to be a core function of my site.

Vic

Of course now I have another where /media-tags/slug is generating a 404.

Sigh.

The problem turned out to be this according to my super-awesome developer:

the problem is on lines 118 and 119 of media-tags.php, i have commented it out now:
include_once ( dirname (_FILE_) . ‘/mediatags_legacy_convert.php’ );
mediatags_plugin_version_check();

looks like something to add backward compatibility

Well, so much for that. ??

I’m getting this on a RSS validator:

<b>Notice</b>: Undefined index: HTTP_ACCEPT in <b>/home/screenra/public_html/wp-content/plugins/wp-super-cache/wp-cache-phase1.php</b> on line <b>401</b>

<b>Notice</b>: Undefined index: HTTP_ACCEPT in <b>/home/screenra/public_html/wp-content/plugins/wp-super-cache/wp-cache-phase1.php</b> on line <b>401</b>

https://www.rssboard.org/rss-validator/check.cgi?url=http%3A%2F%2Fscreenrant.com%2Fpodcasts%2Ffeed%2F

When I disable WP-Supercache that error goes away. But I’m certainly not going to get rid of supercache.

Vic

Looks like your latest update fixed it!

Thanks,

Vic

Belay my last, I’m back to Podpress. Installing the .11 version to see if that fixes anything.