Viewing 15 replies - 1 through 15 (of 16 total)
  • Plugin Author fried_eggz

    (@fried_eggz)

    Hello,

    So you are using Sticky List on a form that creates a user? This is untested since Gravity Forms natively support adding and updating users and WordPress has a nice API for listing them.

    Could you please describe your use case?

    Thread Starter hatchitdesign

    (@hatchitdesign)

    Hi fried_eggz,

    Thanks for your quick response.

    Yes I’m using Sticky List, and here’s why: When the form is submitted the User is purchasing a Service via PayPal. Once paid, an Entry is created and a User is Registered. I’m renaming ‘Entries’ as ‘Orders’ on the frontend.

    I’d like the User to log in and view their own Order (Entry) – which has a field set to Pending. They cannot Edit this Order/Entry.

    I then need to give the Admin ability to Edit this and other Entries. Basically, they will change the ‘Pending’ status to ‘Complete’ or ‘Cancelled’.

    Hope that helps!

    Thanks

    Plugin Author fried_eggz

    (@fried_eggz)

    Sure, sounds clear enough. To get this working you could use two separate forms, one for user sign up and one for ordering services.

    I will however do some testing on a user registration form to see if we can get this working the way you set it up.

    Plugin Author fried_eggz

    (@fried_eggz)

    One more thing. Could you export the form and link to it here. That way I can import it into my dev environment and run some tests.

    Thread Starter hatchitdesign

    (@hatchitdesign)

    Thanks fried_eggz, appreciate all your help!

    https://unlocked.hatchitdesign.com/gravityforms-export-2015-01-27.xml

    Plugin Author fried_eggz

    (@fried_eggz)

    Thanks for the upload. You are using a multi page form. Paged forms are currently not supported in Sticky List. Se the Known Issues section of the plugin page.

    Multi page form support is on the roadmap but there are other issues that need fixes and there is no ETA for this feature.

    Try changing your form to a single page form and see if that works.

    Thread Starter hatchitdesign

    (@hatchitdesign)

    Hi fried_eggz,

    Thanks for your suggestion. I tried this but unfortunately, it didn’t solve the problem and the Error still appeared.

    Do you perhaps have any further suggestions I could try?

    Plugin Author fried_eggz

    (@fried_eggz)

    Hmm, I will run some tests and post back.

    Same error – mine is related to the page redirect… At least its stopping that from occurring. I still get my confirmation but the form should redirect to another form based on certain criteria getting met. That does not occur – if I deactivate Sticky the redirection works. Hopefully that gives you some direction. If helpful it did work at one point its only been in the last 2-3 version this broke.

    Warning: nl2br() expects parameter 1 to be string, array given in /home/jaywolfe/public_html/wag/cms/wp-content/plugins/gravityforms/common.php on line 756

    Thread Starter hatchitdesign

    (@hatchitdesign)

    cmisak you are a genius! It was the redirect that was causing the error.

    Once I removed this the form worked fine.

    Thanks all!

    Plugin Author fried_eggz

    (@fried_eggz)

    I’m currently working on this. It should be possible to use a redirect.

    Plugin Author fried_eggz

    (@fried_eggz)

    This has now been fixed and a new version that fully supports redirects will be uploaded tonight.

    Thread Starter hatchitdesign

    (@hatchitdesign)

    Fantastic, thanks fried_eggz!

    Plugin Author fried_eggz

    (@fried_eggz)

    The redirect issue has been solved and a new version (1.1.7) has been uploaded.

    cmisak

    (@cmisak)

    Awesome! Thank you for working on that. Not a critical issue but have you seen that after an update you have to deactivate than reactivate again. Otherwise it just renders the shortcode.

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘nl2br() expects parameter 1 to be string, array given in /home/hatchitd/public_h’ is closed to new replies.