Forum Replies Created
As an update, I could not justify keeping this plugin on the site, as it was obstructing going live. I have uninstalled it, instead opting for hard coded forms, by following a tutorial.
I would like to use this plugin, and I hope you keep on updating it.
I think a lot of the problem is that unnecessary code and scripts are being loaded in the front-end on every single page. If you locked down the loading to only pages with forms on them, either by checking for an existing ID, or a specific page-template, it might help to keep the speed up. – oh and make the google maps a feature to turn off – it adds on tons of code.
All my best wishes for you.
Well, no, you cannot disable ALL the scripts from the settings (most notably the google maps API calls).
Unfortunately, I have had to move away from using this plugin. When I uninstalled it and deleted the plugin files I managed to cut down the server waiting time (time to render on the server). It came down from around 3-6 seconds to around 800 ms – 1.5 seconds.
It is too bad, but hopefully in the future I can start using the plugin again.
I agree with this – google maps scripts are loaded on every page.
Why are they not loaded inside the if-statement that controls the plugin scripts?
OK, after a bit of experimentation, I found the function add_meta_boxes() in /admin/posting.php. (row 51-57)
Commenting out the contents of this function helped remove the generated metabox WPUF Custom Fields from backend, and the conflict was resolved.
Still, would be nice to have this as an option in the settings though.
I would like to lift this question again.
On content created via backend, I of course do not have these issues.
Is there anywhere in the plugin where I can turn off the creation of the backend meta-box ‘WPUF Custom Fields’? And can’t this be an option in the WPUF settings in the next version? I think this could be valuable for us who have other plugins or who code our custom post types and meta boxes by hand.
I run WPUF Pro 2.1.10
Greatful for any reply, and keep up the good work with this very solid plugin.
I have the same issue on my multisite network. Will cool my boots regarding this then. 🙂
Thank you Tareq, yeah, I guess that is always an option. 🙂 And it is a lot more elegant. Will give it a whirl.
OK, now I feel silly. After a lot of researching and googling, I got a hint that the problem was the way I tried to save the data using update_post_meta()
That function works only on custom meta-fields.
However, it was a lot easier to update using a query through the$wpdb->query
So yeah, this subject can be closed. Hope this helps some one else trying to do the same.