Hello,

I can't seem to get the .htaccess settings needed for this module to work.

Initially, I put them toward the tail end of the .htaccess file, but that resulted in the site displaying an Internal Server Error. So I tried putting them with the other php_value settings -- in the part below the "IfModule mod_php5.c" tag, since the site is running PHP 5.2.6. That didn't result in any error -- but when I went back to the configuration page for the module, it still had the Recommended Settings/Your Settings part, showing my settings as exactly what they had been before. So apparently putting it there didn't have any effect.

Was I correct to put the values within the "IfModule" tags for my version of PHP, or is there somewhere else they were supposed to go? If I did put them in the right place and it just for whatever reason won't accept them, is there any other way I can get this module to run? (No, I don't have access to the php.ini file -- the site is not on a dedicated server.)

Or failing that, any other way of getting a couple of videos onto a Drupal site in some reasonably lightweight, easy-to-play format that doesn't involve YouTube and won't be destroyed by TinyMCE? Most of the other video modules I've seen seem to be massive overkill for this site's needs...

Comments

spidersilk’s picture

spidersilk commented

Quick additional question: having looked through the configuration options a bit, it looks like possibly I could just upload the videos by FTP and put them in the global_import folder, rather than using a form to upload them? Would that get around the problem of not being able to set those PHP values, or would the execution time and input time still cause problems? I know the first two values deal with form uploading, but I'm not sure about the last two.

attheshow’s picture

attheshow commented

Dear spidersilk,

This is actually in the help section of the module, but the .htaccess code you need to add is:

php_value  post_max_size  100M
php_value  upload_max_filesize  100M
php_value  max_execution_time  1000
php_value  max_input_time  1000

I just add this to the very end of my file. It should not have any tags wrapping around it.

Regarding the second option you presented, I believe you're right about the first two configurations variables being related to just form uploads. I think if you're missing the last two settings, however, FlashVideo won't be able to process the videos for you via the FFMPEG binary.

travist’s picture

travist commented
Status: Active » Fixed

Thanks again Mark for everything.

attheshow’s picture

attheshow commented

Sure! No problem Travis. :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

spidersilk’s picture

spidersilk commented
Status: Closed (fixed) » Active

I know what code to add, and I always read all available help files before resorting to posting an issue.

As I stated in my post, when I added it at the tail end like you're saying I should, the entire site died -- "Internal Server Error 500". Typically when that happens as a result of .htaccess changes it means that there was a syntax error or some other invalid instruction, so I assumed on the basis of that that maybe they had to be inside the "IfModule" tags, especially since that was where the other php_value lines in the .htaccess file that comes with Drupal were.

Moving them there kept the Internal Server Error from happening, but also did not seem to have any effect -- I still got the message saying that my settings were wrong.

I'm sorry if any of the above was not clear in my original post.

I don't think my web host blocks php_ini settings in .htaccess automatically or anything like that -- Drupal core has several of those, as do some other programs I've used, and none of them have had problems. So I'm really not sure why this one is being so troublesome...

spidersilk’s picture

spidersilk commented
Status: Active » Closed (fixed)

Closing this again, as I have figured out how to have my own php.ini file even though I'm on a shared host (yay!), so no more need to mess around with .htaccess.