WDE0053: Internal wixData error: Unknown error.

Hi, what is this???

Thanks

Hey @claudio-d-ambrosio

Can you, please, share more details when do you see this error message?

@jaroslavasd I also started getting this message this morning. My page has Selection Tags that filter a repeater; all of those selection tags suddenly broke this morning. However my text search continues to work.

To investigate the issue, I opened up the editor, and that is where i see the WDE0053 error message. I don’t see this message in the live site. However on the live site I see

 Uncaught (in promise)  ...wixCodeNamespacesAndElementorySupport.min.js

I have not made any code changes in a few weeks; Over the weekend I added some new rows to some Data Collections, but nothing that should be breaking

the same thing for me. I haven’t made any changes.

I’ve the same problem too, .contains doesn’t work, i change it to .eq and it works but i need it set to .contains

Thats interesting because my search query filters with .contains() works the ones with .hasAll() fails and throws the error

@info34178 Perhaps it’s a bug on wix’s end maybe? mine was working for ages and stopped around the same time as your problem

@millwards322 I very much think it is Wix’s fault

I have the exact same issue, no changes made. Mine is with .hasSome

Having the same issue here too. My code has both .contain and .eq
At least I know it’s not something I did.

@yisrael-wix Is there a way to escalate this issue? I raised some support tickets this morning but no resolution yet. I don’t want this issue to persist until tomorrow, where more paying subscribers of mine will have a broken experience

In order to assist you will need to provide more information. If you know where this is failing, post your code in a code block as stated in the Forum Guidelines . Explain what works, and what doesn’t work, when and where. Is this a new issue on code that worked before?

Please provide your site URLs so they can be evaluated.

My code has worked for several weeks with no changes, but I will post the relevant pieces in a moment. Here is a visual walk-through of the problem:

function selectionTagsOnChange(fieldToFilter, selectionTags) {
    saveNewPageNumber(1);
    var selectionTagValues = $w(selectionTags).value;
    addFilterAndTagsToGlobal(fieldToFilter, selectionTagValues);
    saveSelectionTagsToSession();
    loadDataToRepeaterForAllFilterCategories();
    console.log("Selection tag (Games) added/removed: " + selectionTagValues);
}

var debounceTimer;
export function searchBar_keyPress(event) {
 if (debounceTimer) {
        clearTimeout(debounceTimer);
        debounceTimer = undefined;
    }
    debounceTimer = setTimeout( function() {
        searchQuery = $w('#searchBar').value;
        saveSearchQueryToSession();
        loadDataToRepeaterForAllFilterCategories();
        console.log("Search (Games) conducted for: " + searchQuery);
    }, 200);

}
...
function loadDataToRepeaterForAllFilterCategories() {
    $w(dataset).onReady( function() {
         var selectionFilter = wixData.filter();

         for (var fieldCategory in filterCategories) {
             if (filterCategories[fieldCategory].length > 0) {
                selectionFilter = selectionFilter.hasAll(fieldCategory, filterCategories[fieldCategory]);
            }
        }

        selectionFilter = selectionFilter.contains(searchQueryColumn, searchQuery);

        $w(dataset).setFilter(selectionFilter)
            .then(() => {
                const pageCount = $w(dataset).getTotalPageCount();
                const totalCount = $w(dataset).getTotalCount()
                $w('#paginationInfo').text = `There are ${pageCount} pages.`
            })
        $w(dataset).refresh();

    });

}

When the Search Bar is typed into or the Selection Tags are clicked, they both call the same function, loadDataToRepeaterForAllFilterCategories(), so its strange that only one of them broke this morning

Hi all,

some of the WDE0053 errors that started this morning are caused by an issue in our system. Our team is currently working on resolving it.

Thanks least i know now I hadn’t done something wrong within my code, have you a rough timeframe it will be resolved?

All sorted now my end thanks :pray:

The issue has been resolved. If you continue experiencing any issues, please let us know.

I’m still having the same issue on my site. I put in a support ticket last night