Most of this stuff is a bit over my head. I'm mostly deal with HTML and CSS. I tried updating from 7 something to 7.27. I now get the following when I enter my url:
Warning: require_once(/home/content/12/10104912/html/includes/common.inc) [function.require-once]: failed to open stream: No such file or directory in /home/content/12/10104912/html/includes/errors.inc on line 62
Fatal error: require_once() [function.require]: Failed opening required '/home/content/12/10104912/html/includes/common.inc' (include_path='.:/usr/local/php5_3/lib/php') in /home/content/12/10104912/html/includes/errors.inc on line 62
Here is line 61-63 from errors.inc
if (!function_exists('filter_xss_admin')) {
require_once DRUPAL_ROOT . '/includes/common.inc';
}
Comments
I also have exactly the same error D7.26 to D7.27
Warning: require_once(/home/content/*./.*/html/includes/common.inc) [function.require-once]: failed to open stream: No such file or directory in /home/content/31/9592031/html/includes/errors.inc on line 62
Fatal error: require_once() [function.require]: Failed opening required '/home/content/*./.*/html/includes/common.inc' (include_path='.:/usr/local/php5_3/lib/php') in /home/content/*./.*/html/includes/errors.inc on line 62
Will I loose all the data?
Can you provide the steps
Can you provide the steps that you follow to upgrade Drupal Core ?
Did you read UPGRADE.txt in the Drupal installation ?
- Darryl Norris
Be Connected: Website | Twitter | LinkendIn | GitHub
I copied the files over from
I ended up reinstalling Drupal and tried to do the update again trying very carefully to follow the instructions.
1. Log in as a user with the permission "Administer software updates".
2. Go to Administration > Configuration > Development > Maintenance mode.
Enable the "Put site into maintenance mode" checkbox and save the
configuration.
3. Remove all old core files and directories, except for the 'sites' directory
and any custom files you added elsewhere.
(I did this in Dreamweaver)
- Make a backup copy of your settings.php file, with a different file name.
- Make a copy of the new default.settings.php file, and name the copy
settings.php (overwriting your previous settings.php file).
- Copy the custom and site-specific entries from the backup you made into the
new settings.php file. You will definitely need the lines giving the
database information, and you will also want to copy in any other
customizations you have added.
4. Download the latest Drupal 7.x release from http://drupal.org to a
directory outside of your web root. Extract the archive and copy the files
into your Drupal directory.
6. Run update.php by visiting http://www.example.com/update.php (replace
www.example.com with your domain name). This will update the core database
tables.
If you are unable to access update.php do the following:
- Open settings.php with a text editor.
- Find the line that says:
$update_free_access = FALSE;
- Change it into:
$update_free_access = TRUE;
- Once the upgrade is done, $update_free_access must be reverted to FALSE.
Same Issue
I am getting the same issue, when i looked i saw the server was deleting the file as soon as i uploaded it via ftp. Have you checked to see if the file exists?
solved
So after calling godaddy to say it was deleting they asked how i was uploading the file. i said filezilla. She said sometimes filezilla will say it uploaded a file but really filezilla thinks the file is corrupt so it does NOT upload the file. All i had to do was go to godaddy ftp client on their site and the file uploaded fine and i was able to move on.
Hope this helps.
Same issue here. But I'm
Same issue here. But I'm using Total Commander. I can't solve it yet. And I can't call the "award-winning support" tel. (480) 505-8877 becouse I'm hungarian. What is the international phone format of this number could somebody tell me please?
Prancz Ádám
Könyvelés, adótanácsadás, webdesign
Update: If you use their ****
Update: If you use their ****** ftp from admin tools you can upload it manualy. I can solve it with this...
Prancz Ádám
Könyvelés, adótanácsadás, webdesign
GoDaddy has apparently fixed
GoDaddy has apparently fixed the problem now.