LG SAEF File Upload.... Throwing my hat into the ring
Development and Programming
Cool… thanks. After installing and reading through this thread a million times, I can’t seem to populate the custom field. Here’s my code for the file upload part.
{exp:weblog:entry_form weblog = "client_files" lg_saef_file_upload = "y" lg_saef_file_upload_dir_id = "1"}
Title: <input type="text" name="title" value="" /><br >
<input type="hidden" name="entry_id" value="{entry_id}" />
<input type="hidden" name="entry_date" value="{entry_date}" />
File 1: <input type="file" name="field_id_28" value="" /><br >
<input type='submit' value='Submit' />
{/exp:weblog:entry_form}The title shows correctly, but the custom field is empty.
UPDATE: After looking at my server, the files aren’t even uploading.
Hi Levi
Just wondering if your plans for a delete function are still in the pipeline?
Not at the moment as I don’t need this feature personally and my time is quite limited these days…. dam clients 😊
Leevi, Just got this working (after a few false starts, but success once I could afford a solid amount of time) - the one thing I’m a bit unsure about. I’m using the {custom_fields} tag for all the other fields within the weblog, which means that the text field for the photo upload field appears. Do I not use the custom fields tag and extract the HTML or is there a simpler way to deal with this? Many thanks.
Hi Leevi - I’m running into the blank CP with this extension enabled too… real shame because the functionality is perfect, and I really though it was the answer to my SAEF file upload prayers! I’m using EE 1.6.4 Build 20080710 with MSM.
You can scratch my last post - got it figured out with a show_fields command on the entries line. I too, however, am having the blank CP problem now. One thing I’ve noticed though is that it is only the front page that shows up blank, and if I happen to paste in an active page after the session ID, everything else shows up just fine. Hope that narrows that problem down for you.
You can scratch my last post - got it figured out with a show_fields command on the entries line. I too, however, am having the blank CP problem now. One thing I’ve noticed though is that it is only the front page that shows up blank, and if I happen to paste in an active page after the session ID, everything else shows up just fine. Hope that narrows that problem down for you.
Best thing to do is turn off the automatic update feature in the extension settings. This should resolve the problem. I think the error has to do with fopen() but I’m not sure.
Still looking into it.
Best thing to do is turn off the automatic update feature in the extension settings. This should resolve the problem. I think the error has to do with fopen() but I’m not sure.
Hi Leevi - that’s fixed it for me, great! I needed to repeat the process for both MSM sites too…
I am having a problem mentioned earlier by mr_dimsum.
My files are uploading, but if i go to the EE CP and check edit the field is blank.
Also is there anyway to stop a file uploading if the SAEF throws up an error? For example if the user doesnt include a title, the file still gets uploaded. So when the user finally does fill out the form correctly there are mulitple versions of the same file on the server.
edit The extension works on my local test server. But not on my real server. Both running the latest EE, both using the same template code.
I’ve figured out what I was doing wrong!
I had assumed that the field order was the same as the field ID. However, it seems these have got out of sync.
So I got the correct field ID from looking at the URL in the control panel.
Looking at the database, the extention was putting the file in the field I originally specified but obviously I never saw that field because it was setup with a different weblog field group.
Glad I could help Joobs 😊
Best thing to do is turn off the automatic update feature in the extension settings. This should resolve the problem. I think the error has to do with fopen() but I’m not sure.Hi Leevi - that’s fixed it for me, great! I needed to repeat the process for both MSM sites too…
Simon - I’m obviously missing something here - how did you disable auto-update on leevi’s ext when you can’t get into the control panel? I’m having teh same issue… I went and simply deleted the extension from the extensions folder via ftp - looks like I shouldn’t have done that cause now I’m getting “the system does not appear to be installed” when I try to login to the CP - looks like I’ll have to do a fresh install (that will be the third time I’ve had to install and build this site :-( )… guess at least I know to turn autoupdates off with leevi’s ext and hopefully it will go alright this time…
EDIT: ok no worries my config file had been wiped for some reason - just copied the code in from the config.bak file and disabled extensions from there - all good ;-)
Markwts, upload a fresh version of the extension. Deleting an active extension will cause site wide problems.
You can disable it if you log into your hosting account and use something like phpMyAdmin. Go to exp_extensions and change the “enabled” options for the three LG upload entries from “y” to “n”. This is how i did it. seems to work.
You might want to backup your database before manually editing it though…
edit i’ve read your response above, if there is an option in the config file then that is probably safer than poking around the database!
Markwts, upload a fresh version of the extension. Deleting an active extension will cause site wide problems. You can disable it if you log into your hosting account and use something like phpMyAdmin. Go to exp_extensions and change the “enabled” options for the three LG upload entries from “y” to “n”. This is how i did it. seems to work. You might want to backup your database before manually editing it though… *edit* i’ve read your response above, if there is an option in the config file then that is probably safer than poking around the database!
Gday Joobs thanks - yeah everything seems to be behaving itself now touch wood 😉
Hey Guys,
I’m working on a new auto - update extension that should resolve these issues.
Cheers