Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

CQ5 blog- Collab vs Social

Avatar

Level 3

I am working in CQ5 blog pages. The JSP's under collab/blog all say that  "DEPRECATED since CQ 5.6.  Use /libs/social/blog/ directly"

What difference will it make if I still wanna go ahead with the collab/blog pages instead of the newer social/blog ?

What are the underlying features that differ in these two Blog systems ?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

I've not dug into the 5.6 version of the blog component yet, but I have quite a bit of experience with the pre-5.6 version. To be honest, it's a feature that I've had some struggles with extending or customizing, but they seem to be making improvements version to version. For this reason, I would recommend using whatever is most recent.

Make sure to ensure that your licensing supports use of this component, though. Sometimes that can get a little tricky.

View solution in original post

2 Replies

Avatar

Level 10

When Adobe places makes a piece of software deprecated, it means that this piece of software will be dropped within a few releases. So having said that -- it works in the current version  - but in future versions - the functionality will be gone. You can still use it if you want; however, it is recommended that you use the new piece of functionality as opposed to the deprecated component. 

Avatar

Correct answer by
Former Community Member

I've not dug into the 5.6 version of the blog component yet, but I have quite a bit of experience with the pre-5.6 version. To be honest, it's a feature that I've had some struggles with extending or customizing, but they seem to be making improvements version to version. For this reason, I would recommend using whatever is most recent.

Make sure to ensure that your licensing supports use of this component, though. Sometimes that can get a little tricky.

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----