Questions around the TYPO3 integration and plugins as well as Flow and NeosCMS
Forum rules: Always add your TYPO3/Flow, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
#1483 by NeulingvonHier
08 Mar 2015, 19:45
Hallo :-)
Im Konstanten-Editor kann ich theoretisch beeinflussen, wie resp. wo externe Links geöffnet werden (Target for external links[styles.content.links.extTarget]).
Leider scheine ich nicht fähig zu sein, das zu ändern. Habe es mit" _tab" und "_window" probiert, jedoch keine sichtbaren Resultate mit der Paypal-Weiterleitung.

Das Ziel wäre, dass wir den Shop in einem iframe einbinden können. Aus Sicherheitsgründen funktioniert aber im iframe die Weiterleitung auf die Paypal-Seite nicht.
Nun haben wir gedacht, dass es funktionieren könnte, wenn die Weiterleitung einen neuen Tab oder ein neues Fenster öffnet.

Habe es auch mit "config.extTarget = _blank" im Setup probiert.

Besten Dank für Unterstützung!
#1484 by aimeos
08 Mar 2015, 21:51
Hey

Thank you for your question. Would be great if you could write in English so non-German speakers are also able to understand the Q&A ;-)

To summarize your question:
Is it possible to use the TYPO3 constants to open links generated in the Aimeos web shop components in a new window?


The plugins use the TYPO3 URI builder to generate the URLs but not the complete HTML links. Thus, setting the extTarget constant won't have any effect as you've already seen but you could overwrite the subpart template to achieve what you are looking for.

First, I would use Firefox's or Chrome's developer tools to change the rendered HTML and insert the "target" attribute for the link manually to see if clicking on that link works as expected. If it does, I can point out the steps to change the template.

Please keep in mind that for PayPals response you need to place the checkout confirm plugin on a page which isn't placed in an iframe.
#2167 by marksyl
05 Dec 2015, 13:24
hello all!

So, i hope, my last question...

Paypal:

paypalexpress.AccountEmail
paypalexpress.ApiUsername
paypalexpress.ApiPassword
paypalexpress.ApiSignature

this configuration of mine is okay, i think, but

paypalexpress.PaypalUrl - i don't know
paypalexpress.ApiEndpoint - i don't know

This is my error message after buy-step:

PayPal Express: Request for order ID "9" failed with "Security error"

what have i forgotten to do?

lg and thanx, marksyl
#2170 by aimeos
05 Dec 2015, 14:42
marksyl wrote:paypalexpress.PaypalUrl - i don't know
paypalexpress.ApiEndpoint - i don't know


They don't need to be set. There are default values for those.

marksyl wrote:PayPal Express: Request for order ID "9" failed with "Security error"
what have i forgotten to do?


Most likely your credentials or the signature value is not correct in your configuration.
#2176 by marksyl
07 Dec 2015, 12:01
hello!

thanx!

credentials or the signature means this 4:

paypalexpress.AccountEmail
paypalexpress.ApiUsername
paypalexpress.ApiPassword
paypalexpress.ApiSignature

if i take the certificate (maybe this is the problem), is this correct to write this very long key as paypalexpress.ApiSignature?



lg, marksyl
#2182 by aimeos
07 Dec 2015, 16:27
marksyl wrote:credentials or the signature means this 4:

paypalexpress.AccountEmail
paypalexpress.ApiUsername
paypalexpress.ApiPassword
paypalexpress.ApiSignature


Yes, that's correct.

marksyl wrote:if i take the certificate (maybe this is the problem), is this correct to write this very long key as paypalexpress.ApiSignature?


The APISignature is rather long, almost 50 chars. If you don't know what's the value for this, please contact the PayPal support. They can tell you where you have to look in your PayPal account for the API Signature value.
#2190 by marksyl
08 Dec 2015, 13:07
Code: Select allconfig.additionalHeaders = Content-Security-Policy: default-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'


that was deactivited in my typoscript-setup-config...

now it worked... i have to test, but it seems good

thanks lg, marksyl
#2194 by aimeos
09 Dec 2015, 10:07
marksyl wrote:
Code: Select allconfig.additionalHeaders = Content-Security-Policy: default-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'


that was deactivited in my typoscript-setup-config...
now it worked... i have to test, but it seems good


You should be aware that some TYPO3 functionality won't work any more as TYPO3 is not prepared to comply with CSP. For example, if you are logged in into the TYPO3 backend and view a frontend page, TYPO3 injects some Javascript code into the page and that won't be executed any more.