I am having the strangest error come up on a site that I am working on. For a while we have had the site in admin only view so we could work on things without any users logging in. Was fine during this phase.
Today we opened up the site to a handful of people to sign up and test the site out. As people started coming in however, every user was getting this error:
"can't open file" with a white screen
The error first pops up when the user tries to register and gets to the final page. This is the part that is supposed to tell the user that a email confirmation link has been sent to them.
Once this error pops up, the error will continue to display for all pages until they clear their cache.
Changes that were done:
1: Prior to opening the site up, the .htaccess was edited to prompt a initial login box (this was done to prevent others from accessing the site while we were moving to a 'beta' phase). I also added a .htpasswd file that contained the details for the users to enter to get to the site. I have tried to delete this edit thinking that it was this acting up, but did not work, error was still displaying.
2: Checking and repairing the joomla session table within the database - my thoughts were that perhaps it was a session issue since it was triggered when the user went to sign up and complete the registration process. This did not work.
3: One of the components that we were using needed a custom edit to the session.php file. "/libraries/joomla/session/session.php" - I reverted this file back to the original, however the error still comes up. Did this, thinking it was session related as the point above)
4: I cleared all cache and purged all expired cache, this had no effect. I also cleared all cache as I did the previous 3 items as well.
So now I am completely stumped on how to go ahead and get this working correct. The error that displays is VERY vague and leaves no information other than it 'can't open file'
Joomla Version: Joomla! 3.4.8 Stable
PHP Version: 5.6.16
Web Server: LiteSpeed
Community Component: EasySocial
Subscription Component: PayPlans
We've sorted this now I think. Looking in the logs one of the site plugins was using the ftp layer to open a file which had been created directly by Apache, and so the permissions didn't allow it.
I've change the permissions now and the error condition seems to have gone.
Related
Background:
I have a WordPress website that lives in a Google Cloud-based load balanced environment, and as I work through getting CI/CD setup I elected to isolate one of the servers so that my team could properly run through isolated testing. Since the website is on a regular domain (www.mybusiness.com), I created a duplicate database from our production DB and pointed the isolated server at this new test database. From there, I updated both the 'siteurl' and 'home' values with the isolated server's IP address in my wp_options table, and from there I can access my isolated WordPress site by simply using the URL. However, this is where things get frustrating: the login page simply refreshes after a successful login attempt, while blatantly incorrect login attempts with invalid credentials properly return user login error messages.
After countless hours searching the Internet, Stack, and elsewhere, I've found that the most common solutions are either:
Clear your browser's cookies / cache.
Try logging in with completely different devices (other cell phones, laptops) to confirm it's not a device or local browser-cache issue.
Deactivate and test each plugin,
Confirm your 'siteurl' and 'home' values are correct.
Test your .htaccess file to confirm that's not the problem.
Clear your user's WordPress 'session_tokens' meta_key value.
Revert back to an older / default WordPress theme to confirm if it's a theme problem
Run WordPress's built-in DB repair tool.
Create new WordPress salts and swap them in inside the wp-config.php file.
Enable the 'WP_DEBUG' constant to see if anything in the error logs pops up.
Test non-HTTPS versions of 'siteurl' and 'home'.
After trying all of the above, nothing seems to work: reverting to an older theme (twentynineteen) still presents the same login page refresh issue, and I've gone through every plugin on the server to see if deactivating one or all of them creates a solution - none seem to be the root cause. Error, mysql, and auth logs are also maddeningly clean.
Interestingly, if I add a trailing slash to my IP address-based 'home' and 'siteurl' value, from 'https://11.11.11.11' to 'https://11.11.11.11/' I do successfully get to the correct internal landing page (https://11.11.11.11/landing-page/) - however it just displays a 404 with the basic white screen.
Current WordPress version: 5.4.7
This leaves me with a few questions:
Is this a file permissions issue somewhere? Are there any key WordPress files in which permissions could create this effect?
Would Apache or anything VPC be in play here? I checked out our Apache .conf files, but those don't seem to be the suspect.
Should we look into a WordPress upgrade knowing we're a bit behind with 5.4.7?
Thank you in advance for the help!
I saw this mentioned before, but I couldn't find an answer.
I just migrated from my staging site to live, using a plug-in All in one WP migration. After a fresh install of wordpress + plugin on the new site, I took the .wpress file exported from staging and uploaded to the new.
Everything was successful, until I was redirected to the perma-links settings area to just save the final changes. However, from then any setting I touch in the perma-links section breaks my site. Any link in front end or back end will automatically download to browser.
After some digging, I found its related to the htaccess page. If you haven't already noticed, I'm new to this. I don't know where to start to test what could be wrong with the htaccess page, so I wiped it clean to at least be able to navigate the site.
Anytime I try to touch any permalinks setting in the backend, it will re-write in the faulty code and I have to go back into the wipe the htaccess again.
The second issue is it's causing any page (besides the homepage) to 404. If I try to preview a page from backend (mywebsite.com/page1) it 404's, and of course front end. Same if I try to create a new page.
Please let me know any other info I can provide. I am open to any suggestions.
Thank you
step 1 export your database then open it in notpad++ then ctrl+f find your website old URL suppose stackoverflow.com/dev and replace it with your live site stackoverflow.com after replacing all URL make save it and make zip again.
step 2 import the database into your site database.
step 3 go to your dev site and download all setup with WordPress now paste the all files into new website directories.
step 3 open wp-config.php file and changes database name username and password.
step 4 open your wp-admin and use the username and password same which one you using for the dev site
step 5 go to permalinks and set it %%postname%%
these are simple steps and I am sure it will work for you. no need to new WordPress installation.
Could provide us with your .htaccess file?
But as someone noticed - problably you don't have mod_rewrite. Contact your hosting company, they should be able to fix your problem
Recently my WordPress sites started acting up on the login page.
When a user provides their credentials and hits enter, the page seems to reload.
No feedback is given when the site reloads. Not even a faulty password message.
When using the "recover lost password" option the page will ask for an email or username but then proceed to do the same thing that the login page does.
When running "wp user list" from the WP-CLI on any of the sites, this is the error message.
WordPress database error Got error -1 from storage engine for query DELETE
FROM `wp_options` WHERE `option_name` = '_site_transient_security_report_performed_recently'
made by include('phar:///usr/local/bin/wp/php/boot-phar.php'), include
('phar:///usr/local/bin/wp/php/wp-cli.php'), WP_CLI\Runner->start, WP_CLI\Runner->load_wordpress,
require('phar:///usr/local/bin/wp/php/wp-settings-cli.php'),
do_action('init'), call_user_func_array,
Jetpack::perform_security_reporting, get_site_transient,
delete_site_option, delete_network_option, delete_option
The server hosts many other WordPress sites and they are all doing this.
When a site is moved to our production server the login page works as it should.
This started out as a problem on only one site and has now spread to the whole server.
Log in to MySQL command line interface or use the graphical client of your choice, and run
repair table wp_options;
If that does not fix it, drop the wp_options table and replace it with a working copy.
If that does not fix it, you will need to debug MySQL deeper starting by perusing the MySQL error log.
I have set up a simple Wordpress site with an order form but I'm struggling to get the site to recognise Sage Pay.
I've been following the initial instructions in the PHP integration kit - http://www.sagepay.co.uk/support/find-an-integration-document/direct-integration-documents:
Create a database and add the necessary tables.
Edit the /lib/config.php and the /demo/config.php to include my Sagepay Account and database details
In the test server for Sage Pay I also added the IP address of my site as an exception.
Every time I run the https://mywebsite.com/demo it returns the error:
Ooops!!!
An unexpected error seems to have occurred.
Try to refresh the page or you can contact us if the problem persist.
This is pretty early on in the but I seem to be doing something wrong. Is there something else that needs edited as the instructions are frustratingly vague.
Would I be better just using a Sagepay Direct plug in with Wordpress e-commerce solutions?
Thanks.
I am also a currently frustrated Sagepay learner. To asnswer you question, I had this problem too. My problem was that i had the database details incorrect. I had my local host details on my test environment, and i had not changed the details correctly in demo/config.php before ftp the file to my webserver. Once i did this, i got over the oops screen. The next problem was that i got a blank screen when running index.php from demo. I was told by sagepay that apache needs restarting as a service everytime somethingortheother happens. So on my local environment i restarted all services in wamp and it worked. I can now see the demo (not that i know what to do now as there are no instructions and the php is hidden in a complex class structure with the html content in some tpl files which i have never seen before - of course there are no instructions in the integration kit at all). Anyway back to the answer. So locally i can run the demo, but i still have white screen on my webserver, becuase i can't restart the apache service there, so that is the next problem. I will keep trying and add anything useful later.
I also had this problem, I had not given the database user account the necessary permissions to access the database.
For 2 days now I have been trying to access my admin page for the zencart on a site I am working on, I have re-uploaded the whole zencart numerous times and I keep getting a blank page when I go to the admin section. Can anyone help?
We will probably need more details to really be able to help. If you just see a blank page (have you checked the source code in the browser? Is it completely blank?) you will need to check the error logs to be able to trace the problem.
If you are using Zen Cart version 1.3.8a or higher you will have the error logging tool enabled by default, so you can have a look for logging files inside the /catalog/cache folder. Take a look at a few files and look for fatal errors, because you probably will have one of those if you are getting a blank page.
By the way, that kind of error doesn't happen without good reason, What is the last thing you have modified/added to your admin site? A new contribution perhaps?