These blog items should be stored somewhere in the JCR - like everything
else in AEM. YOu can look at writing a service that can read them, put
them into a collection and them display them where needed.
You can learn all about Editable Templates here: 1 - Scott's Digital
Community: Guided Journey for Experience Manager on Editable Templates 2
- Adobe Experience Manager Help | Creating an Adobe Experience Manager
6.4 website using Editable Templates 3 - muich larger end to end - WKND
Tutorial Overview Go through these and you will understand how to work
with editable templates and how to create AEM sites by using them.
There is no OOTB way to do this. You should consider moving to Editable
Templates with AEM as that reflects best practice. Also - with policies,
you can control which components an author has access to on a given
page. If you are not familiar with Editable Templates - watch - Scott's
Digital Community: Guided Journey for Experience Manager on Editable
There seems to be a bug here. See the following pic: My OSGi bundle is
active that exposes the required database SQL SERVER driver file. Yet --
there is an error in the LOG file that says it cannot be found. This
does not behave the same as the MySQL Driver file. I recommend opening a
SUPPORT Ticket and state the MS SQL Server Driver file cannot be found
even though its deployed in an active state,
I have only ever used MySQL for the DataSourcePool use case. I have SQL
Server on my DEV Machine. I will test this out and post back. I would
think this could be a DRiver File issue or COnnection String issue when
you setup the configuration required.
We have plenty of video and articles on using MySQL with AEM. See: Adobe
Experience Manager Help | Querying MySQL data using an Adobe Experience
Manager 6.4 DataSourcePool This will show you step by step on how to get
this use case implemented. See the video too at the end of this article.
When you say Template - do you mean the component code? Anyhow - if you
want to perform this task in the HTL itself (I would recommend Java and
Sling Models and use HTL as a view), - see: htl-spec/SPECIFICATION.md at
master · adobe/htl-spec · GitHub
How did you build this? The issue is wrong version is reference. You can
eliminate this error by opening the Manifest file in the OSGI bundle and
remove version. Then the bundle will pick up version AEM exposes.
You need to use Sling Models. You can find the answer in this AEM HELPX
COMMUNITY Article: Adobe Experience Manager Help | Creating a HTL
Repeating Data Set 6.4 Component that uses Sling Models Hope this