With Drupal 6.22 I am creating a new node which should have an attachment. Only, when I try to add the attachment I get this error. I searched on the error on this site and it seems to come up a lot in a lot of different places, but without any clear explanation of why or how to get around it in many. I did run cron ... didn't do anything. I cleared all cookies for the site. Likewise. I don't believe the site is using suhosin.ini since that doesn't show up with a find. I did try doubling the execution time and input time in php.ini. No change. The file is bigger than most attachments ... might even be the biggest so far, but is less than 9MB and I am loading as the administrator. I have no problem transferring the file to the site using FTP, but have no clue how to attach an existing file to an existing node.
By tamhas on
Comments
=-=
are you sure the file is an allowed extension in the settings for the module in question?
Yes, it is a pdf.
Yes, it is a pdf.
=-=
any a spaces or unique characters in the file name that may cause a validation issue?
The file names in question
The file names in question are PracticalConsiderationsinOOABLProgramming_20110919.pdf and MBD_ADayInTheLife_20110913.pdf ... a format I have used repeatedly in the past. The only difference, I think, is that these are somewhat larger than usual.
=-=
Have you tested that theory by shortening the filenames?
Larger files, not longer file
Larger files, not longer file names. The MBD one is clearly shorter than others I have used. Examples include:
OERAStrategies.pdf
OERA_2.0.pdf
OODesignPatterns_20100120.pdf
OODesignPrinciples_20100123.pdf
OOVocabulary_20100116.pdf
ObjectToObjectRelations.pdf
PatternsForManagingRelationalDataInOOABL.pdf
RapidBusinessChangeAndABLProductivity.pdf
ReplaceAnSPWithAClass.pdf
ThinkingOOForTheLegacyABLProgrammer_20110618.pdf
ToCodeOrNotToCode_20110619.pdf
TransformationAndModernizationStrategies.pdf
TransformationTriangle.pdf
Transformation_NeedsAssessment.pdf
UMLProfileForABL_20071112.pdf
WhyArePeopleTalkingAboutGoodOO.pdf
If I could load via FTP and modify the page to point to the already loaded file it would at least get me past this. I just gave these presentations at a conference last week and I am anxious to get them on the site.
=-=
if you upload them through FTP you have to handcode the link to them in the content.
Personally, I'd use a filefield not the core upload module which is what I assume you are trying to attach files with. I'm able to upload files fine in my testing with upload.module attachments. As such I can't reproduce your issue.
Across the four sites which
Across the four sites which are running on this same code base, the built-in attachment feature has been just fine up to now. I'm not sure what benefit there would be to switching to an alternate technology. I would be surprised if the problem was the code in the core upload module.
By "handcode the link" you are talking in terms of adding an < a reference in the text which pointed to the content, not updating the underlying data in the way that the core upload does?
=-=
I can only make suggestions based on the information that I have at the time of the comment. Thus the amount of sites in use or what modules are used on them was unknown.
You've still failed to mention exactly which module is providing the "attachment" feature you speak of. Again my assumption is the core upload module. However, until such time as you confirm this to be the case you're leaving support to guess at the issue.
yes, hand coded HTML in the form of an a href
good luck.
Presumably the core upload as
Presumably the core upload as no special modules are involved. All I am doing is adding a node like many others and including an attachment ... very common on this site in particular as I often provide a PDF even when the full text is provided on the site.
=-=
then something is either causing an issue in the settings or beyond. I can't explain beyond not being able to reproduce the issue on my own 6.x test sites using the upload.module.
other issues with similar reports over the years which may aid in determining why your install is acting up http://drupal.org/search/apachesolr_multisitesearch/%27Validation%20erro...
I'd be testing other content types for similar issues to see if it can't be narrowed down to a specific content type. I'd also be checking any and all contributed modules in use for some kind of conflict.
Yeah, I started with that
Yeah, I started with that search and tried several of the suggestions I found there ... but I won't claim to have read all half million. I have to confess that most of it sounded like "try this", sometimes followed by "it has gone away", but even when it did go away it wasn't because anyone actually did anything or had any clue about why it happened. That is why I posted to see if someone, somewhere had some real insight as to what caused this.
The PDF is 11,451KB. I tried uploading the underlying PPTX which is 952KB and got the same error. Uploading another PPTX which is only 172KB worked. Those numbers made me wonder if the message about 1MB limit was the issue, even though it has never been an issues before.
So, I bumped up the limit in Drupal and then it complained that I had pushed them higher than the limit set in php.ini. So I bumped that and restarted the site. Then Drupal was happy with the new limit.
Then, I tried the two attachments which had been giving me the problem and, presto!, they worked. So, this appears to have been the problem all along.
A more meaningful error message would definitely have helped!
Thanks for your help.