Richard Lynch wrote:
A) Attempt to hack fckEditor to "allow" a PDF to get uploaded, and then display a link to the PDF instead of alink to the fckEditor output. B) Give them a separate, possibly confusing, input to upload files to tie in as links to the fckEditor area C) Dump fckEditor and only allow file upload, requiring them to compose HTML pages in some external application Has anybody faced this, and with VERY non-technical users had better luck one way or another? Which of these fit in best with PHP, and why?
Do they want the PDF to display in the page, or is a link to a PDF ok for them?
Dunno about what's best for PHP, but I'd think about having a separate upload box right below the fckEditor box, clearly marked as a PDF upload box, and then do some linking magic when you process the form.
You said there were templates involved. Depending on how the content from fckEditor is used in the templates, I'd see if I could just put some kind of tag in the templates as a marker for the PDF link to go into, or maybe some JS to add a tag into the fckEditor box when they choose a file to upload. But it all really depends on how the backend is handling the form and how it all eventually gets out to the browser as a page.
I've got a more complicated thing going in my CMS that seems to be ok for the folks to grasp that involves a PDF upload/manager section thingie. But I'm not having to tie it in to fckEditor, and all the PDF's go to one page anyway right now.
Good luck on however you end up working it out. Showing someone how something works before they have a chance to formulate any ideas about how they *think* it should work is always a lot easier that retraining them after they've been frustrated at the "magic box that won't do what I want it too".
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
