I have just migrated six websites from TYPO3 4.x to TYPO3 6.2
In all of these, I use the htmlArea RTE, but only in one of these, the RTE does not work.
It's installed fine, but when I open a content element, the RTE keeps trying to load and simply does not open.
I know that there was a bug related to this (TYPO3 can't enable htmlArea RTE) but this is NOT the solution for my problem.
Because all my other TYPO3 installations work fine, I am really clueless and would appreciate any help.
SOLVED! Just in case anyone else is having a similar problem:
In my PageTSConfig, I had this entry:
RTE.default.buttons.blockstyle.tags.table.allowedClasses.classesTD
But it needs to be this:
RTE.default.buttons.blockstyle.tags.table.allowedClasses
Now everything works perfectly
Related
A day ago my prestashop website, in the comment box of the blog started to display the following message:
And entering the post that explains how to migrate the version of TinyMCE , I do not understand very well how to perform these steps in my prestashop.
How can I update this?a
if you are using a third-party module to make your blog it might be is including its own version of TinyMCE. You should try to dig in its code to understand that.
If this is not the case, the blog uses TinyMCE which is normally included in Prestashop core.
On said that, this second case is likely to be the one. Update the e-commerce unlikely will solve your problem. I honestly don't remember in which version they are with TinyMCE but doing an upgrade like that might break back-office editor forms so I don't think they are keen on that at the moment. They are doing a major rollover to Symfony, I am pretty sure this is their priority right now. As said in one comment, Prestashop's dev team has to solve the issue on their side.
It's just a simple question but couldn't find any helpful solution or hints...I have the current TYPO3 version and watched some videos on YouTube about it and wondered why I have no autocomplete when writing some TypoScript.
I saw it in this video: https://www.youtube.com/watch?v=ZCSIK3lFfwM&list=PL1D69sw7eWECaiqIOLhcSnjgTTjLJdd4I&index=5 at 03:45
Is it possible to do it in the newest version or do I have to use an IDE?
First install the extension ts3editor.
Then you can "activate" auto complete just by pressing CTRL+SPACE. For example, write:
->config.
then press
->"CTRL+SPACE"
then the autocomplete advice/suggestion will pop-up.
I use version 9 and it works fine.
The TYPO3 core offers the extension "t3editor", which is based on CodeMirror and provides syntax highlighting and codecompletion.
I suspect it just isn't activated in your TYPO3 instance. You can check this in the Extension Manager in your TYPO3 backend.
1st edit: As the extension seems to be working in general – please try writing config. on a new line in your editor. The Top Level Objects (e.g. config) aren't auto-completed in the backend, but it should open a box with suggested configurations after you wrote the dot.
t3editor has some restrictions: Nesting isn't supported (see example below). I read it can have problems inside conditions, too.
// This is auto-completed:
config.no_cache = 1
// This isn't:
config {
no_cache = 1
}
In short: t3editor can only help you to a certain degree. It is considered best practice to save all TypoScript (and everything else related to templating) in files into a dedicated templating extension (or sitepackage) and use an IDE. There are TypoScript auto-complete plugins for several editors and IDEs, for example PhpStorm.
If you want more information about using sitepackages, see this video series on YouTube by the offical TYPO3 account, or take a look at my personal templating extension which I use for new websites.
2nd edit: After you wrote you're using the Sprint Release 9.1.0, I was able to test the behaviour in this version and can confirm that code completion won't work in it.
Actually, that seems to be the intended future behaviour of t3editor for the TYPO3 core team. They want to remove this extension in TYPO3 v10 altogether (it's planned to be available on GitHub then). The reason is that they don't recommend to use/save TypoScript directly in the database, but in a separate template extension (see explanation above).
Sources:
TYPO3 Bug tracker, issue #81885
Communication platform TYPO3 Slack, Channel #typo3-cms-coredev, Nov 19th, 2017
So again, I recommend to use an API instead.
Does anybody know, if TYPO3 extension RealURL has support fo workspace?
If I switch to workspace and click to preview each of links on page has href="mydomain.com/index.php?id=xxx" instead of href="mydomain.com/page-1".
In LIVE version everythings OK
I have used automatic conf of RealURL and I have multidomain page...
The Workspace Preview may look like the Frontend, but in fact it runs in Backend context. The Backend may run on a different port, with a different URL etc. and therefore you don't have speaking URLs available in this context. So there is no solution, as far as I know.
Does anybody know, if TYPO3 extension RealURL has support fo workspace?
No, RealURL does not do anything when working in a workspace. This is by design.
I have an old Typo3 installation which was upgraded many times before. At the moment it's at version 4.5.
Because I had several severe problems upgrading, I am thinking of setting up a clean Typo3 6.2 LTS setup and migrate the pages, instead of upgrading again.
My question is now, what is the best way to transfer the pages as well as the calendar, news and TemplaVoila from version 4.5 to version 6.2? I have more than 1000 pages.
Thanks
You can upgrade a TYPO3 4.5 website to TYPO3 6.2 as soon as all extensions used in TYPO3 4.5 are compatible with TYPO3 6.2. I think this will still take some weeks until the major extensions are provided with an update for TYPO3 6.2
If you dont want to wait, you can try to use the patches named in the smooth migration wiki
At least, there is a patch for tt_news.
In case of TemplaVoila you can try using this version which could be compatible with TYPO3 6.2
In case you do not know: The TemplaVoila extension will not be maintained any more (more details about that here), so it is not very future safe to use it on a TYPO3 6.2 website.
If you want to use FluidTemplate and Grid Elements instead of TemplaVoila, you can try to use my extension tv2fluidge to migrate your TYPO3 4.5 website to FluidTemplate and Grid Elements. This is of course a lot of work (creating new page templates and Grid Elementes), but you can keep your page structure and content and do not have to wait for an TYPO3 6.2 version of TemplaVoila.
I don't know if it will be work for 100% but you can copy all tables with prefix tt_news, calendar etc. and pastle them to new db. If you have some images and other files you will find it in uploads/tx_ttnews/ - you should copy it too. I don't use TemplaVoila so I don't know how to move that to another site. And you have to remember about pid and id of pages/ce - they have to be the same
I successfully upgraded TYPO3 version 4.7.12 to 6.1.7, and also followed all steps for upgrading.
http://wiki.typo3.org/Upgrade
All functionality works fine in both side frontend and backend.
But the backend content view looks ugly, see attachment image.
Templating method: TemplaVoila
Please help me where I missed something.
You should be aware, that TemplaVoila is not actively developed any more. It also is not 6.x compatible and will most likely not be fixed to become compatible.
From the looks of things I'd say either TemplaVoila or any other non compatible extension break your backend view. I'd suggest you disable all extensions that are not explicit 6.x compatible and try to enable your way back until you know which extension causes this, and TV is a good candidate for this.
As a possible replacement have a look at fluidcontent or write your own content elements via a simple extension.