So, I cloned an entire server as a development environment.
On that server was a wordpress installation.
The server was logging in to the wrong wordpress installation.
There is probably a 'correct' way to do this. But I found the wordpress options I needed to change in the wordpress database in the prefix_options table. (We have prefixes set to ON for multiple wordpress installations. Our tables are prefixed and referenced with prefix_ prepended in this post.)
SELECT * FROM prefix_options LIMIT 0,20;
From there, you should see why your new wordpress is logging you in to your old wordpress...
Hint:
mysql> select * from prefix_options limit 0,20;
+---------+-----------+-------------------------+--------+
|option_id|option_name|option_value |autoload|
+---------+-----------+-------------------------+--------+
| 1|siteurl |http://notdevelopment.com|yes |
mysql> UPDATE prefix_options SET option_value='http://development.com' WHERE option_id=1;
On that server was a wordpress installation.
The server was logging in to the wrong wordpress installation.
There is probably a 'correct' way to do this. But I found the wordpress options I needed to change in the wordpress database in the prefix_options table. (We have prefixes set to ON for multiple wordpress installations. Our tables are prefixed and referenced with prefix_ prepended in this post.)
SELECT * FROM prefix_options LIMIT 0,20;
From there, you should see why your new wordpress is logging you in to your old wordpress...
Hint:
mysql> select * from prefix_options limit 0,20;
+---------+-----------+-------------------------+--------+
|option_id|option_name|option_value |autoload|
+---------+-----------+-------------------------+--------+
| 1|siteurl |http://notdevelopment.com|yes |
mysql> UPDATE prefix_options SET option_value='http://development.com' WHERE option_id=1;
No comments:
Post a Comment