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!
Related
There was an error in the working CMS and I can not even enter management panel. I did not update PHP on the server, nothing changed in the configuration, and yet I can't enter the administration panel or display the WWW page.
When I try to get on administration panel or on website there is a message like this:
PHP Runtime Notice: Declaration of tx_ttnews_catmenu::wrapTitle() should be compatible with t3lib_treeView::wrapTitle($title, $row, $bank = 0) in /home2/izbampro/public_html/typo3/typo3conf/ext/tt_news/class.tx_ttnews_catmenu.php line 56
Is this a bug related to a too old version of PHP, or could someone break into the server and change the configuration?I have no idea what could have happened, everything worked well several days ago. Please help me with this error.
what do you mean with the administration panel?
in TYPO3 you have the BackEnd where you can do the normal administration and editorial tasks.
it is called normally with domain.tld/typo3/
the other area for administrative tasks is the Install Tool
which is called with domain.tld/typo3/install/
While the Backendneeds a running TYPO3 instance the InstallTool should be callable even if there is no configuration (e.g. database).
regarding your TYPO3 version:
we can guess a little bit with your data:
PHP 5.6.26 will let run TYPO3 only until version 7.6
the function reference t3lib_treeView::wrapTitle will restrict the version in the same way as the classname was available in core up to 4.7. for later version there existed an compatibility extension, first in core, later from TER.
if you have a look onto your server we might have further restrictions.
I will not exclude the usage of older versions up to 4.7:
these versions can be identified by files typo3conf/localconf.php, while since 6.0 the files are named typo3conf/LocalConfiguration.php.
In the same way there is a break in the storing which extensions are active in your installation:
up to 4.7 it was one line in typo3conf/localconf.php, since 6.0 it is an own file typo3conf/PackageStates.php.
You should be able to call the install tool, which will show the version (a screenshot from the appearance after the Install Tool login might help. But first we need to make you accessing the Install Tool.
Are you able to login to the install tool?
the TYPO3 version will decide about the next steps
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'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.
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.
When we push a new version to our server, the old extensions deployed take some time (<7hours in the docs, but I have seen more) to update themselves. The problem is that these OLD extensions may talk to the NEW services/api deployed on the server, thus raising conflicts. And those are very hard to hunt down...
Any advice?
Thanks.
You can't force autoupdate but you can pass api version along with the server response and have extension notify users to upgrade if it is outdated (response version doesn't match hardcoded into extension version).
UPDATE
Ok I just reread the question and looks like author is talking about the extension gallery. In this case you can't just point a user to the gallery as it doesn't allow you to reinstall an extension without uninstalling first anymore (it used to a while ago). In this case, to force reinstall you would have to either ask users to hit "Refresh now" button on the their chrome://extensions/ page, or download and install your extension's crx directly, which has the following (scary) format:
http://clients2.google.com/service/update2/crx?response=redirect&x=id%3D<EXTENSION_ID_HERE>%26uc%26lang%3Den-US&prod=chrome