Skip to content

Move media field to bs modal#4513

Closed
dgrammatiko wants to merge 22 commits intojoomla:stagingfrom
dgrammatiko:media_field_bs_modal
Closed

Move media field to bs modal#4513
dgrammatiko wants to merge 22 commits intojoomla:stagingfrom
dgrammatiko:media_field_bs_modal

Conversation

@dgrammatiko
Copy link
Copy Markdown
Contributor

Select image field (field type media) is using mootools modal.
Without affecting in anyway the logic of the field we can use jQuery and bootstrap.

This needs some visual fixes as the rendered modal needs some css to get to a more appropriate size.
Feel free to submit some ideas or code!

B/C
Should be 100% compatible

Test:
Apply the patch
Go to administrator -> global configuration
and check the functionality of Offline image.
Everything should be ok (except the size of the modal)

@brianteeman
Copy link
Copy Markdown
Contributor

The styling on this is off, there is a size issue with white space at the bottom AND there is now the word Select at the top

before

screen shot 2014-10-11 at 05 22 33

after

screen shot 2014-10-11 at 05 22 48

This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4513.

@dgrammatiko
Copy link
Copy Markdown
Contributor Author

Before:
screenshot 2014-10-11 17 17 29

Now it should act exactly as the old modal + now it is responsive
screenshot 2014-10-11 17 11 05

@brianteeman
Copy link
Copy Markdown
Contributor

Why have you added the title Select or upload an image?
On 11 Oct 2014 15:12, "Dimitri Grammatiko" notifications@github.com wrote:

Now it should act exactly as the old modal + now it is responsive
[image: screenshot 2014-10-11 17 11 05]
https://cloud.githubusercontent.com/assets/3889375/4602869/a1404768-5150-11e4-9e47-55d0a39c4523.png


Reply to this email directly or view it on GitHub
#4513 (comment).

@dgrammatiko
Copy link
Copy Markdown
Contributor Author

Bootstrap modal needs a title: http://getbootstrap.com/2.3.2/javascript.html#modals
If we leave it blank the layout gets ugly, I guess that’s the drawback here, we add another string

@brianteeman
Copy link
Copy Markdown
Contributor

@Infograf thought s on adding another string etc
On 11 Oct 2014 16:52, "Dimitri Grammatiko" notifications@github.com wrote:

Bootstrap modal needs a title:
http://getbootstrap.com/2.3.2/javascript.html#modals
If we leave it blank the layout gets ugly, I guess that’s the drawback
here, we add another string


Reply to this email directly or view it on GitHub
#4513 (comment).

@infograf768
Copy link
Copy Markdown
Member

@brianteeman
No problem adding new strings in 3.4.0

@dgrammatiko
Copy link
Copy Markdown
Contributor Author

@brianteeman Can you provide some appropriate titles for the modals, so I don’t make a bunch of commits?
The PR are #4514 #4561 #4562 #4563 #4575

@dgrammatiko
Copy link
Copy Markdown
Contributor Author

@Bakual how can I solve this:

This pull request contains merge conflicts that must be resolved.
?

@Bakual
Copy link
Copy Markdown
Contributor

Bakual commented Oct 13, 2014

That's very likely due to our friends from the codestyle sprint 😄

What you need to do is update your branch https://github.com/dgt41/joomla-cms/tree/media_field_bs_modal to current staging and resolve any conflicts that may have occured.

There are two possible ways of getting the branch updated:

  • Easy: Just merge staging (from the joomla/joomla-cms repo) into your branch. This will create a "merge-commit".
  • Nice: Rebase your branch with staging. This way, git will kind of rewind your changes, apply all commits from staging and then reapply your commits again. If done properly your PR will still look exactly the same as now, with only your commits.

@rajeshstarlite
Copy link
Copy Markdown

@test, it works fine.

This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4513.

@mrunalpittalia
Copy link
Copy Markdown

Moving to RTC as issue patch more than 2 successfull tests

@dgrammatiko
Copy link
Copy Markdown
Contributor Author

@Bakual and the rest of the PLT:

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!

@dgrammatiko
Copy link
Copy Markdown
Contributor Author

For B/C I reverted the option to use the mootools modal in front end. Lets NOT break every site out there.
Please test again

@Bakual
Copy link
Copy Markdown
Contributor

Bakual commented Oct 19, 2014

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!

I'm sorry to say, but if it's going to break templates that worked fine before, then this will obviously not pass. We will need a different approach then.

@dgrammatiko
Copy link
Copy Markdown
Contributor Author

I closed all 4 requests that infect also the front end. I will do them again as soon as #3231 is committed! Better safe than sorry…

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants