I'm working currently on a typo3 instance which someone different was setting up.
When i go to Admin tools > Extension Manager i see a very different Interface then i'm used to and that i saw in the official documentation.
What i specifically miss is the the setting panel where i can switch the repositories.
My view:
TL;DR: wired extension manager, why?
Related
VSCode's official documentation of Extension Guidelines for WebViews currently discourages the use of WebViews for Wizards, as quoted here below:
Don't
Use for promotions (upgrades, sponsors, etc.)
Use for wizards
Open on every window
Open on extension updates (ask via a Notification instead)
Add functionality that is unrelated to the editor or workspace
Repeat existing functionality (Welcome page, Settings, configuration, etc.)
With the release of VSCode's Webview UI Toolkit I was looking into using them for WebView based Wizards, but because the documentation doesn't recommend this, I'd like to know if there's an official correct approach for wizards. I could not find anything in the official APIs and docs (hopefully I didn't missed it).
My current plan is to go against the recommendation if there's nothing else available.
Thanks!
With TYPO3 9.x Site Configurations were introduced.
In my TYPO3 composer installation the site configurations are stored in /sites/sitepackagename/config.yaml
I would like to know whether it's possible or not to include the site configuration inside a site package.
I'm aware of the possibility to use imports inside the site configuration (like described here) and link to a .yamlfile inside my site package. But I'm looking for a solution without manually touching /sites/sitepackagename/config.yaml.
No, this is not possible. The two possible locations (depending on whether you are in composer mode or not) are <project-root>/config/sites/ and typo3conf/sites/.
This is also described in the docs.
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.
I currently got the task to upgrade a custom made CRM extension named "kbs". It was developed on TYPO3 4.7 and using old namespaces in its classes like "Tx_Kbs_Service_TestService" etc.
I want to upgrade this whole extension to be able to work properly with our current backend version of 6.2. More specifically i want to be able to use the extension builder to make changes to this extension which i am currently not able to do on the 6.2 TYPO3 backend. It is not even an option to select the "kbs" extension in the extension builder.
Of course i reasearched the web but I find it very difficult to find information what you have to do in order to addapt a custom extension.
So far I assume that i will have to change all the namespaces in all my classes manually and maybe watch out for decrecated classes. But I do not really know if that is the way to go.
Does anyone have and guidelines, links or tipps for me? I would really appreciate it!
Thanks in advance,
Simon
To the first question:
In extension_builder only extensions are changeable, they had their original configuration made by extension_builder.
Extension builder itself is only an option to use, and there were also other options to kickstart an extension.
Update:
This is true, that extension builder is not an "editor" for extensions but a tool to help kickstarting an extension.
If I would get the task and extension_builder would be available I would not use it to make changes on the code. It is not 100% sure, that manually changes were not made on the code after its last automatically generated version. And if dummy actions were changed and properly excluded from the config they could be also deleted.
I think your best choice to change the things manually.
There are two source to read first:
TYPO3 6.2 Release Notes.
What's new presentation (TYPO3 6.2)
They contains breaking changes and some example.
If you do not change the PHP version, than changing the Namespaces and some deprecated functions. (The sources above could help to get an idea on those)
One tricky part could be to migrate old image logic into the "new" FAL (File Abstraction Layer). If you don't need to deal with images, then it must be an easier thing to go with.
There is also an extension to help with some migration stuff: smoothmigration.
You can find some hints in this presentation also:
jweiland: Smooth Migration TYPO3 4.5 > 6.2 LTS
After watching some videos on how to use variant subsystems in a design, I was able to get variants working.
But this video tutorial (Managing Design Variants) from Mathworks mentions a Variant Manager which I have been unable to find in my version of Simulink. I am running version R2011b.
My View menu is different form the one in the tutorial, but it shows tabs for the Library browser, the Model Explorer and the Simulink Project. But I don't see any sign of a Variant Manager. I checked the other menu tabs with the same results.
Documentation help doesn't find anything on Variant Manager either.
Is the Variant Manager something introduced in a later version? Which one did it start in?
Or is there something I can configure to in order to use it?
The Variant Manager was introduced in R2013b, see the release notes (under R2013b, Component-Based Modeling).