Blog view count is not increasing while selecting the specific page template
Written By
Pooja Bhambani
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
-
Steps to reproduce:
1. Start Liferay 7.3 SP3.
2. Create a new blog entry.
3. Deploy the blog on the page.
4. Now, create a new Display Page Template. By navigating to Design > Page Templates > Display Page Templates.
5. Create a new entry for blogs.
6. Navigate to the page where blog entries were deployed.
7. Now, create a new entry and select the 'Specific Page Template' which we've created in Step 4 > Publish.
8. Click on the created blog and it'll navigate to the view of the Display page template.
9. Notice, the blog view count is not increasing.
Expected Result: The blog view count must be increased when the user selects the 'Specific Page Template' for viewing the blog.
Actual Result: The blog view count is not increasing when the user selects the 'Specific Page Template' for viewing the blog.
Resolution
- The observed behavior is a known issue/bug.
- If a hotfix is required for this issue, please create a support ticket requesting a hotfix by attaching patch details.
-
Installing Fix Packs and Hotfixes on Liferay DXP will guide to installation of the hotfix in the respective environment.
Did this article resolve your issue ?