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.
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.
I have installed introduction package on my domain.
Question: How to delete the following text at the buttom of the packge: Running with typo3 and bootstrap package?
I'm not why you're suffering from this question while it's pretty simple. Benjamin has made things super easy to manage the stuff within EXT:bootstrap_package
Anyway, you can see the configured constant in the file constants.typoscript. In this file, you can find the copyright note, see the file here.
You can replace with your own or simply leave this empty!
That's it!
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
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've tried changing the models.ejs file located in: node_modules/sails/bin/boilerplates/templates
Seems to ignore any change I make in there.
If you're doing sails generate model, it's using the code in the globally installed Sails, so you'd have to change the template there. On OS X Sails installs globally to /usr/local/lib/node_modules/sails, but it may vary by system.
This is one of the reasons that Sails v0.10 moved to using separate generators rather than baked-in templates!