Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OAuth2: No creation / sync of TYPO3 forms with Mautic #59

Open
mdlrvie opened this issue Jan 22, 2022 · 3 comments
Open

OAuth2: No creation / sync of TYPO3 forms with Mautic #59

mdlrvie opened this issue Jan 22, 2022 · 3 comments

Comments

@mdlrvie
Copy link

mdlrvie commented Jan 22, 2022

I have experienced a problem upgrading an existion system from OAuth1 to OAuth2. OAuth1 is working just fine. But not in OAuth2.By saving a form in TYPO3 Backend, the sync starts, but Mautic shows an error in log (and also by using the form in TYPO3-Frontend):

mautic.CRITICAL: Uncaught PHP Exception OAuth2\OAuth2AuthenticateException: "invalid_request" at /var/www/html/mautic/vendor/friendsofsymfony/oauth2-php/lib/OAuth2.php line 517 {"exception":"[object] (OAuth2\OAuth2AuthenticateException(code: 0): invalid_request at /var/www/html/mautic/vendor/friendsofsymfony/oauth2-php/lib/OAuth2.php:517)"} []

Therefore no form or any fields are created in Mautic.
All the other features like sync of Segments, Tags, ... work quite well.

Systems:

  • TYPO3 10.4.23
  • mautic-typo3 plugin 4.1.0
  • Mautic 3 and 4 (only oAuth2)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@ekkeguembel
Copy link
Collaborator

Hi @mdlrvie, thanks for reporting. We'll take a look!

@oltmanns-leuchtfeuer
Copy link
Collaborator

Hi @mdlrvie. I have looked into this issue and was able reproduce it, thus confirming this bug.
We will further investigate what causes this issue and will provide a fix as soon as possible.

For now you can just use a standalone form und use the common procedure of copying the JS to paste your form onto your page.

@Moongazer
Copy link
Contributor

@mdlrvie Would you be able to check if this issue still exists in the current v4.3.1?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants