mbeasi
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: after php 7.3 upgrade permalinks/links are brokenSorry, I’m sure you’re right that it’s 2.4 (they probably misspoke or I misheard when they told me what they were doing). Thanks, I will ask them.
Forum: Fixing WordPress
In reply to: after php 7.3 upgrade permalinks/links are brokenI tried re-saving the permalink structure before I posted here, and that didn’t work (have tried this multiple times on all our wp sites). I’m beginning to think it has to do with the apache upgrade from what I can find online, though that gets into things that are beyond my reach. This is happening on all our websites (we have multiple wordpress sites and some are multisite) since the php and apache update done by our web host. All the links on all the sites worked before that happened.
Default permalink structure works, no other permalink structure works.
Forum: Fixing WordPress
In reply to: after php 7.3 upgrade permalinks/links are brokenUPDATE: I have discovered that I can get the links working again if (and only if) I switch to the “plain” permalink structure. No other type works. This is okay for that site (it’s not heavily linked-to) but not ideal for other sites we run. Is there something I can do to make other types of permalinks work again?
Thanks so much for following up! I can’t find anything in the spam folder… I’ve disabled spam assassin in case that’s what’s getting in the way, but just to make things simpler, can I change the contact email to [email protected]? Nothing should get held up there. Thanks, and sorry for the hassle!
Hi there. I did the contact form thing a long time ago, but haven’t heard back. I just wanted to update here, though, to let you know that I just did the latest Jetpack update, and this problem still exists. If you have any other recommendations, let me know.
I am depressed to report that deleting and reinstalling did not fix anything. It’s possible that it even created more problems, though I can’t be sure. One of the sites, despite having Jetpack reinstalled and reactivated seems to have lost the “visibility” option on its widgets, which I know is a Jetpack feature. I can’t be 100% sure that this wasn’t broken already (I’ve been paying less attention to that site recently) but it’s definitely broken now. I only mention it in case that gives you a clue as to what’s going on. This particular site is the main site in a multisite install. That functionality weirdly is still present on the other site currently on that multisite. Sadly, I was only using it on the main site, haha.
Things just haven’t been right since the time I had to forcibly remove Jetpack for causing the white screen of death. Something broke then, and I just can’t figure it out.
It happens in both Firefox and Safari (those are the only two browsers I currently have installed).
FYI the instructions in the codex included screenshots and menu items that don’t match what’s available on my versions of these browsers (which, to be clear, are Mac versions), but I think I found the error console anyway. There don’t seem to be any errors. I followed all the instructions.
https://www.dropbox.com/s/nbucj96fzqnsgmk/Screenshot%202017-04-28%2023.06.17.png?dl=0
Other info in case there is anything helpful: All these sites are part of multisite installs. Most are using Genesis child themes, but I tested to make sure the issue still exists on a blog not using Genesis, and it does. The issue definitely only happens when Jetpack is activated. I just tested again on a blog on the same multisite install without Jetpack activated, and the post/page preview and saving drafts works fine. I activated Jetpack and the problem reappeared.
More information: I mentioned before that the “Preview” and “Save Draft” buttons cause this issue to occur… in case it helps to know, if we click “Preview” of a post from the list of all posts, it actually does open the preview. We’ve been using it as a workaround since we otherwise can’t preview posts before publishing them.
Additional information: The same issue occurs when saving a draft of a post while writing it. The draft is saved, but the browser directs back to a new post window, and you have to go retrieve the post from the master list in order to continue working on it.
Okay, I just tried this on one of the sites (deactivating all other plugins, including a couple that were network-activated) and the issue still persists. Still created a new post window instead of showing me a post preview.
Also, here’s a little screen video of what happens.
https://www.dropbox.com/s/zbrtl812ts5ya4h/Preview-thingy.mov?dl=0
Sure! There are a few I work with, but the ones that still have Jetpack activated now are:
https://acttoostudio.com
https://operaworkshop.acttoostudio.com
https://mangabookshelf.com
https://suitablefortreatment.mangabookshelf.comThank you!!
Just piping up to say that this is happening to me too, though so far on my multi-site install, it’s tied to one site in particular. This is the site that is generating the old posts:
https://experimentsinmanga.mangabookshelf.com
An additional note on our version of the issue: We use Sitewide Tags to aggregate all our sites’ posts on the main site (https://mangabookshelf.com), and though this generally works very well (and hasn’t triggered issues with publicize in the past), a title change for a post on the main site seemed to generate repeated “publicize”-ation of the false version of the post on the main site instead of the version on the original site. I don’t know if I’m explaining it well (and probably only people who have ever used Sitewide Tags will understand what I’m referring to), but that’s never happened before either.
Forum: Plugins
In reply to: [Genesis Simple Sidebars] Error after updating to PHP 5.4I just wanted to thank FreestyleMD for this:
You don’t have to delete everything though just
i:0;s:20:”__return_empty_array”;
and subtract 1 from the first integer after a:
We just ran into this problem after updating mysql, and that solution worked perfectly for me. And not deleting all the settings allowed me to keep the working sidebars, which was great.