Catalyx
Forum Replies Created
-
Hi dwinden,
Thanks for the reply and suggested link. I’ll follow the link to spare recreating a server and migrating contents.
Thanks.
Hi dwinden, I’d been informed that deleting the WP root .htaccess file or inserting an empty file would reset my login page and make it accessible. I was hence looking for the file to replace (inserting an empty one didn’t work).
I’ve tried finding the relevant .htaccess file for WP without success. Before deleting and reinstalling my app, which is the last resort, do you have any other suggestions?
Hi dwinden, first, thanks for running me through this.
Running the SQL command didn’t show iTSec or any other plugins active, save one.
Is this a multi-site WP env? I believe it is; it has an empty blogs.dir folder.
WP version? the latest upgrade pushed this week, v4.1.2
iTSec plugin version? From the Readme file, v4.6.13
Is the frontend of this website functional ? Yes.
Is WP installed in a subfolder ? Yes, OpenShift hosts the site and placed it in a subfolder.
Your last query and point may suggest the problem. Searching online, I noticed OpenShift has placed the .htaccess file elsewhere than the app’s root. The path it states on this page does not exist on my installation.
I’m currently searching the server from its root for the file. I’ll respond once completed.
Thanks.
Thanks dwinden, running the SQL command displays the /%postname%/ option value.
The 404 error is replaced with the client browser (Firefox) displaying “The page isn’t redirecting properly”. Similar “redirect” experience with Chrome.
Note that deactivating the iTS plugin (i.e. appending the better-wp-security folder’s name with -bak) results in a 404 error while reactivating it results in the browser reporting as above.
Any further advice is welcomed. Thanks.
I should note also that in phpMyAdmin, under the wp_options table, the itsec_hide_backend option still displays my old login slug, which currently results in a 404 error when attempting to reach it.
This is to note that creating and inserting the new .htaccess file in root does not appear to have changed the itsec_hide_backend optin value in the database.
I am uncertain if this is a relevant factor.
Hi Gerroald,
Thanks for the message. I’m able to deactivate the plugin via FTP. (Note that my folder is still labeled better-wp-security-bak though I believe I had upgraded to iThemes Security.)
My .htaccess file is missing at the root so I created a new one with the supplied code.
I’m still receiving the 404 error when I attempt to reach the new slug.
Could you advise further? Thanks.
EDIT: FYI, I also checked phpMyAdmin’s wp_itsec_log, which shows no 404 errors, and wp_itsec_lockouts, which doesn’t display any lockouts.
Forum: Fixing WordPress
In reply to: 404 Error on wp-admin and Custom Admin URLThanks. I created an .htaccess file in my root directory. The admin URLs still return a 404 error.
Forum: Fixing WordPress
In reply to: 404 Error on wp-admin and Custom Admin URL@laliz Thanks for the suggestion. I had tried reinstalling WP and importing the database and content folders without success.
I’d like to try deleting the .htaccess file but cannot find it at the WP root directory. Would you happen to know what alternatives some server hosts use in place of the file?
PS: my FTP client is set to display hidden files and folders
Forum: Fixing WordPress
In reply to: 404 Error on wp-admin and Custom Admin URL** bump **
Can anyone please advise?
Forum: Fixing WordPress
In reply to: 404 Error on wp-admin and Custom Admin URLThanks for the message.
Because the site is under (delayed) construction, can we please troubleshoot without the URL?
PS: I had activated debug mode and no errors appeared.
Hi David,
I was assuming that UpdraftPlus would scan the file directories and change the settings for the standard WP content folders to backup.
Yes, I should have reviewed the paths of the database and adjusted accordingly. This was not a Updraft issue as you stated but a shoddy migration.
Thanks again for creating a great plugin and the strong support.
Resolved by manually updating database entries to point to new folder path.
I hope this helps others.
Issue resolved: deactivated plugins and restarted server
Trouble source: unknown@lkrnac, thanks for the tip. My problem may have been the Piwik installation, separate from the WP-Piwik plugin. I reset the site tracking in the installation and it recommenced tracking. I haven’t figured out what led to the problem and how to integrate results for the old and new tracking.
Thanks for responding. Yes, the tracking code is still present. The problem seems to have been partly resolved.
I added the site again to the Piwik installation without removing the old one and the plugin and installation now track the site. I now have two sets of stats for one site and some return visitors appear as new.
I don’t know what caused the change but it currently works. Thanks for the plugin.