-
Notifications
You must be signed in to change notification settings - Fork 65
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
FIX: broken "day" link #22
Open
kitzberger
wants to merge
210
commits into
cyberhouse:master
Choose a base branch
from
kitzberger:patch-1
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Remove not changed method in VH
Month and year can be NULL
Fix archive constraint
"news only" save default setting
This can be enabled in the EM
[TASK] use class operator in localconf
FIX: TYPO3 7 LTS deprecation warnings
FIX: TYPO3 7 LTS deprecation warnings II
Fix link to point github repository, not git.typo3.org
Correct requirements to state only TYPO3 7.6 LTS as supported
Resolves: georgringer#9
When using the event restriction (Demand::setEventRestriction) in combination with overwritten News models extending the eventnews ones, the IsEvent check isn't applied. This is due to the additional check added in 32c5dc5 (v6.0.0), which does not account for subclasses.
I haven't used the IsEvent restriction in combination with an extended demand class yet, but as a developer extending eventnews I expect the IsEvent restriction to also be effective on subclasses of the eventnews Demand class.
Contrary to some instructions on the web, extending Flexform fields for version 11 does not include an additional definition of `<TCEforms></TCEforms>` within an element. See: https://docs.typo3.org/p/georgringer/news/11.1/en-us/Tutorials/ExtendNews/ExtendFlexforms/Index.html By removing this element, the flexform field will be displayed correctly again in the backend of TYPO3 v11.
https://docs.typo3.org/p/georgringer/eventnews/main/en-us/ Please also create a webhook (https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/WritingDocForExtension/Webhook.html#github) so that future versions get rendered automatically.
…e backend" This reverts commit c333137.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.