Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter jsolties

    (@jsolties)

    Hi Benjamin, Thank you so much for your response. I had our website contractor look into it and this is what he said:

    This is most definitely a server issue from what I can see. I read through the article at https://wpstackable.com/blog/how-to-fix-the-block-editor-error-updating-failed-error-message-the-response-is-not-a-valid-json-response/ and knew pretty easily that none of those options would cause the issue you’re getting on your site. Which lead me to their last point for “if none of the other solutions work”. So I opened the page, and added a Stackable block to the page and opened up the inspector as they suggested. Everything looked good until I hit publish, which is when the following 403 error does occur:

    Upon clicking the error note it brings up the exact cause which is something to do with GoDaddy. The firewall is blocking it as a XSS attack.

    From the screenshot he sent, looks like it says XSS014 on the GoDaddy error note. He suggested I reach out to you all first since you probably have tons of people on GoDaddy to see if you had heard of this issue before or knew what we need to tell GoDaddy.

    I’ve never seen the issue appear on a page that doesn’t have a Stackable block. And it’s not always. At first, I thought the issue was only with accordion folders but then it did it with the buttons too. I thought maybe it was with newly created pages vs updated existing pages, but I couldn’t find a pattern there either. We did migrate our server earlier this spring, and I think that’s when I began noticing this issue.

    Thank you!

    @jthomasama I had the same question and asked via their support ticket. I asked: “I was wondering if there was a way to hide all rows and only display the row when it’s searched for in the search bar. Visitors to our site will only really need to see what they’re looking for and I don’t want to overwhelm them with other options that don’t apply to them.”

    Here’s how they responded:

    We have some custom codes which will hide the full table until the user select the custom filter.

    After creating the table you need to add the css below to your tables custom css:

    table#footable_303:not(.ninja_has_filter) tbody, table#footable_303:not(.ninja_has_filter) tfoot, table#footable_303:not(.ninja_has_filter) .footable-header {
    display: none !important;
    }

    You need to change the #footable_3o3 with your tables id. See screenshot

    now add the code below to your tables custom javascript:

    $table.removeClass(‘ninja_has_filter’);

    Hope this helps. It certainly saved me!

Viewing 2 replies - 1 through 2 (of 2 total)