I've updated a TYPO3 website from 4.7 to version 6.2.12. As I do so I replaced deprecated classes with the proper namespaces.
t3lib_div to \TYPO3\CMS\Core\Utility\GeneralUtility or
t3lib_extmgm to \TYPO3\CMS\Core\Utility\ExtensionManagementUtility
Now the old extensions are installed. But now I'm facing an error with security extension like this
Oops, an error occurred!
Invalid form/module token detected. Access Denied!
More information regarding this error might be available online.(https://wiki.typo3.org/Exception/CMS/1392409507)
And in other extension I have this error i think it is the same problem
Validating the security token of this form has failed. Please reload the form and submit it again.
I absolutely have no clue what I need to do, any suggestions?
You are running into the CSRF Form Protection.
Please check the commit that introduced this.
Make sure to use BackendUtility::getModuleUrl() for each place you generate a link.
Related
i have installed a plugin in Moodle that is ment to translate textstrings into different (installed) languages.
The installation did work, registering with Google-Cloud and getting an API-Key did work as well. In the (over)load of information on how to use the google service i found some settings that i adjusted.
But . . . i still get an 403 authorisation error.
The google console shows the attempts to get translations but none is made.
Anyone an idea where i should search for a solution?
Regards,
Jan
The plugin link says it's been superseded
"Content translation filter (superseded)"
https://moodle.org/plugins/filter_fulltranslate
Have you tried the new version?
https://moodle.org/plugins/filter_translations
I took over a website for my client and I tried adding an extension to Typo3. When I did, the whole website crashed and displays a HTTP ERROR 500. I found this thread with a similar problem, followed the instructions and erased the key that was supposed to be removed typo3 site offline after extension upload but that didn't work.
I gained access to the cPanel since I couldn't access the backend login page. So now i'm able to access all of the root files and hopefully fix the problem. Does anyone know anything to fix it?
You should read the error log (for the PHP service or Apache, depending on how your hosting works). There you can see the actual error message which then can give you an indication what's actually wrong.
The most common reasons are:
Extension version is not compatible with the version of TYPO3 you used (and you ignored the warning when installing).
Extension is written in a way that it assumes you update the database schema, which may not happen automatically when you install the extension.
Extension calls on classes that must be loaded and does not provide class loading for the installation you use (e.g. some extensions only offer composer support and won't work if you install without composer).
Extension uses PHP modules that are not installed or is incompatible with the version of PHP that is used.
You should be able to recover this by using the TYPO3 install tool to manually update the database schema and perform checks that the extension works (TYPO3 8.7+ only). If that does not help we will need additional information:
Which TYPO3 version do you use?
Was it installed with composer?
What is the exact error message you get in PHP error logs?
If the extension you installed is public, a link to it would help determine why you get the error.
Hope this helps!
We are using WSO2 5.4.1 version and trying to setup IWA using Kerberos. We have done all the configurations as mentioned in the following post.
https://medium.com/#farasath/integrated-windows-authentication-with-kerberos-and-wso2-identity-server-ffcd8263a0f1
When we try to access the application we are getting following exception.
We have checked all the configurations multiple times but not able to figure out the root cause. Can someone help us to find out what could be missing in this setup? Are we missing any additional step?
We have also tried with WSO2 IS version 5.5.0 but still getting same error.
How can we enable additional logging to see what is going wrong with kerberos token decryption?
It was indeed a JDK issue. For some reason we were using Oracle jdk1.8.0_45 and we were facing this issue. We had upgraded the version to jdk1.8.0_162 and we were able to proceed but then we encounter another problem. After authentication we were not getting remote claims in the response from WSO2 IS. As per this post (stackoverflow.com/questions/49997900/…) we upgraded to latest patch of WSO2 IS 5.5.0 and now it is working.
We are able to authenticate user using IWA-Kerberose.
We have SugarCRM Enterprise, Version 7.10.2.0 (On-Demand) and tried to install latest version (v1.5.62) of DocuSign plugin (https://sugarexchange.sugarcrm.com/apps/188/sugar-connector-to-docusign) on SugarCRM.
We followed the installation documentation (https://help.upcurvecloud.com/sugardocusign/Sugar_Connector_to_DocuSign.pdf)
Issue: Once we try to login then Error popups "DocuSign Error!" (Screenshot attached)
Any help will be highly appreciable.
Regards
In your Sugar instance go to Administration -> System Settings -> View Log and check the log for FATAL messages during the attempted login time.
E.g. a possible fatal message could be [FATAL] Platform name violation: unknown platform (<used platform name of connector goes here>).
Since Sugar 7.10 the platform parameter during authorization is limited to platforms known by your instance. Unknown platforms will be rejected and authorization will fail.
This could be the problem if the connector has yet to be updated for this new behavior.
If so either the provider of the connector or you should add the platform to the instance. E.g. by adding the file custom/Extension/application/Ext/Platforms/docusign_connector.php with contents:
<?php
$platforms[] = '<used platform name of connector goes here>';
However this is just a guess of what the problem could be as I have not seen your Sugar's log.
If your have any other fatal error messages, feel free to share.
Edit: Actually the platform enforcing seems to be a 7.11 thing rather than a 7.10 thing. So even if you do see an error as described above, it could only to be a warning (for future version compatibility reasons), rather than the actual source of the problem experienced by you.
So make sure to look for other errors as well.
I'm having difficulty in integrating AEM 5.6.1 with Site Catalyst. It allows me to connect in the configuration successfully, but does not work on the framework setup.
I've followed the standard procedure to connect AEM to SC and it accepts my login in the configuration, but fails on the framework set up with the browser message 'We were not able to login to SiteCatalyst. Please check your credentials and try again.'. Behind the scenes in the server log;
12.12.2014 14:10:06.967 *WARN* [0:0:0:0:0:0:0:1 [1418393406764] POST /libs/cq/analytics/sitecatalyst/service.json HTTP/1.1] com.day.cq.analytics.sitecatalyst.impl.SitecatalystHttpClientImpl Data center 'https://api3.omniture.com/admin/1.3/rest/' responded with errors {"error":{"code":500,"message":"Internal Server Error"}}
12.12.2014 14:10:06.967 *ERROR* [0:0:0:0:0:0:0:1 [1418393406764] POST /libs/cq/analytics/sitecatalyst/service.json HTTP/1.1] com.day.cq.analytics.sitecatalyst.impl.servlets.SitecatalystServlet Call to SiteCatalyst method 'Company.GetReportSuites' failed com.day.cq.analytics.sitecatalyst.SitecatalystException: not authenticated
I've tried accessing via the API Explorer and it works.
I've tried the troubleshooting guide without success.
I can log in to Site Catalyst, I'm an admin, I am in the web services access group.
I've tried using a clean install of CQ5.6.1 with geometrixx - it doesn't work either.
I've tried this from a server and from a localhost/dev machine with the same results. No proxy. I've even tried using the shared secret as the password but then it doesn't connect at all, and fails on the configuration screen.
What might cause this to fail?
If it doesn't work with a fresh install and Geometrixx, then it's probably an Adobe bug. That's typically the first thing support will ask you about.
I would also verify using Geometrixx Outdoors, or a more recent demo site, on your fresh install, just to ensure it's not an outdated ClientLib issue.
I know this isn't a direct answer to your question, but honestly, I would approach the integration differently. I've worked with the AEM-SC framework and it's buggy at best. It's very finicky, it doesn't REALLY work the way the documentation claims, and it requires that you're very specific about what Clientlibs are on the page.
Moving forward, I think using Adobe Dynamic Tag Manager is the better approach, for many reasons. My understanding is that it's Adobe's recommendation as well. I'd consider moving to that. In AEM 5.6.1, you'll have to customize your integration with DTM, but it's not very hard.
Solution: Add a property on the configuration node for sitecatalyst: (eg. /etc/cloudservices/sitecatalyst/my-sc-configuration)
server=https://api.omniture.com/admin/1.2/rest/
it also seems to work with newer API versions such as https://api3.omniture.com/admin/1.3/rest/
It would appear that for 5.6.1 it ignores the OSGi configuration, at least for the configuration screens. With this extra property, the framework page loads without error and allows selection of the RSID.