ahcj

Some variation of this keeps happening more often than not when updating Jetpack on my site. Would like to know if something’s broken on my end that I need to fix after this happens:

PHP Warning: require(/chroot/home/healthjo/healthjournalism.org/html/blog/wp-content/plugins/jetpack/vendor/automattic/jetpack-roles/src/class-roles.php): failed to open stream: No such file or directory in /chroot/home/healthjo/healthjournalism.org/html/blog/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php on line 90
Warning: require(/chroot/home/healthjo/healthjournalism.org/html/blog/wp-content/plugins/jetpack/vendor/automattic/jetpack-roles/src/class-roles.php): failed to open stream: No such file or directory in /chroot/home/healthjo/healthjournalism.org/html/blog/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php on line 90
PHP Warning: require(/chroot/home/healthjo/healthjournalism.org/html/blog/wp-content/plugins/jetpack/vendor/automattic/jetpack-roles/src/class-roles.php): failed to open stream: No such file or directory in /chroot/home/healthjo/healthjournalism.org/html/blog/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php on line 90
Warning: require(/chroot/home/healthjo/healthjournalism.org/html/blog/wp-content/plugins/jetpack/vendor/automattic/jetpack-roles/src/class-roles.php): failed to open stream: No such file or directory in /chroot/home/healthjo/healthjournalism.org/html/blog/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php on line 90
PHP Fatal error: require(): Failed opening required ‘/chroot/home/healthjo/healthjournalism.org/html/blog/wp-content/plugins/jetpack/vendor/automattic/jetpack-roles/src/class-roles.php’ (include_path=’.:/opt/remi/php72/root/usr/share/pear:/opt/remi/php72/root/usr/share/php:/usr/share/pear:/usr/share/php’) in /chroot/home/healthjo/healthjournalism.org/html/blog/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php on line 90
Fatal error: require(): Failed opening required ‘/chroot/home/healthjo/healthjournalism.org/html/blog/wp-content/plugins/jetpack/vendor/automattic/jetpack-roles/src/class-roles.php’ (include_path=’.:/opt/remi/php72/root/usr/share/pear:/opt/remi/php72/root/usr/share/php:/usr/share/pear:/usr/share/php’) in /chroot/home/healthjo/healthjournalism.org/html/blog/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php on line 90
Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.

Mine have been sending correctly with read-more truncation and the image ever since the fix was announced and I switched back to full text.

If this is indeed happening, then it seems that it is different from the original Jetpack issue.

Can other forum participants here confirm that your images aren’t arriving in new-post emails, even with full text and not summary in Settings —-> Reading?

FWIW mine have been truncating correctly at the read-more tag and including the image in emails ever since they announced the fix.

For now until there’s a “read-more” fix, you can set your feeds to summary instead of full text.

Go to Settings -> Reading and find the option, “For each post in a feed, include…”

Change that option from “Full text” to “Summary.”

That will cause emails to include the first few sentences of a post, typically cut off mid-sentence somewhere. It will also not include post images any more.

Not ideal, and not controllable per-post as before with the “read-more” tag, but at least this directs more traffic to your site until there’s a fix for this issue.

Confirming @iwilkerson: I set “Summary” instead of “Full” and now our latest post simply cuts off after N characters. Previously, we’d get all the text before the “More” tag.

So this setting is not the solution. Something this past week or so has broken the “More” tag in subscriber emails.

Indeed, here is the problem and a possible solution:

https://www.ads-software.com/support/topic/subscriber-emails-ignoring-read-more-tag/

Noting it here for anyone else looking for this issue.

Same for us as well. We’ve sent emails with summaries for ages, then suddenly just within about a week ago they have the full text. I’ve set (reset?) “Summary” on the Reading Settings admin page mentioned above, and I guess we’ll see what happens next post.

My guess is that a recent core or plugin update reset this somehow. It would be helpful if someone could investigate this and find out for sure what happened so we know whether or not to look for some other problem.

There is no error on the Web site. This is the message I received at the command line after using wp-cli to update the plugin.

Respectfully, please don’t say “Requires PHP Version: 5.2 or higher” if you don’t actually test on these older versions.

@wdteam: Does this mean we can expect to see this fix in an update? All of us manually applying this fix ourselves upon future unrelated updates to this plugin really isn’t ideal.

I am so happy to be wrong, and I wish I had figured this out before posting.

Much thanks.

I see now what it is:

$bbpress_version = explode( '-', bbp_get_version() )[0];

Function array dereferencing is not available until 5.4.

So the simple matter of not fetching the array first and then dereferencing on the next line prevents many hosts from being able to use this plugin.

(Testing this just now, and after that minor change the plugin activates.)

Respectfully, I don’t think you understand the context of this problem for many site administrators.

1. The PHP project itself has EOLed (for example) 5.3.3, however distros continue to support it with backported security and bug patches of their own.

2. PHP 5.3.3 (with backported security and bug patches) remains the default in CentOS 6.9, which is supported until 2020. More recent versions are not available via their repositories. Hosts would have to upgrade PHP outside of the CentOS packages and assume the maintenance burden from then on.

3. About 50% of sites running PHP as of August 2017 are at versions less than 5.5:
https://w3techs.com/technologies/details/pl-php/5/all
https://w3techs.com/technologies/details/pl-php/all/all

4. Updating PHP is not like simply updating my Web browser. Real-world production hosts like mine are filled with various work by various developers over at least several years. Bumping PHP further than a maintenance release would almost certainly mean unnecessarily breaking things that are hard to find, probably tricky to fix and written by people I’ve never met who are long gone.

I think it might be reasonable to assume that the language features you’ve used that require PHP 5.5+ were not actually necessary for you to develop this plugin.

I hope you will consider making sure this plugin is available to the greatest number of real-world users by ensuring it works on a really strong majority of servers in the wild.

I did use the contact form on that page at about the same time I posted here. I will look forward to hearing back on that message.

However, I would like to suggest that this should be public and conspicuous information so that people can decide whether to buy the premium plugin.

The pictures and information to which you refer ought to be easy to post right here for others to see.

Also, can a moderator edit a submitted message before approving it?