Response title
This is preview!
Move this topic
1.1.4 is duplicating page containers
in jQuery Mobile
•
8 years ago
I have a production site that I have been converting from 1.3.2 to 1.4.4
and have just hit a problem with chagnePage() and
pagecontainer('change") duplicating a page container in the
DOM. I have a list of items that I can edit and when I click on an
item's button and this code runs.
- $("body").pagecontainer("change","/maintainPromo/",{'type':'post','reloadPage':true,'data':{'marketcampaignpk':mrkid}});
- $("#br_promoMaint").remove();
before changPage fixed the problem but surly there is something
wrong going on here. I also tried changing reloadPage:false
and got the same result.
Is there something I am doing wrong or is this a bug?
Thanks.
1
Replies(10)
Re: 1.1.4 is duplicating page containers
8 years ago
It's not "duplicating a
pagecontainer". That's impossible There is one page
container. It is the
<body>
element. There is some confusion over the page
container widget because it was
written so that in some future version there might be multiple page
containers. (e.g. load a page into some div).
There's nothing unusual about this. The first page loaded is always retained. If that bothers you, you can remove that page.I can see two pages with the same ID.
You should not use IDs on pages
unless you are using a multi-page documents. You should avoid
IDs as much as possible. There are problems using IDs in
JQM because you cannot duplicate a page in a document, and
that is very hard to manage in JQM, because it means you
cannot duplicate an ID in your entire project.
Your "fix" worked by
accident. It removed only the first page,
because if you duplicate an ID
and search for it, the browser will give you only the first
element with that ID.
An ID is like an address. There
should not be more than one "20 Elm Street" in the same
city (document).
Leave a comment on watusiware's reply
Re: 1.1.4 is duplicating page containers
8 years ago
-
I am using multi-page documents and my production version is working just fine.
-
It is duplicating page containers. If I edit a row and hit the back button 6 times then I have 6 page containers with the same ID.It's not "duplicating a pagecontainer". That's impossible There is one page container. It is the <body> element. There is some confusion over the page container widget because it was written so that in some future version there might be multiple page containers. (e.g. load a page into some div). -
- I think I found the problem. By setting data-dom-cache to false
fixed the issue. Smells like a bug to me.
-
-
Leave a comment on jimboidaho's reply
Re: 1.1.4 is duplicating page containers
8 years ago
It is not duplicating page containers. <body> is the page
container. There is one page container.
Maybe you mean something else.
You still haven't shown us any code or markup that will
demonstrate the problem. It's hard to help when all you give is a
fragment of code
Make a demo page or create a jsFiddle, and we can tell you why it
is doing what it is doing.
You aren't trying to mix single-page and multi-page are you?
You can't do that. If you use multi-page ALL of the pages need to
be included in the document. You cannot load additional pages.
If you do, "back" will misbehave. As well, if you try to
load a multi-page into a single-page, it will only load the first page.
The two are like oil and water. They do not mix.
Simple decision tree for single-page/multi-page:
- Do you have a very small site or app, a half-dozen pages or less,
and it will never get bigger than a half-dozen pages ever in the future?
yes -> use multi-page, at your own risk
no -> use single page
Leave a comment on watusiware's reply
Re: 1.1.4 is duplicating page containers
8 years ago
Sorry for the misunderstanding. The duplication was at the
data-role="page" level. The problem started after
upgrading to 1.4.4 and it happened anywhere a page was being called from
an edit list. The problem was fixed by
setting data-dom-cache="false". Here is how
most of my pages are formatted.
<div id="br_main" data-role="page"
data-dom-cache="true" data-theme="a">
<?php echo $this->setMenu() ?>
<div data-role="header"
data-position="fixed" data-tap-toggle="false" data-theme="a">
<?php $this->includeHeader('hdr_main'); ?>
</div><!--end
Header div -->
<div id="mainContent"
data-role="content" class="main-content">
<h2>
<?php echo $this->getHeader() ?>
</h2>
<?php echo $this->getContent() ?>
</div>
<!--end Content div -->
</div>
Leave a comment on jimboidaho's reply
Re: 1.1.4 is duplicating page containers
8 years ago
There is no reason to set data-dom-cache
to true if you are using a multi-page document. The page is already
cached. data-dom-cache
is only useful when using single-page documents. It tell jQuery Mobile
not to remove the page when you navigate away from it.
It's not very helpful to post PHP code code. Instead, post the
HTML that the PHP produces. jQuery Mobile doesn't know or care
what language you use on your server, and in any case, we can't
guess what HTML it produces.
Easiest way to get help here: post a link to your site or set-up a
jsFiddle. Posting bits and pieces gets guesses, not answers.
Leave a comment on watusiware's reply
Re: 1.1.4 is duplicating page containers
8 years ago
There is no reason to set data-dom-cache to true if you are using a multi-page document.I have a list of items that can be edited and when I edit the item and go back to list page, the list refreshes when set to false. Not a big deal so I set all data-com-cache to false.
I should have taken the PHP code out. What I was trying to
show was all my pages are doing this when data-dom-cache is set to
true and this wasn't the case with 1.3.2. My site generates
most of the code on the fly so it is difficult to show code.
I really don't know how to setup a mock up using jsFiddle
since I need to call external pages. My site is mostly under
password protection so I guess I will leave at that for now.
Thanks.
Leave a comment on jimboidaho's reply
Re: 1.1.4 is duplicating page containers
8 years ago
since I need to call external pages
This
is your problem.
You
CANNOT mix multi-page and single-page documents. Pick one.
IMO
multi-page is over-used. It is appropriate for a very small site
or app with a very limited number of pages. It is for the very
limited case of some little site or app with, say, 4 or 5 pages.
PERIOD. A "micro site".
The documentation now cautions
about this (it didn't always) but for some reason a lot of
developers fall in love with the multi-page document concept. It
is deeply flawed unless your site/app is one of the few that is
suitable for it.
It does provide a convenient
way to create small multi-page demos, and that is part of the
problem. Way too many demos have led developers astray because
they were written as a multi-page document. Typically, they
are demonstrating something else - a
multi-page document was used to "simplify" the demo -
and the author has neglected to caution that multi-page is
usually not practical for real sites.
It is extremely limiting,
your site/app almost certainly WILL outgrow it, and then
it is a very costly and time-consuming refactor to rewrite the
site once it has been built-out to some considerable size.
Do your self a favor and switch
to single-page documents while it is still practical to do so.
Leave a comment on watusiware's reply
Re: 1.1.4 is duplicating page containers
8 years ago
Not sure how you figure I use
multi-page documents out of wondering how to load single page
documents using
jsFiddle
. I have never used multi-page
documents. I never like the concept.
In summary, when I upgraded from
1.3.2 to 1.4.4, any page that had
data-dom-cache="true" would not release when
navigating back and the page would be added again to the dom each
time the page was loaded again. The problem was solved by
setting the data-dom-cach="false".
Thanks.
Leave a comment on jimboidaho's reply
Re: 1.1.4 is duplicating page containers
8 years ago
I am using multi-page documents and my production version is working just fine.
I have never used multi-page documents. I never like the concept.
Yes. Because that is EXACTLY what data-dom-cache="true" is SUPPOSED TO DO!any page that had data-dom-cache="true" would not release when navigating back
If you didn't want to keep pages after the user navigates
away from them, do not use data-dom-cache="true".
You do not have to explicitly set it to false, though, because
the default value is false. It hash nothing
to do with the JQM version - this has always been the case.
To avoid confusion, I would urge others to post a link to their
site or to set-up a jsFiddle, instead of playing a game of 20
questions. If you show us a complete example of what you tried,
then any confusion over terminology can be easily clarified.
Leave a comment on watusiware's reply
Re: 1.1.4 is duplicating page containers
8 years ago
Which is it?
My
bad. I do
not
use
multi-page documents.
Yes. Because that is EXACTLY what data-dom-cache="true " is SUPPOSED TO DO !OK. That makes since so I guess there was a behavior change between 1.3 and 1.4.
All
is well and thanks for all your help.
JIm
Leave a comment on jimboidaho's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic
Reply to jimboidaho's question