annmariedwyer

For me, it was the bbPress clash. Commenting out the line fixed it.

If you want to keep the current version, you can use this patch. It is in a few other threads.
https://www.ads-software.com/support/topic/223-warning?replies=16

I followed the instructions and removed JetPack. A fresh install gave the same line 4534 error.

When attempting to approve comments, I got this:

Warning: Cannot modify header information – headers already sent by (output started at /home/content/94/9852494/html/wp-content/plugins/jetpack/jetpack.php:4534) in /home/content/94/9852494/html/wp-includes/pluggable.php on line 876

Update:

Today’s update created a new error:

Warning: Invalid argument supplied for foreach() in /home/content/94/9852494/html/wp-content/plugins/jetpack/jetpack.php on line 4534

The warning on activation remained the same:
The plugin generated 169 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

Update:

I deactivated it to see if something was set wrong and got this error message:

The plugin generated 169 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

@mattyrob

They may be pointing back to that ancient thread to explain how the wp_cron works, but it is definitely not infallible. This is the one which eventually led to the fix of my script-stripping nightmare: It was part wp_cron, part nannybot, but in the end pivoted off the cron.

Dev changed wp_cron in 3.5. It solved a number of problems. Generally, fixing something has unintended consequences.

After a couple days, I have run into a snag. Tonight, only two of the 15 emails which should have gone out did. I do know the difference between the last two days and today was the scheduler. I scheduled today’s post, but the two days prior were live posts.

The scheduler has caused a ton of issues for me since 3.5. (script stripping, HTML leeching) It may be worth a look in codex to see if there are lingering issues since 3.5.1.

I have some feedback from parts of the mailing list which were being neglected. Thus far, with about 20% of my queries returned, the ALT_CRON fixed the issue. I will update again if it is merely a partial fix or was the solution we needed.

Curious though, any idea why this just cropped up after all this time?

I have the same issue. I schedule all of my posts. I have already been on the telephone to ensure I am not being throttled (and mine has been restricted via S2 @ 15 since the first email).

I added your define line to config. I should know in five minutes if it worked.

As above, I can send directly, but the subscriptions do not go out. My last email which issued without a problem was 17JAN (all my other posts were scheduled while I was away). I came back to a load of email asking why they were not getting email.

@jeremy

I have just spent the better part of an hour reading the reviews of other users. I have found at least one instance of every one of my points in the reviews dating back to early November, 2012. My review of December, 2012, would have been no surprise had you (Automattic) [innuendo moderated]. Likewise, some of your five star ratings are professing the drag time (one I did not mention), the unfriendly UI and overall malfunction of the plugin complicated with multiple bug fixes within days of the release.

Most WP.com users I have encountered who move off WP.com to Automattic hosted sites never see how plugins work when they are not forced on them by their host. Ones which see what .org users’ plugins which do not kick their users off, actually load their photos and comments, do not strip out input with overreaching CSS, do not kick mobile users in the screen and smooth loading are left with a deflated feeling because “owning their own website” is not what they envisioned.

Indeed, none of this review is a surprise. All of it is in the documentation should you choose to read it. How inconvenient is that? Hmm. Sounds a lot like putting the deactivate button in the sales propaganda.

@jeremy

Thank you for the response, but I have chosen against JetPack and disabled it. It comes onboard with fresh WP installs and I got it with the upgrade 3.4.x. It was not something I chose to download, and out of the box, I hated it. It is of note, all of my complaints with it were from test driving Automattic’s suggestion of an all-in-one plugin. I tried it to see if I would like it better than the cocktail of plugins I do like.

RE 2: Before Jetpack was on my server, there was no RSS feed of mine in the WP.com “reader”. Your argument does not hold water WP.com would voluntarily seek out blogs to insert in its reader. From the time I jumped from WP.com, I was not in the reader. When JetPack came on board with the WP upgrade, my feed reappeared in the WP.com reader. It does not take calculus to do the math. Automattic = WordPress

My telephone call to Automattic concerning this issue confirmed JetPack was responsible for loading feeds of all sites who activated it.

RE 4: I did disconnect them. I did report this. It is disconnected now, so this is a non-issue. However, for those who are thinking they are stuck with what is already on when it is activated, this can be a real downer. From the look of the comments here, it appears you may have made this more friendly in the UI. I would think the disconnect button would be more appropriate beside the “activate” button, not hidden in the “read me” propaganda.

RE 2&4: Although I disconnected JetPack, my RSS remained in the reader. Apparently, the only way for me to remove it from the reader is to stop posting to my site. At half a million hits per month, that is unlikely.

RE 5: When the only plugin on the site was JP, all of the links rendered wrong. Claim what you want, there was either a conflict with JP and WP or just JP being wonky. Either way, it was unacceptable. Protocol is deactivate plugins one at a time to correct issues and isolate problems. I deactivated JP and the problem was solved. As is typical with Automattic support, all errors are user errors.

RE beta: I have been on many beta teams. If I believed Automattic cared about the .org folks, I would be glad to beta on one of my smaller sites. I am not willing to use my big site to do it, however, because I have never seen Automattic consider there are blogs which drive real traffic.

RE 9: Rather than slimmer sheets and additional ones for the modules which need extra CSS, the sheet was huge considering I was not interested in more than a couple of the modules. It is your plugin. Style it the way you want. I do not have to like it. I also have the capacity to overwrite it.

RE 10: You have loads of reports of WP.com, Automattic hosted users and .org users who have massive problems staying logged in. Shame on all of them for not knowing to come to the JetPack thread to report they knew what was wrong with their out of the box WP app. I hardly think this is a surprise issue. I still encounter it when I go to Automattic hosted sites which use JP. I know because when I get booted, I ask if they are using JP. I hold my opinions unless asked, as there are many who are satisfied with your plugin.

To say it is unfair of me to hold the opinion this plugin represents a headache for those who are not run of the mill, once a month or meme bloggers is indicative of only wanting good reviews and not getting honest feedback.

You cannot. The only way to fix this until the bug fix is released is to insert the script after the post goes live. Once it is live, WP will not strip the script out of your ad.

Thank you for resolving this ticket without answering my questions. It leads me to finding a new theme.

I understand that. If there is no substantive change to features I actually use, I am not willing to upgrade. The theme drop box has nothing new since I downloaded it except a fresh install.

If there are updates, which files are updated? I opened a number of core .php files to see no changes, although in my child theme I changed them from what is shown.