Closed (fixed)
Project:
Asset
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
27 Jul 2007 at 13:01 UTC
Updated:
1 Jan 2008 at 21:52 UTC
Failure in WYSIWYG within TinyMCE
Inserted images are incorrectly shown in TinyMCE as being on seperate lines even when they are rendered correctly in published page as inline.
May seem a minor issue but breaks the WYSIWYG functionality and confuses non-techy users.
Comments
Comment #1
John Bryan commentedJust correcting the priority level from accidental minor setting
Comment #2
zroger commentedThe tinymce definitely needs alot of massaging. There are various problems that I have yet to find a decent answer for.
I have finally got the align setting working, which works by wrapping every asset in a div and applying a class based on the align setting. This has a nice effect of rendering the almost the same in tinymce as it does when fully rendered.
Please test out the latest code from DRUPAL-5 branch and see if this seems to be any better.
Comment #3
cirotix commentedActually wrapping the assets into div bring one problem if you justify your text. The div comes embeded in a
and 1) it is not valid html, 2) breaks the justifying of your p. Therefore asset shouldn't go in a div but rather in a span. However it could bring some problems to the management the asset. Don't know.
Comment #4
wmostrey commentedYou're right. There's a huge update coming up that fixes this.
Comment #5
cirotix commentedreally ? I am really looking forward this update. Any ETA ? Can we have an overview of the bugs fixed/new features ? I am using asset in production for one of our clients (and actually have hired people from digget for this) and I am planning to use it again in an other project. So I am really pleased to see that a new release is coming.
I have some dev notes on using your hooks to write some new formaters (and soon new asset types). I really should shape them to be readable and update the handbook page.
Comment #6
wmostrey commentedWell the version is ready on production on the new amnesty.org (official launch date: 10 december). It's a matter of taking out the amnesty-specific requests and contributing it. This will probably be done in december. As far as I can see all bugs are fixed, and here are some features:
- cck fields!
- asset manager to edit/move/delete assets and folders
- panels support
- support for .flv files
- many, many smaller tweaks to enhance usability
This version has been thoroughly QA'ed already, but new bugs will probably be found, and fixed :)
Comment #7
cirotix commentedOuAh. You are really making my day, even my week. Any chance that you can release earlier than December ? If the info you want to wipe out are not confidential, I would be happy to help you to clean the thing. We are launching a project together with msn and I am not too happy with how does the module now (and have no time to hack on it). Don't misunderstand me, it is already awsome, but not really at a production-bullet-proof level and needs some work when it comes to usability.
I want it now ;) (really). And my proposal to help you in the cleaning process it serious.
btw, it is nice to see that amnesty.org will launch on Drupal.
Comment #8
scroogie commentedIm looking forward to the new version of Asset as well. I've seen the new amnesty.org was launched. looks great! congratulations!
Comment #9
wmostrey commentedIt has arrived with many bug fixes, including this one. Please open new issues when you encounter them in order to keep a clean overview.
Comment #10
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.