CQ5 Updates

As we come across issues or tips that I think would be beneficial to authors, I'll update that information here.
-Erin Yarbrough

The green indicator boxes in the 'published' column should show you which pages have been activated and when. The blue boxes should show which pages have been modified since activation. BUT... alas this isn't working as it should. We've stood up a second authoring environment (let's call it author 2) for disaster recovery in the event something happens to the author environment you use (let's call this one author 1). And, the way we make sure Author 2 is identical to Author 1 is by pushing any changes you make to your site from Author 1 to Author 2. We're essentially publishing content changes between two authoring environments. Therefore the system sees we're publishing content even though it's not being pushed live (just to Author 2). Don't believe the little green boxes.

11/24/09

It's come to our attention that when you create a hyperlink and then decide to change what that link is, you have to first remove the existing link (unlink) before adding the correct one. It's annoying - but just an FYI until we know why or how to fix.

11/12/09

Weirdo yoga lady is gone and we now have a new login page. :)

11/12/09

Don't you like to see messages that say "fixed" within them? I sure do :)

We'd had an issue up until last week where frequently users couldn't log in to cq5author.ou.edu and we'd have to restart the system on our end. We put a fix in last week that so far has proven successful. Zero restarts since.

11/3/09

Some of you may have noticed an annoyance in the system of kicking you out while you're working, taking you to the login screen, but not offering you a place to log in again. Sigh, we suffer from this too. We've done as much research on our end that we can and have a ticket in for this. We'll update here when we get a resolution. It's frustrating, but you can close out your browser and reopen to solve the issue for now.

9/14/09

The table component is lacking as it stands now. However, we have a hotfix installed in our test environment that completely re-works the current component. Merge cells, add rows/columns anywhere in the table and set table dimensions - oh my! This is how the table component should work, for sure. Hopefully we'll be able to deploy this to your author environment later this week after additional testing.

9/14/09

We've found a bug with the system that when you try to activate a digital asset with a comma and space, it won't activate and ends up blocking everything else that gets activated after that. So, until we get a resolve for the issue, change all file names that include ", " during upload. For example, a file: "yarbrough, erin.pdf" could be changed to "yarbrough,erin.pdf" and should activate just fine

9/14/09

Last time we were installing updates to author I failed to ensure the management page we built for the Digital Assets was copied over correctly. So... while you can get to the page, it's not displaying correctly. We'll work on this and post here when it's resolved.

9/10/09

We've noticed an error has started happening where you can add an OU Text component to the page but after saving text, nothing shows on the page:

1) After you enter content and click "ok," you may see a message pop up and say "200" and give you the option to click "OK."

2) You click OK and alas, no content shows up.

3) After opening the component back up to check the content, you see the text for a split second and then it disappears. 

I say all of this as a warning until we figure out what the issue is - save as much as possible when you're creating new text on your page. I haven't seen the issue yet when you're editing text - only if it's a new text component.

9/10/09

I mention in the CQ5 training videos that there's an issue with versioning in author. But, I don't really explain what the issue is. The problem we've run in to with versions is that when you try to "roll back" to a previous version, the page sometimes freaks out and throws and error on to the page instead of your content. This is an issue that only occurs when an OU Text/Image component is on the page, but it also doesn't occur EVERY time that component is on a page.... so weird.

The good news is that there's a hotfix out for this issue - we just haven't been able to test thoroughly enough yet. When we do and it's working, I'll post it here.

9/10/09