spiteyourface

I assume you mean Settings > Network Setup within WP?

Yes, this seems to be the case. What else should I be looking for?

Edit: a fix to the .htaccess file may have resolved the issue. Will report back if that proves not to be the case.

• This reply was modified 5 years, 8 months ago by spiteyourface.

Good (bad) to know, I guess? Annoying because I’ve been using this gallery for a while now, and while updating has always been a bit buggy, it suffices and I don’t want to rebuild my whole site. But currently It’s stubbornly stuck at whatever it looked like yesterday, twanging back like a rubber band against any change I apply.

I think we agree that the theme is publishing the manifest error codes. But I’m still not sure if the connection attempts are something automated by the theme itself or refer to an actual human action, or if making the distinction helps us find what is actually publishing the errors?

My host support offered the following “at some other location, you are trying to connect to db as main mysql user, and its password appear to have changed.”
This, again, is consistent with an actual thing that happened where a third party was given the wrong password. Perhaps that event is coincidence, but it seems related? Even if that in itself is a separate issue to the theme then publishing the resultant errors.

I don’t know if that helps us? Still waiting on Theme support regardless.

As to the original question of upgrading to MySQLi, my hosts confirmed the understanding that MySQL is outdated and that a change to MySQLi could be expected ‘in the future’ but then deferred me to my web developer to look into resolving the concern. But I am my web developer. So I still need those starter tips?

Okay, well it’s now running twentysixteen. It’s not much cop with my content but you’ll see that the MySQL errors aren’t there. I guess that means it’s the Motion Picture theme, then?

Not yet. The site is so widget driven etc that I thought it might be more efficient just to take the site down until I receive support, which I’m certain won’t be before monday now if at all (the Obox page is ambiguous).

Also, I kinda can’t because, it turns out, even the wp interface is plagued by these intrusive error messages and the options for themes are obscured.

The errors refer to real login attempts made with an incorrect password, which is perhaps what it chooses to display as NO? So I can account for the connection errors as such, just not these manifestations of the error messages?

Could the following be related? It’s from the wp-login.php

I’m purely going on the ‘filter the error messages displayed above the login form’ bit here, being terribly literal. I assume that code is as expected, but could something be interacting with it strangely?

if ( ! empty( $errors ) ) {
			/**
			 * Filter the error messages displayed above the login form.
			 *
			 * @since 2.1.0
			 *
			 * @param string $errors Login error message.
			 */
			echo '<div id="login_error">' . apply_filters( 'login_errors', $errors ) . "</div>\n";
		}
		if ( ! empty( $messages ) ) {
			/**
			 * Filter instructional messages displayed above the login form.
			 *
			 * @since 2.5.0
			 *
			 * @param string $messages Login messages.
			 */
			echo '<p class="message">' . apply_filters( 'login_messages', $messages ) . "</p>\n"

Thanks. I know it’s not too revealing but even having a user name public is compromising. I’ve contacted the theme support in advance and await their reply.

There’s nothing obvious (to me) in the setup.php that the error points to, either.

I’m reluctant to post a direct link because of the security issue but you can easily find the site by adding dot com to my username.

the WP_DEBUG was already set to false.

I’ll contact them, but they’ll probably take a while to respond, especially at the weekend. In the meantime have you any idea where/what is generating those publicly visible error messages? Because so long as they’re present they’re a security risk.

Thank you for asking. A more serious problem has arisen first of all. The aforementioned MySQL errors, which I thought were just appearing on my WP login page are actually public on my homepage!

Any person visiting my site is seeing a string of errors (relating to real world login errors) at the top of the page, quite publicly, revealing delicate private login information.

Please advise how to remove and prevent this or to why it is happening?

As to your question.. A standard wp install hosted on a standard hosting service. What specifically do you need to know?

Good lateral thinking brasofilo (slaps head) That shouldn’t rightly have made a difference if the input data was already right, but as a matter of fact – it fixed it! (for noooooooow)

What actually happened was I did as brasofilo suggested, which took me through to the next stage of the installation set up. I added my details, it bought up that smug little ‘expecting more steps?’ message and declared itself installed, so I clicked ok and… ERROR ESTABLISHING A DATABASE CONNECTION.

oh.

Thinking the active wp-config.php probably had some changes in it from various customizations on my other site, I instead replaced it with a fresh new config.php adapted from the wp-config-sample.php file that comes in the installation zip. Even though this is exactly how I generated the first one in the first place.

The data I entered was definitely correct across all three or more versions/attempts so (as indicated by the latter hiccup) there must have been something astray in the rest of the dynamics of that file?

Anyway, all I can tell you is that swapping it out for a new file generated from the sample file, fixed it on this occasion.

Many thanks all!

Well spotted maoski, thanks. But that is only an overhang from my retyping/trying alternative host names. Therefore the problem predates that mistype and subsequently, has still made no difference.

No suggestions, binomiale and still stuck my end. All help very welcome.