Multiple Issues on 6.3.2 (Beta Channel)

Wappler Version : 6.3.2
Operating System : Windows 10
Server Model: NodeJS
Database Type: MariaDB
Hosting Type: localhost / Docker
Beta Channel

Expected behavior

What do you think should happen?

When upgrading from 6.0.2 to the latest version 6.3.2 I would expect the existing project to work the same but I have multiple problems with Data Views and Node single page app. The SPA issue has happened starting from 6.0.3.

Actual behavior

Data View Issue

Data Views with a filter applied now error out with 99+ errors in the network console, bringing the site to a crawl until a page refresh. I have a dropdown for a location value, then an input field to search multiple values based off of an API response and a repeat on the page to show all the values which narrow down based off of the search and dropdown selected. The single input field searches all values.

Error: (changed some values for public view):

Error parsing expression: Warehouse==select_location.value&&(Example1.contains(input_search.value, true) || Example2.contains(input_search.value, true) || Example3.contains(input_search.value, true) || Example4.contains(input_search.value, true) || Example5.contains(input_search.value, true)) TypeError: t is undefined

Filter applied: (Values blurred for public view):

Yes I noticed the filter has more fields than the error but I am reporting what it shows. This same filter works just fine and very quick on 6.0.2 (beta channel).

SPA Issue

Navigating between some pages do not navigate fully. I click on the nav button coming from the layout and the URL changes however the content of the previous page stays on the content side until I click on another nav button. This also happens from a button inside the content page that triggers a browser - Go To using internal link as the same as the layout navigation buttons. This was working fine on 6.0.2 but it has had issues on every update I have tried up until the very latest.

There are no errors happening in the browser console for this one to help troubleshoot.

Data View Search Issue

Using the above filter that has been working previously, now on the latest version when doing a search the repeat with the content inside that gets its data from the Data View no longer updates as I type in the data. I have to navigate to another page (“next” from the data view) and back then it works all the time until a page refresh.

How to reproduce

  • Detail a step by step guide to reproduce the issue
  • A screenshot or short video indicating the problem
  • A copy of your code would help. Include: JS, HTML.
  • Test your steps on a clean page to see if you still have an issue

For one example of the data view filter being used: (changed some values for public view)
This is pulled from the Data View - Filter - Code section

Warehouse==select_location.value&&(Example1.contains(input_search.value, true) || Example2.contains(input_search.value, true) || Example3.contains(input_search.value, true) || Example4.contains(input_search.value, true) || Example5.contains(input_search.value, true) || Example6.contains(input_search.value, true) || Example7.contains(input_search.value, true) || Example8.contains(input_search.value, true))

After further testing the SPA issue while writing this up it seems to happen when clicking on a button within the content page which that button has on it a click dynamic event that uses the browser element from the layout page, using the Internal option selected. It then correctly navigates to the next page. From that page when trying to navigate again either by using the button or by clicking on any of the nav buttons from the layout page the URL updates but the content from the page is still there and the new content is not. Click again on another nav button then it goes. As mentioned this started happening from 6.0.3 onwards. 6.0.2 worked without issue.

Thank you for any assistance. I would like to start using the newer versions with all the fixes and features but as needed I have been just downgrading back to 6.0.2 to make changes and publishing from there.

Can you send me the exact filter expression in a private message to me, it seems that you get an error while parsing the expression. I tested it with the edited expressions you posted but got no error.

Can you also tell me the exact versions of dmxAppConnect.js, dmxDataTraversal.js and dmxRouting.js. The versions can be seen in the comment within the file.

Hi Patrick,

Sent you a private message for the filter expressions. Here are the versions for those files.

App Connect
Version: 2.0.0-rc.3

App Connect Data Traversal
Version: 2.0.0-beta.7

App Connect Routing
Version: 3.0.0-beta.4

I have updated an update for the routing extension, you can also test it out.

An update for the data view that fixes an issue with the data not updating when filter changes. Not sure if it also fixes your specific problem with the filter.

dmxDataTraversal.zip (5.1 KB)

Hi Patrick,

I replaced those files in the project with those two .zip files you provided. I can confirm the issue of data not updating when filter changed is fixed. Unfortunately the filter is still having the problem showing the same error as well as the routing not routing correctly.

The versions seem to be showing correctly to the updated ones according to the browser console. I did clear cache and cookies as well.

App Connect Routing
Version: 3.0.0-beta.5

App Connect Data Traversal
Version: 2.0.0-beta.8

Thanks

Here an update for App Connect that fixes some small issues with the expression parser and better error handling in the parser when error occurs in a formatter function. Not sure if your filter error is fixed with this, please let me know if it helps.

dmxAppConnect.zip (114.8 KB)

Hi Patrick,

I’ve just sent you a PM with the updated information. For the filter errors, seems related to using the case insensitive option.

Fixed in Wappler 6.3.3

This topic was automatically closed after 47 hours. New replies are no longer allowed.