[SOLVED] new 5.0.7ne install 2 items

[jason]

was 5.0.6ne, now I installed 5.0.7NE w/o problems, but have 2 questions:

1) This time on the install script it added a new Y/N for 'convertd' with 'N' as default. I did not see this at all in the 5.0.6NE script. I searched what this was and looked like it was in previous versions possibly for converting attachments to HTML? I am still not sure, so I did not install it. What exactly is convertd / what does it do /is it required?

2) Release notes for 5.0.7 FOSS mentioned 'chameleon skin' availiable, but it is not there for 5.0.7NE, or at least not on my fresh install. Will there be one available elsewhere?

Thanks for your guidance.

[gnyce]

I also would be interested in these two items before I do our upgrade. With regard to No. 1), the release notes say:

"An alternative implementation of the convertd daemon used for text
extraction and conversion to HTML is now available as beta in 5.0.7. The
new implementation is Apache multi-process based, as opposed to the
original implementation which was multi-threaded. When libraries used to
handle attachments fail or crash, the multi-process implementation allows
for better availability. Since the new implementation is still in beta, the older
multi- threaded implementation continues to be the default. If you are
experiencing a high number of 400 (try again) error codes during LMTP
delivery, or if you are seeing too many kvoop processes consuming
memory, you can try the new Apache-based convertd.
Run /opt/zimbra/convertd/bin/upgrade_v2 to upgrade.
Run /opt/zimbra/convertd/bin/downgrade_v1 to downgrade.
You must install the new zimbra-convertd package for it to be available.
(Bug 2161)"

So by not converting it, you cannot use the v2, but if it is not the default behavior, that might not be a bad thing.

[mmorse]

Originally Posted by jason

2) Release notes for 5.0.7 FOSS mentioned 'chameleon skin' availiable, but it is not there for 5.0.7NE, or at least not on my fresh install. Will there be one available elsewhere?

It's not a skin, it's the ability to set these per domain:
zimbraSkinLogoLoginBanner
zimbraSkinLogoAppBanner
zimbraSkinLogoURL
zimbraSkinSecondaryColor
zimbraSkinSelectionColor
zimbraSkinForegroundColor
zimbraSkinBackgroundColor
See Bug 24164 – Need "chameleon" skin for more info.

[LMStone]

Originally Posted by mmorse

It's not a skin, it's the ability to set these per domain:
zimbraSkinLogoLoginBanner
zimbraSkinLogoAppBanner
zimbraSkinLogoURL
zimbraSkinSecondaryColor
zimbraSkinSelectionColor
zimbraSkinForegroundColor
zimbraSkinBackgroundColor
See Bug 24164 – Need "chameleon" skin for more info.

Hi Mike,

This looks great, thank you, but neither the bug report nor the NE Release Notes (unless I missed it) give the zmwhatever command syntax for implementing this.

Can I keep the logo files out of the /opt/zimbra directory tree?

Do I need to set all of these attributes or can I just set the logo file ones?

Will setting these attributes survive a ZCS upgrade?

The Andy Clark's comment in the bug report says one has to set a virtual hostname attribute for this to work. Is that still true?

Anything else I should be asking? :-)

Thanks for this; this is an important client fix for us!

All the best,
Mark

[phoenix]

Originally Posted by LMStone

This looks great, thank you, but neither the bug report nor the NE Release Notes (unless I missed it) give the zmwhatever command syntax for implementing this

Mark

It's a zmprov command and full details of this change are on P24 of the Release Notes.

[LMStone]

Originally Posted by phoenix

Mark

It's a zmprov command and full details of this change are on P24 of the Release Notes.

Thanks! I must have had a "senior moment" there going over the Release Notes the first time!

All the best,
Mark

[DEREKB]

Mark,
have you tried implementing this logo per domain option ?
I've setup domainA to point ot one set of logos and domainB to another set.

There seems to be inconsistent results. If I browse to domainA then the correct logo shows. If I then browse to domainB it changes to the second set of logos. If I then broswe to domainA again the logos don't refresh and the domainB logos remain on-screen.

I've tried this is IE 7,8 Beta and Firefox 2 & 3 . Same behavior. I've tried refresh browsers with ctl-F5 and clearing out all caches etc.
I've tired it from multiple PC's.
I've also tried shutting down zimbra and clearing the java "work" folder.

Would there be jetty caching going on server-side whereby it's not fully rebuilding the page when it sees the request coming from the same IP address within a few minutes of the last request

Anyone else tried the "chameleon" skin option ?

[mmorse]

Fixed for 5.0.8: Bug 29706 – Skin overrides only work for one domain

[DEREKB]

that new Skinresource.class file has done the trick. Everyone is happy now !
Thanks,