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
Poll Setting : The calendar stays on 11 January and life span date is -1-11-30 #3694
Comments
On kunena 4.0 i can't open the calendar like on k5.0, i think for the calendar on crypsis i need to replace it by something using bootstrap to make it working |
xillibit
added a commit
to xillibit/Kunena-forum
that referenced
this issue
Feb 25, 2016
xillibit
added a commit
to xillibit/Kunena-forum
that referenced
this issue
Feb 25, 2016
xillibit
added a commit
to xillibit/Kunena-forum
that referenced
this issue
Feb 28, 2016
810
added a commit
that referenced
this issue
Feb 28, 2016
K5.0: Crypsis poll datepicker can't be opened(fix for boostrap 2) #3694
Which crypsis or blue eagle ? |
With both templates |
810
added a commit
that referenced
this issue
Mar 2, 2016
K5.0: Crypsis B3 poll datepicker can't be opened(fix for boostrap 3) #3694
xillibit
added a commit
to xillibit/Kunena-forum
that referenced
this issue
Mar 3, 2016
810
added a commit
that referenced
this issue
Mar 4, 2016
Poll Setting : The calendar stays on 11 January and life span date is -1-11-30 #3694
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce the issue
Click on poll symbol and check the calendar setting
Expected result
In the calendar - current date
life span date - should it be 0000-00-00?
Actual result
Kunena 4.0
The calendar stays on 11 January
life span date is -1-11-30
Kunena 5.0
you can't open the calendar - the button has no reaction
life span date field is empty
Joomla 2.5.28 and Kunena 4.0
Only this combination works correctly.
System information (as much as possible)
Joomla version: 3.4.8, 3.5.0 beta 2
Kunena version: 4.0.10, 4.0.11 dev,
Php version: 5.6.17-nmm1
Database version: 5.5.46-nmm1-log
Additional comments
The text was updated successfully, but these errors were encountered: