Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter dekortage

    (@dekortage)

    Fantastic. That’s what I was getting at with the timing-out over file size, though I wasn’t exactly right.

    Glad it’s working for you.

    Thread Starter dekortage

    (@dekortage)

    That does sound like a pain. I’m not having the problem — I’ve tested it with 2.5mb and 3.0mb files.

    I don’t know how much you know about PHP, but I would consider editing the upload files and putting in some breaks or echos throughout it, trying to trace the point it is breaking. That’s what I did and finally tracked the break to the multibyte functions.

    I’m not sure, but in thinking about it further, I would see if it has anything to do with the system’s post-upload thumbnail generation timing out over the file size.

    Does it make a difference if you upload the file via the “Link” file insertion, versus the “Media” insertion? Not sure if upload via Link would include the thumbnail stuff.

    Or, maybe I’m talking out of my butt. But I’m sorry that you have the problem. I hate when software doesn’t work correctly and you can’t figure out what is going on.

    Thread Starter dekortage

    (@dekortage)

    And it was set to zero previously? (e.g. no limit)

    Is there any chance your problem is on the browser end? Depending on the config, sometimes IE has problems with uploads that Firefox does not (or, occasionally, the other way ’round).

    Thread Starter dekortage

    (@dekortage)

    You said you changed the config for the file upload size. Was that the config in the plugin? Or the config in WordPress? Or did you do something in a php.ini file?

    What is your max upload size in PHP?

    Thread Starter dekortage

    (@dekortage)

    I figured out the problem. The file upload plug-in requires the multibyte string functions in PHP. These are built into PHP5, but if your host is running PHP4, the functions have to be included in your host PHP configuration. In my case, they weren’t included and there was no way that end-users could add them. However, PHP5 is an option on my host, so I switched to that and everything began to work fine.

    Note that after switching to PHP5, I had to restore the docroot back to the original default (instead of blanking it out). Under PHP4, the multibyte functions would cause the PHP script to fail, so the File Manager window code would never appear — it just came up blank (my original problem, above). But if I blanked out the docroot, the plug-in code would run into the permissions error, which caused the plug-in to skip the code with the multibyte functions, so the File Manager code would appear but wouldn’t be able to see or upload any files. Fun, eh?

    But PHP5 solved it all.

    Thread Starter dekortage

    (@dekortage)

    Thanks for the information. I’m still struggling with just getting the file manager window to appear without the permissons error.

    Thread Starter dekortage

    (@dekortage)

    Resolved this problem by editing the ‘docroot’ in the ‘config_tinybrowser.php’ file to this:

    $tinybrowser[‘docroot’] = ”;

    The file manager window now appears as it should. However, it is headlined with an error that it is “Unable to create the ‘/mysite/localgroup/wp-content/uploads/shared/media/’ directory”. As a result, I cannot actually upload a file That directory exists on the server and has full read/write priveleges for everyone (UNIX permissions 777) so I can’t figure out why it does not see the directory. Maybe there’s another pathname I need to edit someplace.

    There are two sets of links, one for commenters and another for posters. So you have to edit four lines of HTML in that area, and you’ll fix all the links.

    I had the same problem, but only after I adjusted WordPress so that it worked from my domain’s root directory instead of the /wordpress subdirectory.

    So here’s how I fixed it. Open up users2csv.php and look at lines 227-233. Remove the text “<?php bloginfo(‘url’);?>/wp-admin/” from those lines. It now works for me.

    I think you can only have one theme per WordPress installation. However, if you are handy with PHP, WordPress custom fields, HTML, and CSS, you can simulate multiple themes within one installation. Basically, you use PHP in the theme files to test for a post’s custom fields or tags, then creates a custom CSS class reference in the HTML (such as putting a special “class” on the body tag), then have extra CSS layout descriptions in your style.css file that results in a different visual display.

    It’s a bit of a hack, but it works… if you know PHP and such.

Viewing 10 replies - 1 through 10 (of 10 total)