DMXzone App Connect Support Product Page

Bugs?

Reported 30 May 2017 11:01:14
1
has this problem
30 May 2017 11:01:14 Dave Smith posted:
Hi,
I'm in the process of converting a platform to App Connect and have come across a couple of bugs...

1) Hide fails on repeat with Fuzzy Search. Trying to hide paging if no results are available via Fuzzy Search and the paging control still displays.

2) When you try to edit the Expression for the Fuzzy Search App Connect displays an error.

3) Various types of form inputs do not display, nor can be validated, in form tree view. Datetime Local for example.

4) Experiencing 'Header already sent' error in logs while using a query (outside of DMX, it's a custom query) which uses the GET method, that works fine with Data Bindings but fails with App Connect.

Have found a few others but failed to write them down at the time.

Any advice appreciated!

Thanks in advance,
Dave.

Replies

Replied 30 May 2017 13:04:11
30 May 2017 13:04:11 Dave Smith replied:
Update:

Problem #4 is related to the Security Provider Enforcer. When the PHP block for the 'SPE' is removed the query returns the expected results without the error....
Replied 30 May 2017 13:38:31
30 May 2017 13:38:31 Teodor Kuduschiev replied:
Hello Dave,

I have a few questions about the reported issues
1) How are you trying to hide the paging with fuzzy search exacty?

2) What expression are you using, which displays an error and what the error is?

3) Where do the form fields not appear? What do you mean they cannot be validated?

4) What is the custom script/query you are using, which causes this issue?
Replied 30 May 2017 18:20:04
30 May 2017 18:20:04 Dave Smith replied:
Hi Teodor,
I will send everything through to support. Will name the E-Mails related to their above question order.

Thank you.
Replied 31 May 2017 06:37:50
31 May 2017 06:37:50 Teodor Kuduschiev replied:
Hi Dave,
Thanks, for the emails - we will check these issues.
Replied 31 May 2017 10:22:51
31 May 2017 10:22:51 Dave Smith replied:
Thank you Teodor.
Replied 06 Jun 2017 09:51:05
06 Jun 2017 09:51:05 Dave Smith replied:
Morning,
Just checking in to see if there are any updates to the above?

Thanks and regards,
Dave.
Replied 15 Jun 2017 11:10:38
15 Jun 2017 11:10:38 Dave Smith replied:
Still having the same issues. Update appreciated if possible?

Thanks.
Dave.
Replied 15 Jun 2017 21:49:57
15 Jun 2017 21:49:57 George Petrov replied:

Hi Dave,

Here are some answers for you
Quote
1) Hide fails on repeat with Fuzzy Search. Trying to hide paging if no results are available via Fuzzy Search and the paging control still displays.


You really should be using the fuzzy search filter on your data source - so the easies in your case on a data view - and then just make a repeat region from this filtered data view. Do not add filters on the final repeat regions.

Quote
2) When you try to edit the Expression for the Fuzzy Search App Connect displays an error.

Make sure your data sources are the the highest level - so put them on top of the page.

Quote
3) Various types of form inputs do not display, nor can be validated, in form tree view. Datetime Local for example.

We will add the datetime input type in the next update

Quote
4) Experiencing 'Header already sent' error in logs while using a query (outside of DMX, it's a custom query) which uses the GET method, that works fine with Data Bindings but fails with App Connect.


You really should put the Security Provider Enforcer PHP code block as the very first thing on your page - do not put any custom code before it.

Hope it is a clear now.

Greetings,
George

Replied 15 Jun 2017 22:16:45
15 Jun 2017 22:16:45 Dave Smith replied:
Hi George,
Thank you for answers to the above really very appreciated.

Still having a problem with the below though:

QuoteYou really should put the Security Provider Enforcer PHP code block as the very first thing on your page - do not put any custom code before it.


This is the case with the page in question yet the error persists.. I have sent Teodor a code sample via the Support E-Mail. As I mentioned it works perfectly fine in all other circumstances but combined with 'SPE' it causes the error outlined above in my initial post.

Any further advice very appreciated.

Thanks again.
Replied 26 Jun 2017 10:42:20
26 Jun 2017 10:42:20 Dave Smith replied:
Still experiencing this issue with Security Provider Enforcer using custom queries contained within the page. The same thing happens with cURL requests. We use a lot of cURL requests to various API's so this does represent a real problem. Works fine with the old HTML 5 Data Bindings though.....?

Reply to this topic