Redirects are randomly disabled

  • Resolved robertkk

    (@robertkk)


    2 months ago

    Hi, I have a form with many redirects and when adding requests, e.g. XML/JSON API and saving, the action randomly returns disabled for different redirects. When I change the option to enabled, nothing happens and sometimes new disabled ones are added.
    Random disabling of redirects occurs when we have more redirects.


    Additionally, when adding new redirects, the ids grow strangely, so in the case of adding dozens of new redirects, we get ids over 1000. Only after saving does the id normalize, but the problem with disabling random redirects appears.

    Problem cf7

    I also tested this locally on a clean WordPress and the same problem occurs.

    PHP: 8.1.29
    I have set max input vars to 10000.

    I am asking for quick help because it is blocking me from starting a new page.

    Thank you.

    • This topic was modified 2 months ago by robertkk.
    • This topic was modified 2 months ago by robertkk.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Kush

    (@kushnamdev)

    Hi there,

    Thank you for contacting us.

    We appreciate your cooperation in reporting the issue you’re encountering. We are sorry for the inconvenience, and we have confirmed the problem. A bug report has been created and forwarded to our product development team for review.

    What happens next?

    Our product team will evaluate the impact of this issue compared to other open bugs and upcoming features, and assign a priority level to the bug report.

    Our developers prioritize the highest-priority issues first, so we cannot provide a specific timeline for resolution at this time.
    If you have any additional information that may assist with prioritization or resolution, feel free to reply to this email.

    We will update you via this thread once the issue is addressed and a fix is released. You may also check the product’s changelog for updates and fixes included in each release.

    If you have any additional questions or concerns, please feel free to open another ticket. Again, we apologize for the inconvenience and thank you for your patience

    Thread Starter robertkk

    (@robertkk)

    Hi there,

    Thank you for your reply, but I would like to express my concerns about the approach you’re taking.

    Redirects are a core functionality of the plugin, and when dealing with a larger number of redirects, they simply do not work as expected. This is a critical issue, and I don’t quite understand how prioritization of bugs works in this case. I have purchased a plugin that isn’t functioning properly, and that should automatically give it the highest priority.

    For now, I’ve managed to partially mitigate the issue by setting max_input_vars to 30,000, but this greatly reduces server performance. Moreover, it’s hard to understand why such a high value is required to handle saving only 50 redirects. Even with this high max_input_vars setting, the issue with id numbering persists, and increasing this number further results in significant performance degradation. Why should so many variables be required when the recommended limit is usually much lower?

    At the moment, I have 50 redirects, but I plan to add more. Am I going to be forced to set max_input_vars to 60,000 or even higher? Many hosting providers are likely to block such high settings, which would create an additional issue. Please correct me if I’m wrong, but this seems like an unsustainable solution in the long term.

    I would also like to clarify that I disagree with the statement that it’s just a matter of prioritization. A fundamental functionality of the plugin is broken, and this must be addressed immediately. I’m probably not the only user facing these issues, as I’ve seen several other threads with similar complaints.

    I kindly request that you expedite the fix for this issue.
    Thank you.

    Plugin Support AndreeaR

    (@andreearadacina21)

    Hey @robertkk,

    I am sorry for the confusion our reply created. We treated it as a priority issue, and our development team worked on addressing it. We will let you know as soon as the solution will be released.

    Thank you for your patience!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.