Of course, you could also try to fix TinyMCE so the paths are correct from the source... ;)
That would be my preferred method, but if I change the paths in TinyMCE, then it will not display the images in WYSIWYG mode. It needs the physical path to preview assets in WYSIWYG mode. So if the paths are correct, the images appear broken in the WYSIWYG. Correcting the URLs is the goal here. The way I am doing it, with regular expressions, I am finding each anchor and img tag that contains one of the problematic paths, exploding all the attributes, fixing the src or href attribute, and then re-assembling the tag with all its attributes. I was relying on the Html helper to rebuild each tag with all of its attributes and the new path. But now I am going to have to basically re-write the exact thing that the Html helper does, which is dumb. I really liked cakePHP up to this point. But there needs to be a bit more flexibility in this area. When it comes to building content management systems, which is 90% of what I do, "presentation" IS my data. I need to be able to massage the data, which is presentation, from anywhere within the application. Preferably *without* rewriting functionality that is already written. -Rosie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
