Problems after updated Joomla 3.6 and Fabrik 3.5. Urgent Help please!!!

[cheesegrits]

1. List http://www.fisiolar.pt/index.php/pt/tarefa (online version) not opening and retrieving "syntax error, unexpected end of file"
   1. List /index.php/pt/tarefas (Akeeba backup on your side) filters and php plugins do not work,

This is now fixed in github, and working on my local copy.

1. Auto fill in form http://www.fisiolar.pt/index.php/pt/tratamentos-fisioterapia/form/11/ for the element name "valor_fisiot" is not working

You had an error in a load JS event, trying to set the style on a text area. That JS error short circuited the loading of Fabrik JS. Should be fixed on your site, and works locally now.

List http://www.fisiolar.pt/index.php/pt/sessoes-de-tratamento-secretariado/pacotes-de-sessoes not opening (Warning: Header may not contain more than a single header, new line detected in...)

If it's the ORDER BY mysql error I was seeing on your site, that was fixed in github recently. I'm running latest github code on my copy of your site, it's working.

Filter trigger on change not working for any list - see as example: http://www.fisiolar.pt/index.php/pt/contactos/contactos-inbound

Regardless of which method you select, if the filters include either a range filter, or a checkbox / multiselect filter, we will set it to "Submit button", simply because there is no way to properly handle "change" submission when using filters which involve more than one change. You wouldn't want it auto-submitting when you click one checkbox, if you want to search for two or more. Or when you change just one part of a range.

In Fabrik administrator forms page (http://www.fisiolar.pt/administrator/index.php?option=com_fabrik&view=forms) there are 4 pages of forms when only 2 are needed.

I'll put that on my list to look at when I get time.

-- hugh

 

[gnavarro]

Hugh,

I've tested all the issues and they are all working again. Thanks!

You've forgot the issue #1:

Please see the following detail view:

http://www.fisiolar.pt/index.php/pt/profissionais-saude/candidaturas/details/3/1965

Knowing that the element 'categoria' when = "Enfermagem" = 16(raw)(http://www.fisiolar.pt/administrator/index.php?option=com_fabrik&view=element&layout=edit&id=586)

If you look into my JS config for the element 'categoria' (see attached img) you'll see as an example that I have... on load: when element "caregoria" != "16", hide group "Candidaturas (Experi?ncia Fisioterapia)"...

... And you can see that this group that corresponds to the Label " N?vel de Experi?ncia Adquirida em Fisioterapia" is not hiding on load!

In Fabrik previews versions this was ok, so something has changed!

I appreciate your help on resolving this issue.

 

[cheesegrits]

Haven't forgotten, just haven't got time for it today, I already put about 4 hours in on this stuff today. I'll get to it tomorrow some time.

-- hugh

 

[gnavarro]

Ok Hugh. Thanks!

 

[cheesegrits]

OK, I thin I've resolved that.

Several issues ...

Your 'colaborador' element had a JS event with the code "fb_candidaturas___colaborador.value ="0";", which is just wrong. I replaced it with this.update('0') on your live site..

There was another this.setStyle('...') load event, which I've fixed on your live site. That would have worked in a previous version of Fabrik, as for 'load' events, 'this' used to be the DOM element rather than the Fabrik element object (it was a mistake on our part), so we fixed that so 'this' is now the Fabrik element ... but that breaks bacward compat, so you need this.element to get the DOM element. So if you have any other pages that do that, you'll need to change them. Use Chrome, and the Developer Tools, so you can see JS errors thrown on the page, which will tell you when that happens.

There was also an issue with Fabrik's handling of dropdown values in a details view, which I've fixed in github.

-- hugh

 

[gnavarro]

Hugh,

I've tested and everything's ok. Thanks!

Other issue:

ISSUE 7

- The form http://www.fisiolar.pt/index.php/pt/formulario-de-recrutamento the JS only works correctly only in desktop, because on mobile it gets messed up. What I can tel is that for the element "categoria" the JS functions are choosing the wrong raw value.

Example:

Supposing we select categoria = "Terapia da Fala" for both Desktop and mobile. The results are:

• Desktop: "categoria" label = Terapia da Fala | Value = 15
  • (Correct and is hiding what it's supposed to)
• Mobile: "categoria" label = Terapia da Fala | Value = 11
  • (Wrong and is hiding the corresponding to value 11)

ISSUE 8

When in any List that has an element with a custom link using ajaxify links:

1. The map element inside the model window doesn't show the map;
   1. See list http://www.fisiolar.pt/index.php/pt/pacientes column "paciente"
2. The JS is not hiding the elements inside any model window;
3. After closing the model window the clicks on the drop-down button on the list stop bringing down the menu (if you reopen the model and close it the button starts to work again).
4. If you apply filters in any list the modal windows show different forms or shows the form in editing mode instead the details view.

I appreciate your help resolving these ones. Thanks

 

[cheesegrits]

Hmmm, 7 is going to be a pig to debug, and right now I can't actually do it. To debug mobile pages, you have to hook the phone up to a computer running Chrome with USB ... and I recently got an HTC 10 and gave my trusty HTC 1 M7 to a friend ... and the HTC 10 has USB C ... and the wall charger / cable I have is USB C to USB C ... and my car charger has a hard wired cable ... so I don't have a USB 2/3 to USB C cable I can use to hook my phone up. I'm not about to pay local brick & mortar store prices for cables, so I'll have to get it through Amazon Prime (I just ordered it). But it's a holiday weekend, so that won't get here till Tuesday of next week.

Out of interest, can you try changing the event you use for that from 'click' to 'change', see if that has any effect. From what I can tell, the issue seems to be with timing of the event. We used to see issues with IE on the desktop with 'click' events, where they would receive the value of the dropdown prior to it changing, and using 'change' rather than 'click' would fix that.

For 8, I'll try and find some time over the weekend to look at it, but it's a holiday weekend in the US, and I'm heading to South Carolina to spend some time with my wife (she's living there for a while, looking after her very elderly grandmother). It's an 8 hour drive. So it'll probably be Tue or Wed of next week before I can devote much time to it.

-- hugh

 

[gnavarro]

Ok Hugh. Have a nice trip to South Carolina. Thanks for the update.

Sent using Tapatalk

 

[cheesegrits]

Did you try using the 'change' event?

-- hugh

 

[gnavarro]

Hugh,

Yes. It corrected the issue 7

Do you have any update about issue 8?

 

[cheesegrits]

I'm still in South Carolina, I'll probably be driving home tomorrow. According to Amazon, my cable was delivered today.

-- hugh

 

[cheesegrits]

Issue 8, points 1, 2 and 3 ... as I mentioned several times ...

There was another this.setStyle('...') load event [...] So if you have any other pages that do that, you'll need to change them. Use Chrome, and the Developer Tools, so you can see JS errors thrown on the page, which will tell you when that happens.

And again. this was a this.setStyle() on a textarea load event, which needs to be this.element.setStyle(). I've fixed and tested locally, but not on your live site. And again, this was throwing a Javascript error, which was short circuiting all the other JS in that modal load (like running other JS events, showing the map, setting up the code that runs when you close the window to re-enable the dropdowns, etc).

BTW, is there any particular reason you are setting the style on textareas with a JS event, rather than with a custom CSS?

-- hugh

 

[gnavarro]

Hugh,

It's strange because I did the change for all this.setStyle('...') to this.element.setStyle('...') earlier when you first told me to! I've checked that same change again for the list http://www.fisiolar.pt/index.php/pt/pacientes and it's this.element.setStyle('...') for the element 'obs_fisiolar' and the issue 8 maintains.

I used the chrome inspection to see the JS errors but I don't know how to analyse it and obtain an action to correct the issues. Please see the attached img to confirm if I'm looking to what I should.

BTW, is there any particular reason you are setting the style on textareas with a JS event, rather than with a custom CSS?

I'm using the JS event because I've never used a custom form CSS before and it was working ok... that's why. Probably is more consistent to use custom form CSS... I've to read about it and try to implement it but I believe that is not so simple as JS event.

Can you please look directly to my online version and debug this page because by the JS errors I'm seeing there are more problems generating the issue 8.

Thanks in advance!

 

[gnavarro]

Friendly Bump!

 

[cheesegrits]

Haven't forgotten you, I've been working on it, just haven't resolved it yet.

-- hugh

 

[gnavarro]

Hugh,

The Fabrik update 3.5.1 is available. Should I update it, or for now wile debugging leave it as it is? Also do you have any update for me?

 

[gnavarro]

Friendly Bump!

 

[cheesegrits]

Working on it.

-- hugh

 

[gnavarro]

By the time this is taking I suppose that by debugging my site a lot of issues and bugs were found and some corrections are being made to Fabrik core installation files

Any update yet? It's important to have all declared issues resolved as soon as possible to test and see if other found issues will be also corrected or if other new ones appear with the implemented resolution.

Thanks once more for your support

 

[gnavarro]

Friendly bump!