Ashish Kumar (Ashfame)

That command can be run by anyone. I can do that, if I knew the domain or website in question.

This issue is clearly about tinymce JavaScript file not being loaded because its behind authentication. As soon as you make it available with the right rule, it will start working. That curl command is only to test whether your server change actually made it auth free or not.

Alternatively, you can also try to open https://yourdomain.com/wp-includes/js/tinymce/tinymce.min.js in a private (Firefox) or incognito window (Chrome) or a different browser where you are not logged in, to test the same.

I still don’t understand why the WordPress install can’t reside in just a subdirectory “features” under exampleB.com with its url as exampleB.com/features?

Its still possible to do so without changing what’s what on which server. exampleB.com/features sitting on server interacting with the world will proxy back to server which runs WordPress but also has exampleB.com as the host being requested & URL of that install. And it would respond with whatever, just spit out the html as it is and it should all be better than manipulating things?

I still don’t understand why the WordPress install can’t reside in just a subdirectory “features” under exampleB.com with its url as exampleB.com/features?

Whatever styles you need the pages to have, can be done on a theme level.

And if there is still something that’s forcing you to use this setup, it would be better if you were serving pages without the iframe, after doing whatever HTML manipulation you need to do. This would make it appear as HTML coming from just exampleB.com/features but I would say this, this is unnecessarily complicated without any good reasons for doing so, atleast from what I have understood so far.

Ok, the siteurl and home is correct. Like your webhost support said, there is something that’s redirecting you once you login, which depends on where that resides i.e. in code or in database.

And based on the screenshot in your original post, I can see you are logged in on the site, as I can see admin bar. Can you try accessing https://karmasteel.us/wp-admin/plugin-install.php directly, to see if its redirecting you away from all admin pages or not? This would atleast enable you to disable plugins or install plugins easily. And jump to specific pages in admin. ??

If you have access to file manager in your hosting account panel, you can still install plugins by uploading the files under wp-content/plugins directory. I need you to install Better Search Replace plugin as originally suggested by Jesús above. Then you want to replace all occurrences of https://mcgeesteel.com and https://mcgeesteel.com with https://karmasteel.us. This has a very good chance of replacing your configured redirection and fixing the issue.

If you forgot to “Accept cookies” via your admin account (which is weird because why do you have to accept anything with your own website?), clearing the browser once or just retrying in a different browser should solve your issue.

You can even try to login with your admin account in a private (Firefox) or incognito window (Chrome) and then see if it all works there.

However, my SMTP configurations are not working.

You need to get the SMTP configuration done correctly, before your install would be able to send emails that actually reach people’s inboxes. What’s the issue with the SMTP configuration that you can’t get it right?

Oh so you want the links in the content to be exampleB.com/features/something but they are obviously of exampleA.com/something, is that right? Or you want the user to navigate to exampleB.com/features/something when clicked? Or something else?

Either way, its not going to be possible with iframe embedding. This is a very unusual setup. Can you clarify what’s really the reason behind the setup this way? That way I would be able to make better recommendations.

In terminal, can you try this command and tell me the output:

curl -I https://yourdomain.com/wp-includes/js/tinymce/tinymce.min.js

If you get a 200, then its clearly free from authentication and your original issue is something else. But if you get a 401 or 403, then .htaccess change is not clearly correctly done. In that case, what’s the location of the .htaccess file where you made that change?

I don’t see anything obviously wrong when I visited the 2 pages you linked. Content seems to be responding well to screen width.

Any interaction or issue a re-check can only be done in Google Search Console.

You can try reading more about the report here – https://support.google.com/webmasters/answer/9063469?hl=en

That being said, I got to know Notice: The Mobile Usability report is being retired soon. Read more

Whatever domain or URL that is visible to the world is what would be used everywhere. Outside world is not aware of whether the server proxies the request back to another server or serve the request directly. Whatever domain or URL you want in the front for the world to see is what should be setup on the server that interacts with the world.

If I have misunderstood your setup or usecase, please explain with example domains such as example.com, example.org etc

For reliable email deliver-ability, you would need to use a email service and a SMTP plugin to connect to such service. This often has a free plan for low volume of emails but beyond that you would have to pay.

Its totally possible to send out emails as-is with your webhost, provided they have quality control over what emails are sent out. Often users abuse their webhosts and hurts the reputation of emails coming out of such IP addresses.

So, best solution would be to use a SMTP service and a SMTP plugin. Often after configuring the plugin, you can test whether the connection works.

Receiving fake calendar invites as means of bringing attention to showcasing spam content has been around for a while now. What you describe fits that bill. I don’t think WordPress has any role in that at all. If you want to look into this more, I suggest reading articles when you search for “Calendar spam” or “meeting invitations spam” in a search engine.

Modern look is very subjective. You probably want to learn CSS to style elements the way you want them to look.

I see that you are using a block based theme, so you can use query loop block to show posts which would update the list as new posts are published.

• This reply was modified 1 year, 9 months ago by Ashish Kumar (Ashfame).

@kingcace Hi, Since you mentioned that you updated the domain in WordPress, can you confirm that you changed both “siteurl” and “home” in wp_options table?

This query would show you both values:

select * from wp_options where option_name IN ("siteurl","home");

If they don’t match the new domain, then that could be the problem. Could you show us the value for both rows, like this:

MariaDB [example_com]> select * from wp_options where option_name IN ("siteurl","home");
+-----------+-------------+--------------------------+----------+
| option_id | option_name | option_value             | autoload |
+-----------+-------------+--------------------------+----------+
|        40 | home        | https://example.com      | yes      |
|         1 | siteurl     | https://example.com      | yes      |
+-----------+-------------+--------------------------+----------+

That being said, don’t worry, this is fixable. Just need to figure out what’s causing the redirection from the WordPress admin panel to frontend homepage ??

Can you check the file permission on plugin-install.php? If its not readable by web server, its as good as not existing there. See https://www.ads-software.com/documentation/article/hardening-wordpress/#file-permissions

If that looks good, check whether any page in admin work? Like “Posts”, “Appearance”, “Plugins”?

Top level links in menu all point to a php file under wp-admin . If none of them works, then I would say rewriting requests in your server configuration is not correct. Every request is supposed to check whether a file exists at the requested URL. If it does, request goes to that file, else rewritten to index.php in root.

This would be .htaccess file if you use apache or nginx config file if you use nginx.