[MGNLSTK-518] When logo is not defined on a page, the page is requested from the server twice Created: 11/Nov/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: None
Affects Version/s: 1.1.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

From the user list:

I don't know.
These are the steps I made:

1) Duplicated stkArticle
2) Renamed as projectSearchResult
3) Duplicated paragraph stkSearchResult (in feature catalog)
4) Renamed as projectSearchResult
5) Changed paragraph modelClass to <package>.ProjectSearchResultModel
(the one you see in my original message
6) Instantiated a new page and assigned projectSearchResult tpl
7) Instantiated a new paragraph in mainArea of the page
8) called the page with ?queryStr=myText parameter at the end

9) Got 2 request!

I've replicated this also on demo.magnolia-cms.com, doing the following
steps:

1) create a new "untitled" page
2) calling it (so using POP theme..)

The second request seems to happen onDomReady event (jQuery / DOM
related..). Maybe a bug on STK POP Theme?

Just to be complete:

HTH, Matteo

I can confirm that this really happens. The simplest way to reproduce:

  • create new home page
  • check the http headers when opening the page (page is requested twice)
  • try as many times you want, the page will always be retrieved twice
  • open the "Page info" dialog, setup the logo and save the dialog
  • page is no longer requested twice, but only once


 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 07:27:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.