Skip Navigation

[Resolved] I am not able to edit, disable, or delete Toolset custom code

This thread is resolved. Here is a description of the problem and solution.

Problem:

The customer was unable to disable a custom code in Toolset settings due to a 403 error caused by their hosting security system, which blocked Ajax requests to admin-ajax.php, labeling it as an exploit attempt. The firewall prevented changes that required Ajax, such as disabling custom code or modifying certain settings within the Toolset plugin.

Solution:

We identified the issue as being related to the firewall blocking Ajax requests. The customer contacted their host to whitelist the necessary URLs, which allowed them to enable and disable custom code successfully. However, the issue persisted when making changes to the search and pagination section in a view. As a workaround, we moved the CSS from the Search and Pagination section to the Loop CSS, and the problem was resolved, allowing the customer to save the changes correctly.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Sao_Paulo (GMT-03:00)

Tagged: 

This topic contains 32 replies, has 3 voices.

Last updated by Mateus Getulio 2 months, 3 weeks ago.

Assisted by: Mateus Getulio.

Author
Posts
#2737930

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hello Andrew,

We performed a few more tests and confirmed the issue doesn't seem to be happening in other servers.

As a workaround, we moved the CSS section from the Search and Pagination to the Loop CSS. We appended the code to the end of it and everything seems to be working now.

We're able to save the search and pagination and the CSS is being correctly applied even though it has been moved to a different section.

Can you please confirm it is OK now?

Thank you,
Mateus

#2738109

Hi Mateus,

It is working now!

Just to confirm, you moved the CSS code from the Search and Pagination section to the Loop section below?

In the future should I start to do this for my other views as well?

Thank you to your team for the help with this!

Thank you,
Andrew

#2738532

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hi Andrew,

That's correct, I moved it a section bellow.

For other views, likely you won't face this issue since it is happening with a specific set of CSS rules, but in case it happens, you can move it to the loop CSS section, it gets applied to the search and pagination just the same.

Thank you for you patience and cooperation with getting it fixed.

Best,

#2742952

Thank you so much Mateus for your help in this.