Skip to content
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

Media Manager-validation required on delete button #4777

Closed
wants to merge 3 commits into from

Conversation

jainrimjhim20
Copy link

mediamanager

@superfoght
Copy link

Confirmed. I get a message now :) http://screencast.com/t/XJGLzlTVj

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

@dimitargsg
Copy link

@test Tested this successfully.

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

@deepanshu-jha
Copy link

The issue is related to the usage of JToolBar::appendButton() function in com_media as there is no such boolean parameter available(true or false) which if passed can generate an alert box asking for making a selection from the list. Where as in case of other pre-defined JToolBar buttons, like publish , unpublish etc. the alert popup can be easily implemented by simply passing the boolean parameter.

The important point in this case which needs to be enlightened is that the delete button in this issue is not the pre-defined JToolbarHelper::deleteList(); but it is a custom JToolBar::appendButton(); button. So, the work around for this would be customizing the javascript code in the component but not in the library files.I am working on it.

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

@jissues-bot jissues-bot changed the title Media Manager-validation required on delete button #4775 Media Manager-validation required on delete button Oct 17, 2014
@brianteeman
Copy link
Contributor

Based on the last comment I am setting this one as Needs Review by maintainers

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

@orware
Copy link
Contributor

orware commented Oct 18, 2014

The solution for this one seems to be ok (and I was able to test it successfully as well).

The current Travis CI build failure being shown on the Pull Request page for this one seems to be unrelated to the actual patch itself.

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

@sparkosis23
Copy link

I was able to reproduce the bug: in Media Manager, click the Delete button with nothing selected. It reloads like it's doing something with no error or confirmation of what happened. After applying the patch, tested again and clicking Delete button without anything selected results in error box "Please first make a selection from the list". Bug fixed.

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

@Hackwar
Copy link
Member

Hackwar commented Feb 3, 2015

There is an error in the unittests with your changes. Please see if you can fix those.

Merge remote tracking branch 'upstream/staging'
@wilsonge
Copy link
Contributor

I can't see anything wrong with this - removing from needs review. Can I have one test here to confirm the patch is still required and works as expected before it goes RTC please?


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

@brianteeman
Copy link
Contributor

@wilsonge is the comment about unit tests no longer valid either?


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

@wilsonge
Copy link
Contributor

I don't think so. There are no unit tests failing with this and there are none covering this kinda stuff anyhow. I think Dmitris will throw a small hissy fit about using script tags rather than using JDocument but given the age of this PR i"d rather merge this if it works and then get him to do that separately

@MATsxm
Copy link

MATsxm commented Apr 12, 2016

success with BEFORE:
screen shot 2016-04-12 at 18 15 51

then AFTER:
screen shot 2016-04-12 at 18 16 19


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

@MATsxm
Copy link

MATsxm commented Apr 12, 2016

I have tested this item ✅ successfully on 97f89dc


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

@brianteeman
Copy link
Contributor

I have tested this item ✅ successfully on 97f89dc

For consistency this is correct.

Personally this type of functionality should be labelled "you are an idiot why did you click without selecting"


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

@brianteeman
Copy link
Contributor

RTC
Not a new feature as this functionality is present everywhere else so setting 3.5.2 milestone


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

@joomla-cms-bot joomla-cms-bot added the RTC This Pull Request is Ready To Commit label Apr 13, 2016
@brianteeman brianteeman added this to the Joomla 3.5.2 milestone Apr 13, 2016
@rdeutz
Copy link
Contributor

rdeutz commented Apr 13, 2016

@rbsl-rimjhim could you check the merge conflicts, thanks

@wilsonge
Copy link
Contributor

Robert as this PR is 18 months old think this is one of those cases where we can do it ourselves ;)

@rdeutz
Copy link
Contributor

rdeutz commented Apr 13, 2016

Feel free to do it :-P

@brianteeman
Copy link
Contributor

I will do it now

@brianteeman
Copy link
Contributor

See #9891


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

@joomla-cms-bot joomla-cms-bot removed the RTC This Pull Request is Ready To Commit label Apr 13, 2016
@wilsonge
Copy link
Contributor

Merged #9891

@wilsonge wilsonge closed this Apr 13, 2016
@rdeutz rdeutz modified the milestones: Joomla 3.5.2, Joomla! 3.6.0 May 1, 2016
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.

None yet