Cobb78

Update: removed WordPress and did a fresh install. No problems, except for trying to get my old posts to be recognized.

@esmi that was the original problem, and of the several suggestions I was given (and others I found for others experiencing the same problem), none worked. It was then stated by someone that the only resort was a fresh install.

The database was exported as an sql yesterday, while running WordPress 3.9.1.

Today, things were so screwy on WordPress (unable to post, or edit posts, and it was suggested that I do a fresh install of WordPress and then import the database. I did that, and according to MyphpAdmin, it was done successfully.

What I’m saying is that they aren’t linking up.

Am I correct in assuming that the database password for the previous install of WordPress is the one I need to insert into the config file in order to get it to recognize the imported database?

If not, I guess I’m lost.

Is it possible that the table prefix needs to be changed in the config file (someone suggested that)? If so, how do I find the database table prefix?

Thanks for putting up with me.

Ok, I guess I’m just showing my stupidity here…

I’ve opened the wp_config.php file, and what exactly am I supposed to change? And what am I supposed to match it with?

I’ve got the database name (same as what’s already there)

I’ve got the database username (same as what’s already there)

The password from the original database is different than what’s in the config file. But when I changed that and re-uploaded it via ftp, the entire website stopped showing up.

Forgive my ignorance on the matter, but how do I do that?

Did that, and it didn’t fix the problem. And now, when I’m in the dashboard, there’s a new stupid thing showing up across the top:

“Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/…/public_html/wp-includes/functions.php on line 3193”

So, all in all, that didn’t fix the problem.

Update 2: reverted to an old version of Firefox, and still having the same problem. I’m convinced this has something to do with WordPress 3.9.1

Disagree, I’m having the same problem, and it’s theme twenty-fourteen, with no active plugins (all deactivated, that is).

Update: I installed Palemoon, and attempted to edit the posts in that browser, but still the same problem.

OK, I’ve done the following:

-Deactivated all plugins except WooCommerce. Still having the same problem.
-Already running theme TwentyFourteen.
-Not using a cache plugin.
-https://TheCobbSix.com

All worked just fine before, but have upgraded to 2.1.8 and now the problem exists.

That really stinks. Truly, it stinks.

The problem is causing me to lose subscribers. Please reply.