• SPForm strange behavior#

  • Susann Reply #1, 6 months ago

    Reply
    Im trying to find out why SPForm doesn t work.
    Using Revo vers. 2.1.5 and SPForm 3.2.0 rc1.
    1. Snippet call in Contact Us works only with [[SPForm and not with [[!SPForm].
    2. Logged in the preview is fine of "Contact us! and "Thank You" page.
    But if its activated it goes to my 404 error page instead of the correct id of the Thank You page.
    Of course no email was sent.
    Should I better reinstall SPForm or possible just try out an other server ?
    The latest error from the log :mysite.com/core/model/modx/processors/element/propertyset/get.php : 82) PHP warning: Invalid argument supplied for foreach()
    I thought SPForm is exactly what I need for my site but it should work.

    Any ideas how to solve this ?






  • BobRay Reply #2, 6 months ago

    Reply
    If you clear the error log and visit the contact firm, does that error come back?

    Make sure you have this in the <head> section of the page template:

    <base href="[[!++site_url]]" />


    Also, make sure the "thank you" page is published.

    [Update] I just tested and it works for me with MODX 2.1.5 either logged in or not. Actually, it only works for me with the *uncached* version.

    [[!SPForm]]


    BTW, SPForm 3.2.0-rc2 is available. I don't think it will fix your problem, but it can't hurt to try it. I'd suggest uninstalling and removing the current version first (right-click on it in Package Manager and select "Remove Package"), since you're having trouble with it.


  • Susann Reply #3, 6 months ago

    Reply
    Thanks! Good to know it works in version 2.1.5
    I will try it on an other server with the latest version.
    I just would like to know why I can t use the cached version of SPResponse and SPForm on my site.





  • Susann Reply #4, 6 months ago

    Reply
    Can´t believe it but it works at my other server.


  • BobRay Reply #5, 6 months ago

    Reply
    You could have a corrupted file either in SPForm or in MODX at the problem site.

    I can't think of a server configuration that would cause that problem, but that doesn't mean there isn't one.