todaydata
Forum Replies Created
-
I just realized the best and easiest fix for this. I just needed to change the wordpress url to https://blog.todaydata.com/blog instead of https://todaydata.us/blog. Now everything works as expected including saving edits and publishing.
So now:
wordpress url: blog.todaydata.com/blog
site url: blog.todaydata.comBefore it was
wordpress url: todaydata.us/blog
site url: blog.todaydata.comAlthough both urls point to the same site, the first works, and the second does not. And previously, before the last update, the second did, in fact, work.
Yes, thanks. Seems this is the problem since the update.
The address blog.todaydata.com is actually on the same server as todaydata.us. There is a dns A record on on the todaydata.com server pointing blog.todaydata.com to the same server as todaydata.us. So, blog.todaydata.com and todaydata.us are on the same server. All this worked correctly before. Yet, somehow wordpress thinks they are on different servers.
Moving to the same domain would cause me seo issues since my seo is built on blog.todaydata.com. I can’t move the blog to the todaydata.com host because that is a windows server and I don’t feel confident that wordpress works correctly on windows.
The thing is that everything was working great before this last update.
I guess I can use my work around to temporarily change the site address to the wordpress address when I need to add a blog post or edit.
When I go to https://blog.todaydata.com, it is not trying to force https. It goes directly there. There is a security certificate on https://todaydata.com, not on the subdomain. I am not sure why you get the force and i don’t. As you said, this could be a clue, but the problem only arises when I try to save a draft or publish.
I have also deactivated (and then reactivated later) all plugins to ensure they could not be causing the problem.
Per where the access control header is coming from, the error message says that it is coming from
https://blog.todaydata.com/wp-json/wp/v2/users/?who=authors&per_page=100&_locale=user.
This is something built into wordpress that I don’t have any understanding of.Thanks for continuing to help on this.
Do you mean headers set in the theme? I tried a the theme twenty nineteen and get the same problem. Can you tell me what part of the header is incorrect? Thanks.
They are different because I have a dns record pointing from blog.todaydata.com to todaydata.us/blog. It has always worked before the last update.
I have tried to set headers in httaccess but it did’nt do anything.
Forum: Plugins
In reply to: [Meta Tag Manager] wp 4.9.1 No meta tags appear in source codeThanks. I got rid of the other plugin.