Duvenhage

Well to be honest I never checked those logs, only the installer log I checked, and didn’t see much there.

I can try installing a package again and check all logs, see if there’s something in there.

Hello Cory and thanks for the response,

And yes, as I mentioned earlier in the first post, all that happens on same location, and also on my localhost. Permissions are fine, everything else is identical for all projects, it just happens.

To add a bit more detail here, I once tried installing a package twice with an interval of few days on the same location. First time it worked perfectly well, and the second time it ended creating the blank wp-config.

It might also be helpful (or totally irrelevant) to add that, I came up with the idea of comparing my packages with another package that was created by a friend of mine, which was working just fine.

The only difference was that his package had also the htaccess file and mine didn’t. I usually delete htaccess, error logs and wp-config after the package is created.

Hello again.

A Question here. I used to add the installer.php file to the archive.zip and extract them altogether on my host. So that after extraction, on my root directory I had all site files, plus the installer.php file., then I would run the installation.

Does it have any difference comparing to the other method where you put installer.php file outside the archive.zip file and along with it (without extracting the zip file) in the desired directory?

Does the wp-config file being empty, have anything to do with “how” you do it?

Well all this time I’ve been switching between Brute Force Prevention and Rename Login features.

The problem is after some point I started experiencing some weird problems with my website.

With Rename Login feature enabled, the custom form works perfectly, but I see some errors and warnings when I manually type /wp-admin or /wp-login.php. Also the new url name I chose (sitename.ir/signin) doesn’t load and include my css files and stylesheets.

With Brute Force feature enabled, typing /wp-admin or /wp-login.php perfectly redirects me or users to the homepage. But custom login form stops working.

Hi wpsolutions.

Sorry I thought the plugin reads the backup folder contents for default settings.

The custom login form is used on homepage and it gives access to another custom page provided by the theme which includes users’ data and stuffs like that.

I put the link here. Though it is in my own language, you’ll easily find the custom form :

https://www.atlasportal.ir

No problem ??

Well this may help a bit here. I tried disabling all security and firewall features. Then tried enabling and testing only Rename Login and Brute Force Prevention features individually.

Everything was fine. So I guess there’s a conflict here with Brute Force Prevention and another feature (not Rename Login).

Maybe reconfiguring the plugin fixes the problem.

Yes it was weird to me too seeing that message “wp-content folder not found”

Anyway I tried manually installing the new version. It loaded with my settings since I didn’t delete the backup folder on my host.

No change. Same problem exists.

Hi mbrsolution.

I tried upgrading to the latest version.
It said “wp-content not found.”

Edit : Do you suggest manually deleting the current version and installing the latest one?

Hi mbrsolution,

Thanks for your response. I personally prefer to have Brute Force enabled.
Considering what it does and how you described it, it’ll be the best choice for me.

But what can do I do about the custom login form provided by the theme?
It doesn’t work when Brute Force is enabled as I mentioned earlier.
Do you have any suggestions?

Hi again.

I’m afraid to say that my problem still exists, and it’s even worse now.
When Brute Force is enabled, people can only log into my site using that secret phrase, and as I know it is not supposed to be like that. The chosen phrase is only for me. In this case the custom login form provided by theme is not working.

I tried enabling Rename Login feature instead. In this case custom login form works properly. But when users manually enter /wp-login.php, some errors and warning messages appear which is not really good. Also the new login page url I’ve chosen (mysite.com/signin) does not include stylesheets and css files and it’s just a white page with 2 inputs and some texts.

Disabling the plugin doesn’t help either.

So far I have done nothing but switching between Rename Login and Brute Force Prevention features.

Hi. Sorry for the late update on the topic. I tried Rename Login Page feature again.

My login / registration forms are working again. Except for the fact that now when I manually enter /wp-admin or /wp-login.php it leads me to the 404 page (which is ok) and shows a warning message saying there’s an invalid argument for a foreach function in one of my theme files.

It sounds like something doesn’t match here, I don’t know.

P.S : The string I chose to be used for login page is “signin”. My stylesheets are not loaded on that page.

Cookie Based Brute Forced seems to be a much better method, but I may have to switch back to Rename Login Page. Anyway I’ll try that and let you know.

So, I guess the fastest possible solution is that I turn Cookie Based Brute Force Prevention feature off and use Rename Login Page feature again, right?

Hi.

@mbrsolution : I can check that.

@wpsolutions : I’ll give it a try. But about the last part where you said

Since you stated that you activated the cookie based brute force prevention feature, you should be accessing the login page via your special link with the secret word. Did you try that?

I can access the login page using that special link, but it’s about my users actually.
I mean, the custom login form provided by the theme isn’t working, and when my users manually enter /wp-login.php it redirects them to homepage. So they can’t access their account.

PS. It seems like I’m no longer able to install a plugin through FTP. It says “wp-content not found”.

Manually adding a plugin using the hosting panel doesn’t work either.