Thread

Using the built-in ‘Upload File’ in the Publish window, I am able to select a file (in our case a pdf, but have tested with small jpgs, too) from my desktop and upload it.  However, in the following dialogue both ‘Insert Link’ and ‘Insert URL’ (confusing semantics there, right?) do nothing.  Nothing changes in the textarea field that is selected.

In this particular example the textarea field is a TinyMCE window, in case that has any bearing.  I’m still running 1.6.7 (need to test out the upgrade with my site’s configuration before pushing live).

Any idea what’s going on here?

*Update:* At post #4 I confirm that this is concerning TinyMCE fields.  Has anyone else run into this?

Here is a list of my extensions and plugins:

inlikealion, if you create a regular textarea field, does it work then? Trying to see if TinyMCE is a factor.

Hey, Sue!

I just checked in a plain text field and it worked.  However, my clients need to be able to insert files into their main blog posts which (unfortunately) are being run as TinyMCE inputs.  Any thoughts on how to work around this?  My guess is that it is having trouble targeting the input field because the whole thing is replaced by the MCE javascript, right?

A big change of direction would be to convince the client that they really don’t need a wysiwyg and instead need to learn Textile or Markup, then convert the field type to that and test everything.  I’d rather not go that route as the client wants their easy formatting and are now used to it.  It would be bad to now ‘lower’ the user experience,  not to mention the extra time converting and testing.

Does the image need to be in its own field, or mixed in with the rest of a textarea? The reason I’m mentioning it is that there are other extensions such as FieldFrame and nGen File Field. You’d need to be running PHP5 on the server, though.

I don’t believe the client and designer have hashed that out explicitly, but I’m operating under the assumption that they want it mixed in the same field.  I started this project back before FF* was out and I haven’t had a chance to ‘learn up’ on it, though I liked the premise.

* FF-› FieldFrame, not FireFox - site’s not _that_ ancient.

It definitely sounds like a TinyMCE issue, working as it does with a plain text field. Personally I don’t have much experience with that, but it’s seems to come up often enough. Let me move this thread to Howto for some community support.

Does anyone have experience getting File Upload to work with a TinyMCE field?

The problem isn’t the file upload, the problem is the EE tag https://ellislab.com/asset/images/team-photo/, which is used to save the filepath in..

We could use Javascript to change https://ellislab.com/asset/images/team-photo/ ==> /images/uploads/
However, I have no idea where I could put this in the TinyMCE filesystem..

I agree that the problem isn’t the actual upload (I can confirm by ftp and EE’s File Upload browser that it is successful), but I assumed it was breaking when the EE engine is trying to insert the link into the hard-coded textarea, which no longer exists because TinyMCE is replacing it via js with the TinyMCE window.

Is it really a matter of changing the the URL from full site to an absolute URL?

Has a solution to this issue been found? I am facing the same situation.

I had to take a different route due to time constraints, but I did find this link, which in the additional part of the linked post, at the end, might hold the key to our problem.  I simply didn’t have time to research the security implications and test on my dev site.

Here is the link:
http://expressionengine.com/wiki/TinyMCE_and_ExpressionEngine_Integrated_File_Upload_Management/

Let me know what you make of it.