Merged
Conversation
Contributor
|
I have tested this item ✅ successfully on 801e029 This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10375. |
Contributor
|
Simple fix direct to RTC This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10375. |
Contributor
|
@Fedik one request from me, as I guess the field calendar is still not working correctly with the new repeatable can we add: // Handle the calendar field
if($.fn.fieldCalendar){
$row.find('.field-calendar-wrapper').fieldCalendar();
}And I will provide the required changes in the calendar-setup.js and the calendar field with the use of JLayouts |
Member
Author
|
@DGT41 I think should not be a problem to add it in same time when will be changes for the calendar-setup.js 😉 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
It seems year already has changed, and I missed this 😄
sorry!
here is update for the copyright year in the subform field #7829