ciateam
Forum Replies Created
-
Forum: Plugins
In reply to: [Advanced Custom Fields: Extended] Struggling to get AJAX button to workI don’t suppose you have a “worked example” somewhere showing how this all fits together?
I’m confused mostly by the order of each part of the process and how it all “talks to each other”.
I can see pushing the button is triggering the ajax call, but how do I “use that”? Where do I use it?
Even in the simple example you provided:
https://thisinterestsme.com/simple-ajax-request-example-jquery-php/There’s a user asking the same kind of thing:
Dan Statham
Something I have not seen an answer for: where does the $.ajax(… go? And how is it invoked?It’s assumed people already understand, but some, like myself aren’t familiar with the process enough to figure it out.
Again this is new to me and most information out there doesn’t really explain it very well, and because WP has it’s different handling of AJAX and ACFE has it’s own functions for handling them, it’s a minefield when you’re trying to start from scratch randomly googling.
I don’t mean to be a pain, but dissecting a working example is always the best way for me to understand.
Thanks again.
Forum: Plugins
In reply to: [Advanced Custom Fields: Extended] Struggling to get AJAX button to workAhh I totally misunderstood how this worked.
Thank you for the detailed reply as usual Konrad, I’ll get to reading.
Mtorrance, thank you very much for your efforts in looking into this further, apologies for the delay saying it, haven’t had much time to even investigate myself.
I hope they get an official fix in soon.
Take care
I’ve had no response in the WPBakery forum.
Artem, I appreciate the problem may not be caused by your plugin directly, however, it is the only plugin that causes this behaviour in the WPBakery plugin.
No other plugin seems to have issue with the WPBakery plugin incorrectly using that hook. I’m not even sure why WoodySnippets would cause that conflict, but maybe there is a way you could look into seeing what in your plugin triggers this, and think of a workaround?
Given that we don’t seem to be getting a solution from them
Thanks again
Forum: Plugins
In reply to: [Advanced Custom Fields: Extended] Column Behaviour in BackendHi, sorry for not explaining, those are tooltips through another ACF plugin.
I turned all the plugins back on before I took the screenshots, since disabling them had no effect.
The issue persists in firefox and in chrome with no extensions enabled.
No JS errors only warnings relating to https being disabled (because the plugin is disabled)
I’ve made a clone of the site if you want the login?
https://fbuild.clientsinabundance.com/testarea/wp-login.php- This reply was modified 5 years, 8 months ago by ciateam.
Forum: Plugins
In reply to: [Advanced Custom Fields: Extended] Column Behaviour in BackendThanks again for the quick response.
Here are the screenshots:
Test columns in new field group seemed to ignore columns too, with / without endpoint.
https://nimbusweb.me/s/share/4692267/7y5d17ywlkf6wy0uf8ps
Also, changing any of the settings for the field group: Style, position, label placement, instructions placement does nothing for the backend.
I’d be happy to give you access to the staging site if that helps?
- This reply was modified 5 years, 8 months ago by ciateam.
Forum: Plugins
In reply to: [Advanced Custom Fields: Extended] Column Behaviour in BackendThis is so weird. I have disabled every plugin except ACF pro and ACFE and switched to the Twenty Twenty theme and it’s still doing it.
No additional css in customise or new functions in functions.php, I don’t understand where this styling is coming from.
If I disable ACFE the metabox styling goes away (obviously because columns no longer work, the behaviour is different), but it’s the only plugin that makes a visual change to the backend when disabled no matter which theme I use.
Any ideas?
- This reply was modified 5 years, 8 months ago by ciateam.
You are an awesome person, thanks very much for your prompt and detailed responses.
Take care!
Thank you very much for the detailed response, I really appreciate it.
With regards to the filter solution:
add_filter('acfe/form/load/form=my-form', 'my_acfe_form_user_args', 10, 2); function my_acfe_form_user_args($args, $post_id){ // Disable current post id $args['post_id'] = false; // return return $args; }I have multiple forms on multiple pages with different purposes, will I have to manually add filters for each form, or is there a way I can catch them all with one filter?
Thanks very much for your time and patience.
Ok.
I’ve posted this in the WPBakery support forum.
https://ww.wp.xz.cn/support/topic/conflict-with-woodysnippets-plugin-frontent-editor/
Any ideas on a possible solution (if I get no luck on the other forum)?
Thanks again
“You turned on the mode and reproduced the error, but nothing appeared in the debug.log file after that?”
Yes that’s exactly right.
**actually turns out my host redirects error logs to a specified folder**
So the error display is below
[08-Sep-2020 19:03:00 UTC] PHP Fatal error: Uncaught ArgumentCountError: Too few arguments to function WINP_Execute_Snippet::executePostSnippets(), 1 passed in /home2/clienub3/public_html/fbuild/1599226458833/wp-includes/class-wp-hook.php on line 287 and exactly 2 expected in /home2/clienub3/public_html/fbuild/1599226458833/wp-content/plugins/insert-php/includes/class.execute.snippet.php:75 Stack trace: #0 /home2/clienub3/public_html/fbuild/1599226458833/wp-includes/class-wp-hook.php(287): WINP_Execute_Snippet->executePostSnippets(Object(WP_Post)) #1 /home2/clienub3/public_html/fbuild/1599226458833/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters('', Array) #2 /home2/clienub3/public_html/fbuild/1599226458833/wp-includes/plugin.php(544): WP_Hook->do_action(Array) #3 /home2/clienub3/public_html/fbuild/1599226458833/wp-content/plugins/js_composer/include/classes/editors/class-vc-frontend-editor.php(372): do_action_ref_array('the_post', Array) #4 /home2/clienub3/public_html/fbuild/1599226458833/wp-content/plugins/js_composer/include/classes/edito in /home2/clienub3/public_html/fbuild/1599226458833/wp-content/plugins/insert-php/includes/class.execute.snippet.php on line 75 [08-Sep-2020 19:03:12 UTC] PHP Fatal error: Uncaught ArgumentCountError: Too few arguments to function WINP_Execute_Snippet::executePostSnippets(), 1 passed in /home2/clienub3/public_html/fbuild/1599226458833/wp-includes/class-wp-hook.php on line 287 and exactly 2 expected in /home2/clienub3/public_html/fbuild/1599226458833/wp-content/plugins/insert-php/includes/class.execute.snippet.php:75 Stack trace: #0 /home2/clienub3/public_html/fbuild/1599226458833/wp-includes/class-wp-hook.php(287): WINP_Execute_Snippet->executePostSnippets(Object(WP_Post)) #1 /home2/clienub3/public_html/fbuild/1599226458833/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters('', Array) #2 /home2/clienub3/public_html/fbuild/1599226458833/wp-includes/plugin.php(544): WP_Hook->do_action(Array) #3 /home2/clienub3/public_html/fbuild/1599226458833/wp-content/plugins/js_composer/include/classes/editors/class-vc-frontend-editor.php(372): do_action_ref_array('the_post', Array) #4 /home2/clienub3/public_html/fbuild/1599226458833/wp-content/plugins/js_composer/include/classes/edito in /home2/clienub3/public_html/fbuild/1599226458833/wp-content/plugins/insert-php/includes/class.execute.snippet.php on line 75Thanks again for the response
Oddly, there are no php errors in debug.log
Also, there are no snippets active. Just the default snippets that are disabled when installing woody snippets.
I tried this on a fresh site. Same issue.
The error in the console is:
?vc_editable=true&vc_post_id=19&_vcnonce=7d9bfd96e4:1 Failed to load resource: the server responded with a status of 500 ()But only happens if Woody Snippets is activated.
Awesome. I will do this and get back to you.
Thanks very much for the response.