Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.6.0 is breaking because of renamed setup.txt > setup.typoscript #22

Closed
t3easy opened this issue Jul 8, 2020 · 9 comments
Closed

1.6.0 is breaking because of renamed setup.txt > setup.typoscript #22

t3easy opened this issue Jul 8, 2020 · 9 comments
Assignees
Labels
bug Something isn't working

Comments

@t3easy
Copy link
Contributor

t3easy commented Jul 8, 2020

No description provided.

@froemken
Copy link
Contributor

froemken commented Jul 9, 2020

Which TYPO3 Version are you using? The new .typoscript extension is available since TYPO3 8.7.: https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/8.7.x/Feature-78161-IntroduceTypoScriptFileExtension.html.
So it may not work in TYPO3 8.7.0.

@t3easy
Copy link
Contributor Author

t3easy commented Jul 9, 2020

Ah, the description was lost...
It is breaking if you include the file with
<INCLUDE_TYPOSCRIPT: source="FILE:EXT:video_shariff/Configuration/TypoScript/setup.txt">
or @include

@froemken
Copy link
Contributor

froemken commented Jul 9, 2020

Ah, you mean because of the renamed file which is breaking in this feature release (1.6.0)?

@froemken froemken added the bug Something isn't working label Jul 9, 2020
@t3easy
Copy link
Contributor Author

t3easy commented Jul 9, 2020

Yes. Releasing a 2.0.0 would have been good to follow semver rules.

@pascal20997
Copy link
Contributor

I think we should create a new bugfix or feature release and add a setup.txt that includes the setup.typoscript file. Maybe we can add a comment into that file like "This file will be removed in video_shariff 3.0.0." The TemplateService searches for .typoscript first, so the setup.txt shouldn't make problems in addition to the .typoscript file. What do you think?

@t3easy
Copy link
Contributor Author

t3easy commented Jul 9, 2020

I don't know, what happens in a case if both .txt and .typoscript exist but I think .typoscript has priority and the txt is not used if it's included by include_static_file.
The added required constants.typoscript is also "breaking" if files are loaded with INCLUDE_TYPOSCRIPT, because it's new that you have to include them...

@pascal20997
Copy link
Contributor

You're right that's a new requirement. One solution would be either to increase the version to 2.0.0 or to customize the setup.txt a bit. There is only one constant right now so we could override the value of the default thumbnail inside the setup.txt.

Example of setup.txt:

# This file was replaced by setup.typoscript.  It will be removed in video_shariff 2.0.0

<INCLUDE_TYPOSCRIPT: source="FILE:EXT:video_shariff/Configuration/TypoScript/setup.typoscript">
lib.video_shariff.defaultThumbnail = EXT:video_shariff/Resources/Public/Images/DefaultThumbnail.png

@t3easy
Copy link
Contributor Author

t3easy commented Jul 9, 2020

By the way, configuring settings of a plugin in the lib tree is odd ;) plugin.videoshariff.settings.defaultThumbnail corresponds more to the convention of TYPO3 Extensions.

@pascal20997
Copy link
Contributor

The idea of lib.video_shariff was that video_shariff is not a "plugin" like e.g. news. It just overrides the fluid_styled_content templates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants