Hello,
Odd issue, working on a form and eventually after a save the admin area switches to using site CSS and the frontpage is displayed inline in the designer tab. The action buttons across the top stop working (404 errors, etc shown on the site frontpage). Basically at this point nothing can be done any longer with the form. I've deleted and restarted the form twice and got the same thing.
[attachment=0]chrono.jpg[/attachment]
Basically the form is 3 container fieldsets with text and dropdown options in each.
Any ideas?
Odd issue, working on a form and eventually after a save the admin area switches to using site CSS and the frontpage is displayed inline in the designer tab. The action buttons across the top stop working (404 errors, etc shown on the site frontpage). Basically at this point nothing can be done any longer with the form. I've deleted and restarted the form twice and got the same thing.
[attachment=0]chrono.jpg[/attachment]
Basically the form is 3 container fieldsets with text and dropdown options in each.
Any ideas?
Hi lordsiris,
:-( Sorry, no - never seen that before. Are there any clues - error messages, etc? if you look at the page source?
Bob
:-( Sorry, no - never seen that before. Are there any clues - error messages, etc? if you look at the page source?
Bob
Bob,
No, no error messages at all, just loads with the CSS and stuff all wacky. When looking at the source of the designer i can see all the html from the frontpage with classes appended for the designer (guessing javascript adding them to elements). I'm at a loss right now, have to step away for a bit and look at it again later.
lordsiris
No, no error messages at all, just loads with the CSS and stuff all wacky. When looking at the source of the designer i can see all the html from the frontpage with classes appended for the designer (guessing javascript adding them to elements). I'm at a loss right now, have to step away for a bit and look at it again later.
lordsiris
Bob,
Please don't expend any more brain cycles on this, guess with the number of elements in the form and the javascript requests it appears to be triggering my mod_evasive module (thought i was whitelisted, but guess not). With mod_evasive disabled, the form admin area runs as expected. Hopefully no one else sees this same issue, but if they do at least they know its not your extension and to look at the server a little closer.
Kind regards,
lordsiris
Please don't expend any more brain cycles on this, guess with the number of elements in the form and the javascript requests it appears to be triggering my mod_evasive module (thought i was whitelisted, but guess not). With mod_evasive disabled, the form admin area runs as expected. Hopefully no one else sees this same issue, but if they do at least they know its not your extension and to look at the server a little closer.
Kind regards,
lordsiris
Hi lordsiris,
I hadn't head of mod_evasive before but - from a quick look - it would be triggered by ChronoForms. The number of inputs in the ChronoForms admin form editor can be very large indeed - several thousand is not uncommon. And the Ajax option which has been added to avoid problems with some other servers settings would probably trigger mod_evasive :-(
Maybe it is possible to whitelist the IP address (es) you use for development?
Bob
I hadn't head of mod_evasive before but - from a quick look - it would be triggered by ChronoForms. The number of inputs in the ChronoForms admin form editor can be very large indeed - several thousand is not uncommon. And the Ajax option which has been added to avoid problems with some other servers settings would probably trigger mod_evasive :-(
Maybe it is possible to whitelist the IP address (es) you use for development?
Bob
This topic is locked and no more replies can be posted.
