I have a site in drupal it was working fine, suddenly it is not running.I am getting following
error message:
The file could not be created.
The file could not be created.
The website encountered an unexpected error. Please try again later.
If anyone has experienced a similar issue I'd love to know how you fixed it!
Thanks much in advance!
Related
I moved my codeigniter project from a microsoft azure server on to a new dedicated server. However I am getting nothing but issues. The site worked absolutely perfect on the azure server, none of the files have been changed or anything - but it just don't seem to work.
I first started getting errors saying that the Model can't be found, (i am still trying to fix this)
https://stackoverflow.com/posts/comments/103619729?noredirect=1
and now the latest error i get when going to a different page on my site i get
An uncaught Exception was encountered
Type: ParseError
Message: syntax error, unexpected ''
File: public_html/index.php
Line: 319
Function: require_once
I then looked at index.php and the line in question is :
require_once BASEPATH.'core/CodeIgniter.php';
any ideas what I can do to fix this? is it something to do with how my server is setup? do i need to change something in Apache?
Please help!
My SugarCRM is hosted at Microsoft Azure, suddenly I am getting this message:
This page contains the following errors:
error on line 2 at column 1: Document is empty
Below is a rendering of the page up to the first error.
A reboot does solve a problem, but I want to fix the core issue.
Please suggest. Reboot is fixing issue.
I'm attempting to troubleshoot a custom module I'm working on. The website seems to work fine with no noticeable or logged errors. When I enable Magento developer mode I get a white screen. This points towards PHP errors.
When I check my server error logs I'm getting the following error:
PHP Fatal error: Class 'Mage' not found in /var/www/index.php on line 41
I'm not exactly sure what to do? Googling hasn't seemed to help much. I'm only getting this error in developer mode.
What version of Magento that you are using? It seems your index.php has been changed.
The best way to debug this, you can:
Compare your files to the freshly downloaded Magento code.
Check index.php on line 41, if there's code calling 'Mage' class
Just FYI, if the code exists and you need it. You can move the code after this code (line 68 on Community 1.8.1)
require_once $mageFilename;
Hope this help.
Try by adding the following line inside index.php at the beginning file.
$_SERVER['MAGE_MODE'] = 'developer';
Hope you will see the error message.
In codeigniter i have started one property related project for my client.
I am getting an error
Fatal error: Class 'CI_Controller' not found in H:\php2\htdocs\property\system\core\CodeIgniter.php on line 233 after i have complete some development.
I have really search it for many time in google and in stackoverflow but still didn't get solved.
Thanks in advance,
Well, m not sure but i guess it can happen because of changes in database settings.
codeigniter sometimes show this very weird behaviour that giving this fatal error "CI_Controller" not found even there's nothing wrong with the core files.
so- try debugging like this-
1)check your database seetings located at config/database.php
2)If it does'nt works, re-uploading the system files.
I hope this helps.
Check your database config in application/config/database.php it's one of the major time consuming error message I faced with CI. Because the error message was simply misleading. So, check the database config first.
just copied my joomla site folder to godaddy domain and when i visit the home page i get this error
Fatal error: Call to a member function getDefault() on a non-object in /home/content/88/8216088/html/public_html/includes/router.php on line 123
any help ?
After some Googling, I've found a similar thread at http://forum.joomla.org/viewtopic.php?p=2441892. Since this sounds like a bug, I don't really think we will be able to solve it here.
The best thing you can do now is to try to help Joomla! developers with reporting the issue and following their instructions for debugging and solving it.