DDEV is the official local development tool of Drupal. And like Drupal, DDEV depends on the support of the open source community.
By urlookinhappy on
Dear communty,
I am running two websites on drupal 7 with php 5.6, and when I switched to the next higher php or to even more higher versions, a white blank screen appear. Both sites react the same.
1.) Could the problem be caused due to the fact that for switching a couple of months ago from 5.3 to 5.6, I had to delete the "node export" modul of both sites - I don't think so, does it? -
2.) When I repeat the same error next time and look into the server error-log-file, will the error message indicate exactly where the problem comes from? How would the error message look like if it refers to the switch to a higher php-version ( an example )
3.) Can I post here the error message in order to find a solution?
4.) What kind of problem could it be? anyone had the same problem before and found a solution?
Interestingly, for other sites that run also drupal 7 I had no problem at all and could switch them directly from 5.3 directly to 7.4.
For your support and replies many thanx and best regards,
urlookinhappy
Comments
=-=
1) node export - tough to know what the issue was. In future please provide versions of modules so that research can be performed. ensure the two sites that have issues are fully updated (including all contrib modules).
2) Depends on the error. PHP does deprecate functions so a deprecated function error could be due to the change in PHP version.
3) If the error output is extensive you can place it on https://pastebin.com/ and drop a link to it in your post/comment.
4) Unanswerable at this point.
Thanks VM,
Thanks VM,
updates a done so far.
deleted "node export" is not involved?
Is it normal that the blank white screen appears instead of indication of error? does this indicate a heavier problem or a less important problem?
What if I do not get a extensive error code, should I contact the hoster and provider - they should have detailed information for which I have the right to get it?
=-=
If the node export module is deleted its code can't run. That said, I assume you performed the uninstall properly and not simply deleted the folder from the file system leaving the module enabled and configuration in the database.
Review documentation for Drupal WSOD. this can occur if the code is dying before it gets to drupal error message functions. Yes it's common but your PHP error logs should be capturing the errors. Using the doc mentioned you can sometimes get the error to print to the screen.
If the error output isn't extensive (very long) you can post directly in your posts/comments. Hosting support won't help with CMS issues / code issues etc.
1.)"node export" I simply
1.)"node export" I simply deleted the folder for both websites - not more - The problem disappeard and I could switch from 5,3 to 5,6. Should I do now something else now - it's 3 months ago -?
2.) Pls explain a little more in detail: Which doc should I use to get the error printed to the screen (maybe)? If it is WSOD, where do I have to log in, where do I find it? , and if I find it , what info should I look for? I am sorry for these questions.
=-=
1) that's not how modules are uninstalled. They should be disabled and uninstalled before the folder is deleted from the file system. Move the site back to an environment where they can be properly uninstalled.
2) You should read the linked doc in my comment so that I don't have to regurgitate what is already there.
Last question for today:
Last question for today:
1.) the uninstall issue cannot be the problem, can it? I checked and I see that I disabled it, furthermore, as far as I remember my first try to switch to a higher version ( I went directly to 7.4) was doen before I deleted "node export module"
2.) I visited the website of your link, but you told me that I schould include the error code if it is long. So what exactly do I have to do to get the error code on the screen eventually?
=-=
1) disabled is not uninstalled and it is unlikely to cause an issue with a PHP upgrade but to avoid future issues it should be looked at further. I'm only mentioning it due to it being mentioned in your opening post. if you don't think it's relevant to anything then ......
2) Drupal WSOD link is what you should be reading in my comment @ https://www.drupal.org/forum/support/module-development-and-code-questio...
Thanx VM, sorry, was too
Thanx VM, sorry, was too unconcetrated while talking to you - I landed on the moom and have found the link with the codes for index.php etc. Will include them asap and place them here.
But I don't get it, I received error codes on the screen when I switched the first time. Screen showed "node export module-error" How could the screen error reporting have been automatically deactivated? So if it was deactivated for what ever reasons, I should have not received the first error message on the sreen. Don't you see this too?
=-=
nothing is deactivated. Sometimes PHP or Apache can die before the errors get to the screen which I've already stated. You don't need to have the errors print to the screen if you can get them from the logs. You haven't stated whether you can or can't. The fact that errors aren't printed on the screen isn't an issue by itself.
You are asking questions that can't be resolved without more information related to the error output. One set of errors and how they are on screen may not have anything to do with secondary issues. Without the actual error output, all anyone can do is guess which is where your questions are coming from. So instead of guessing, get the output of the logs (in one way or another).
To see errors printed on the
To see errors printed on the screen, navigate to: Administration » Configuration » Development » Logging and errors and select "All messages, with backtrace information". Click "Save configuration".
Do this on your development/testing site. You don't want error messages exposed to the public on a production site.
- gisle