rickfitz

No console errors or warnings in front-end or in the page editor. I’ve tried in both Chromium and Firefox with same results. I duplicated the page, and it happens there too. Really odd…

In the duplicate page I then deleted all the Oxygen content – and now it works! So it looks like there may be a conflict with something in Oxygen, but only with that page, and only when using the Classic Editor.

When I have time I’ll see if I can track it down further, and report back.

Thanks,
Rick.

Sorry, I’ve currently removed the plugin. Don’t need it for a while as there’s still work to do on the site.

I don’t think there’s any issue here related to your plugin – it’s a WP / server configuration problem that I need to sort out with my host when I have time!

As far as I can see, you use the wp cron function to fetch pages to build & refresh the cache. The problem is that when wp uses curl to fetch the page, it’s unable to verify the ssl certificate, which is from Let’s Encrypt. So if I understand this, the PHP setup doesn’t have access to the necessary certificate info. As the wp installation, php and letsencrypt are all sourced from my hosting company (lcn.com), I’m hoping they can resolve it. But I’m too busy with other stuff this week – so hopefully next week.

I’ll post any results here when I can. Meanwhile, any other suggestions would be most welcome – or corrections if my understanding is all wrong!

Me too. It’s a bug in the performance.php file. Line 675 is in the wrong place; it should be immediately after the “Skip on error” block, not before it!

If you choose to fix that (at your own risk!), then the error gets logged before the process is aborted, and you’ll be able to see the error in the Swift log.

In my case, the cache pre-building is unable to fetch any pages due to an SSL issue.

HTH, Rick.

Looks correct to me. Can’t test immediately as I have several other mods in the file and it’s on a live site!

I’ll email separately to describe my changes and see if you’d like to merge into your plugin or whether my requirement is too different to make it worthwhile.

Many thanks for the really useful plugin and lightning fast support!

Rick.

Thanks for the update, but it’s causing a new problem!
You’ve declared $post global, so the ticker shows the data from the current page (which is what the global $post holds), and not the specified post!

My version looks like this:

   if ($options['show_excerpt'] == 'true') {
      setup_postdata( $post );  // RCF added
      $content .= ' - '.get_the_excerpt($post);
   }

Just the commented line added – nothing else.

Cheers, Rick.

• This reply was modified 6 years, 5 months ago by rickfitz.
• This reply was modified 6 years, 5 months ago by rickfitz.

UPDATE:
Reverting to older PHP removed the error message, but the excerpt still didn’t work when not specifically defined for post – i.e. failed to create excerpt from post content.

FIX:
Inserting ‘setup_postdata($post);’ just before the call to ‘get_the_excerpt($post);’ seems to fix the problem, with any PHP version. (This sets up the necessary data as if the call was from within the loop, and is recommended in the WP Codex.)

Note: the excerpt problem didn’t always occur – seemed ok on a test site, but not the real one – presumably depends on the state of the global vars when the ticker is rendered.

HTH, Rick.