Tried to deactivate the plugin via database – as seen here:
https://www.ostraining.com/blog/wordpress/disable-a-wordpress-plugin/
Still no luck whatsoever
Hello! Check .htaccess and wp-config.php I suppose redirection may be there.
Nothing whatsoever :(.
This is config.php:
<?php
/**
* The base configuration for WordPress
*
* The wp-config.php creation script uses this file during the
* installation. You don't have to use the web site, you can
* copy this file to "wp-config.php" and fill in the values.
*
* This file contains the following configurations:
*
* * MySQL settings
* * Secret keys
* * Database table prefix
* * ABSPATH
*
* @link https://codex.wordpress.org/Editing_wp-config.php
*
* @package WordPress
*/
// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'BLABLABLA');
/** MySQL database username */
define('DB_USER', 'BLABLABLA');
/** MySQL database password */
define('DB_PASSWORD', 'BLABLABLA');
/** MySQL hostname */
define('DB_HOST', 'localhost');
/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8mb4');
/** 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
*/
BLABLABLA
/**#@-*/
/**
* 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 = 'ep_';
/**
* 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.
*
* For information on other constants that can be used for debugging,
* visit the Codex.
*
* @link https://codex.wordpress.org/Debugging_in_WordPress
*/
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');
This is .httacess
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
I even tried to reinstall the whole WordPress. Then I actually got ONCE into backend during the installation. But after I signed off, it went back to the same behavior :(. The database should be clean, nothing in wp-config, nothing in .htacess (even tried to delete it). So they had to hide some setting somewhere else. DAMN YOU iTheme security 😀 !!!
http://www.epic-tv.cz/wp-admin
Hello!
Very strange! Your site now is full of content, you returnd it from backup after you made clear installation? Maybe some cache on server side? But too long…
Try adding to .htaccess:
RewriteRule ^(/)?yourslug/?$ /wp-login.php [QSA,L]
RewriteRule ^(/)?wp-register-php/?$ /wplogin?action=register [QSA,L]
This was added by plugin to mine. Replace “yourslug” to your slug.
Hi there. Thanks for advice. I made it this way, with no success :(. Have I done it wrong?
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
RewriteRule ^(/)?epicator/?$ /wp-login.php [QSA,L]
RewriteRule ^(/)?wp-register-php/?$ /wplogin?action=register [QSA,L]
Seems to be ok. Try to duplicate “RewriteEngine On” like this:
RewriteEngine On
RewriteRule ^(/)?epicator/?$ /wp-login.php [QSA,L]
RewriteRule ^(/)?wp-register-php/?$ /wplogin?action=register [QSA,L]
Nope 🙁 epic-tv.cz/wp-admin
.htaccess state:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
RewriteEngine On
RewriteRule ^(/)?epicator/?$ /wp-login.php [QSA,L]
RewriteRule ^(/)?wp-register-php/?$ /wplogin?action=register [QSA,L]
I looked through database and found:
(156, 'itsec_hide_backend', 'a:7:{s:7:"enabled";b:1;s:4:"slug";s:9:"<strong>myoldslug</strong>";s:12:"theme_compat";b:1;s:17:"theme_compat_slug";s:9:"not_found";s:16:"post_logout_slug";s:0:"";s:12:"show-tooltip";b:0;s:8:"register";s:15:"wp-register.php";}', 'yes'),
(3310, 'itsec-storage', 'a:13:{s:6:"global";a:27: ... s:12:"hide-backend";a:6:{s:7:"enabled";b:1;s:4:"slug";s:13:"<strong>mynewslug</strong>";s:12:"theme_compat"; ...
Second block contains a lot of text, I replaced the most with “…” here.
(You can read about my troubles with old and new here: https://wordpress.org/support/topic/hidden-login-page-is-comprimised?replies=2 )
So you can also try to make backup and see what is there.
OMG, stroung tags shouldn’t be there! =)))
Seems that first occasion is setting for old version of plugin and second is new. Much garbage!
Ok. I will try to export the database, but I think that I already deleted everything concerting itsec from the database :-/
So you can try make backup of whole site and install it to some other hosting (hostinger.cz may have free plan). Use hosts file on your local to address it (not to change DNS). And you will know for sure, if problem is in files/database or on server side of your today hosting.
I made files backup and searched for slug in files. Nothng found.
Another idea is to find old version of plugin and try to install it.
etnmathy, and one more thing. I think you should better not delete everything from DB, but put the values you need.
Yeah this COULD be solution – reinstall WP again and install that plugin, since after the installation it is the single opportunity to get inside backend. And then change everything in it. And then hope it will work 😀
