Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
After removing the 7.39 Drupal files, other than the Sites folder and subfolders from my Cpanel and replacing these with the 7.41 Drupal core folders/files, my site is now white with this fatal error: Fatal error: Call to undefined function user_access() in /home/artlov5/public_html/testing/includes/menu.inc on line 3929.
Has anyone dealt with this issue or have a suggestion to correct it?
Thanks!
Comments
Comment #2
cilefen CreditAttribution: cilefen commentedIt seems like not all of the core files are present.
Comment #3
Skaione CreditAttribution: Skaione commentedRight on cilefen, I removed those 7.41 files and folders I had uploaded and then reuploaded a new Core 7.41 which seems to have worked
Comment #4
cilefen CreditAttribution: cilefen commentedComment #5
Skaione CreditAttribution: Skaione commentedSince updating the site to 7.41 I continue to receive black screens when I choose various options from the admin menu like Content - Add Content - Basic Page and am also unable to X out of windows like the Basic Page window. I've truncated (cleared) the dr_cache and removed and reuploaded the Drupal Core 7.41 to the file manager but this is not correcting the problems. Does anyone have any other solutions?
Comment #6
cilefen CreditAttribution: cilefen commented@Skaione Are there any PHP log errors associated with those blank screens? Is xdebug enabled?
Comment #7
Skaione CreditAttribution: Skaione commentedWhen I select an action now like Modules the screen grays out so I'm unable to take further actions. If I select Install New Module that white window will open up where I can upload a module but I'm unable to X out of it and if I select Modules again the whole screen will gray out. I was getting a PHP error that had something to do with the Cache_Rules. I do not believe the xdebug is enabled.
I'm wondering if it's a good idea to start from scratch with a new Drupal 8 site after November 19th? My goal is to create a multi vendor site using UberCart, I'm trying to find compatibility info for UberCart with Drupal 8, what would you suggest?
Thanks
Comment #8
cilefen CreditAttribution: cilefen commentedAs for the PHP error, please post the current error. Also, check your browser's console and post any errors here too.
As for 7 vs 8 and UberCart, the core issue queue is not an ideal place for strategic suggestions and tips. Try asking in IRC in the #drupal or #drupal-support channels. Also, the Support forum and Drupal Answers on StackExchange can be helpful.
Comment #9
Skaione CreditAttribution: Skaione commentedHello cilefen,
I checked with my hosting provider and found that there are no PHP errors. They logged into my site and attempted to replicate the problem with the grayed out screens but they did not have any issues. So we did a PING check on my system, he found that my PING speed is about twice as fast as his. Have you ever heard of this type of issue? My internet connection PING speed is 96 ms or a little faster. Do you know what speed Drupal uses?
Thanks for your help
Comment #10
cilefen CreditAttribution: cilefen commented@Skaione I do not understand what you are asking in terms of ping speed. Have you got any console errors when you use the site?
Comment #11
Skaione CreditAttribution: Skaione commented@cilefen, I'm getting this error message on the homepage of my site; Notice: Undefined index: dasya in include() (line 4 of /home/artlov5/public_html/testing/modules/system/html.tpl.php).
Comment #12
cilefen CreditAttribution: cilefen commentedmodules/system/html.tpl.php has not got an
include
statement so I would double-check your drupal files are correct.Comment #13
webservant316 CreditAttribution: webservant316 commentedsame error observed here.
Comment #14
webservant316 CreditAttribution: webservant316 commentedComment #15
webservant316 CreditAttribution: webservant316 commentedok, in my use case this error was caused when running drush on a website that had bigger problems. manually restoring the website from backup fixed me up. no problem with the codebase only the database.