I have installed kloxo control panel, this is the address http://173.212.227.142:7778/. Then I made domain for my test site, which shows me preview from this link, http://173.212.227.142:7778/sitepreview/kids.com/index.html, which is right.
Now I have installed drupal but it is very hard for me to set here. I have made changes in configuration file like database, and in base_url. But didnot getting the site and it shows me a blank page.Site should come with this address, http://173.212.227.142:7778/sitepreview/kids.com/kids/index.php. I made the base_url as http://173.212.227.142:7778/sitepreview/kids.com/kids.
Please suggest me the solution.
Thanks
If you have a problem in your settings.php file, Drupal won't be able to connect to the database but will show you a page telling you such. The White Screen of Death means there is some kind of php error. It is difficult to know what kind of error from your description. Look in your error logs for php errors and tell us what you see, and it will be easier to help you out.
The white page could be the result of a php error, possibly due to a configuration/setting oversight. You should check your Webservers error log(s) for this, as they might give you some hints on possible causes.
Read this: http://drupal.org/node/158043
Related
I am getting following error on a new website created on IIS. I am able to see URL Rewrite deployed on this IIS instance. But the new website is not configured to use it. Please find the screen shot of the error message also attached. I searched across numerous forums and no find. I vaguely remember somehow fixed this issue previously, may be 1 year back or so . Since there is no log of the solution traced anywhere, I am in the same bad situation once gain. Please help me if anybody solved this kind of problem.
Thanks in advance
Praveen
Finally I was able to make out what is going wrong. IIS is adding dependency on URLScan by default when a new website is created, but not sure why. I was able to see this in ISAPI Filters (Please refer attached screen shot). Everything worked fine once I removed URLScan from ISAPI filters.
I am currently building a website using drupal 7.x. Unfortunately I cannot seem to enter the admin/config page. Every time I click on the configuration tab on the administration menu, I only get a blank page. Then I created another sample site. It also has the same problem and I am using WAMP server. I cleared cache and finds no difference. I have searched for similar issues, but could find none. Can someone please tell me what I am doing wrong?
A number of things can cause the White Screen of Death, but the most common things to check:
As suggested above, memory limit may need to be increased.
Have you enabled any modules other than those in Drupal core? Try disabling contributed modules and enable individually until you experience the error, to help you identify which module is causing trouble. If you can't access the modules admin page, you can disable them in the database - the system table has a 'status' field. 1 means enable, 0 is disabled.
Could it be a permissions issue? Check admin access permissions or try logging in as the superuser (user ID 1).
Lots more and discussion here and here.
Finally I got the answer. Increase the max_execution_time in php.ini file. It solves the issue.
A few things to try...
Check your php error log for clues.
Create a simple file that calls phpinfo() and see what your memory_limit is. It may need to be increased.
Try tweaking your php.ini to get it to display an error message instead of a blank page.
I tracked this very issue to l10_update module, once I enable it, admin/config shows the WSOD. Once I disabled it, everything's fine. So:
- unchecking the localization_update module in the "modules" list
- de-installing it from the modules list
- deleting directory sites/all/modules/l10n_update
- and re-installing the module (from the same tar.gz file)
Source: https://www.drupal.org/node/1141160
A site have run ok for some time. But recently, when I upload a image, it is always raising this error:
An unrecoverable error occurred. This form was missing from the server cache. Try reloading the page and submitting again.
The first time i uploaded the image is ok. but when I create the second article and upload a image, it shows the above error. And the upload button disappeared.
Does anyone konw how to correct it and what's the reason of this error emergence ?
Apparently the problem is not Drupal. Most likely a setting on the server. If you use hosting services. please contact support, they may be something advise. Also recommend looking into the FAQ page the module loads the image coordinates.
Also, to test this problem, try to move the website to your local kompyuter and test does not appear whether this problem. Good luck. And update all the modules before actual sosoyaniya. Poeksprimentiruyte module load module dev.
Some other users have had the same sort of issue. See this thread on Drupal.org and this question at Drupal Answers.
Try to disabling caching under admin/settings/performance and set minimum lifetime to none. Also try clearing the caches on your site and in your browser and try again.
The problem is in cache_get() function inside includes/cache.inc file.
At line no. 42, there is a check :
if (isset($user->cache) && $user->cache > $cache->created)
Time of user cache, is always coming as bigger than cache's creation time. That is why, this function returning zero and file is not uploaded.
However I could not find the solution yet.
Our website keeps logging a "page not found" error under the Drupal Recent Log Entries, but we do not know where it is coming from. When clicking into the detail of the error, the location is marked as "http:///*", user is "Guest", and severity is "warning". Does anybody have ideas on where we can find out what's causing these errors to log?
Page not found warnings like this can be caused every kind of code that triggers an http request, like loading a .js or .css file or an image. A way to debug this is the quick-and-dirty method described by Lullabot which means that you add a debug_backtrace() at the point where the warning is registered (in your case probably the watchdog() function, see the comment by Randy Fay).
PS. #Arvind: If you're using the Drupal API correctly, there shouldn't be too many drupal_goto calls in your code.
do you have atypo error in your code? check if you have mistakenly commented coz i see /* in the link.
This has to be a local error. I would check for my drupal_goto calls in my code.
this is my guess and i'm no drupal expert. let us know if it helps.
atb!
You might have an issue with your favicon like I did, although I don't recalling it generating errors in my watchdog.
It's what triggered a lot of page not founds on my setup.
Basically, you normally put your favicon in your root. However, some browsers ( I believe IE6 ) , don't check the root for your favicon, but your theme folder.
I just duplicated my favicon in my theme folder, and my problem was solved.
Worth a try.
Please see my DNN Forum Post for more details.
I've never had any issues with DotNetNuke installations. But with the new v5.20 (or v5.02, whichever it really is), everything runs perfectly fine through installation. I then get to the main default portal homepage. But as soon as I click any of the links available to continue (Home, Register or Login) I get 404 errors every time with a reference back to the applicable aspx page (Home.aspx, Register.aspx or Login.aspx.).
Windows 7, IIS7, SQL Server 2008. All permissions are setup properly on the directory and in IIS. I would think this is an IIS7 configuration issue, but I've tweaked everything in there a half-dozen times. No one at DNN is returning answers on my forum post anymore either after one guy tried.
Help!
This is something to do with the Friendly URL stuff. I found this blog post which talks about the Friendly URL Provider architecture. This made me try changing the urlFormat attribute for the DNNFriendlyUrl provider from "humanfriendly" to "searchfriendly", which made the URLs the way they used to be. I'm not sure exactly where things are going wrong and don't really have time to dig into it at the moment, but hopefully this will be helpful to get you moving again too.
With the release of DNN5 (up until 5.02.01 as of the time of writing), the friendly URL provider won't work when DotNetNuke is not on default port 80. There are different solutions floating around, but the simplest is just to replace the DNN friendly URL provider with the free one from iFinity. The installation is really simple and included in the download. Or see the following blog post:
http://www.sailer.com.au/dotnetnuke/dnn5-friendlyurl-port
Okay have you tried the 'old style' of login - domain.com/default.aspx?ctl=login
If that still doesnt work then i have to say that most likely something has happened to IIS - if so then you might just see if you can install the package you have on a different box or have a friend try a different box
I have done 2 upgrades with 5.2 and a few test installs with the Starter Kit Package and Install packages and have never seen this problem - not to say that it doesnt exist.
My next trial would be to go and redownload the install package from CodePlex and start from scratch to see if you can make the same thing happen again.
OKayone thing I dont think that has been mentioned in reading through everything is double check IIS.
My first guess without looking on your server would be to check if something happened to the 'check file exists' setting - i know this is changed in IIS7 so I cant point to the exact place to check this.
Here is a link to the IIS7 forums on it - http://forums.iis.net/t/1092696.aspx
http://forums.asp.net/t/1191083.aspx
either one might help - google also has a lot on this
Tell me how this goes in checking up on it and we can move forward from there!
you probably need to reg_iis on the version(s) of asp.net that your IIS is going to support.
http://msdn.microsoft.com/en-us/library/k6h9cz8h(VS.80).aspx
If the right version is not set up then you will get the 404 error
So placing it under port 80 works, right?
Is there a good reason not putting it under that port?