Move content history to bs modal#4561
Move content history to bs modal#4561dgrammatiko wants to merge 10 commits intojoomla:stagingfrom dgrammatiko:content_history
Conversation
Same as #4513 and 4514 but for content history Content history is currently using mootools modal. Without affecting in anyway the logic of the field we can use jQuery and bootstrap. B/C Should be 100% compatible Test: Apply the patch Go to administrator -> Banners -> create a new banner change the alternative text and save it again repeat the last part for few more times press the versions button Everything should be ok
|
Why: which is anyway wrong as you should use |
|
Hmm, found out that we indeed have to reload language to get the modal title translated. |
layouts/joomla/toolbar/versions.php
Outdated
There was a problem hiding this comment.
I think you will get problem with approval, with such things ... problem:
- use the inline css, that repeats in different files
- use
!important
This make problems for support this code in future.
I think better make some 'unified' styling for the modal in the template style
There was a problem hiding this comment.
I agree strongly with @Fedik. Don't use inline styles and especially no !Important. I will personally redirect all complaints from template designers to you and share your home address with them 😄
There was a problem hiding this comment.
One more think to get 100% B/C is needed here:
I removed the moo tools modal close code SqueezeBox.close(); and replaced it with jQuery("#userModal").modal("hide”); Best practice I think is to proxy the old function to the new if SqueezeBox is not defined. Some JS guru for this? @Fedik ?
|
@DGT41 I am not guru, and for me another notice: JHtmlBootstrap::renderModal('versionsModal', array( 'url' => $link, 'title' => $label ,'height' => '600px', 'width' => '800px'), '');will become: JHtml::_('bootstrap.renderModal', 'versionsModal', array( 'url' => $link, 'title' => $label ,'height' => '600px', 'width' => '800px')); |
|
@test |
|
@tested Succesfully |
|
moving to RTC as we have more that 2 successful tests |
|
moving to RTC as we have more than 2 successful tests |
|
The PRs regarding Media Field, User Field and Content History are also used in the front end. That might break the rendered design IF THE TEMPLATE is not BOOTSTRAP compatible. (the old modal uses it’s own css file). I wrote it! |
|
For B/C I reverted the option to use the mootools modal in front end. Lets NOT break every site out there. |
|
Will try again when #3231 is committed |


Same as #4513 and #4514 but for content history
Content history is currently using mootools modal.
Without affecting in anyway the logic of the field we can use jQuery and bootstrap.
B/C
Should be 100% compatible
Testing:
Go to administrator -> Banners -> create a new banner
change the alternative text and save it again
repeat the last part for few more times
press the versions button
Everything should be ok
Before:

After:
