Fatal error: Call to a member function setRecipients() on null in C:\xampp\htdocs\first\core\profiles\standard\standard.profile on line 24
plzz help me..i got this error after providing username email id and password info of the site

Comments

pawarbr13 created an issue. See original summary.

cilefen’s picture

Title: fatal error in xampp while drupal installation » Fatal error: Call to a member function setRecipients() on null in standard.profile
Component: browser system » other
Category: Support request » Bug report
Priority: Major » Normal
Issue tags: +XAMPP
Parent issue: #2223575: PHP Fatal error: Call to a member function get() on a non-object »
cilefen’s picture

Are there any other warnings or errors?

What is the version of XAMPP and what is the version of PHP on the site?

alexpott’s picture

The only way this could happen is if the contact form with the ID feedback does not exist... see standard_form_install_configure_submit().

How are you doing the install?

Turamarth’s picture

Same problem here > Fatal error: Call to a member function setRecipients() on null in C:\xampp\htdocs\Drupal\core\profiles\standard\standard.profile on line 24

XAMPP Version 5.6.21
PHP Version 5.6.21
Database Server version 10.1.13-MariaDB

Turamarth’s picture

Reviewed the OPCache config in php.ini, and change a few things to optimal performance and works now. check https://www.drupal.org/node/2623566 & http://php.net/manual/en/opcache.installation.php

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

greta_drupal’s picture

I'm using:
XAMPP v. 3.2.2
PHP 7
Windows 8

This XAMPP installation already includes the [opcache] section in PHP.ini file, as described in first comment here: https://www.drupal.org/node/2623566 (about configuring OPCache). But, you do have to enable it -- it is off by default, and add the zend_extension URL reference (see note below). For good measure, I increased limits for a few options in this subsection, per the other suggested OPCache configuration website. My steps to resolve:

1. Stopped Apache.

2. Modified and saved PHP.ini file

[opcache]
; Determines if Zend OPCache is enabled
opcache.enable=1

; Determines if Zend OPCache is enabled for the CLI version of PHP
opcache.enable_cli=1

; The OPcache shared memory storage size.
opcache.memory_consumption=128

; The amount of memory for interned strings in Mbytes.
opcache.interned_strings_buffer=8

; The maximum number of keys (scripts) in the OPcache hash table.
; Only numbers between 200 and 100000 are allowed.
opcache.max_accelerated_files=4000

...

; How often (in seconds) to check file timestamps for changes to the shared
; memory storage allocation. ("1" means validate once per second, but only
; once per request. "0" means always validate)
opcache.revalidate_freq=60

...

; If enabled, a fast shutdown sequence is used for the accelerated code
opcache.fast_shutdown=1

...

And, I added the zend_extension reference to the PHP.ini file [PHP] section -- important to add it in this section. I added it at the end of the "Paths and Directories" subsection of that PHP section:

;;;;;;;;;;;;;;;;;;;;;;;;;
; Paths and Directories ;
;;;;;;;;;;;;;;;;;;;;;;;;;

...

; Tyme added to resolve install issue
zend_extension = "C:\xampp\php\ext\php_opcache.dll"

;;;;;;;;;;;;;;;;
; File Uploads ;
;;;;;;;;;;;;;;;;

3. Restarted Apache.

NOTE: The ellipsis in the above represent unchanged code omitted for compactness.

greta_drupal’s picture

Related to this issue, it should be noted that during the (auto) installation process, Drupal merely recommends that OPCache be installed -- not require it. In that case, no user should get this error attempting to complete a Standard installation. #UI-UX-Fail

I have never used the 'auto' core install before, but decided to test it. It took 4 attempts to get a successful basic, Standard install! -- between this error and other necessary PHP.ini tweaks needed - not reported in install.txt file.

The install.txt file really should include the following recommendation:
1. Modify PHP.ini file thusly:
A. Increase memory to: memory_limit=256M
B. Increase execution time (at least on XAMPP) to: max_execution_time = 120
C. Modify for OPCache [ref to instructions *]

(Especially given that users coming from WordPress are use to a < 5 min install, with no required php.ini modifications.)

cilefen’s picture

Yeah, weird things can happen when memory is exhausted.

install.txt links to https://www.drupal.org/requirements and the PHP section of that page links to https://www.drupal.org/docs/7/system-requirements/php that includes some of these details. Both pages are editable and have discussion pages. I don't know the history here, but I assume the intent of install.txt is to keep things simple to alleviate maintenance (because install.txt is part of the codebase) and to offload fine details to drupal.org.

By the way, the opcache settings you posted in #8 are all commented-out.

greta_drupal’s picture

Yes, I get the idea of brevity in the install.txt file. But, it does include a few other "server tips", so these important roadblock ones seem appropriate. I mean, we are talking about basically a single sentence. ...As for the remarked out opcache settings: good catch; sure, they should be uncommented on the day. I'll edit my post. (My local, XAMPP install works with them commented or uncommented.)

badmintonalcala’s picture

I'll follow the https://www.drupal.org/docs/7/system-requirements/php
Adding the requested requirements por Drupal 8.

Almost everything it's fine.
I couldn't set up the opcache.file_cache_only
opcache.file_cache = true ; it's no value by default
;opcache.file_cache_only = true ;Raise HTTP 500 if active

Maybe it's something related to my hosting service. I don´t know.

The rest of the configuration i follow the recommendations.

Then, i can access start page.
(Note: a have a problem them,...
Redirects to external URLs are not allowed by default, use \Drupal\Core\Routing\TrustedRedirectResponse for it.
but that's another issue....)

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

sahu g’s picture

i also face same problem plz help me

sahu g’s picture

Fatal error: Call to a member function setRecipients() on null in C:\xampp\htdocs\library\core\profiles\standard\standard.profile on line 25

cilefen’s picture

Did the findings in #9 not help?

Neelanjana Das’s picture

i tried the comments #8 and #9. the problem is still not fixed.

Fatal error: Call to a member function setRecipients() on null in C:\xampp\htdocs\beckelectric8\core\profiles\standard\standard.profile on line 25.

This is what i keep getting

FreeXenon’s picture

Same problem.

I made changes from above and same error
I performed an install previously with no problems and now I am having the issue.
Very strange.

just installed Xampp on Win 10 with latest Drupal 8

FreeXenon’s picture

I just did a fresh install of XAMPP and D8 and only made the changes to the php.ini for max execution time and max memory

- D8 installed ok

it may be the opcache settings causing the issues for some reason. =O

anyone have an idea why?

cilefen’s picture

It is hard to say without knowing exactly the opcache settings configured, and the version of PHP.