CUNY Academic Commons

Thanks Boone.

I was able to turn off subscriptions altogether as a stopgap, but have received some complaints from folks who had grown accustomed to getting the alerts.

Unfortunately, I am unable to attempt the shortlinks solution from the issue you to, as I am now completely unable to access Jetpack. When I click on the Jetpack menu item on the sidebar of the dashboard, or any of the submenu items, I'm taken to a blank grey screen.

In the meantime, our institutional twitter account (@murphyinstitute) has stopped auto-tweeting our posts. Potentially related?

Thanks for any guidance you might be able to provide.

Thanks,
Leah

Hi Leah - Sorry to hear you're still having issues.

The grey screen you've described is occurring because of a bug in PressForward, which is causing fatal errors. I've just put a hotfix in place, and I'll follow up with a proper fix within the next day. For the moment, you can access the Jetpack dashboard again.

It's possible that the PressForward fatal error was responsible for the subscription failures. Do you have any more content in the queue with which you could test this theory?

I've opened an upstream bug ticket for the PressForward fatal error. Until I hear back with details from their dev team, I'll keep my hotfix in place.

Leah, please do let me know when you get a chance whether notifications are being sent now.

Hi Boone,

I'm able to access Jetpack again, but things aren't working as hoped:

(1) When I turned subscriptions back on, the bad link problem returned.
(2) Looks like shortcodes (the solution from the issue to which you referred me) are already activated. I turned them off, and that didn't seem to have any effect.
(3) Twitter notifications (which until now happened via Jetpack's Publicize) aren't working.

In the meantime, I've turned off PressForward, which hasn't been working for a while anyway.

Thanks again,
Leah

Hi Leah - I'm afraid it's looking like your problems are internal to Jetpack, rather than between Jetpack and other parts of the Commons. Because most of Jetpack's functionality happens on wordpress.com's servers, there's little that I can do to debug. I think your best course of action at this point is to reach out to Jetpack support to report your existing problems. They'll be able to look into their internal logs to detect problems with outgoing notifications, and they may also have something to say about the weird permalinks. I've found them to be pretty responsive in the past. https://jetpack.com/contact-support/

Please let me know if they're able to help you, and feel free to loop me into the conversation if necessary.

I wanted to record here that I sent an upstream bug report to PressForward, and had a fix committed, that should fix the fatal error described above in future versions of PF: https://github.com/PressForward/pressforward/issues/859

Thanks so much, Boone!