Tibor Paulsch

Update: viewing the page source it seems that there is no extra CSS loading on the front end.

If I add the CSS from gf-form-multicolumn.css to my theme’s CSS it is fixed.

Looking at the source code of the plugin, it seems the CSS is only being registered, but never enqueued.

	public function enqueue_admin_preview_scripts( $styles, $form ) {
		wp_register_style( 'preview_stylesheet',
		                   plugins_url( '/public/css/gf-form-multicolumn.css',
		                                __FILE__ ), array (), $this->_version );

		return array ( 'preview_stylesheet' );

	}

• This reply was modified 4 years, 2 months ago by Tibor Paulsch.

Hi,

I have updated to 3.1.4 but layout is still broken, also after updating the CSS settings for the form.

Hope there is a fix..

Regards, Tibor

Update: I did some more testing, but it seems Boxzilla is blocking all ajax functionality for GravityForms (?)

Thanks Luke! Makes sense and works like a charm now.

Thanks for the quick reply Luke. Editor gives the same ‘Template file /blocks/block-name.php not found’ message.

Hi Daniel,

Thanks for taking the time to share your solution! I ended up using Easy Fancy Box instead of Featured Video Plus, but good to know this can work too.

Cheers, Tibor

Update: I just found out my added action to send an email with xml-file attached does work anyway. The mails were in my spam-box.

Hi Danny!

I’m playing around with the hf_formm_success hook and using the action you gave as an example, but nothing seems to happen; the form gets submitted, but the console gives an error:

HTML Forms: failed to parse AJAX response.

Error: "SyntaxError: Unexpected token < in JSON at position 0"

I tried to add another action, which gives the same error, but then with ‘Unexpected token A’.
No idea where the ‘A’ is coming from though :-S

What I’m actually trying to accomplish is that after submission, the submitted values are saved in a XML file (using SimpleXML) that then needs to be send as an attachment to a defined mail address (any tips are much appreciated :-)).

Last but not least: I really love the concept of this plugin! Thx!

I’m missing it on bulk-editing a custom post type; on posts it’s there.

Great job Kyle! Much appreciated!

Exactly the same issue as Sean Dempsey describes; downgrading to 1.6.3.2 unfortunately had no effect.

The less generic the function name the better, but 30.000 active installs later and without complaints I would probably also not bother too much ??

After nine months I am also not sure anymore ??

I guess I did not recognize “disable_emojis” as being a prefix.

Update: looking at it again, I still would not see it as a prefix in

function disable_emojis()

Yep; no matter what content type.

I have only one connection; a custom post type to pages. I’ll send you a screen shot of the error I get in the console. Hopefully that will shine a light ??