doctorproctor

Aha, I believe that did it! I didn’t have that module activated to date.

I’ll confirm and send in a final note here, then we can close the thread.

Jim

Alas, that trick is already in our wp-config.php, thanks to @kraftbj.

Happy to take next steps as recommended, and thanks.

Jim P.

Jeremy, many thanks. Re. “Follow Site” button, um, that was easy!…sorry about that.

Re. the Follow button creation routine, I wonder if you could pull @kraftbj into this conversation, as he knows our Jetpack configuration: basically we are running SSL on a WPEngine multisite, and I’m not sure we can do those wp-config.php edits (forcing admin over SSL and setting port to 443) without something else on our Jetpack configuration going haywire. If it sounds workable for our situation, then I can go ahead and do that.

Regards,

Jim

Oops, the WP.com follow button creation routine isn’t working either; when I enter my Jetpack enabled site it says:

“Please check you’ve entered the address of a WordPress.com or Jetpack-powered site and try again.”

Would appreciate help diagnosing, as this could be really helpful to my students on this multisite.

Jim P.

Thanks, Jeremy!…some good ideas there.

I actually can’t figure out, however, how to add a site to the Reader via

https://wordpress.com/following/edit

without following it in the usual way (i.e., going to a WP.com site and clicking the Follow link). Maybe that’s why the prompt says “Search your followed sites”?

Jim P.

We are now seeing that the second call does not routinely occur, and the Edit CSS code is not getting rewritten for display (at least now). I think I’ll close this thread and we’ll pretend we figured it out!…at any rate Jetpack doesn’t appear to be the culprit.

Okay, I now have an update. First, deactivating all of the above plugins didn’t solve the problem! But, second, I’ve discovered that the “problem” is only one of what is *displayed* in the Edit CSS box, now what is actually *saved* via Edit CSS, i.e., I can edit the CSS, click Save Stylesheet, and the CSS I entered is saved and functional…however, it just doesn’t show up as such in the Edit CSS box.

Interestingly, when I view page revisions (our host allows ≤3 revisions), I see two occur almost simultaneously when I click Save Stylesheet: the first indeed saves the CSS I entered, and the second overwrites that CSS with the <p> </p> code that led me to submit this support request. Additionally, the <p> </p> code that replaces it is *not* current, i.e., this is not a simple case of wpautop() happening, but rather the earlier <p> </p> code I originally noticed.

I will also check with our WPEngine host to see if it’s something on their end re. versioning.

Regards,

Jim P.

When I re-save custom CSS it gets the wrapper, sadly. I’ve tried wrapping some lines in <div> </div> to see if that would disable e.g. wpautop(), but no dice…it all gets re-wrapped with <p> </p>. I’ve tried a couple other workarounds, but every time those para wrappers show up on every line.

We are running a multisite, and this behavior is not found on other sites. Additionally, this behavior is recent, so if plugin-related it must be due to a recently updated plugin. Currently the plugins active on this site that are not active on the comparison site I just checked include:

-Author Avatars List
-Nav Menu Roles *updated recently
-Poetica
-PressForward
-Raw HTML Pro *updated recently
-Toolset Access
-Types
-WP Views (these last three part of Toolset CPT plugin suite, none updated recently)

I see no particular reason why Nav Menu Roles nor Raw HTML Pro would be interfering.

I sure appreciate your help! And can continue diagnosing as needed.

Regards,

Jim P.

Great, sure appreciate your quick reply here (and that of the Jetpack support person as well)…will add my thoughts on GitHub…Jim P.

The above is close to what we need, but it sounds like by uncommenting that code only *newly created* sites are affected. We would like to network enable Jetpack on a multisite, then automatically connect all *existing* sites to a single wp.com account (in part so as to enforce wp.com authentication on all sites, via method documented here)…how would this be done?

Sure appreciate,

Jim P.

Inexplicably, without Inline Comments update not explicit word from our WPEngine host that they changed something in the database, the above problem has now disappeared, at least for comments on the last three days of posts…I can only hope that it doesn’t return! I’ll mark as closed for now.

Jim P.

I’ve now attempted to replicate the above on other sites on our multisite, and it appears that the problem is limited to the above site only. This suggests that there is some database issue that is affecting this one site only (though recall that it does not affect regular comments, which post okay; what would be the difference?). I’ll check back with WPEngine to see if they have ideas.

Regards,

Jim P.

Kevin, hope we can move forward with this one soon, as it persists…Jim P.

The below comes from the WPEngine tech support person…let me know how we may test further…Jim P.

***
I’ve confirmed that caching isn’t the issue here, as I’ve exempted the subsite from caching and posted an inline comment and it appeared on the incorrect post. I’ve also exempted the entire network from caching and the issue persisted. Furthermore, when logged in to the dashboard (as is required to post) pages aren’t cached….I haven’t seen this issue on our platform when searching through past tickets so I’d recommend working with the developer of the plugin…As far as I can tell, there aren’t any issues with the database so it’d be best to get additional input from the developer.…When I made a test comment on https://ds.lclark.edu/envs160sp15/2015/02/15/more-than-tgal (post ID 755) it looks like the comment was posted to https://ds.lclark.edu/envs160sp15/2015/02/01/blurred-lines (post ID 332). It’s odd because those posts both have very different post IDs and different authors. That information could also be good to bring up with the developer.

If there’s anything he says we need to do from our end, please let us know!

I went back to v2.1.1 and experienced same problem…did not attempt to go back to earlier versions as I suspect database may not be backward-compatible. It’s weird, as I think it worked correctly, once, but just once…in all other cases my comment is posted on another post of the same author, typically (but not always) an earlier post by that author. I’ll email our WP service provider WPEngine to see if they have ideas on whether the database could have gotten messed up in some way, but go ahead and try a couple more quick comments at ds.lclark.edu/envs160sp15/ and you should see what we’re experiencing. (Again, this does not happen with regular comments on form at bottom of post.)

Regards,

Jim P.