i haven't had this problem using slim or anything else before.
When I do a change in my IDE, and then reload the page, the change is not always instantly visible. That is, i have to wait a couple seconds, then try again.
How comes? is there a way i get force this process quicker?
I am not sure but maybe it's this:
in intellij-idea there is an option "preserve timestamp" in settings - deployment - options. Maybe that fools laravel into thinking the files didn't actually change
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.
i have a solution
it has 2 projects inside.
there are an exe and a website.
the issue occurred when clicking F5 to start the debug process.
when i have set the exe to the default StartUp project. The exe can run normally, and the break point can be reached correctly.
however, when i have set the website to the defualt StartUp project. The website can be launched, however the breakpoint cannot reach. also the version isn't the latest one, it looks like it is loading the last succeed version (no error and warning too)
I have to right click the website project and click start new instance in the Debug every time I have modified something!(which is very troublesome)
Thus, I want to know why my F5 isn't equal to the Start new instance, as it is working normally in the other solutions.
I fixed that but the below procedures after struggled from extra many clicks compiling experience.
the cause is that there is unknown reason that the build checkbox isn't checked in the configuration manager. simply check it and everything looks fine again...
hopefully it can save someone time who suffered from this issue in the future
I've installed the TYPO3 from scratch on an empty DB.
Everything worked fine until I reached the point where you have to create your first Backend user.
Well, I filled in the form and clicked "continue". Then, the page reloaded and nothing happened. Checking the DB showed me that the Backend user has been created, so I left the Install Tool and accessed the Backend via "domain.com/typo3". Logging in worked fine, as well.
But now, when I try to access the Install Tool in the BE (via the tab on the sidebar), it still wants me to create my first BE user. The installation process stays permanently on 80%.
I'm looking for a method to trick T3 to think that the installation process is finished, because it actually is.
The only thing I did differently than usually was to click on "Continue, I know what I'm doing" in the first step. T3 complained about the always_populate_raw_post_data=-1 and I created a php.ini in the root directory to fix that and continued without checking because I thought it'd fix the problem.
Thanks!
You can check this setting in your LocalConfiguration.php:
$GLOBALS['TYPO3_CONF_VARS']['SYS']['isInitialInstallationInProgress']
You have to set it to false.
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
Is there any way to prevent start/load of DevExpress and/or Vissual assist?
Even if disabling it's up'n running the next time.
When using a limited cpu larger projects sometimes freezes everything for a bunch of minutes each time you forget to disable (and seems like I forget it each time).
Tried both out and one of them could be a nice contribute, if disabled by default.
I cannot tell you about VAssist, but automatic loading of CodeRush is controlled by the DevExpress--> Options-->Core-->Startup-->Load manually option.
I couldn't find the Startup option under Core; till I changed the Level to Expert from New User
To load it up again, you can go to Tools->Load DevExpress.
To bring up the options page, do Ctrl+Alt+Shift+O and change it to expert mode in bottom left pane.