lcklem

This is ridiculous!! I have been waiting for an answer for 5 days. The updated plugin is not working!! How do I report the developer for lack of response and communication!!

• This reply was modified 6 years, 11 months ago by lcklem.

I sent an e-mail with screen shots directly from my email with descriptions.

Hi Rene,

Thank you for getting back to me. I moved the site manually by copying all of the files from the staging site to the live production site and then I changed the site and home URL’s in the database, wordpress and the wp-config file. I have most recently used Velvet Blue to go through the URL’s, etc and change the name, but it did not change any of the references below.

All of the staging site tables had the word staging at the beginning of the tables. Those have been removed from the database. The staging folder has also been removed from the server.

It will not let me include a snapshot or image of the wpstg references in the wp-options table, so I will do my best to show the information.

272384 wpstg_settings a:4:{s:10:”queryLimit”;s:4:”1000″;s:9:”fileLimit”;… yes
272404 wpstg_existing_clones a:1:{i:0;s:7:”staging”;} yes
279388 wpstg_version 2.3.0 yes
279389 wpstg_installDate 2016-05-02 02:47:04 yes
279390 wpstg_RatingDiv yes yes
279391 wpstg_firsttime true yes
279392 wpstg_is_staging_site false yes
279393 wpstg_hide_beta yes yes
286189 wpstg_version_upgraded_from 2.2.4 yes
285720 wpstg_start_poll no yes
300410 wpstg_existing_clones_beta a:1:{s:7:”staging”;a:6:s:13:”directoryName”;s:7:”… yes
300411 wpstg_poll no yes
300412 wpstg_beta no yes
300413 wpstg_rating No yes

This is copied from the database table, but not drilled down to each entry. I have run a search through all of the database tables and these are the only pieces left that have the word staging or wpstg in them. I hope this helps since I cannot attach a photo or file.

That particular health check plugin will not work on my website. It crashes everytime I try to check a plugin.

I installed the wrong plugin so it did not have debug information. So I installed the other plugin that did and I cannot access the site on Chrome, but it is coming up on Microsoft Edge with no problem.

Just a note. It is only affecting the wp-admin. The front end of the website has no issues.

<?php
/** Enable W3 Total Cache Edge Mode */
//define( ‘WPCACHEHOME’, ‘/home/cpck101/public_html/wp-content/plugins/wp-super-cache/’ ); //Added by WP-Cache Manager
//define(‘W3TC_EDGE_MODE’, true); // Added by W3 Total Cache

/**
* The base configurations of the WordPress.
*
* This file has the following configurations: MySQL settings, Table Prefix,
* Secret Keys, WordPress Language, and ABSPATH. You can find more information
* by visiting {@link http://codex.wordpress.org/Editing_wp-config.php Editing
* wp-config.php} Codex page. You can get the MySQL settings from your web host.
*
* This file is used by the wp-config.php creation script during the
* installation. You don’t have to use the web site, you can just copy this file
* to “wp-config.php” and fill in the values.
*
* @package WordPress
*/

// ** MySQL settings – You can get this info from your web host ** //
/** The name of the database for WordPress */
define(‘DB_NAME’, ‘cpck101_wp118’);

/** MySQL database username */
define(‘DB_USER’, ‘XXX’);

/** MySQL database password */
define(‘DB_PASSWORD’, ‘XXX’);

/** MySQL hostname */
define(‘DB_HOST’, ‘mysql1003.mochahost.com’);

/** Database Charset to use in creating database tables. */
define(‘DB_CHARSET’, ‘utf8’);

/** The Database Collate type. Don’t change this if in doubt. */
define(‘DB_COLLATE’, ”);

/**#@+
* Authentication Unique Keys and Salts.
*
* Change these to different unique phrases!
* You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
*
* @since 2.6.0
*/
define(‘AUTH_KEY’, ‘F-oU:bGfqZ~Y)~6ErN^^>uupsOTH._},L9OH{j)-A2jb7rWQpLO)MSI#z0=x;Uc7’);
define(‘SECURE_AUTH_KEY’, ’37f+DHK7K:}>-j)K(le$x?[j,qqG|[zeh&Ond3H*Uw>M$Oaz++p@+)/0|83 Y(I ‘);
define(‘LOGGED_IN_KEY’, ‘AoFPJ6i$4++b-to8ulw9KK)a55}+nNuf6?)z)ZrxhbL:1P+f%08>Qc_i67B?fh’);
define(‘NONCE_KEY’, ‘b4Y0&A.[V<p7bNO?yIY<nY<YgZ&naBSmik+$ddJqwZ9D<o7KeG`rFf>#sSIJe,F.’);
define(‘AUTH_SALT’, ‘#2<~L5Aub(T mf,P0{nTC-DEatb5_I3j+(v|–H16l%Oa0K+C-m(s(HF4;Nq>t|Y’);
define(‘SECURE_AUTH_SALT’, ‘K7]~(o+P<^e+/=F=_i)N51rgc!Xf+8yvVBt)@2@|~}(=XF-rNFoPbCn}|GM-p%’);
define(‘LOGGED_IN_SALT’, ‘X*D aS<kk2r))Ur^[c3<87}r1a.t;N8P3+ Uh+M!FNm-G0,6Yjov5?/t.*kRBZ[Y’);
define(‘NONCE_SALT’, ‘bz(nAJ8q5W)k-3@Cyif;tT:NW{{{&OYb:b;|GfN%N?U5IH2!/T[k-EKLWcz2aFyx’);

/**#@-*/

/**
* WordPress Database Table prefix.
*
* You can have multiple installations in one database if you give each a unique
* prefix. Only numbers, letters, and underscores please!
*/
$table_prefix = ‘wp_’;

/**
* WordPress Localized Language, defaults to English.
*
* Change this to localize WordPress. A corresponding MO file for the chosen
* language must be installed to wp-content/languages. For example, install
* de_DE.mo to wp-content/languages and set WPLANG to ‘de_DE’ to enable German
* language support.
*/
define(‘WPLANG’, ”);

/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*/
define(‘WP_DEBUG’, false);

/* That’s all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined(‘ABSPATH’) )
define(‘ABSPATH’, dirname(__FILE__) . ‘/’);

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . ‘wp-settings.php’);

Yes, I do. Everything is still the same. Nothing changes.