forced use of mootool by calling JHTMLbehavior::modal on all items views about k2 HOT 7 CLOSED

Hi. Unfortunately the Joomla! modal is required for front-end editing. The check that is there checks three things:

1. If user is logged in modal is loaded since it is required for front-end editing.
2. If we are on an item page, modal is loaded in order to open the item image in modal.
3. If there is an extra field in page that requires the Joomla! modal ( extra fields of type link which open in lightbox for example ).

If none of the above is true, then you should not get the modal loaded in your page.

from k2.

I don't think that this logic is proper :

1- test if the user is not a guest is not sufficient, for example on a
site, where you have 'registered' user and no front-end editing. So the
test 'a user is not a guest' => it should be able to edit, is not correct
in all cases

2- if a K2 site, use bootstrap modal, or any other modal mechanism (e.g
NoNumber), then modal is handled outside. So decision to include
Behavior.modal, should be made at the template override level.

or controlled by this define flag of yours.

3- same for any lightbox image

In my case, I was able to inject bootstrap and jQuery, long before Joomla
3, but when I'm trying to get ride of mootool in the front-end, this is
quite the last remaining place where this is injected by force in this code.

I don't think that I'm alone trying this I'm the Joomla 2.5 path.

On Tue, Sep 10, 2013 at 3:29 PM, Lefteris Kavadas
[email protected]:

Hi. Unfortunately the Joomla! modal is required for front-end editing. The
check that is there checks three things:

1. If user is logged in modal is loaded since it is required for
   front-end editing.
2. If we are on an item page, modal is loaded in order to open the
   item image in modal.
3. If there is an extra field in page that requires the Joomla! modal
   ( extra fields of type link which open in lightbox for example ).

If none of the above is true, then you should not get the modal loaded in
your page.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-24159250
.

from k2.

I don't disagree in total with you but there are somethings to consider:

1. Removing the modal from the item view will make images open in the current tab. This will confuse most of the users who will come back here to post an issue. This will also happen for extra fields of type links.
2. Not all users are familiar with JavaScript so they can add their own lightbox.

To summarize i do agree with you that we need to cut off mootools completely, but doing this now will generate a lot of confusion to the users and will make current sites look broken.

from k2.

I understand that very well
(same reason as raising the issue instead of patching the code directly and
monitor on every commit and upgrades).

Could it be possible to introduce a new constant and a logic shortcut, that
will get over this if statement for people that use explicitly this new
constant (or define) so existing code will continue to work unmodified and
people could choose to set it by any means (perhaps not even need to
escalate it to a configuration seen in the component options).

A first though the already referred constant was about that, and it is not
very documented, adding an other one… ;-)

Regards

On Tue, Sep 10, 2013 at 5:34 PM, Lefteris Kavadas
[email protected]:

I don't disagree in total with you but there are somethings to consider:

Removing the modal from the item view will make images open in the
current tab. This will confuse most of the users who will come back here to
post an issue. This will also happen for extra fields of type links.
2.

Not all users are familiar with JavaScript so they can add their own
lightbox.

To summarize i do agree with you that we need to cut off mootools
completely, but doing this now will generate a lot of confusion to the
users and will make current sites look broken.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-24170308
.

from k2.

An option in K2 paramaters is a possible solution, but this is something i cannot decide on my own. I need to talk with the rest members of the team.

from k2.

The Joomla modal will be removed for non editing features in K2 2.7.0 thus resolving this issue.

from k2.

would be perfect !!!!

Thanks in advance.

from k2.