? Success

User tests: Successful: Unsuccessful:

avatar andrepereiradasilva
andrepereiradasilva
27 Feb 2016

Description

This PR adds searchtools to com_modules modal layout modules view.

Also, in normal layout:

  • improves responsive visual (mobile/tablet/desktop)
  • the acess column now orders by access level designation and not by access level id (it doesn't make a lot of sense order by the access level ID ... but makes sense order by the acess level DESIGNATION).
  • code improvements
Before PR (modal)

before-pr

After PR (modal)

after-pr

How to test

Normal view:
1. Install latest staging and apply this patch
2. Go to Extensions -> Modules
3. Check if search, filters, ordering and pagination are working properly
4. Test on mobile and tablet (ex: reduce browser width)

Modal view (test in frontend and backend):
1. Go to any content and click on "+Module" button on the editor to open the modal layout
2. Check if search, filters, ordering and pagination are working properly.
3. Test selecting a position or a module.

Observations

  1. Changed the modal default list when in the backend, now also shows other states (trashed, archved and unpublished). Why? To show the same states as "+Article" modal - consistency. In the frontend only shows enabled modules in the current language or in All language.
  2. Added a new /components/com_modules/models/forms/filter_modules.xml file to control the frontend searchtools fields (a similiar one already exists for the com_content in /components/com_content/models/forms/filter_articles.xml). Please tell if there are any problems with this.
avatar andrepereiradasilva andrepereiradasilva - open - 27 Feb 2016
avatar andrepereiradasilva andrepereiradasilva - change - 27 Feb 2016
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 27 Feb 2016
Labels Added: ?
57d952b 27 Feb 2016 avatar andrepereiradasilva cs
avatar brianteeman brianteeman - change - 27 Feb 2016
Category Administration Modules UI/UX
avatar brianteeman brianteeman - test_item - 28 Feb 2016 - Tested successfully
avatar brianteeman
brianteeman - comment - 28 Feb 2016

I have tested this item :white_check_mark: successfully on ba84682

Tested successfully - I still see zero value in the style box


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

avatar andrepereiradasilva
andrepereiradasilva - comment - 28 Feb 2016

I still see zero value in the style box

sorry, didn't understand your comment.

avatar brianteeman
brianteeman - comment - 28 Feb 2016

Dont worry about it - just personally dont see the need to add a style here
as I think it is better to be done in the module and just confuses the UI
here with a function right at the top that is not easy to understand or
even that most people will even have a clue what it is for

On 28 February 2016 at 13:06, andrepereiradasilva notifications@github.com
wrote:

I still see zero value in the style box

sorry, didn't understand your comment.


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

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

avatar anibalsanchez anibalsanchez - test_item - 29 Feb 2016 - Tested successfully
avatar anibalsanchez
anibalsanchez - comment - 29 Feb 2016

I have tested this item :white_check_mark: successfully on ba84682

Test OK


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

avatar brianteeman brianteeman - change - 29 Feb 2016
Status Pending Ready to Commit
avatar brianteeman
brianteeman - comment - 29 Feb 2016

RTC thanks


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

avatar joomla-cms-bot joomla-cms-bot - change - 29 Feb 2016
Labels Added: ?
avatar shubhamnba2009
shubhamnba2009 - comment - 2 Mar 2016

Hi, i want to contribute by testing this PR.
I have a ques and this may seem silly to some. What does the term latest staging means?

avatar alikon
alikon - comment - 2 Mar 2016

Means the latest "version" on the current branch "staging" it contains all
pr merged
On 2 Mar 2016 8:39 am, "Shubham Rajput" notifications@github.com wrote:

Hi, i want to contribute by testing this PR.
I have a ques and this may seem silly to some. What does the term latest
staging means?


Reply to this email directly or view it on GitHub.

avatar anibalsanchez
anibalsanchez - comment - 2 Mar 2016

The term 'staging' refers to something that's staged to be delivered.

In Joomla context, it is the name of all the latest accepted changes.

Then, to test a new change, you have to download from Github the latest
staging (click in the main repo Download button) and install that version
for testing.

Additionally, some PRs provide the whole Joomla to avoid the hassle of
patching.

Happy testing !
On Mar 2, 2016 8:39 AM, "Shubham Rajput" notifications@github.com wrote:

Hi, i want to contribute by testing this PR.
I have a ques and this may seem silly to some. What does the term latest
staging means?


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

avatar shubhamnba2009
shubhamnba2009 - comment - 2 Mar 2016

Just one more small doubt. I have installed joomla version 3.4.8 and using xampp to run it.
So lnstalling latest versiofromn means I have to download latest version github then remove 3.4.8 version and then install latest version of joomla? Is this the procedure or I can upgrade the 3.4.8 version without removing it? Thanks in advance

avatar anibalsanchez
anibalsanchez - comment - 2 Mar 2016

Both procedures are valid. However, if you upgrade from 3.4.8, then you are
also testing the upgrade.

  • In most cases, it is better to download the whole staging
    https://github.com/joomla/joomla-cms/archive/staging.zip and test only PRs.
    In this way, you optimize your time and it is easier to isolate cases and
    results.

  • If you are testing the upgrade itself, then you have to test the
    upgrading process. For example, this PR #9221 was hot because J3.5 is going
    to apply a new MySQL collation (utf8mb4) to certain tables. In this case,
    the PR has the steps to apply the upgrade, since it had several (and more
    comlex) steps and combined with other associated PRs.

According to my experience, it is simpler to start from staging.zip
https://github.com/joomla/joomla-cms/archive/staging.zip and test "easy"
issues:

https://issues.joomla.org/tracker/joomla-cms/?state=open&sort=issue&direction=desc&tests=3&easytest=1&stools-active=1
https://github.com/joomla/joomla-cms/archive/staging.zip

avatar brianteeman brianteeman - change - 12 Apr 2016
Milestone Added:
avatar brianteeman brianteeman - change - 12 Apr 2016
Milestone Added:
avatar wilsonge
wilsonge - comment - 12 Apr 2016

Can we solve conflicts here please :)

avatar joomla-cms-bot
joomla-cms-bot - comment - 13 Apr 2016

This PR has received new commits.

CC: @anibalsanchez, @brianteeman


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

avatar joomla-cms-bot joomla-cms-bot - change - 13 Apr 2016
Labels Added: ?
avatar joomla-cms-bot
joomla-cms-bot - comment - 13 Apr 2016

This PR has received new commits.

CC: @anibalsanchez, @brianteeman


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

avatar andrepereiradasilva
andrepereiradasilva - comment - 13 Apr 2016

ignore again the unit tests label, somehow my git changed the filename of the xcache unit test, i reverted.
Seems my git has some issues with the naming of that file, maybe because is windows...

Conflicts fixed. @brianteeman please remove again the label sorry.

avatar brianteeman brianteeman - change - 13 Apr 2016
Labels Removed: ?
avatar rdeutz
rdeutz - comment - 13 Apr 2016

Two questions:

1) Why was the type column removed?
2) Because it changes the interface, shouldn't this go into 3.6.x?

avatar brianteeman
brianteeman - comment - 13 Apr 2016

Dont know abut the removal of the type column (perhaps a mistake I only noticed the removal of the pages column which was meaningless) but this was only a "feature" added in 3.5.0 and to me its a bug fix/improvement

avatar andrepereiradasilva
andrepereiradasilva - comment - 13 Apr 2016

the type column is there is only hidden in tablet view.

avatar brianteeman
brianteeman - comment - 13 Apr 2016

As per your screenshot in the first post and a retest I just did right now which shows the same as your screenshot.
Type IS there in the search tools but is NOT there in the displayed columns which as shown in your own screenshots was there before

avatar rdeutz
rdeutz - comment - 13 Apr 2016

@brianteeman what was added in 3.5.0?

avatar brianteeman
brianteeman - comment - 13 Apr 2016

@rdeutz this a new plugin not present util 3.5.0 #8064

avatar rdeutz
rdeutz - comment - 13 Apr 2016

funny I have testet it, I am getting old :-), thanks

avatar andrepereiradasilva
andrepereiradasilva - comment - 13 Apr 2016

ok will check the type column, maybe the popup is a tablet size (width) and so it doesn't appear.

avatar andrepereiradasilva
andrepereiradasilva - comment - 13 Apr 2016

just tested, yes the popup is tablet size, i will change it.

avatar joomla-cms-bot
joomla-cms-bot - comment - 13 Apr 2016

This PR has received new commits.

CC: @anibalsanchez, @brianteeman


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

avatar andrepereiradasilva
andrepereiradasilva - comment - 13 Apr 2016

Done.

BTW not related to this PR, but the popups width shouldn't be fixed!

avatar brianteeman
brianteeman - comment - 13 Apr 2016

All good to me - will let @rdeutz decide on 3.5.2 or 3.6


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

avatar rdeutz
rdeutz - comment - 13 Apr 2016

I think this here is edge case and I plan to merge it into 3.5.2, because #9208, #9206, #9198 fixing bugs and should be merged in 3.5.2 and this one here would make the interface more consistent

avatar brianteeman
brianteeman - comment - 13 Apr 2016

thanks

On 13 April 2016 at 17:28, Robert Deutz notifications@github.com wrote:

I think this here is edge case and I plan to merge it into 3.5.2, because
#9208 #9208, #9206
#9206, #9198
#9198 fixing bugs and should
be merged in 3.5.2 and this one here would make the interface more
consistent


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#9232 (comment)

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

avatar andrepereiradasilva
andrepereiradasilva - comment - 13 Apr 2016

ok will fix the merge conflicts in the other 3 PR when i have time.

avatar rdeutz rdeutz - reference | 4cdf71a - 14 Apr 16
avatar rdeutz rdeutz - merge - 14 Apr 2016
avatar rdeutz rdeutz - close - 14 Apr 2016
avatar rdeutz rdeutz - change - 14 Apr 2016
Status Ready to Commit Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2016-04-14 05:02:47
Closed_By rdeutz
avatar rdeutz rdeutz - close - 14 Apr 2016
avatar rdeutz rdeutz - merge - 14 Apr 2016
avatar joomla-cms-bot joomla-cms-bot - close - 14 Apr 2016
avatar joomla-cms-bot joomla-cms-bot - change - 14 Apr 2016
Labels Removed: ?
avatar andrepereiradasilva andrepereiradasilva - head_ref_deleted - 14 Apr 2016
avatar rdeutz rdeutz - change - 1 May 2016
Milestone Removed:
avatar rdeutz rdeutz - change - 1 May 2016
Milestone Added:
avatar rdeutz rdeutz - change - 1 May 2016
Milestone Added:
avatar rdeutz rdeutz - change - 1 May 2016
Milestone Removed:

Add a Comment

Login with GitHub to post a comment