LeoKesler

Thank you.

Hello,

I am using your plugin for years without any issue, including with AMP enabled.
For some reason, without any change, the plugin do not cache normal pages anymore.

First, I tested visiting the page with another browser. After many refreshes, the page still no cached (no comments in page source code) .

Second, I was using precache. That piece of log from first page was taken when the plugin was doing the precache.

I tried many things to fix the issue: fully updated wordpress, clean database, disabled all plugins excepts yours, full remove/reinstall/reset of your plugin, another memcached instance, but all without any success.

The most frustrating is the other site have the same configuration and it works.

I understand you do not develop the plugin anymore.
I am posting my issue here to get some visibility. Maybe other user had the same issue and knows how to fix it.

I do not know if this is correct, but I think something like this will test if there is amp activate and inside that code you can disable the output of plugin.

if ( function_exists( 'is_amp_endpoint' ) && is_amp_endpoint() ) { 
//code for amp here
}

https://www.ads-software.com/support/topic/is_amp/
https://docs.mashshare.net/article/126-disabling-mashshare-buttons-on-amp-pages

Sorry, I am not a programmer.

I found it how to do it.
The plugin add an option AMP in Appearance menu. There is an option to remove the featured image.

Thank you very much for link, it solved the issue.

Some more info. Using latest nginx + php7.09. This log is from my error.log from nginx.

2016/08/18 14:39:51 [error] 19004#0: *2013114 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught Error: Cannot use object of type WP_Post as array in /PATH/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/inc/nxs_functions_adv.php:155
Stack trace:
#0 /PATH/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/inc/nxs_functions_adv.php(145): nxsAnalyzePostFilters(Object(WP_Post), Array)
#1 /PATH/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/NextScripts_SNAP.php(88): nxs_snapCheckFilters(Array, Object(WP_Post))
#2 /PATH/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/NextScripts_SNAP.php(77): nxs_snapPublishTo(Object(WP_Post))
#3 /PATH/wp-includes/plugin.php(524): nxs_snapLogPublishTo('publish', 'auto-draft', Object(WP_Post))

Hi,

Your plugin display related posts in an AMP page (accelerated mobile page).

What I want to know if is possible to your plugin to ignore AMP pages and only to use related pages in normal pages.

Maybe some wp_dequeue_script in functions.php ?

Same error, with “Exclude path” blank .

Let me give you some more information, because I think you are forgetting some of advanced options of your plugin and wordpress.

I setup a facebook autopost. In advanced, I checked the option to republish automatically and checked “Loop it. Reset and Start from the begining”. After some months, the plugin will start to republish some old posts.

Now, what is a private post ?

Private content is published only for your eyes, or the eyes of only those with authorization permission levels to see private content. Normal users and visitors will not be aware of private content. It will not appear in the article lists. If a visitor were to guess the URL for your private post, they would still not be able to see your content. You will only see the private content when you are logged into your WordPress blog.

You can read more in Codex:
https://codex.www.ads-software.com/Content_Visibility#Private_Content

More here:
Private: Viewable only to WordPress users at Administrator level. (private)
https://codex.www.ads-software.com/Post_Status

So what exactly are you asking us to do?? At the time you make post private it’s already autoposted.How SNAP can un-autopost it?

Who is asking for un-autopost it ? I am asking to you make the plugin check if the next post to be (re)published is marked PRIVATE before the plugin (re)autopost it. If is Private, then try the next post in queue.

Why SNAP will use a published post marked like private ? It is irrelevant if the post has been republished before or not. The post is Private now, so it must not be republished by your plugin. Remember the option: “Loop it. Reset and Start from the begining”

1. You make new post and publish it on your site for everybody to see.

OK

2. SNAP autoposts it to all your social networks.

OK

3. You make post private

.
OK

4. If the option “Loop it. Reset and Start from the begining” is checked, SNAP will check the actual status of the next post to be republished. If it is Published AND NOT PRIVATE, then republish (when it is your turn to be republished). But if the post is marked PRIVATE, dont republish it, try the next post in queue.

Private post never gets “Published” status, so SNAP will never post it. It might only happen if you make it “Published” at some point.

Exactly the issue. The post was published in the past, but now it is marked private.

If someone mark a post (already published or not) private, is because he dont want that post showing for a while (or forever).

If it was published or not, it is irrelevant.

Please, fix this issue / change this behavior.

OK.
Resolved.

@cbunting99,

If possible, post your settings.
I am searching for more info about zionx.

In my small VPS, I am using php-fpm 5.6 (with zend opcache enabled, 96MB ), php-memcached with 64MB and this plugin.
Using the same test and my site is ssl enabled (https), I am getting this, using the “/” folder

Requests per second:    211.18 [#/sec] (mean)
Time per request:       18.942 [ms] (mean)
Time per request:       4.735 [ms] (mean, across all concurrent requests)
Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        5   18   1.6     17      27
Processing:     1    1   0.7      1      11
Waiting:        0    0   0.3      0       4
Total:         14   19   1.4     18      28

Using some post link, the requests by second are ~15-20% lesser , if the page have been cached by wp-ffpc. I still can use ab -c 100 and still get very high numbers with cached pages.

Without wp-ffpc, I was getting numbers similars to khromov and many timeouts and slowdowns.

Expiration time too low ?

Maybe your cache is too big. Clear the cache and do a precache. When it finish, check the actual memory used.

After a clear history/cookie and a reload, these are the cookies:

[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected] (only have google analytics info)

For now it is working. Like I said, it happens sometimes. I only use IE to check if the cache is working or if the layout is OK.

Off topic: the time showed in comments (at source page) dont show the correct time. Its showing, I think, the UTC time and not the timezone configured in WordPress (for me, UTC-3).