I have upgraded a website from typo3 v7 to v10,
in this website i have a blog extension tx_t3extblog and an added localisation code with typoscript:
_LOCAL_LANG {
en {
read_more = read more
}
de {
read_more = weiterlesen
}
}
This code is not running anymore, i don't know why, maybe because this _LOCAL_LANG is not working anymore on typo3 v10 or somthing else?
Related
I have just updated my typo3 site from 8.7.29 to 9.5.11 following the official documentation. From technical point of view everything went fine: the upgrade wizard ran successfully in all the required steps and there are no complains from all the available checking tools (database, extensions,...).
The additional problem was that I had to migrate from css_styled_content to fluid_styled_content (because scc_styled_content is not supported anymore by typo3 9). So I modified my old template to work with fluid. After that everything is fine except the fact that all the internal links are not rendered correctly. In particular in the FE all the internal links are reported as:
<a class="internal-link" href="t3://page?uid=246" title="Opens internal link in current window">My link</a>
So obviously typolinks are not parsed correctly.
Some other users reported a similar problem when the extension frontend editing is used. In my case the problem is still there even if this extension is disabled...
Do you have any idea on what is going on?
Thanks a lot for your help!
Today in one of our older sites we found an issue with the RTE Editor. For any of our users the editor does not load. It is stuck on loading as you can see in the image below.
Now I realize that the version we are using for TYPO3 is extremely outdated, the version is 4.5 support has been gone for ages and I wouldn't dare to just update this site.
We haven't updated or changed anything in the configuration so this wouldn't be the case. I've also tried to remove all caches from the site, create a new user and give them all rights and trying several different computers. None of this has helped fix the issue.
Wondering if anyone has a idea on where to search or how to solve this.
Are you using Chrome 73 as browser? This version breaks the rtehtmlarea integration. You need to backport the patch which is provided for TYPO3 8.7.
File: typo3/sysext/rtehtmlarea/htmlarea/htmlarea.js
Line : 2224
search for:
src: Ext.isGecko ? 'javascript:void(0);' : (Ext.isWebKit ? 'javascript: '' + HTMLArea.htmlEncode(this.config.documentType + this.config.blankDocument) + ''' : HTMLArea.editorUrl + 'popups/blank.html')
change to:
src: Ext.isGecko ? 'javascript:void(0);' : (Ext.isWebKit ? (Ext.isChrome ? 'about:blank;' : 'javascript: '' + HTMLArea.htmlEncode(this.config.documentType + this.config.blankDocument) + ''') : HTMLArea.editorUrl + 'popups/blank.html')
You probably have a javascript error which stops execution of further javascript.
on loading the data is adapted (from TYPO3 format to HTML) and the editor is build by modifying the DOM. As browsers change in behaviour and javascript engine the old javascript might run into errors with current browsers.
You could try to use another browser.
Otherwise you could disable the RTE in the user settings, although it means you have to edit text as HTML source.
I have migrated a TYPO3 6.2.31 page to TYPO3 7.6.23
Most stuff works fine.
At the moment I have the Problem with a view helper.
I got this error:
Could not analyse class: "FluidTYPO3\Vhs\ViewHelpers\SwitchViewHelper" maybe not loaded or no autoloader? Class FluidTYPO3\Vhs\ViewHelpers\SwitchViewHelper does not exist
How can I fix this error?
Thanks!
The PHP class SwitchViewHelper has been removed between VHS version 2.4.0 & 3.0.0. Cause 3.0.0 was TYPO3 7 compatible, which includes its own SwitchViewHelper.
Depend, how you call such SwitchViewHelper in your FLUID templates - I guess something like
vhs:switch
You should change it to
f:switch
and also adapt to f:case, f:defaultCase ..
See https://docs.typo3.org/typo3cms/ExtbaseGuide/Fluid/ViewHelper/Switch.html
Im searching the web for hours now, tried probably all of the million answers out there regarding this topic... but unfortunately there wasnt a solution among them. So...
Update:
Is there a proper way to open external urls in Phonegap Version 2.3 without using a plugin?
There are a lot of solutions for lower versions than 2.3 out there, but non of them actually did the trick.
Thx.
It seems that Cordova is already providing a solution for my problem in version 2.3.
This makes plugins like ChildBrowser obsolete.
The answer is InAppBrowser
check the following links:
stackoverflow
and the doku:
official doku
Make sure to implement this at the right spot. In my case it was a element of a listview. I implemented it like this:
$(document).bind("mobileinit", function(){
...
$('.listviewmain').delegate('li', 'tap', function(event, ui, e) {
var index = $(this).closest('li').index();
if(result.news[index].id == "ads") {
var ref = window.open('http://google.com', '_blank', 'location=no');
// attach listener to loadstart
ref.addEventListener('loadstart', function(event) {
var urlSuccessPage = "http://myloginapp/success/";
if (event.url == urlSuccessPage) {
ref.close();
}
});
}
...
}
Hope this helps :)
My client wants to update an old tt-news installation version 2.x. Unfortunately the former maintainer of the site quit the job and let me do his job and although there is a huge category tree of news none of the categories are selected in the plugin configuration dialog at several locations. This seems to work with an older Typo3 4.1.3 but not when I update to a newer version. My question is it possible the tell tt-news with Typoscript or with a constant the current news category and how?
plugin.tt_news {
categorySelection = 2,3
# show only selected categories
categoryMode = 1
}
Details about this: http://typo3.org/documentation/document-library/extension-manuals/tt_news/3.1.0/view/1/4/