Resolved Bug


This bug has been marked as resolved.

TinyMCE Problems with IE 7 and IE 8

Permalink 5 2 Browser Info Environment
Add a content block, put some text in it, then save it and open the same content block for editing the text for the second time: you can't mark or edit the text until you click on a button (e.g. bold).
or edit the text, press cancel an re-edit the text again, you will see the same effect. it's always the second "editing click", it's never the first one.

we noticed this problem only with internet explorer 7 and 8 on different computers.

Tags:

tinymce, upgrade 5.4.0.5
Status: Resolved

Still Valid:

This bug is valid a newer version of concrete5. View Current Bug
mesch
View Replies:
digievo replied on at Permalink
digievo
I tested in IE8 on Windows Xp SP3 and I can edit fine without having to click a button.
Mnkras replied on at Permalink
Mnkras
#1 this is not a concrete5 issue,
#2 i cannot reproduce on IE8
Mnkras replied on at Permalink
Mnkras
Closing due to it not being a bug with C5
andrew replied on at Permalink
andrew
I can confirm this too. Done it from IE 8. Edit, update, edit again without reloading page.
Remo replied on at Permalink
Remo
can be reproduced using these steps:

1. Add a new content block
2. Enter some content
3. Update
4. Edit the content block and add some more characters
5. Update
6. Edit the content block again
7. Click on some text you've entered (not in the whitespace!)
8. You can't enter any text
9. Click on "Bold" (or any other button)
10. You can enter text now..
melat0nin replied on at Permalink
melat0nin
I get the same issue in ie7
tecnolord replied on at Permalink
tecnolord
Thanks to Green2Go (http://www.concrete5.org/profile/-/23330/)
The bug is only related to tinymce and IE :

http://tinymce.moxiecode.com/punbb/viewtopic.php?pid=73682...

http://sourceforge.net/tracker/index.php?func=detail&aid=298403...

quote:
The _mce_start is used on IE to determine the current selection. However I don't see how they will be left in there since we delete them directly after we insert them. However the upcoming release scheduled early next week will use a different method of getting the current selection and it doesn't use these span elements so then it will be impossible to get them in there.

--------------------------------------------------------------------------------
Best regards,
Spocke - Main developer of TinyMCE

end quote

so it is not concrete5. But still a bug. There is mentioning of a solution: the GitHub version until we release it and try that out. The rewrite also fixes problems with input method for non western languages like Japanese.

--------------------------------------------------------------------------------
Best regards,
Spocke - Main developer of TinyMCE

but then.. i have no clue how to do that.
andrew replied on at Permalink
andrew
We are a bit out of date with TinyMCE, but I'd hoped to be able to get a new version in before 5.4.1. Is this fixed in recent stable releases? Or just in a development version? I don't think I'm going to grab a development beta again - since that's what this current one is and it has some issues.
tecnolord replied on at Permalink
tecnolord
The message from spocke to grab the github version is from 2010-04-24 19:08:53
and the last release is from 2010-06-30 13:55:38
so i guess that tinymce=b.tinyMCE={majorVersion:"3",minorVersion:"3rc1",releaseDate:"2010-02-23"

has been upgraded. and there has been mentioning of the IE fix and also the deletekey problem.

But, to be honest, i have no clue if it is a stable release and fixed. I wish i knew more and would test it if i could.
I'm going to test if i can find out more and then let it know.
But... don't get your hopes up too high :) (on my testing capabilities, not the TinyMCE bieng fixed :) )
tecnolord replied on at Permalink
tecnolord
I have renamed the tinyMCE folder to tinymce_old and uplaoded the current release with the new version and simple editing works. I have no clue if it would break anything i don't see, but one problem already has left the building. When i select the dropdownboxes they work as i would expect (with previous version the color selector appeared erratically about 200-500 pixels higher then the dropdown.)

I'll fiddle some more and will let you know about the results.
In the meantime i would advice anybody NOT to 'upgrade' tinyMCE on a production website without good testing and/or proper knowledge about the concrete5 inner workings. As i said. i have no clue about what is going wrong if you just do what i did. But i just fiddle with the websites.
(testing it onhttp://www.pbpgamer.com)

for isntance...i found out that when you "update" like me you can't edit the HTML straight away. it appears UNDER the texteditor. (still testing :-))

Hmmm. and i just found out that my colorswatch editor dropdown still shows up 200-300 pixels above the dropdown. :-/
editing works "normal" though...
zoinks replied on at Permalink
Yeahh... Is this fixed yet?

I was testing out TinyMCE in IE8... the dropdown for paragraph or header styles does not dropdown.

Since my client uses IE8, this is really unfortunate.

concrete5 Environment Information

# concrete5 Version
5.4.0.5

# concrete5 Packages
Anmelden (1.0).

# concrete5 Overrides
blocks/autonav, blocks/content, blocks/vvl_trennlinie_eins, blocks/vvl_trennlinie_zwei, languages/de_DE, single_pages/dashboard, single_pages/redirect_user.php, themes/vvl

# Server Software
Apache

# Server API
cgi-fcgi

# PHP Version
5.2.6-1+lenny8

# PHP Extensions
bcmath, bz2, calendar, cgi-fcgi, ctype, curl, date, dba, dom, exif, filter, ftp, gd, geoip, gettext, hash, iconv, imagick, imap, ionCube Loader, json, libxml, mbstring, mcrypt, mhash, mime_magic, mysql, mysqli, openssl, pcre, PDO, pdo_mysql, posix, ps, Reflection, session, shmop, SimpleXML, soap, sockets, SPL, standard, suhosin, sysvmsg, sysvsem, sysvshm, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend Optimizer, zip, zlib.

# PHP Settings
log_errors_max_len - 1024
max_execution_time - 30
max_file_uploads - 50
max_input_nesting_level - 64
max_input_time - -1
memory_limit - 32M
post_max_size - 21M
safe_mode - Off
safe_mode_exec_dir - /usr/lib/php5/libexec
safe_mode_gid - Off
safe_mode_include_dir - <i>no value</i>
sql.safe_mode - Off
suhosin.log.phpscript.is_safe - Off
upload_max_filesize - 20M
mysql.max_links - Unlimited
mysql.max_persistent - Unlimited
mysqli.max_links - Unlimited
pcre.backtrack_limit - 100000
pcre.recursion_limit - 100000
session.cache_limiter - nocache
session.gc_maxlifetime - 7200
soap.wsdl_cache_limit - 5
safe_mode_allowed_env_vars - PHP_
safe_mode_protected_env_vars - LD_LIBRARY_PATH
suhosin.cookie.max_array_depth - 50
suhosin.cookie.max_array_index_length - 64
suhosin.cookie.max_name_length - 64
suhosin.cookie.max_totalname_length - 256
suhosin.cookie.max_value_length - 10000
suhosin.cookie.max_vars - 100
suhosin.executor.include.max_traversal - 0
suhosin.executor.max_depth - 0
suhosin.get.max_array_depth - 50
suhosin.get.max_array_index_length - 64
suhosin.get.max_name_length - 64
suhosin.get.max_totalname_length - 256
suhosin.get.max_value_length - 512
suhosin.get.max_vars - 1000
suhosin.memory_limit - 0
suhosin.post.max_array_depth - 50
suhosin.post.max_array_index_length - 64
suhosin.post.max_name_length - 64
suhosin.post.max_totalname_length - 256
suhosin.post.max_value_length - 200000
suhosin.post.max_vars - 5000
suhosin.request.max_array_depth - 50
suhosin.request.max_array_index_length - 64
suhosin.request.max_totalname_length - 256
suhosin.request.max_value_length - 200000
suhosin.request.max_varname_length - 64
suhosin.request.max_vars - 5000
suhosin.session.max_id_length - 128
suhosin.upload.max_uploads - 25

Browser User-Agent String

Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C)