chiggins

Otto:

In this case, the auto-detect finds flash, but the flash I have evidently isn’t the super newest where the uploader actually works. Thing is, I’m not willing to short circuit my package manager to get it, that’s kinda the point of the package manager.

I’m not a big fan of using flash where standards-based html/js/css will do the trick, and it sure seems like making this functionality dependent on an app that you guys have no control over is risky.

So, I’d argue philosophically that browser-detection and auto-enabling is great and unobtrusive, but not giving me the ability to manually shut it off is kinda lame, especially considering that I am given the option of robustitude over convenience with editors.

That’s just my opinion, and I can totally see the other side of argument. My own solution was just to go into includes/media.php and set the damn thing to false ??

Hi all,

Here’s the thing. The bug I have with it, I’m reasonably sure, is related to my version of flash rather than any bug with WordPress.

Now, given, I’m on Ubuntu, and I know that’s not a huge share of the platforms/browsers out there. But if you check the Ubuntu forums for problems with flash (especially if you’re running the 64-bit version), you see that the supported flash package is usually a little behind the newest linux version, but it doesn’t always matter. Fixing flash for us just isn’t as high a priority for them, which is fine.

But it does raise an issue, namely: why doesn’t WP have an option, perhaps next to the one that shuts off the annoying wysiwig editor (why, yes, I gots ‘pinions, heh), that allows you to just shut off the flash uploader if you don’t want it? Why does this require a 4 line plugin?

Thanks for listening, cheers, and keep up the great work everyone ??

Hi Benjamin,

Excellent Idea. I’ll add that to the list of Todo’s (shouldn’t be too difficult, which increases the chances I’ll be able to get to it fairly quickly ?? )

I just had this problem and figured it out, there’s a comment in the add_submenu_page function that says that if it’s adding a submenu to a top-level menu that doesn’t already have one, it’ll add the top-level as a submenu tab. I don’t get that either. The other problem I was having was with having the submenu generation in the same file as the top-level menu, which evidently isn’t good either.

The work around I ended up with was to:

1. call the add_submenu_page() functions before the add_menu_page() function, and
2. have each submenu page in its own file rather than trying to put a generation function in the top-level menu’s file

The last part bothers me, because the Codex explicitly says that it’s better to use the optional function arg in each case, but I couldn’t get it to work that way.

Dunno if that helped at all?