Joel,
 
Most of the bugs centered around me begining able to use the FCKeditor with 
Firefox. I try and use the tool as out of the box as possible and my 
upgrades usually go very well. (learned that way back in 1999!) I allow 
users to customize things like tables and graphics sometimes outside of CSS 
and need to use either the supplied RedDot Text editor or FCKeditor becuase 
of the easy end user interfaces. Most of the FCKeditor issues are the same 
as in version 10 if you are using that version. Here is a summary of my bug 
tickets for FCK. Jump Marks will set in content but not be found to link 
to.(You can set a jump mark target in the text and then link to it in 
the RAD editor if necessary) I use the Database to house my assets and 
there are issues with using FCK to link to files, the issues are fixed 
partically in a HF but it is only working for certain file types. (Images 
but not PDF files, weird but true) My workaround for users who want to use 
Firefox and FCK is to upload their files using the RADeditor (in 
Firefox) and then switch back to FCK. I only recommend this for seasoned 
editors who can understand the concept. I have all levels of users on the 
system. There are still limits on file size due to IIS (out of the box) on 
MS Server 2008 R2. I use MS SQL 2008 R2 as well. 
 
If you use the database to house your assets and do not use the Asset 
Manager (we do not own it) and try and use the Folder jobs in SmartTree 
named Asset Manager Maintenance or Asset Control they do not work in 
version 11 with HF1-3. They work fine in version 10. The only work around I 
was offered until the HF comes out with be to Transfer Data Storage folder 
content into the local server. This is not an option as there is no way to 
un-convert it back to the database storage for ease of Exports and Imports. 
 
One huge note with using the Database to store your assets is when your 
publication jobs run they will publish ALL assets even if they are not 
modified. This is in a bug ticket I have too. BUT!!!! even with all my 
assets publishing from the database storage my publication times are cut in 
HALF! I can't wait till the bug fix for the database storage publication to 
be fixed becuase I think the publication will be even faster. 
 
I have not noticed anything major in the RedDot Text Editor if you are 
using that BUT if you want your users on multiple platforms. Letting them 
switch between IE and FireFox and highly customize things like table/images 
users will have to stick to one platform (IE or Firefox) or else some of 
the code will be wiped when the go back to the RedDot Text editor becuase 
of the way it codes things like Image right/left etc and Table colors.
 
I can explain anything else in detail if necessary I don't want to get to 
long winded. 
 

On Friday, June 29, 2012 10:45:52 AM UTC-4, Joel Kinzel wrote:

> Just curious what bugs you've found? We are getting ready to upgrade and 
> any bugs would be good to know about going into the upgrade! 
>
> On Wednesday, June 27, 2012 1:27:06 PM UTC-5, SLC Webmaster wrote:
>>
>> This is good news to hear. Upgraded a few weeks ago to 11 HF 3 from 10.1 
>> and waiting for the next few hot fixes to fix some bug tickets I have 
>> submitted. Users seem to be happy. Publication time was greatly reduced. 
>> There are some issues with publication since all assets are database stored 
>> and not locally on the OpenText (We do not own Asset Manager), but those 
>> bug fixes are submitted and I think publication times will be even faster 
>> with a HF. 
>>
>> On Saturday, June 9, 2012 5:08:00 AM UTC-4, Christoph Straßer wrote:
>>
>>> Migrated our old productive WSM 10.1 SP2 / W2K3 - system yesterday to a 
>>> new W2K8 R2 with WSM 11.0 HF3. (Have about 30 projects, some of them are 
>>> pretty large.) Almost everything looks good so far. At least compared to 
>>> the older versions. ;-)
>>> We are looking forward to next week, when our authors / content editors 
>>> start working with the new 11.0 - system. Personal feeling is good, but you 
>>> never know whether users raise some (error-)conditions no one expected 
>>> before...
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"RedDot CMS Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/reddot-cms-users/-/hVqgdYtZFNAJ.
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/reddot-cms-users?hl=en.

Reply via email to