chrisco23
Forum Replies Created
-
I finally had a moment to return to this issue, and it seems I’ve resolved it.
I decided to look into deactivating other plugins that might be causing trouble.
Since I had noticed in the WP debug.log session_start() warnings relating from oauth code in the UpVote plugin, and yes I know these are only PHP Warnings, but it seemed as good enough place to start, so I deactivated the UpVote plugin, ran the optimization without error, and reactivated the UpVote plugin.
I still wish I understood more about what the actual conflict was, especially since it may come up again on some future update. I never really found what was really causing Yoast to give the error, as I found nothing in the WP logs, the nginx logs, the mysql logs, etc.
I don’t know if I mentioned this is a multisite WP site, in case that might somehow be relevant.
Thanks for bearing with me.
Yes I meant to say that I hadn’t initially had WP-CLI installed but that I installed it as part of this debugging effort.
I have tried all of the steps without any luck.
Thank you for your detailed reply.
I am an underemployed/semi-retired web dev myself so I follow what you suggest, I think.
I’m not a WP guru and I didn’t have WP-CLI installed but I am running this site and a few other WP sites on a linode, so this is something I should know about.
However, still no progress.
Chromium Version 88.0.4324.96 (Official Build) Arch Linux (64-bit) $ uname -r 5.10.10-arch1-1This site in question is in “stealth mode” but I just want to be sure I have things well under control in terms of managing the basics (to start) of Yoast.
- This reply was modified 5 years, 4 months ago by chrisco23.
A bot or something had sent this for moderation and I’m not sure at what point it was posted. I got no email.
Also, I see no way to edit the post.
So in the last 6 hours I’ve made some progress, but some issues still remain.
I don’t see anyway to edit the post so I will reply here with the current state.I have had some communication with the developer or development team of the UpVote plugin. But since I know some of these remaining issues are really dealing with nginx multisite config, and not the plugin per se, I hope it’s ok if I update by cutting and pasting what I just pasted on the UpVote support threads.
As follows:
I have set up multisite and added a site, and I can go to both sites and see the theme (I have changed the color scheme and site title). This much is good.
So let’s call the domain I started with (all working) domain.com. Then I have created a subdomain, call it new.domain.com.
Now, I can go to either domain, and I can see the header changes per my title and color settings.
domain.com works fine.
on new.domain.com:
1. I click the ’+’ button, and the URL goes to https://new.domain.com/submit-story/
But the page is not a story form. The top header looks ok. Under that I see: TRENDING NOW | < > | Sorry, no trending stories at the moment.
Archives
and down here I see posts that are generic WordPress posts/stories. No upvote functionality. It’s the “Hello world!” post/story and another that I created manually through the Dashboard.2. I’m pretty sure this is an nginx config issue but when I am logged in as Network Administrator, I go to my sites->new.domain.com (the title of it), which points to https://new.domain.com/wp-admin. This nginx redirects me to a completely unrelated site. I’ve hit something similar before where nginx falls back on the first domain alphanumerically. So it’s doing that. A site I have whose domain starts with numeral “2”. This despite the fact that I have added a default server, 00-default.conf.
2.a. It seems I can at least get to the dashboard of new.domain.com, by being logged in as Network Administrator, and going straight to new.domain.com.
new.domain.com/wp-admin takes me to the wrong site completely new.domain.com/wp-admin/index.php works
Forum: Plugins
In reply to: [Polylang] All pages Redirects To homepageI have this problem and I’m on polylang 2.1.
Please advise, thanks!
Forum: Plugins
In reply to: [Polylang] Can’t switch back to default languageSeconds later I discovered that the “Espanol” link was still pointing to “http” and we recently added LetsEncrypt SSL. Looks to be resolved.