https://legacy.forums.gravityhelp.com/topic/custom-upload-directory-plugin-and-gf Gravity Support Forums Topic: Custom Upload Directory plugin and GF en-US Mon, 20 Apr 2026 13:19:00 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/custom-upload-directory-plugin-and-gf#post-43158 Mon, 05 Dec 2011 16:58:36 +0000 sascha 43158@https://legacy.forums.gravityhelp.com/ <p>Ok, I got a reply from the author of CUD. Not sure if those requirements can be met with a hook/filter in GF? I would value your opinion on that....</p> <p>"Yeah, I just realized we don't need any special flag at all. They just need to provide</p> <p>$_REQUEST['Upload'] or $_REQUEST['html-upload']</p> <p>and either:<br /> global $post<br /> global $post_id<br /> or $_REQUEST['post_id']"</p> <p>Would that make sense to integrate into GF? </p> https://legacy.forums.gravityhelp.com/topic/custom-upload-directory-plugin-and-gf#post-43114 Mon, 05 Dec 2011 09:42:02 +0000 sascha 43114@https://legacy.forums.gravityhelp.com/ <p>Hi again,<br /> the post_id (as a global?!?) is actually enough. I need to pass that on to CUD and tell CUD that the request came from GF. </p> https://legacy.forums.gravityhelp.com/topic/custom-upload-directory-plugin-and-gf#post-43110 Mon, 05 Dec 2011 07:42:47 +0000 sascha 43110@https://legacy.forums.gravityhelp.com/ <p>Hi there,<br /> made good progress! Tracked it down to the following GF function:</p> <p>private static function copy_post_image($url) in forms_model.php</p> <p>1. How can I make the (just created) post information available during that function? I need the author, category, post type, post id. When I var_dump ($post) I get NULL.... I guess if I have the post ID I can get all the information by adding a get_post to the copy_post_image($url) function.</p> <p>2. If that is not possible: can I get any $entry information at this stage?</p> <p>Thanks! </p> https://legacy.forums.gravityhelp.com/topic/custom-upload-directory-plugin-and-gf#post-43107 Mon, 05 Dec 2011 04:37:45 +0000 sascha 43107@https://legacy.forums.gravityhelp.com/ <p>Hi again,<br /> looked at the official function reference for "wp_insert_attachment" referenced above. It basically inserts a file from the "uploads directory". The problem is that GF bypasses the uploads directory modified by CUD, but uses only the one given in the WP media settings instead.</p> <p>So the questin really is:<br /> How does GF get that file to the uploads directory and where does it get the uploads directory path from? Which functions/code does it use to do that? Where is it in the code of GF?<br /> That might help me figure out why it bypasses CUD....<br /> Grateful for any help with this! </p> https://legacy.forums.gravityhelp.com/topic/custom-upload-directory-plugin-and-gf#post-43106 Mon, 05 Dec 2011 04:17:02 +0000 sascha 43106@https://legacy.forums.gravityhelp.com/ <p>Hi at GF,<br /> I'm back on this issue again and banging my head. Could you let me know where in the GF code exactly the attachment is uploaded to the directory, basically where the above functions are called? And also if the post is created before the attachment is uploaded or after? Maybe that will give me a hint on why the following filter gets bypassed:<br /> add_filter('upload_dir', 'cud_custom_upload_dir');</p> <p>A whole walkthrough of the process of creating a post and uploading an attachment in GF would be great and hopefully together with the CUD developer we can get this issue sorted! </p> https://legacy.forums.gravityhelp.com/topic/custom-upload-directory-plugin-and-gf#post-36723 Fri, 30 Sep 2011 13:49:56 +0000 Carl Hancock 36723@https://legacy.forums.gravityhelp.com/ <p>Gravity Forms uses the functions I referenced above to add the image to the media library. So those are the functions that are used to handle media library attachment and processing. </p> https://legacy.forums.gravityhelp.com/topic/custom-upload-directory-plugin-and-gf#post-36686 Fri, 30 Sep 2011 08:27:46 +0000 sascha 36686@https://legacy.forums.gravityhelp.com/ <p>Hi Carl or anyone,<br /> my head is buzzing. No idea why the filter is being bypassed. The filter is in the wp_upload_dir() function (functions.php in wp-includes) which GF uses as well. Any idea why it's not being recognized? I'm not sure how WP processes filters..... </p> https://legacy.forums.gravityhelp.com/topic/custom-upload-directory-plugin-and-gf#post-36498 Wed, 28 Sep 2011 16:26:43 +0000 Carl Hancock 36498@https://legacy.forums.gravityhelp.com/ <p>The functions we use are:</p> <p>wp_insert_attachment()<br /> wp_update_attachment_metadata()<br /> wp_generate_attachment_metadata()</p> <p>The first one inserts the attachment into the Media Library. The 2nd and 3rd function calls above are used together to then create the image sizes, etc. </p> https://legacy.forums.gravityhelp.com/topic/custom-upload-directory-plugin-and-gf#post-36495 Wed, 28 Sep 2011 16:11:04 +0000 sascha 36495@https://legacy.forums.gravityhelp.com/ <p>Thanks. I have contacted him. We will see what he says....<br /> Can you let me know which WP function and when GF is calling when you submit a form that sends a post submission? Maybe I can have a look myself why the CUD settings are being bypassed. Might just need another add_filter/apply_filter somewhere else to make this work.<br /> It would be great if you could point me to the right files &amp; functions for both GF and WP.<br /> Maybe it also has to do with the order that GF calls the WP functions?<br /> Anyway, any pointers to the right files would be appriciated in case I do not hear from the CUD developer. </p> https://legacy.forums.gravityhelp.com/topic/custom-upload-directory-plugin-and-gf#post-36471 Wed, 28 Sep 2011 14:39:34 +0000 Carl Hancock 36471@https://legacy.forums.gravityhelp.com/ <p>Gravity Forms uses built in WordPress functions to add the image to the Media Library and then WordPress processes the image and moves it where it needs to go. Gravity Forms itself doesn't handle this, it calls a WordPress function to do this. Most likely the CUD plugin is applying hooks to to do what it does in such a way that it isn't applied to this function. You may need to discuss this with the CUD plugin developer. </p>