Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Stripe
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Extensions
Stripe
Commits
fdb60a32
Commit
fdb60a32
authored
4 years ago
by
mattwire
Browse files
Options
Downloads
Patches
Plain Diff
Fix for future start date compatibility with recurringbuttons extension
parent
b7e5a5b5
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!127
Fix for future start date compatibility with recurringbuttons extension
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
js/recur_start.js
+1
-1
1 addition, 1 deletion
js/recur_start.js
with
1 addition
and
1 deletion
js/recur_start.js
+
1
−
1
View file @
fdb60a32
...
...
@@ -27,7 +27,7 @@
// Remove/insert the recur start date element just below the recur selections
$
(
recurSection
+
'
#stripe-recurring-start-date
'
).
remove
();
$
(
recurSection
).
a
ppend
(
stripeRecurringStartDateSection
);
$
(
recurSection
).
a
fter
(
stripeRecurringStartDateSection
);
// It is hard to detect when changing memberships etc.
// So trigger on all input element changes on the form.
...
...
This diff is collapsed.
Click to expand it.
mattwire
@mattwire
mentioned in issue
recurringbuttons#12 (closed)
·
4 years ago
mentioned in issue
recurringbuttons#12 (closed)
mentioned in issue recurringbuttons#12
Toggle commit list
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment