I found this issue with a fresh install of Drupal 11.0.4 running PHP 8.3.8.
When the "Sender name" and/or "Subject" input field(s) are disabled under "Manage Form Display," an error is triggered after submitting a custom Contact form (core module).
Thank you to everyone who's working towards core solutions.
-------- Begin ERROR ---------------------
The website encountered an unexpected error. Try again later.
TypeError: Drupal\Component\Utility\Html::escape(): Argument #1 ($text) must be of type string, null given, called in /chroot/home/plhscentenial/plhs100.com/html/core/lib/Drupal/Component/Render/FormattableMarkup.php on line 256 in Drupal\Component\Utility\Html::escape() (line 431 of core/lib/Drupal/Component/Utility/Html.php).
Drupal\Component\Render\FormattableMarkup::placeholderEscape() (Line: 205)
Drupal\Component\Render\FormattableMarkup::placeholderFormat() (Line: 195)
Drupal\Core\StringTranslation\TranslatableMarkup->render() (Line: 15)
Drupal\Core\StringTranslation\TranslatableMarkup->__toString() (Line: 142)
contact_mail()
call_user_func_array() (Line: 407)
Drupal\Core\Extension\ModuleHandler->invoke() (Line: 273)
Drupal\Core\Mail\MailManager->doMail() (Line: 181)
Drupal\Core\Mail\MailManager->Drupal\Core\Mail\{closure}() (Line: 593)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 180)
Drupal\Core\Mail\MailManager->mail() (Line: 114)
Drupal\contact\MailHandler->sendMailMessages() (Line: 223)
Drupal\contact\MessageForm->save()
call_user_func_array() (Line: 105)
Drupal\Core\Form\FormSubmitter->executeSubmitHandlers() (Line: 43)
Drupal\Core\Form\FormSubmitter->doSubmitForm() (Line: 589)
Drupal\Core\Form\FormBuilder->processForm() (Line: 321)
Drupal\Core\Form\FormBuilder->buildForm() (Line: 48)
Drupal\Core\Entity\EntityFormBuilder->getForm() (Line: 92)
Drupal\contact_storage\ContactFormViewBuilder->view() (Line: 45)
Drupal\contact_storage\Controller\ContactStorageController->contactSitePage()
call_user_func_array() (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 593)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 121)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 183)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 53)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle() (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 709)
Drupal\Core\DrupalKernel->handle() (Line: 19)
------------ End ERROR ----------------
Additional gripe: collecting the first and last names separately for later use as Dear [first_name] is common. Collecting the full sender name as a single input is not required. Additionally, being unable to alter the label of the default "Sender email" within the "Manage fields" display is not ideal, as most people are used to seeing "Email Address" as the label.
Related Issue: https://www.drupal.org/project/drupal/issues/2753253 →
Regarding sending as HTML under "Contact settings", there are instructions that we need to use Swiftmailer, which is the only module Drupal has tested. However, if a person visits the Swiftmailer module project page, they will find that the module is not supported due to a security issue.
https://www.drupal.org/sa-contrib-2024-006 →
I realize I'm describing a few issues here and that they should be addressed separately. My apologies. However, with the issue queues showing little to no activity or progress towards solutions on Contact form specific problems, I feel it's good to list these issues here in the hopes that someone can escalate the need for attention regarding a most basic yet complex feature of the Internet (contact forms).
You're welcome
+1 and willing to co-sponsor development if anyone else is interested in picking this back up.
Hello all, I've read through this thread and I'm looking for some guidance with an update issue from 10.2.7 > 10.3.1 in which I'm receiving the following (possibly) related error... in which I'm seeking a direction as Google search results have not been too helpful. TR pointed me to this thread (Ref: https://www.drupal.org/project/typed_data/issues/3464120#comment-15701671 💬 Error: Class name must be a valid object or a string Postponed: needs info ). Thank you in advance for any assistance any of you may be able to contribute.
An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /update.php/start?id=383&op=do_nojs&op=do
StatusText: parsererror
ResponseText: Error: Class name must be a valid object or a string in Drupal\Core\TypedData\TypedDataManager->createInstance() (line 99 of /chroot/home/oceanbe1/oceanbeachsandiego-rv1.com/html/core/lib/Drupal/Core/TypedData/TypedDataManager.php).
-----------------------
Drupal database update
Error message
Warning: Undefined array key 1 in Drupal\system\Controller\DbUpdateController->results() (line 432 of core/modules/system/src/Controller/DbUpdateController.php).
The update process was aborted prematurely while running update # in system_post_update_add_langcode_to_all_translatable_config.module. All errors have been logged. You may need to check the watchdog database table manually.
The following updates returned messages:
system module
Update add_langcode_to_all_translatable_config
Processed 550 items of 876.
-----------------------
Error: Class name must be a valid object or a string in Drupal\Core\TypedData\TypedDataManager->createInstance() (line 99 of /html/core/lib/Drupal/Core/TypedData/TypedDataManager.php)
#0 /html/core/lib/Drupal/Core/TypedData/TypedDataManager.php(108): Drupal\Core\TypedData\TypedDataManager->createInstance()
#1 /html/core/lib/Drupal/Core/Config/Schema/ArrayElement.php(155): Drupal\Core\TypedData\TypedDataManager->create()
#2 /html/core/lib/Drupal/Core/Config/Schema/ArrayElement.php(57): Drupal\Core\Config\Schema\ArrayElement->createElement()
#3 /html/core/lib/Drupal/Core/Config/Schema/ArrayElement.php(104): Drupal\Core\Config\Schema\ArrayElement->parse()
#4 /html/core/lib/Drupal/Core/Config/Schema/ArrayElement.php(138): Drupal\Core\Config\Schema\ArrayElement->getElements()
#5 /html/core/lib/Drupal/Core/Config/Schema/ArrayElement.php(24): Drupal\Core\Config\Schema\ArrayElement->getIterator()
#6 /html/core/modules/system/system.post_update.php(270): Drupal\Core\Config\Schema\ArrayElement->hasTranslatableElements()
#7 /html/core/includes/update.inc(236): system_post_update_add_langcode_to_all_translatable_config()
#8 /html/core/includes/batch.inc(296): update_invoke_post_update()
#9 /html/core/includes/batch.inc(138): _batch_process()
#10 /html/core/includes/batch.inc(94): _batch_do()
#11 /html/core/modules/system/src/Controller/DbUpdateController.php(195): _batch_page()
#12 [internal function]: Drupal\system\Controller\DbUpdateController->handle()
#13 /html/core/lib/Drupal/Core/Update/UpdateKernel.php(115): call_user_func_array()
#14 /html/core/lib/Drupal/Core/Update/UpdateKernel.php(76): Drupal\Core\Update\UpdateKernel->handleRaw()
#15 /html/update.php(27): Drupal\Core\Update\UpdateKernel->handle()
#16 {main}
Thank you!
#14 and #18
Hi TR,
I'm admittedly grasping at straws.
I saw "TypedData" and Google sent me here.
I'm familiar with your work on Ubercart.
Please point me in a different direction and I'll go there.
- cheers
joshuautley → created an issue.
#75 Thank you!
I've been holding off dealing with this issue for a while now and finally got the energy to tackle it again. Once I isolated the error and Googled it, found this thread, and implemented the following with success!
composer require 'drupal/rules:^4.0' 'drupal/typed_data ^2.1'
vendor/bin/drush cache:rebuild
I see. I have done this manually on my own.
Thank you for writing the actual patch.
joshuautley → created an issue.
Same, I just saw that version 7 release. My guess is that API changes too frequently for it to be worth it. After review of apps in the QB app store and apps in the Shopify app store EVERYONE says run away.
Previous, "Ocean Beach MainStreet Association"
Current, "Ocean Beach MainStreet Association (dev site)"
No special characters to begin with. Just added (dev site) and hit save.
Holy crap, changing the site name worked for me as well.
joshuautley → created an issue.
Awesome, thank you.
joshuautley → created an issue.
joshuautley → created an issue.
Update: We are now on Drupal 10 and continuing with the transaction test and are still receiving the following error: "The credentials supplied in the authorization request are invalid."
Please advise.
I once worked with a great programmer in the late 90's / early 2000's who went by "Jello", his DJ name. When we worked on some DoD contracts I was doing a lot of ActionScript (Adobe Flash). I'd run to him with all these things and he'd stop me. He'd then say, start with one little thing, then once that's working move on to the next. Very valuable advice.
I've got everything working on this project now except keeping the emails out of the Spam/Junk folders. I've worked on some University projects in which I used Sendgrid and that worked great, but for this project, we're hoping to just use this site and now third-party services.
Thank you for the Mailpit tip, I've not heard of that resource before. I do not use DDEV either. I'm on a VPS as a one-man army helping out a friend on this one. I appreciate your help. So, far Simplenews is a great module and you've provided five-star support!
Well, it would help if I entered a first name for my admin account. Doh!
I just sent a test to five different emails and noticed that the emails sent to everyone other than my admin account worked just fine. Since the admin account already existed before I added the First Name field I had neglected to enter a value.
Here are the tokens that do work...
Account Name: [simplenews-subscriber:user:account-name]
Display Name: [simplenews-subscriber:user:display-name]
First Name: [simplenews-subscriber:user:field_first_name]
Text Value: [simplenews-subscriber:user:field_first_name:value]
This is the token that doesn't work... (which I don't need, I just threw it in there)
Corresponding user: [simplenews-subscriber:user]
So, this is not a bug and it works as designed.
Apologies.
Ressa, Thank you for looking into this.
joshuautley → created an issue. See original summary → .
I'm going to try Unsubscribe as discussed here here https://www.drupal.org/project/simplenews/issues/3194680 →
Let me know if this is still correct in version 4.
Thank you.
joshuautley → created an issue.
After some more experimentation, I think the synchronize method is now working. I may have needed to clear the cache.
As it is now when I use the Import from CSV module, I then use the mass subscribe option by pasting a comma-separated list of the email addresses from the user import CSV, and then after reviewing a couple of users I see that the default newsletter has been subscribed.
joshuautley → created an issue.
joshuautley → created an issue.
Disregard. ID10T < I hadn't enabled the module yet. LOL
Same here. And, yes I cleared the cache. This is a fresh D10 install via composer with a very minimum number of other modules.
joshuautley → created an issue.
Excellent, I will test it out. Thank for the update.
joshuautley → created an issue.
I found that if I require all modules in one go (just two in this instance) I can update to version 4.
composer require 'drupal/masonry' 'drupal/masonry_views'
Performing require on just Masonry, then the other doesn't work.
However, upgrades to D10 for the site running Masonry are still failing.
I think this has more to do with my capabilities with composer and my understanding of the .json file than it does with these modules.
My main gripe comes from a non-developer perspective and Drupal's lack of keeping up with other platforms as it relates to front-end presentation capabilities. Drupal is by far the best at SO much, but sometimes it is very difficult.
I do contribute to module development when my skill set aligns if at the very least I review the installation process and report on bugs.
You can close this as resolved.
joshuautley → created an issue.
Is this module abandoned?
Awesome, I'll apply the patch, test, then report back.
Thank you Damien!
Thank you, Damien! I've tested this on a couple of installs and your recommendation solved my issue.
+1
joshuautley → created an issue.
joshuautley → created an issue.
Awesome, thanks again. Much appreciated.
Thank you John
Got it. I'm a dork. I had an old version outside of the contrib directory. Deleted it and boom, all is good.
Update, having deleting the composer.lock file did NOT resolve this issue.
I had this occur on a second site and decided to delete the composer.lock file and run update.php which seems to have resolved the issue.
Is this just an issue with my composer -or- is there an issue in the update code for the module? Other modules did not require this step.
joshuautley → created an issue.
joshuautley → created an issue.
It took me quite some time, but after reviewing entries within the database the format for us must be Epoch time.
U Seconds since the Unix Epoch (January 1 1970 00:00:00 GMT) See also time()
As discussed here > https://www.php.net/manual/en/datetime.format.php
joshuautley → created an issue.
Lighting fast reply. Thank you for that solution.
joshuautley → created an issue.
@kristi-wachter, it's good to see a response to community concerns. In some instances, we're losing people to Shopify due to Drupal not having a stable solution for recurring payments.
I am available to review patches and provide feedback through dev sites.
Thank you for your contributions.
Excellent! Thank you.
Thank you both for your honesty.
@fchandler that seems to have worked for me as well. Thank you.
Any thoughts as to why mine locks to version 5.1.11?
@Mingsong, that's the same thing I did. I just have to declare the php version because some of my modules require that.
I ended up getting around the issue by downloading the .tar file, extracting it and replacing the files with the new version.
I also deleted my composer.lock file and ran composer update. During that, I noticed the lock file wrote in version 5.1.11
What version is declared in your lock file?
joshuautley → created an issue.
joshuautley → created an issue.
This error just popped up again with version 8.x-1.0 running on Drupal 9.5.5
#0 [path omitted]/modules/contrib/youtube_import/src/Form/YoutubeImportForm.php(35): youtube_import_get()
#1 [internal function]: Drupal\youtube_import\Form\YoutubeImportForm->buildForm()
#2 [path omitted]/core/lib/Drupal/Core/Form/FormBuilder.php(534): call_user_func_array()
#3 [path omitted]/core/lib/Drupal/Core/Form/FormBuilder.php(281): Drupal\Core\Form\FormBuilder->retrieveForm()
#4 [path omitted]/core/lib/Drupal/Core/Controller/FormController.php(73): Drupal\Core\Form\FormBuilder->buildForm()
#5 [internal function]: Drupal\Core\Controller\FormController->getContentResult()
#6 [path omitted]/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(123): call_user_func_array()
#7 [path omitted]/core/lib/Drupal/Core/Render/Renderer.php(580): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}()
#8 [path omitted]/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(124): Drupal\Core\Render\Renderer->executeInRenderContext()
#9 [path omitted]/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(97): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext()
#10 [path omitted]/vendor/symfony/http-kernel/HttpKernel.php(169): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}()
#11 [path omitted]/vendor/symfony/http-kernel/HttpKernel.php(81): Symfony\Component\HttpKernel\HttpKernel->handleRaw()
#12 [path omitted]/core/lib/Drupal/Core/StackMiddleware/Session.php(58): Symfony\Component\HttpKernel\HttpKernel->handle()
#13 [path omitted]/core/lib/Drupal/Core/StackMiddleware/KernelPreHandle.php(48): Drupal\Core\StackMiddleware\Session->handle()
#14 [path omitted]/core/modules/page_cache/src/StackMiddleware/PageCache.php(106): Drupal\Core\StackMiddleware\KernelPreHandle->handle()
#15 [path omitted]/core/modules/page_cache/src/StackMiddleware/PageCache.php(85): Drupal\page_cache\StackMiddleware\PageCache->pass()
#16 [path omitted]/core/modules/ban/src/BanMiddleware.php(50): Drupal\page_cache\StackMiddleware\PageCache->handle()
#17 [path omitted]/core/lib/Drupal/Core/StackMiddleware/ReverseProxyMiddleware.php(48): Drupal\ban\BanMiddleware->handle()
#18 [path omitted]/core/lib/Drupal/Core/StackMiddleware/NegotiationMiddleware.php(51): Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle()
#19 [path omitted]/vendor/stack/builder/src/Stack/StackedHttpKernel.php(23): Drupal\Core\StackMiddleware\NegotiationMiddleware->handle()
#20 [path omitted]/core/lib/Drupal/Core/DrupalKernel.php(718): Stack\StackedHttpKernel->handle()
#21 [path omitted]/index.php(19): Drupal\Core\DrupalKernel->handle()
#22 {main}
joshuautley → created an issue.
joshuautley → created an issue.
@Cottser Thank you
joshuautley → created an issue.
joshuautley → created an issue.
@rivimey #46 following up on this as it relates to commerce_recurring.
Has anyone used the patch in #41 successfully in this use case?
joshuautley → created an issue.
Problem/Motivation
Seeking to add recurring payments for memberships through integration with https://www.drupal.org/project/commerce_elavon → .
Should we still "Expect pain."?
I do not see any outstanding issues for this version.
@_gradient_ How much "pain" did you endure? I imagine it is relative to each individual's tolerance and experience.
joshuautley → created an issue.
joshuautley → created an issue.
You're welcome
As an observer, this is why I continue to push for our clients to adopt Drupal. The community of developers (and designers) are absolute rock stars. Here we are with module development going strong for version seven while version ten was just released. The continued support in our community is impressive. If any of you are ever in San Diego, reach out, and let's connect.
This issue has appeared again in version 8.x-1.0.
Per @slewazimuth #2 suggestion I tried to uninstall and reinstall with no luck.
Resolved by using...
joshuautley → created an issue.
joshuautley → created an issue.
joshuautley → created an issue.