Can somebody explain the deffirent between WebContent Management 2DAY(Adobe DayCQ4) and CQ5 ?
CQ 4 is just an earlier version. CQ was initially develeoped by Day Software AG which was bought by Adobe a few years ago. The latest version is no longer called CQ but AEM though the continued with the numbering so it is AEM 6.
Though the basic concepts of CQ were introduced with CQ 4, CQ 5 is quite different. As CQ 4 is a legacy product, you don't find much information anymore.
Related
My sites are set up and working fine with the free version TinyMCE 5 in the cloud. I guess it's their AWS.
Can we continue to use it even though version 6 was apparently released? If so, for how long? Do they leave their old versions up and available?
Right now I feel "if something's not broken don't fix it."
Thanks.
TinyMCE 5 will continue to work to past March 15, 2023 - You can see exactly which version in the TinyMCE 5 series is supported in the Tiny Docs page on Supported Versions. This way, you can plan out a timeline for migration: https://www.tiny.cloud/docs/enterprise/system-requirements/#supportedtinymceversions
If you'd like to try TinyMCE 6 to see what it offers, the new documentation for TinyMCE 6 is also ready: https://www.tiny.cloud/docs/tinymce/6/
Migrating to TinyMCE 6 is straightforward – it involves adjusting the cdn script for accessing Tiny in the cloud, and then checking for Plugin and Option names that have been renamed in the transition from Tiny 5 to Tiny 6. The Migration guide has all the information: https://www.tiny.cloud/docs/tinymce/6/6.0-release-notes-overview/#overview
I am using Lucene 3.5.0 for index creation. Zend-Framework-1.8.2 with PHP-7.1.12 is being used to search index.
I have upgraded Lucene from 3.5.0 to 8.4.1. The indexes are now created with Lucene 8.4.1. But searching index gives error. I believe I need to upgrade Zend-Framework and PHP.
So, could anyone please provide the pointers on which Zend-Framework and PHP version is compatible to use with Lucene 8.4.1 indexes?
Well ... bad news for you.
The Zend Search component concerning Lucene is not maintained since years and has been archived a long time ago. Even on Packagist the package is marked as This package is abandoned and no longer maintained. No replacement package was suggested.
Same goes for Zend Framework. Even Zend Framework 3 is not maintained anymore. The follow up is the Laminas Framework.
My suggestion would be that you switch to Laminas, the successor to Zend Framework. Most components of the Laminas Framework are already PHP 8.1 compatible. Say goodbye to the ZendSearch component. This component is not developed further and will prevent you from using current PHP versions in the future. PHP 7.3 has reached an end of life already. PHP 7.4 is in a security fixes only state since december 2021 and will reach an end of life by end of this year. Zend Framework and ZendSearch will not work for the foreseeable future, if they should work now.
Just use one of the following alternatives:
Elasticsearch
Pucene
Solr
Sphinx
Very little has changed in a while for BIRT. Since the project seems still heavily used, it would be interesting to know if there are future plans and if so, what is entailed in those plans. Subsequently, based on the development status: Is BIRT still a safe platform to base development on or is it expected to just be conserved in the current state such that occuring bugs probably won't get fixed?
We decided to use BIRT instead of Jasper 8 years ago.
We are still using 4.2.1 for development and 4.3.0 for production runtime.
I reported several bugs since then and only very few of them got fixed.
Furthermore, I developed some patches to enhance the word emitter output - with no reaction from any one at all.
I also developed a patch to allow kind of a vertical tab (to place something at a fix y position on the page (but not in the page footer). With my previous experience of the community, I did not publish that one.
I can say that while the source code is quite easy to read, it is nevertheless almost impossible to understand what is actually going on, because the functions are extremely deeply nested.
My conclusion with 8 years experience of using BIRT for production:
PROS:
BIRT is very powerful and flexible, you can achieve some very cool results.
The quality of the resulting PDFs.
There are only very few things I miss and cannot work around.
The runtime engine is very stable and fast enough, very few problems.
The community is helpful.
CONS:
From an open-source perspective, it is one of the weakest projects I know of.
New versions tend to introduce more bugs than they fix.
Bugs, ideas and patches from the community seem to be ignored most of the time.
Lack of internal code quality and documentation.
Update Dec 2021:
BIRT is back again!
The open source project is quite busy (see answer by Alexander Fedorov) and every help is welcome.
It looks like there will be a new release soon.
Until then, building BIRT yourself (with Eclipse 2021-09 and Java 11) has become quite easy thanks to the common effort of the community.
Metadata and information about the health of an Eclipse project can be found on projects.eclipse.org:
The Birt project is still alive, but not as active as before:
there has been only one release per year since 2016 and
in the last three months there have been more than 20 commits from 11 contributors.
Like all open source projects, the success of the project depends on participation. Therefore, I encourage everybody to report bugs and propose changes to Birt and other open source projects.
Update: Good news, Eclipse Birt has been rebooted. It is under active development again, there have been more than 100 commits in two and a half months and the release 4.9.0 is scheduled for March 16, 2022.
The Eclipse BIRT project has been restarted recently, and we are working to prepare Eclipse BIRT 4.9 release.
Contributors are very welcome. Here is the brief instruction regarding steps how to join this effort: https://eclipse.github.io/birt-website/docs/community
Latest versions of BIRT are not available in maven.
When I say CQ5 I mean the version 5.5.
I would like to know the major differences in features.
I have seen AEM 6.0, the core of it is the same as CQ5. I checked out the examples, all the examples are the same, the only difference I found was the UI of WCM i.e. there is a new look and feel for it but you can still switch to the classic mode.
CQ5 still encourages coding in JSP i.e. it still uses scriplets.
Is there any alternative to using Scriptlets in AEM 6.x?
I feel Adobe just changed the look and feel of CQ5 and they have released a new version of it called AEM 6.x
What are the killer features of AEM 6.x that are not there in CQ5 ?
I would recommend you to take a look for release notes
I like below features quite a lot:
A new repository Apache Jackrabbit Oak.
Sightly, a new templating language that way you can avoid scriptlet code to a great extent.
Supporting better user management by delegating the permissions.
Create projects wizard & project templates
The above ones are very few which I have highlighted. There are many more so as per my opinion its not just UI changes so make sure you go through release notes to learn and then justify accordingly.
I was looking on the following question and would be interested how this might work in wicket 1.5:
Administrating internationalized wicket applications
Watch for updated properties in Wicket
Would be thankful for any help!
i18n in Wicket 1.5 (and 6.x, 7.x as well) is the same as in 1.4.