Resolved Bug


This bug has been marked as resolved.

Custom Attributes box blank

Permalink 6 0 Browser Info Environment
I had this problem iin v5.5.0 and it persist in 5.5.1. The Custom Attributes under Page Properties show a blank pop-up sccreen. See attached picture. The Meta box and more important Exclude from Nav option is not available under Custom Attributes.

For this reeasons, I downlgraded last time from 5.5.0 to 5.4.2.2. version . I noticed the same problem/bug exist. These are important features under Custom Attributes, this issue makes 5.5.1 crippled and not ready for prime use.

1 Attachment


Status: Resolved
ssiddiqi
ssiddiqi replied on at Permalink 2 Attachments
ssiddiqi
OK, it is a IE 9 and 8 specific issue. I log in to Concrete5 5.5.1 with FireFox and Chrome, the Custom Attributes box is OK. See attached picctures. IE9 and IE 8 show a blank Custom Attrbutes pop-up.
rsmitty replied on at Permalink
rsmitty
In IE9, nothing shows up for cusom attributes as shown above. I took a look at the code. If I comment out lines 27 & 32 in file concrete->elements->collection_metadata_fields.php, everything shows up ok. In IE8, a big error comes up right away when I click on page properties via the page and via the sitemap. The fix above does not fix that. I tested for C5 version 5.5 and 5.5.1.
ssiddiqi replied on at Permalink
ssiddiqi
Can we not do a "if" specific for IE9? I suspet it is a Java issue with IE9.
Brian1961 replied on at Permalink
Brian1961
I see the same problem ;-(

Does someone have a workaround for this ?
Brian1961 replied on at Permalink
Brian1961
I think it is getting even worth ;-(

We have 2 concrete5 5.5.1 site in production and on both I can't even change the page name (title) and other page properties in Internet Explorer 9.

Am I the only one that has seen this bug ?

I think that this is a huge Bug, as many clients use Internet Explorer... and telling them to update to lates version will cause problems.

We have also tested in IE8 and also here the Custom Attributes are not working correct and saving the properties also act strange as
it on IE8 made changes to title but cannot get out of edit mode.

Did nobody really test this before it was released at a recomended update ??? That is not cool

// Brian N
ssiddiqi replied on at Permalink
ssiddiqi
Per my experience, Concrete5 behave well in FireFox. I maybe wrong, but I think Concrete5 developers optimize it for FireFox. I had noticed minor hicks in Chrome. Internet Explorer versions do not behave well. I reported this problem for version 5.5.0 but it was not fixed in 5.5.1. You have two choices, either downgrade to 5.4.2.2. or use only FireFox.
Incompabilities with Internet Explorer actually crippled the Concrete5 5.5.x. A few people I know, are either reluctant to upgrade to version 5.5.x. One of them want to move to ImpressPages.
andrew replied on at Permalink
andrew
We are currently investigating this bug in IE8 and IE9 and will post back here with a fix for your site (and will also include this in an update.)
ssiddiqi replied on at Permalink
ssiddiqi
Thanks. I have worked out a temporary fix. It works for IE 9. I have not tested for IE8. in concrete-->element-->collection_metadata_fields.php, add <!--[if !IE 9]>-->
and after
<form onsubmit="return ccmPageAttributeSearchFormCheckResults()">
close the IF i.e. add <!--<![endif]-->
similarly at line 32 before </form> add <!--[if !IE 9]>-->
and add <!--<![endif]--> </form> save the file.

Also in your theme header.php add the following immediately after <head>
<!--[if lt IE 9]>
<script type="text/javascript" src="<?php echo ''.$this->getThemePath().'http://ie7-js.googlecode.com/svn/version/2.1(beta4)/IE9.js'?>"></script>
<![endif]-->

The above jascript from Google Code supposed to help with IE Java incompabilities. It does not thing for Custom Attributes bug.

With these changes, I have a working Custom Attributes (Page Properties) iin IE9, Firefox, and Chrome.
ssiddiqi replied on at Permalink
ssiddiqi
sorry some typing mistakes.
It should be in heder.php

<!--[if lt IE 9]>-->
<script type="text/javascript" src="<?php echo ''.$this->getThemePath().'http://ie7-js.googlecode.com/svn/version/2.1(beta4)/IE9.js'?>"></script>
<!--<![endif]-->
Mnkras replied on at Permalink
Mnkras
That won't work,

it should be

<!--[if lt IE 9]>-->
<script type="text/javascript" src="http://ie7-js.googlecode.com/svn/version/2.1(beta4)/IE9.js"></script>
<!--<![endif]-->
ssiddiqi replied on at Permalink
ssiddiqi
Thanks for correcction. This does help with Java incompabilities with IE.
ssiddiqi replied on at Permalink
ssiddiqi
The other work around could be take concrete->elements->collection_metadata_fields.php from 5.4.2.2 put it concrete->elements->, replacing collection_metadata_fields.php. The fonts kind of look big and dirty, but everything works in IE9,8, Firefox and Chrome. Make a backup of collection_metadata_fields.php before replacing it from 5.4.2.2 version. It worked at my system, but you never know.
AndyJ replied on at Permalink
In IE9 I just hit compatibility view and the attributes became visible...updated - apologies - thought this had worked but still did not allow me to save the attributes...
ssiddiqi replied on at Permalink
ssiddiqi
I tried compability mview in IE9 before reporting this bug. I had same issue. It was not saving the changes.

Make a backup of collection_metadata_fields.php and apply changes which I reported. It works
chages from line 27 to 32

<div class="ccm-block-type-search-wrapper ">
<!--[if !IE 9]>-->
<form onsubmit="return ccmPageAttributeSearchFormCheckResults()">
<!--<![endif]-->
<div class="ccm-block-type-search">
<?php echo $form->text('ccmSearchAttributeListField', array('tabindex' => 1, 'autocomplete' => 'off', 'style' => 'width: 155px'))?>
</div>
<!--[if !IE 9]>-->
</form>
<!--<![endif]-->
</div>
andrew replied on at Permalink
andrew
Thanks for pointing me to this. You can actually safely just remove both the form opening and closing tags from this include. That fixes the problem in IE9 and the instant search functionality still works in all browsers I tested (IE9, Chrome, Firefox).

I have included this fix in github as of this morning and it will be in the next concrete5 release.
andrew replied on at Permalink
andrew
I have checked a fix for this into github as of this morning.

concrete5 Environment Information

Windows 7, WAMP
Linux, php 5.3.8, Apache, mySql

Browser User-Agent String

Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; BRI/1; BRI/2)