I'm currently making a webpage and running it locally on localhost for testing. But whenever I make a change to that page and want to see the result in the browser I run into a "problem". I have to update (press F5 or the update button in the browser) several times for the site to show. In the meantime it's just white...
Let's say I have the site up in my browser (looking good), and then I make a change and want to see it. I press the update button in my browser one time and the site is now just white. I press it again and again, but it stays white. Until I press it a random number of times, and it works. Sometimes I just have to update once, and sometimes I have to update 7-8 times. Sometimes it's fast as hell, and other times it's slow as my schools computers.
Does anyone know if there might be a problem with the site itself (and this problem will continue to exist, even after I upload it to the server), or if it's just a problem with my internet/ computer/ known problem when running on localhost?
I'm using XAMPP on a Mac and have tried testing the page in both Safari and Chrome.
Thanks for all the tips in advance!
From Europe with a problem,
Alekplay
EDIT 1:
It turns out Chrome decided to give me an error message instead of a white screen now. It says "no data received", and Safari is still just blank. Any ideas? I've tried turning off caching.
EDIT 2:
Did some tweaking here and there, and found out that it's SimpePies autoloader.php that's causing my problems. Any of you have any knowledge around SimplePie, and know how I can make the site load faster? It's fine when I've commented out require_once('php/autoloader.php');, but I need that for my feeds to load. Any ideas?
Into chrome you can turn caching off. Just take a look to this page :
http://geek.michaelgrace.org/2011/09/disable-google-chrome-cache/
With Chrome: CTRL+SHIFT+R
I don't know about Safari.
That may be something related with the cache or with apache itself.
Find out if you have any error on apache's error.log. It might be related to an error similar to this one:
AH00052: child pid 62969 exit signal Segmentation fault (11)
then you should check: "[notice] child pid XXXX exit signal Segmentation fault (11)" in apache error.log
Basically it states to try to increase output_buffering in your php.ini
You would have to run a backtrace on the coredump to know why it crashed, as indicated elsewhere. In mi case it was APC, and the error went away as soon as it was disabled on php.ini. Yours might be because some other cause.
Related
Was using LiveServer no problem for quite some time, suddenly I go and refresh the page and it changes /index.html to /undefined. Nothing I do fixes it, if I erase the /undefined, it displays the proper page for a split second then returns to /undefined.
I have attempted to uninstall & restart VSCode then reinstall, unsure what to do from here.
Turns out you cannot use certain words in your JS code or it will ruin it.
Hello i've some trouble about windows managing with Watir gem in Ruby.
I've working with watir '6.2.1' until I finished to write my program, and I always got an error that is "Element is not clickable at point (x, y)..." never at the same location, whereas really nothing was on the button that i want to focus.
In this case, i just needed to update watir to don't have this error again.
I think that this error was resolved, but i've the same error, that I already had, when i want to click exactly in the same location as before.
Before i've update watir to the last update, i used
browser.window.resize_to(1366, 786), it's worked and i did not have the error anymore.
Now, it's not working. My window does not resize anymore.. When i put back the old version, it's the same issue.
I'm sorry about my bad english, i hope that you understand what i want to explain.
Most likely you need to update your chromedriver. I get bit by that every so often because the browser will update automatically and without alerting you to that fact.. So it's not uncommon to have the browser get 'ahead' of chromedriver and things stop working or start working in strange weird ways until you realize what is going on and update chromedriver.
n00b here. After searching the forums I have not yet come across this problem as I am experiencing it.
I have a CI site that was working correctly until about three days ago. My problem is as follows:
On button click - Page Loads correctly.
On Enter press - CI Blank Page of Death loads.
For example: When I login, after the login process has run it must reroute me to the Dashboard, unless I still have a temporary password where I get rerouted to the "Change Password" screen first and then to the Dashboard.
AS LONG AS I USE THE BUTTONS AND CLICK THEM EVERYTHING WORKS.
On ENTER PRESS, I get the Blank Screen of Death.
However, on TAB to BUTTON and then ENTER it works.
The problem is not consistent however. I have some processes that do not have views attached and NONE of them will run - hit ENTER and get blank. They are all failing on ENTER PRESS.
I am slowly going off my trolley. Logging is ON, Directories for cache and logs are 775. NOTHING is showing in my logs...
First Try to active error handlers for displaying of errors for addittional info to post here what error is occuring..
// change settings for error handler to show errors
// $this setup is used for checking errors for development to be shown....
ini_set('display_errors', 1);
error_reporting(E_ALL);
by the way if your using CI version 2 higher
you can see it in its index.php file an configuration for displaying error also.
define('ENVIRONMENT', 'development'); //just set up environtment to development
Even though there are accepted answers I wanted to add a way that worked for me to figure out this problem.
Usually the "Blank Page" indicates a PHP parsing error somewhere in the code. Strange thing for me was that on my local MAMP based test server the code ran fine. I FTP it to my hosted server and all of a sudden, blank page of death.
Even though I had errors on, log errors on, display errors on, nothing appears in any log file.
I was able to find the error by a funny little trick. I added an echo line in CodeIgniter.php in the system/core. Obviously hacking the core was not a great idea but all I wanted to do was to see how far it was getting in the load process.
When my echo appeared after trying to load a page on the remote hosted server it also displayed the parsing problem in a derived controller! Not sure why the error did not come out without the "echo" added. But adding it seemed to trigger some output to be generated, IE my echo line and the PHP parse error was appended.
Not sure if this will help anyone but it turned out to be a nice easy way to find the error which only showed on the remote server.
Obviously, don't forget to put your core file back to its original state without the echo.
This was fixed by copying the application into a fresh CI 2.3 install.
I have no idea what actually caused this "erratic" behaviour.
The application worked correctly as designed whenever a BUTTON was CLICKED but gave the blank death screen when ENTER was PRESSED.
This inconsistent behaviour is what threw me. The fact that my logs (CI and APACHE) also showed nothing was also very strange. Had this been a parse error, surely the behaviour on "Click" and on "Enter Press" should have been the same.
My non-view controllers for various ad-hoc admin jobs are now also working correctly, which they were not before, as they use "Enter Press" (having no buttons to "Click").
I am still going to invite best guesses as to why this behaviour occurred the way it did.
Surely someone out there (Phil Sturgeon et al) with extensive CI experience has encountered this non-consistent blank screen behaviour and knows what caused it.
Thank you to all the people who took the time and effort to assist me!!!
Big UP!!! StackOverflow!!!
probably error in INCLUDE login.php
My problem was Apache stop working because of ...Skype! Skype actually work on the same 443 and Apache didn't start! I hate this Skype! Bring me nuts for a while.
Installing php5-pgsql worked for me
I have shared hosting with hostgator and until about a month ago, things were dandy. Now.. every 2 to 3 minutes, I'll click a link and the browser won't resolve for about a full minute. This is any of my sites.. and links that are both database calls or very simply html hyperlinks. It's with any browser and at work or home.
I've opened 2 tickets with hostgator and they swear all their tests show that there are no problems, but.. I get this over and over and over again.. and have for weeks now.
Is there any kind of error outputting I could do.. or tools of any kind that would allow me to troubleshoot this myself?
Not sure about other browsers, but Google Chrome has a tool to measure the time a website took to load. Click the wrench icon in the top right, then go to Tools -> Developer Tools. Then you will see a new section at the bottom of the screen. Click the Network tab and it will show you a lot of data about the latency etc. It will also show you which file is the one that is taking the longest. Hope this helps.
From a console on the server itself, use the wget command to pull a page. Do it periodically in a script, logging to a file. Put it in cron. That'll show you if there are any lag issues with the server itself. If that looks good, then it's somewhere in the network. You could do a similar test from another box on another provider, which if comes up clean, points to your ISP or DNS as the culprit.
I am using a dedicated test SL web application that hosts SL object I am debugging.
I am debugging using basic F5 and use browser Google Chrome. Sometimes a bug happens, how I reproduce it.
I was running build->debug like 100 times already, but then I made a mistake that caused StackOverflowException and happened in main page constructor and afterwards when I rebuild and hit F5 it says no symbols have been loaded. Note that NOTHING has changed , I use the same 2 buttons combinations rebuild solution-> start debugging.
In order for debug to continue to attach I need to close XAML main page , open it again (in visual stuido) and hit rebuild ->f5 again, afterwards it works fine. (found this solution after SOME time)
I am not sure whats bugged but it appears to be a bug somewhere in SL to me.
Question is - whats going on maybe someone can explain.
This sounds more like Chrome's isolation mode for plug-ins. Generally speaking it's best to manually attach to the Chrome process that is running Silverlight (which isn't always one VS attaches to when pressing F5).
Actually error was super simple, I wasn't understanding how "exactly" xap works, it was a little more magical to me than it is. I just needed to rebuild & clear cache in browser ( chrome in this case) to attach successfully. For some reason I thought that local version doesn't require clear cache call.
Actually chrome is pretty bad to debug silverlight so I recommend IE for this sole purpose, sometimes debugger simply fails to attach to chrome, in that case you usually need to do this by attach to process - choose chrome with silverlight name there.