webmistressofthedark

Yes I know all this. I’m beyond that. I always install my own WP into the FTP, then my own theme, via the WP. I never use ‘helper’ services.

The host will simply give me the account name and password for the FTP/cPanel of the new acct. I will create the database name and password myself. So of course it will change. This will be a whole new account.

I did have the config file step listed in my first post.

My actual question was, should I restore the DB as is, or rename it? The second part will be the same but the first won’t because it will have the new acct letters, as I described above.

• This reply was modified 3 months, 2 weeks ago by webmistressofthedark.

Thank you for this information.

By looking at the configuration of the site that fixed itself and worked, I was able to see what file was missing.

But it wasn’t the one in the notice… very strange.

• This reply was modified 8 months, 1 week ago by webmistressofthedark. Reason: Fixed a typo

OK so I checked with the first hosting account and it had msqlnd checked. (last selection under the M)

The second one that was not allowing search did NOT have that checked and I wonder why.

After checking it, the search now works for the sites on that server.

Very strange indeed that the first one corrected itself?

Thank you for this explanation although I’m still not clear on what exact code I should put in the htaccess file if any. This site is targeted as it is my State Senator and I am sure enemies would love to have access to mess it up.

I just updated a plugin, got that message, but by simply hitting the Updates button again, it took me back to the admin area, and the plugin updated fine and I did not get tossed into maintenance mode.

Thus I was saved from having to go into FTP and remove the dot maintenance file. So at least now I know it’s not anything malicious that is causing this.

The error message specifically mentions the iFrame. However, it was just the front page that was iFramed so I ‘m not sure why WP thinks the admin page was part of that.

I have seen several versions of the code to add to the htaccess file to stop iFrames but is there something else I have to erase to stop WP from thinking it is still iFramed?

In the background the plugins update just fine, but I ALWAYS have to go in and remove the maintenance dot file from the FTP in order to gain access. Then I see they were indeed updated.. so it’s not a problem with the plugins.

The plugins are LiteSpeed Cache and Hubbub

I did have Securi scan and they said no hacks. The issue is the file won’t STAY deleted.

I have tried deleting the content, changing permissions, but perhaps I should change the name?

This was a problem site I never should have taken over… someone else’s problems.

I had two sites that I created and they were not harmed, and I removed some redirection files and had Google remove them from search although they didn’t seem to exist and nothing was harmed on the pages. I updated, removed any bogus users, and those are OK.

Thanks for all your suggestions. I appreciate it.

Thank you. I do know HOW to delete it, but the problem is it just keeps coming back!

What does 777 allow? How will that affect it? Is that giving me edit/delete rights or something?

I tried that but it keeps re-appearing on refresh.

Should I try removing ALL permissions so it cannot execute?

• This reply was modified 1 year, 3 months ago by webmistressofthedark. Reason: Added info

By the way, the question I asked on the other forum was NOT framed as an ‘answer’ but only a question as to whether the code the server tech gave me was the right thing or not. Obviously people ask questions like this because they do not know what the fix could be..

I am still baffled as to @gappiah’s attitude. I could simply have been told that the tech did not give me the proper fix.

This was the first time I ever had anyone try to iFrame a website and use it in a scam so I had no idea how to deal with stopping it.