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.
Related
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.
In his Sentry TYPO3 Integration, Helmut Hummel defines the environment via $GLOBALS['TYPO3_CONF_VARS']['SYS']['environment'] here.
I've never seen this TYPO3_CONF_VARS setting before and searching the TYPO3 core of TYPO3 9.5 I can't find it either.
Background to my question is, that the environment detection doesn't work for me with the Sentry TYPO3 Integration. I have defined the TYPO3_CONTEXT in my .htaccess file like this:
SetEnvIf Host "ddev\.site" TYPO3_CONTEXT=Development/DDEV
So the question is, do I just need to define $GLOBALS['TYPO3_CONF_VARS']['SYS']['environment'] manually in my LocalConfiguration.php / AdditionalConfiguration.php or is there a better solution?
You need to define it manually, or dynamically based on application context.
The setting was introduced by the extension itself and is not provided, nor used, by TYPO3 itself.
Usually, if you want to modify anything installation wide in $GLOBALS['TYPO3_CONF_VARS'], it's put into the typo3conf/AdditionalConfiguration.php file.
Some configurations, that are only relevant for extensions you might also find in those extensions ext_localconf.php files, but that's probably not what you need.
LocalConfiguration might work, but that one is generated and overwritten by the install tool.
As a side note: The default configuration can be found in typo3/sysext/core/Configuration/DefaultConfiguration.php.
Does tx-news extension (v7.3.1) work with the workspaces feature of TYPO3? The documentation at https://docs.typo3.org/p/georgringer/news/7.3/en-us/Misc/MissingKnownErrors/Index.html only mentions known problems with versioning feature.
When a record is created in a preview workspace, can it be previewed correctly?
thanks
s
I tested it and I'm happy to say that news & TYPO3 v9.x work very well with the workspaces feature (see attachment of preview page).preview of workspace changes with news EXT
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 am new to Typo3. We have Test and Development Instances(CMS site) build through Typo3. We dont have problem in Development Instance but have in Test instance. The problem is, Whenever we change some content in pages from Backend, that content is not reflected in Frontend until 24hrs. Still now we did not find the solution. Please, if anyone of you know the solution, please share it. Thanks.
I have TYPO3 version 6.2 and there I have often problem that it is not enough to remove the cache due the backend and I have to remove cache manually.
That means to remove the content of typo3temp/cache/*. Then I can see the changes immediately. (I have to do that especially when I am changing translations).