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

If you have arrived here from a search, please read the thread before commenting. The immediate cause seems to be a need to configure opcache.

Support from Acquia helps fund testing for Drupal Acquia logo

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.)

javier-franco’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.

karthiselvam.seeralan’s picture

Please help me I followed #8 & #9 and I am getting same error message

Thanks,
Karthiselvam Seeralan

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

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

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

santhosh_1795’s picture

IGNORE THAT ERROR GO TO YOUR LOCALHOST/DRUPAL_NAME AND ENTER
ITS WORKING...YOU CAN MAINTAIN YOUR WEBPAGE..
AFTER THAT YOU CHANGE YOUR EMAIL ID AND SITE EMAIL...
THANKS.

Prashant_kr_verma’s picture

FileSize
18.73 KB

Please help me I am getting

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

Thanks,
Prashant

hassengh’s picture

@greta_drupal
thanks for your post
the change in php.ini (under php ) and php.ini (under apache )

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

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

EnzoX’s picture

Same problem here with Drupal 8.4.4.
+ Windows 10 Home 64 bit
+ XAMPP Version 5.6.31
+ Apache 2.4.26
+ MariaDB 10.1.25
+ PHP 5.6.31 (VC11 X86 32bit thread safe) + PEAR

PHP Fatal error: Call to a member function setRecipients() on null in ****\\web\\core\\profiles\\standard\\standard.profile on line 25, referer: http://******/core/install.php?rewrite=ok&langcode=it&profile=standard&continue=1

cilefen’s picture

Issue summary: View changes
devu_divya’s picture

Error
The website encountered an unexpected error. Please try again later.
Error: Call to a member function setRecipients() on null in standard_form_install_configure_submit() (line 25 of core\profiles\standard\standard.profile).

standard_form_install_configure_submit(Array, Object)
call_user_func_array('standard_form_install_configure_submit', Array) (Line: 111)
Drupal\Core\Form\FormSubmitter->executeSubmitHandlers(Array, Object) (Line: 51)
Drupal\Core\Form\FormSubmitter->doSubmitForm(Array, Object) (Line: 585)
Drupal\Core\Form\FormBuilder->processForm('install_configure_form', Array, Object) (Line: 314)
Drupal\Core\Form\FormBuilder->buildForm('install_configure_form', Object) (Line: 899)
install_get_form('Drupal\Core\Installer\Form\SiteConfigureForm', Array) (Line: 593)
install_run_task(Array, Array) (Line: 549)
install_run_tasks(Array) (Line: 117)
install_drupal(Object) (Line: 44)

Getting this error while configuring my first site..kindly help

Senthil Kumar Kumaran’s picture

I solved this issue by commenting the below line from file core\profiles\standard\standard.profile (line no. 24) and refreshed the page during installation process. Drupal site had installed successfully. The issue might be because of unavailability of the feedback form which is provided by default as contact entity. Still i have not validated the root cause. I will come up with permanent solution through a patch or in a standard way shortly. Thanks.

Line to be commented during installation when you are facing the error,

ContactForm::load('feedback')->setRecipients([$site_mail])->trustData()->save();

After successful installation, i reverted back my changes. Please note that this is a hack of core and make sure to revert back the changes.

Senthil Kumar Kumaran’s picture

Yes! My assumption was right. There is no contact entity with the machine name "feedback". Only one contact entity is available by default on fresh Drupal setup which is "Personal contact form" with machine name as "personal" . Hence, the below is the fix for this issue.

File: core\profiles\standard\standard.profile

/**
 * Submission handler to sync the contact.form.feedback recipient.
 */
function standard_form_install_configure_submit($form, FormStateInterface $form_state) {
  $site_mail = $form_state->getValue('site_mail');
-  ContactForm::load('feedback')->setRecipients([$site_mail])->trustData()->save();
+  ContactForm::load('personal')->setRecipients([$site_mail])->trustData()->save();
}

Please validate and advise if i'm wrong. Thanks in advance.

Senthil Kumar Kumaran’s picture

Assigned: pawarbr13 » Unassigned
Status: Active » Needs review
sjerdo’s picture

Status: Needs review » Needs work

Actually the profile standard contains an install YAML file for the feedback contact form: contact.form.feedback.yml

After creating the feedback contact form, the recipient for the form should be set to the site mail.
The personal should not have the site mail as recipient, since this form is for contacting users.

Is the feedback Contact Form not yet available in standard_form_install_configure_submit?

bdupls’s picture

Thanks Senthil, #30 worked for me on Windows 10, Mamp Pro 4 D8 install.

kurinjiselvan v’s picture

Hi..

I am also faced this issue, please follow the steps to solve this issue. No need to change the File: core\profiles\standard\standard.profile

  1. Open the php.ini file
  2. Follow the comment #8 instructions
  3. Increase the max_execution_time = 120 in php.ini file
  4. Restart the Apache Server

Now you can start the drupal fresh installation process. Please delete the past drupal installation and start with fresh.

kurinjiselvan v’s picture

Status: Needs work » Needs review
Issue tags: +drupal installation issue
viraj7686’s picture

Changed below configurations during Drupal 8 setup:

Added:
$cfg['ExecTimeLimit'] = 6000; within "C:\xampp\phpMyAdmin\config.inc.php" file

Updated:
post_max_size=8M to post_max_size=750M (File: C:\xampp\php\php.ini)
max_execution_time=500 to max_execution_time=600 (File: C:\xampp\php\php.ini)
max_input_time=60 to max_input_time=5000 (File: C:\xampp\php\php.ini)
memory_limit=128M to memory_limit=100M (File: C:\xampp\php\php.ini)
max_allowed_packet = 1M to max_allowed_packet = 200M (File: C:\xampp\mysql\bin\my.ini)

Finally, I've comment out ContactForm::load('feedback')->setRecipients([$site_mail])->trustData()->save(); from the file "\core\profiles\standard\standard.profile" and it really worked while D8 in the final installation process (also mentioned in #30).

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

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

npcoder’s picture

I am using Drupal Version 8.6.7. I got same error stated above.
Thanks @Senthil Kumar Kumaran, your suggestion helped.

File: core\profiles\standard\standard.profile

/**
 * Submission handler to sync the contact.form.feedback recipient.
 */
function standard_form_install_configure_submit($form, FormStateInterface $form_state) {
  $site_mail = $form_state->getValue('site_mail');
-  ContactForm::load('feedback')->setRecipients([$site_mail])->trustData()->save();
+  ContactForm::load('personal')->setRecipients([$site_mail])->trustData()->save();
}
mas2405’s picture

Faced same issue as stated.
able to fix
Thanx @viraj7686 @Senthil Kumar Kumaran @greta_drupal

rahul_sankrit’s picture

Recommended php.ini settings:
The following settings are generally recommended as providing good performance:

opcache.memory_consumption=128
opcache.interned_strings_buffer=8
opcache.max_accelerated_files=4000
opcache.revalidate_freq=60
opcache.fast_shutdown=1
opcache.enable_cli=1

XAMPP comes with PHP OPCache we just need to enable it. To enable the extension:
1.Open the file with editor: c:\xampp\php\php.ini
2.Add those above lines after [opcache]
4. Open php.ini and Add to resolve drupal installation issue
zend_extension = "C:\xampp\php\ext\php_opcache.dll"
3.Re-Start Apache

Here is the sample code:

[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=0

; 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 1000000 are allowed.
opcache.max_accelerated_files=4000

; The maximum percentage of "wasted" memory until a restart is scheduled.
;opcache.max_wasted_percentage=5

; When this directive is enabled, the OPcache appends the current working
; directory to the script key, thus eliminating possible collisions between
; files with the same name (basename). Disabling the directive improves
; performance, but may break existing applications.
;opcache.use_cwd=1

; When disabled, you must reset the OPcache manually or restart the
; webserver for changes to the filesystem to take effect.
;opcache.validate_timestamps=1

; 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

; Enables or disables file search in include_path optimization
;opcache.revalidate_path=0

; If disabled, all PHPDoc comments are dropped from the code to reduce the
; size of the optimized code.
;opcache.save_comments=1

; Allow file existence override (file_exists, etc.) performance feature.
;opcache.enable_file_override=0

; A bitmask, where each bit enables or disables the appropriate OPcache
; passes
;opcache.optimization_level=0xffffffff

;opcache.inherited_hack=1
;opcache.dups_fix=0

; The location of the OPcache blacklist file (wildcards allowed).
; Each OPcache blacklist file is a text file that holds the names of files
; that should not be accelerated. The file format is to add each filename
; to a new line. The filename may be a full path or just a file prefix
; (i.e., /var/www/x  blacklists all the files and directories in /var/www
; that start with 'x'). Line starting with a ; are ignored (comments).
;opcache.blacklist_filename=

; Allows exclusion of large files from being cached. By default all files
; are cached.
;opcache.max_file_size=0

; Check the cache checksum each N requests.
; The default value of "0" means that the checks are disabled.
;opcache.consistency_checks=0

; How long to wait (in seconds) for a scheduled restart to begin if the cache
; is not being accessed.
;opcache.force_restart_timeout=180

; OPcache error_log file name. Empty string assumes "stderr".
;opcache.error_log=

; All OPcache errors go to the Web server log.
; By default, only fatal errors (level 0) or errors (level 1) are logged.
; You can also enable warnings (level 2), info messages (level 3) or
; debug messages (level 4).
;opcache.log_verbosity_level=1

; Preferred Shared Memory back-end. Leave empty and let the system decide.
;opcache.preferred_memory_model=

; Protect the shared memory from unexpected writing during script execution.
; Useful for internal debugging only.
;opcache.protect_memory=0

; Allows calling OPcache API functions only from PHP scripts which path is
; started from specified string. The default "" means no restriction
;opcache.restrict_api=

; Mapping base of shared memory segments (for Windows only). All the PHP
; processes have to map shared memory into the same address space. This
; directive allows to manually fix the "Unable to reattach to base address"
; errors.
;opcache.mmap_base=

; Enables and sets the second level cache directory.
; It should improve performance when SHM memory is full, at server restart or
; SHM reset. The default "" disables file based caching.
;opcache.file_cache=

; Enables or disables opcode caching in shared memory.
;opcache.file_cache_only=0

; Enables or disables checksum validation when script loaded from file cache.
;opcache.file_cache_consistency_checks=1

; Implies opcache.file_cache_only=1 for a certain process that failed to
; reattach to the shared memory (for Windows only). Explicitly enabled file
; cache is required.
;opcache.file_cache_fallback=1

; Enables or disables copying of PHP code (text segment) into HUGE PAGES.
; This should improve performance, but requires appropriate OS configuration.
;opcache.huge_code_pages=0

; Validate cached file permissions.
;opcache.validate_permission=0

; Prevent name collisions in chroot'ed environment.
;opcache.validate_root=0

; If specified, it produces opcode dumps for debugging different stages of
; optimizations.
;opcache.opt_debug_level=0

opcache.fast_shutdown=1
opcache.enable_cli=1
pagodzik’s picture

Answer #39 helped me, without comment any lines:
https://www.drupal.org/project/drupal/issues/2780071#comment-12940740

rwilson0429’s picture

If you are getting this error on install, I agree with the comment in #23. For now, ignore the error and just go to the site url and make whatever changes you need to make to site using the admin ui.

merauluka’s picture

Here is a patch that seems to resolve the issue for me. It adds an existence check around the feedback form. In standard installations, without custom config it should work just as before. But with custom config, such as when the feedback form was removed, it should no longer error out.

I wrote this against 8.7. But it should work for 8.6 also.

merauluka’s picture

fehin’s picture

@merauluka, thank you! Your patch worked.
For anyone who needs similar help, I applied the patch using the instruction on this page:https://groups.drupal.org/node/518975

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

TechCarlo’s picture

I have faced this issue just now, search the internet for possible solutions, and got here.
I don't want to edit my php.ini file or apply a patch so I decided to solve this myself.

I solve this by editing this file C:\xampp\htdocs\drupalroot1\drupal-testsite\core\profiles\standard\standard.profile
Removing the function which has an error
This is the code to be removed(just cut it to your clipboard CTRL+X) :


function standard_form_install_configure_submit($form, FormStateInterface $form_state) {
  $site_mail = $form_state->getValue('site_mail');
  ContactForm::load('feedback')->setRecipients([$site_mail])->trustData()->save();
}

after that, Reload the drupal intallation screen and voila, drupal is installed.
It will have and error though saying that standard_form_install_configure_submit function is missing. To fix that, put back the code we removed earlier back to the standard.profile file, save, reload the site, and error fixed.

samhaldia’s picture

Configuraing opcache as in #8 or follow https://www.php.net/manual/en/opcache.installation.php Reolved my issue

AmruthaKR’s picture

FileSize
43.69 KB

Hi Team,

I am getting below error after following #30 and #37

Please help me to resolve the issue

Apigee Developer Portal Kickstart 8.8.6Installation tasks
Choose language(done)
Verify requirements(done)
Set up database(done)
Install site(done)
Configure Apigee Edge(done)
Configure site(active)
Install demo content
Error
The website encountered an unexpected error. Please try again later.
Error: Call to a member function setRecipients() on null in apigee_devportal_kickstart_form_install_configure_submit() (line 48 of profiles\contrib\apigee_devportal_kickstart\apigee_devportal_kickstart.profile).
apigee_devportal_kickstart_form_install_configure_submit(Array, Object)
call_user_func_array('apigee_devportal_kickstart_form_install_configure_submit', Array) (Line: 114)
Drupal\Core\Form\FormSubmitter->executeSubmitHandlers(Array, Object) (Line: 52)
Drupal\Core\Form\FormSubmitter->doSubmitForm(Array, Object) (Line: 591)
Drupal\Core\Form\FormBuilder->processForm('install_configure_form', Array, Object) (Line: 320)
Drupal\Core\Form\FormBuilder->buildForm('Drupal\Core\Installer\Form\SiteConfigureForm', Object) (Line: 955)
install_get_form('Drupal\Core\Installer\Form\SiteConfigureForm', Array) (Line: 624)
install_run_task(Array, Array) (Line: 577)
install_run_tasks(Array, NULL) (Line: 117)
install_drupal(Object) (Line: 44)

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

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

sassafrass’s picture

@merauluka, thank you! Your patch worked.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
newswatch’s picture

I am surprised that the problem is still there.

I got this error today with D 9.3.7.

Thankfully #37 worked for me.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Status: Needs review » Postponed (maintainer needs more info)
Issue tags: +Needs issue summary update

This will need an issue summary update. Specifically what steps to reproduce

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)
Issue tags: -

Closing as outdated. If still an issue please reopen updating the issue summary with steps to reproduce.

Thanks!