Since the new Qcubed version that uses jQuery i can't figure out how to get uploadify working again without some nasty hacks.

I used to have jquery and the uploadify javascript files in my header.
Then, in myForm.tpl.php i had the javascript that activates uploadify, like jQuery(someEle).uploadify(options).
Now, since Qcubed loads the javascript files like jquery at the end of the form, there are conflicts with the jquery being included in the header and the uploader stops working.

What i am wondering now is what's the best way to add custom javascript files at the end of the form? i would like to add the uploadify.js there and then also add my custom javascript code that enables uploadify with QApplication::ExecuteJavascript($strCode).

I hope it's clear what i mean and i would be very grateful about any hints!

thanks

Not sure if this is a Qcubed thing, but I am pretty sure it is. A weird text file is being generated on my server, but I can't pin down which action of my website is doing it. It's being generated in /tmp and has the name "*username*_license.txt _readme.txt deprecated drop.sql" and it lists a few more files. This are the names of the directories/files in my public_html folder.

The files content is some weird characters and
"
Usage:

Cannot open argument file(argrcv)

MDY//
"

Any ideas? I'm at a loss for what to do.

Thanks
Rory

Hi all,

I have a question regarding the file permissions set on code-generated files (this is actually using the latest version of qcodo, but I'm guessing this is still the same as I haven't read anything about file permissions in the changelog).

The filesystem is linux/centos (ext3). When the code generator creates files (for example, a new class in /includes/data_classes/MyClass.class.php) the file permissions are set as 666 (or, read & write for owner, group and everyone else).