Oh right, didn’t realise that the files were deleted from the server when you selected ‘remove’; I thought they were just removed from the entry. So that’s a double edit though isn’t it - first to remove the old one and then a second to upload the new one with the same name?
So that’s a double edit though isn’t it - first to remove the old one and then a second to upload the new one with the same name?
When you mark a file to delete, a drop down comes down to let you upload a new file. The question will be, what happens first? If the deletion is done first, your upload will be golden. If the upload is done first, you may get an error. Only one way to find out.
Thanks dude, I totally bypassed that silly little drop down box. D’oh!
—- edit——
Realized that when you change the file type to file for a new custom field, the right side area thingy doesn’t change automagically to choose an upload location. Hence why I missed it. Can this be modified?
Go to the custom field group and make sure that you choose the correct file upload location in custom field settings. It’s next to the “file” dropdown list.
If it is indeed in the same entry then no problem just go ahead and click on the remove check-box and then choose the new (same-named) image and everything should be fine.
No, it wasn’t working out like that for me. That’s what I was doing and was getting the message about trying to upload an image with the same name. Anyway, not too worried about it as long as it can be done in one or two edits.
One piece of advice: don’t use if:else with them, only simple {if}{/if} conditionals (you can use {if imageUpload != “”}foo{/if}{if imageUpload == “”}bar{if}). I’ve seen weirdness when using the advanced conditionals with it.
Matt,
The more I thought about this the more I’m not sure about it. It makes perfect sense what you’re saying, but this would require me to create an additional custom field and it’s type would be “file.” I would hate to have one custom field “file” type and then a second custom field (the one I created originally for the image) just sitting there no longer doing anything.
For my site, having two fields isn’t a big deal at all because I’m familiar with EE but this situation came up on another site too (the business I work for) and they could really benefit from the file extension but I really think having two fields in the publish page might get confusing for the users that will be updating the site. Might have to get someone to do some work with the MySQL database like your first suggestion.
Yes, that is certainly one downside to the suggestion.
You could set the old field to hidden, though, and move it all the way to the bottom of the publish screen. I often do that with deprecated or older fields that aren’t used anymore, but I still need data from.
just a quick question (not wanting to read 35 pages of this post):
is it possible to add information to the uploaded images (I’m using it in multiple upload mode)? like image titles and image descriptions? would be something like custom file fields?
I am currently using 1.0 in conjunction with the File Manager module for a client. I have been u sing File as a header image uploader while using the normal file uploading capabilities for summary and body text. I quickly noticed that my Header Image directory is available to the File Upload. This is only a slight problem.
My biggest concern is that the File Upload allows you to “select field” which has the custom_field as an option in the dropdown. While bug testing I inserted an image into the custom_field (file) which went through with no problems. Now I’m seeing a mix-mash of broken javascript due to the insert.
Is there any way to limit the fields dropdown to exclude the custom file fields? Has anybody else experienced a similar issue and found a solution? Thanks in advance.
Just recently I encountered what seemed a completely unrelated problem having to do with my inability to access a custom field groups fields in order to edit from the Control Panel.
When I select “Add/Edit…” a blank page loads. With error reporting enabled I get no errors written to the blank page.
Strangely enough, changing the field group name from “team_info” to “team_information” seemed to eliminate the problem.
I did go thru an elimination process to see if any of the extensions I have enabled might be to blame. It seems that the problem goes away when I disable this extension.
I’m not at all sure what going on here but I’m concerned that this might be causing trouble that’s not readily visible.
