I can only see changes to live WP site when logged in - php

For some reason I can only see changes to my site when logged in to Wordpress. I've downloaded and modified some files/pages (style.css, content-post.php, etc) using Filezilla but the changes don't appear on any browser without me being logged in to Wordpress. I've tried clearing the cache but no luck. Any idea whats happening, perhaps something to do with temporary files?

Disable caching plugins if any installed.

Related

Change Wordpress theme on theme-broken installation

I'm developing a Wordpress theme for a client, and I've done a mistake that caused the Wordpress to show the classic error page "There has been a critical error on your website". It's very simple to fix this when you have some advanced access to the server (like an FTP, SSH, cPanel, web-based file manager or something else). But, in this case, I don't have any other access than wp-admin!
I've asked my client for some access (FTP, cPanel or any other), but he don't have any other access too.
So, thinking a bit, I still logged in on this Wordpress (cookies are set), and I'm trying to change the theme from URL (I know the Twenty Twenty One theme is installed). So, I copied the URL that activates the Twenty Twenty One theme from my localhost, changed the domain to match the domain of broken website, and picked up a nonce from DevTools. The final URL is like this:
http://dev.example.com/wp-admin/themes.php?action=activate&stylesheet=twentytwentyone&_wpnonce=5f324abc99
Tried to access this from my logged-in browser and... Won't work :( It shows the "There has been a critical error on your website" message.
So, I'm here to ask you... There's another way to change the Wordpress theme outside the panel on a theme-broken installation?
Thank you for all!
Good day, mate.
I see its a common problem when you install Plugin
or theme and everything crash(
If you can not have access to FTP or Cpanel, try to Reinstall WP.
It will delete all themes and refresh the plugins.
After that you can upload and install new themes and website will work.
Go to Dashboard, click Updates and find Re-Install Wordpress button.
Tell please of it helps you...

Can't stop wordpress site from redirecting to the old installation folder

Basically the whole site was like this when I took it: sitename.com/wp <- it was the official address of the whole site.
I tried moving all files from public_html/wp to just public_html. It didn't work of course. I gave up and deleted database and made my own and installed the wordpress once again. Now I am able to log in and even though I have access for example to this url: https://sitename.com/wp-admin/options-general.php I still am redirected to sitename.com/wp when I try to go to sitename.com. Is there an option to make it work normally?
There are a few places to see for this issue
First of all disable all the cache plugins if any and browser's cache
Secondly, check in wordpress settings the URLs that you have there (settings - general)
Make sure you have the default htaccess file, before that take a backup of everything
Maybe a site url would be helpful;

Drupal 7: Localhost/user link defaults to website/user

I am really new to Drupal and playing around with this existing Drupal site.
I did a FTP transfer of all the files to my local computer directory. I currently got it on a Vagrant box and I can access the site via http://192.168.56.101/html.
I can do http://192.168.56.101/html/anything-but-user and it brings me to the proper area on the site. However I can't do localhost/html/user, because it redirects me to the website URL rather than the local URL.
I tried clearing the cache (with Drush). I scanned all files in the system and changed the web url to the local URL [not sure if I need to do any other command], and I can't seem to find anything in the .htaccess files that would lead me to this.
The href="/user I would greatly appreciate any advice or help in figuring out this solution.
--UPDATED
There was a module called "Secure Pages" that was causing the user and registration links to be locked and static to prevent redirects to phishing sites. I had to disable this module using "drush pm-disable securepages" in the terminal.
Some typical items you may want to check:
Check if you get the same problem using another browser. If with another browser it works, then it is pretty sure a cookie problem. To solve that, delete the cookie in the browser where you have the problem.
Make sure "clean urls" is enabled. Refer to "https://drupal.stackexchange.com/questions/165029/clean-url-leads-to-duplicate-url-after-migration-to-another-hosting/165044?s=1%7C3.9647#165044" for more details on that.
Make sure the value of "base_url" is set correctly (in your settings.php).
If module Secure Pages is enabled, then try to (at least temporary) disable that moduel to see if it helps.
Apparently, there was a mod called "SecurePages" that was causing the URLs to be static to prevent someone from changing them and redirecting users to a phishing site.

No longer able to access Wordpress admin panel

I am no longer able to access the admin panel of a Wordpress site. 2 days ago I added a plugin, loaded some new content, and things were working fine. The client loaded some regular blog posts, and today, it no longer works.
First of all, the error itself:
I go to URL: mydomain.com/wp-admin, the browser redirects to: mydomain.com/wp-login.php?redirect_to=http%3A%2F%2Fmydomain.com%2Fwp-admin%2F&reauth=1
The error message says:
Not Found
The requested URL /mother/18/readf.php was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to
use an ErrorDocument to handle the request.
What I know so far:
Nothing in .htaccess redirects to mother/18/readf.php
A search of similar errors gives a lot of results where urls within normal sites seem hijacked to sell antidepressants, viagra, etc. When I say normal sites I mean that there are sites that do logistics,
https://www.google.com.ar/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=mother//readf.php&safe=off&nfpr=1&start=10
https://www.google.com.ar/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=mother//readf.php&safe=off&nfpr=1&start=10
Disabling all plugins doesn't help (I renamed the plugins folder and then tried to log into the admin).
Searching the database for readf.php or mother doesn't show anything obvious.
The client claims to only have made changes to content since yesterday, when the site admin was still working. (Yes, claims... they have superadmin access, so this might not be true).
Has anyone come across this issue? Any ideas on what I can look for next?
Sounds like you got hacked. Time to fix it right the first time, or you will get hacked again. You need to replace all core WP files/folders (except wp-config.php and wp-content), but scan the uploads folder and theme for exploit code and modified files or added files, like readf.php. Replace all plugins, too.
Also scan the database for eval code and added administrators. (See "My Site was Hacked" below).
Change all host, FTP and WordPress passwords in the process. Scan your own PC for malware that might have grabbed logins and passwords.
Tell your web host you got hacked; and consider changing to a more secure host.
Carefully follow FAQ - My Site Was Hacked at WordPress.org.
Then take a look at the recommended security measures in Hardening WordPress and Brute Force Attacks at WordPress.org.

WordPress won't stay logged in

I moved my WordPress install from a development server to a freshly installed CentOS Apache 2.2 PHP 5.3 server. Initially, everything was working well. Logging in wasn't a problem, but then I noticed after logging in as a WordPress user and loading a new page I would be logged out.
What PHP settings do I need to have enabled, or are there any other considerations, when using a fresh server for WordPress that would make users not able to stay logged in (almost like the session isn't saving them)?
edit
It seems like the server isn't logging people in, but is reading the $_POST variable, so why would WordPress not save logging in?
The answer was looking at output_buffer. When this was off, the wp functions couldn't save to the session because something was already writing to the header.

Categories