I have the drupal 8 varbase distribution with the rules plugin installed.
(version Rules: 8.x-3.0-alpha4
Typed Data: 8.x-1.0-alpha1)
When I make a rule to send an email when a user changes his/her account, I get the following error:
The website encountered an unexpected error. Please try again later.
Recoverable fatal error: Object of class Drupal\user\Entity\User could not be converted to string in Drupal\Core\Mail\Plugin\Mail\PhpMail->format() (line 32 of core/lib/Drupal/Core/Mail/Plugin/Mail/PhpMail.php).
I use direct input data for all fields of the form, no data selectors. How can I fix this?
Updates to drupal solved the issue, this question can be deleted.
Related
I'm trying to set up an email to go to my custom domain name, which I will call "mydomainname". Currently I can send emails to "contact#mydomainname.com" and receive no error from sending the email, but the received email does not show up in my bucket or spam folder.
I've been following instructions on this github and this tutorial .
I don't understand what the github instructions mean for the instruction that states
"Modify the values in the config object at the top of index.js to specify the S3 bucket and object prefix for locating emails stored by SES. Also provide
the email forwarding mapping from original destinations to new destination."
I've tried to guess at what that means by changing the index.js file to the as shown here
I suspect there is an error in the code above,
As well, I receive the following error for the JSON in my lambda-basic-execution
And the error that I receive
.
.
.
I've included the following screenshots for reference
This is my recipient rule
This shows some information on the settings of my lambda page
The error you show is just a warning for the resource not existing, you should still be able to create the policy for the same.
See if you actually did create the policy and test it again.
Also make sure there are no invalid or duplicate rules which may be causing the issue
We experience the following problem: when we send an email via EXM, links inside the email body doesn't work for some users.
Links inside email body are always converted by default to something like:
http://domainname/sitecore/RedirectUrlPage.aspx?ec_contact_id=xxxx84B137D2037C7D180&ec_message_id=xxxxB4CEAA3FD1A3B&ec_url=%2fthelinkpath
that is obviously done for tracking reasons.
However, some users experience 404 error when navigate the link. The Log always says the following:
ERROR EmailCampaign: Object reference not set to an instance of an object.
Exception: System.NullReferenceException
Message: Object reference not set to an instance of an object.
Source: Sitecore.Analytics
at Sitecore.Analytics.Tracking.StandardSession.InitializePage(ICurrentPageContext currentPageContext, ICurrentPageContext oldPage)
at Sitecore.Analytics.Tracking.StandardSession.Identify(String userName)
at Sitecore.Modules.EmailCampaign.Core.Pipelines.RedirectUrl.IdentifyContact.Process(RedirectUrlPipelineArgs args)
at (Object , Object[] )
at Sitecore.Pipelines.CorePipeline.Run(PipelineArgs args)
at Sitecore.Modules.EmailCampaign.UI.RedirectUrlPage.HandleMessageEvent(ID messageId, ID contactId)
at Sitecore.Modules.EmailCampaign.UI.MessageEventPage.OnLoad(EventArgs e)
The only way to fix this error for the user is to clear his cookies or use another browser or use incognito mode. The user is currently logged out from the website.
Sitecore version 8.0 + EXM
Has anyone faced this problem before?
Indeed, this is because of cookies stored from previous sessions, thanks Tchami.
Sitecore Support answer was the same:
This error occurs when you open multiple mails with multiple
contactId's in the same browser.
But they didn't propose any solution except for clearing cookies or using another browser.
However, we don't want to break user experience even for this rarely appeared cases.
So, in order to handle the exception, we have found that the following pipeline processor should be rewritten:
<processor type ="Sitecore.Modules.EmailCampaign.Core.Pipelines.RedirectUrl.IdentifyContact, Sitecore.EmailCampaign" />
You can have a look at the code of custom processor here.
How do I get a registration code or otherwise solve this problem?
While writing this question, I realized the crux of this problem is the bottom-most part of this question: I'm not getting the popup I'm supposed to get and when I enter the URL in a browser it says invalid registration code.
I'm attempting to develop an Alexa Voice Service application. Website/companion service only. I have gone through the Reference Implementation Guide twice and have double checked that all of the setup has been done correctly.
This is the server error I get: invalid registration code. I never did anything with a registration code and can't seem to find anything about a registration code (relevant to Alexa) anywhere after googling quite a bit.
Listening on port 3000
error: { [InvalidRegistrationCode: The provided registration code was invalid.]
name: 'InvalidRegistrationCode',
message: 'The provided registration code was invalid.',
status: 401 }
Error: Can't set headers after they are sent.
Here's the client output:
vlcj: (DefaultMediaPlayer.java:183)
addMediaPlayerEventListener(listener=com.amazon.alexa.avs.AVSAudioPlayer$1#4b3a4950)
There was a problem connecting to the Companion Service. Trying again in 2 seconds. Please make sure it is up and running.
[DEBUG] joining on thread Thread[Timer-0,5,com.amazon.alexa.avs.AVSApp]
There was a problem connecting to the Companion Service.
Trying again in 2 seconds. Please make sure it is up and running.
The AVS launcher opens too, and when I record something and send it I get:
com.amazon.alexa.avs.AVSException: 403 Invalid Access Token
The instructions mention (at the very bottom of the reference guide) that I need to:
Please register your device by visiting the following website on any system and following the instructions: https://localhost:3000/provision/************** That URL is supposed to pop something up once the companion service but that hasn't happened.
Any thoughts on how can I fix this?
I was following a good document Project: Raspberry Pi + Alexa Voice Service at https://github.com/amzn/alexa-avs-raspberry-pi . It describes all steps very well.
Please take a look at the following steps:
3 - Getting started with Alexa Voice Service
3.1 Register for a free Amazon Developer Account
3.4 Register your product and create a security profile.
6 - Enable Security Profile
This thread on the Amazon developer forums seems related: http://forums.developer.amazon.com/forums/thread.jspa?threadID=11327&tstart=0
Quoted response:
There are a number of potential issues causing that error.
You might be sending an invalid scope. Are you sending "alexa:all" as
the scope? Or, your security profile might not be correctly linked. Is
it selected in the dropdown on the developer portal?
Are you getting an access token from the companion service, or is the
text box blank? If you're not getting an access token, check that your
device serial number matches between the companion service and the
java client. If you're getting an access token, the problem is more
likely with your security profile.
You should also look at these threads to see if they're helpful...
(links removed due to reputation requirement)
If that doesn't help, you'll probably have more luck asking the AVS team directly on their forum site.
I'm using the oauth playground for the Directory Members Update tool https://developers.google.com/admin-sdk/directory/v1/reference/members/patch
Whenever I try to update an existing member in the group I'm encountering an error 500 message. Is this a temporary issue or am I missing something.
When generating the request I am providing the groupKey, memberKey, and role:MEMBER for the patch body. If I provide the exact same arguments for the Update function things work just fine.
Thank you.
James
Only the role should be in the body since its the only value that is changing.
i came accross the following error, when my client tries to edit list data through datasheet view from terminal machine.
The Web application at xxx could not be found. Verify that you have typed the URL
correctly. If the URL should be serving existing content, the system administrator may
need to add a new request URL mapping to the intended application.
Note: this error is coming with only 1 list. All other lists are working fine. i m using sharepoint 2007 on 32bit
This may be related to alternate access mappings.
I had this issue, and the clue was that the datasheet was referencing a URL of the form:
_http://hostname/site/...
instead of
_http://hostname.domain/site/...
ie. the datasheet was not referencing the fully qualified domain name (FQDN).
If the error message states The Web application at _http://hostname/site/..., ie. the error doesn't use the FQDN, alternate access mapping may resolve it. The end of the error message seems to suggest alternate access mappings, although it is not entirely explicit.
I resolved this by adding an alternate access mapping as follows:
internal url: http://hostname
public url: http://hostname.domain (FQDN)
Default Zone in my case, should work for other zones.
hope this helps :)