X-Cart forums

[Freakmode]

I had a couple of files sent to me by TXS, one for mobile only load init and one for both. We only waned mobile on phones no tablets but i agree that it should be based on screen size as I have a 10" tablet and a 5" phone both of which can take the full site.

[kevfromwiganinlancashire]

I have TXS xMobile template, there is a link for "full site" also there is a slider that comes out offering to take you to the mobile site. By default it shows mobile on iPad2 (10"?) and looks ok but you can select full site, also you can force the return to mobile slider to appear by scrolling the screen.


Kev

[Stizerg]

Did anyone try to replace jQuery with jQuery Mobile? Are all jQuery libraries should be loaded?

[carpeperdiem]

here's a minor bug that was easy to catch -- only needed to fix if you use the textarea input for product options -- such as a message or monogramming...

file:
/skin/txs_xmobile/modules/Product_Options/customer_options.tpl

FIND:

<textarea id="po{$v.classid}" name="{$poname}">{$v.default|escape}</textarea>

REPLACE WITH:

<textarea id="po{$v.classid}" type="textarea" name="{$poname}">{$v.default|escape}</textarea>

(the type="textarea" was missing)
there was no way to format this field without the type= defined


[EDIT] -- there was another way to edit this -- without defining type="textarea" -- define the width here:
@media only screen and (max-width : 446px) {
.contact-holder input[type="text"] {width: 170px;}
#b_country {width: 170px;}
textarea {width: 270px;height: 80px;}
}

This is a workaround... [/EDIT]

[carpeperdiem]

Originally Posted by Will Hayes

Hi Davy,

Yes, this looks like a good amendment to make to xmobile, we will discuss in more detail here today and let you (and other customers) know of the recommended changes. We've been researching the "official" word on this from Google and it seems to be good practice to include this response in the header, so we are happy to implement this:
https://developers.google.com/webmasters/smartphone-sites/details

we will keep you posted.

regards
W.

Will,
Any progress on the "vary" header?
Thx
J

[carpeperdiem]

I attended SMX conference in New York City this week. One of the speakers was a product manager from Google, who was discussing techniques best practices for delivering content to cross-platform devices.

Although on the surface it appears that Google is saying, "responsive" - what they REALLY are saying for sites that have the technology, they should be serving dynamically, EXACTLY as we are with xMobile.

The Googler said that for many sites, "responsive" solves the issue.
google does NOT want m. content
google does not want entirely different sets of content

When I asked the guy about dynamic content serving to each platform, he expressed that the tech to do this was out of the league of most SMBs and this was an enterprise solution.

When I told him that we had this available to us on x-cart, he was surprised.

I asked him about the vary header. I also asked him about indexing a slightly different page for mobile versus desktop.

He said that sites serving dynamically MUST follow webmaster guidelines to the letter, else risk penalty. But he also said in the same breath, that serving dynamically as we are with xMobile is "the best of both worlds". This method is superior to responsive in google's eyes if a site can pull it off technically.

SO -- back to post #51 -- Will, is xMobile using the vary header and following Google's webmaster guidelines to the letter? Yes or no, please?

Thanks
J

[Will Hayes]

Hi Jeremy,

Right now xmobile does NOT use this VARY header.

But we plan to implement a new option within the xmobile admin area to allow the admin to either switch this on or off.

As you know, the VARY header is a server response header. These headers are usually controlled at a server level, this is why we were a little reluctant to include this option before - but by allowing the admin to choose if they want to include the header or not, we can change the response header from within PHP if the admin wants it.

I think that is the best of both worlds.

regards
Will.

[carpeperdiem]

Hi Will,

I am a bit confused...
Ilya emailed me last week and told me:
"As I can see you already have "vary: user-agent" header in place."
And then nothing further when I put up a big ??? since 07 Oct.
Ticket: #VAL-920-79445

I have a meeting tomorrow with a google adwords account manager, and the subject of mobile utilization (and budget) are on the table. It would be best to know if xMobile is actually telling google who it is (vary header) or not.

Thanks in advance for the clarification.

J

[Will Hayes]

Jeremy,

I have no idea why you are confused, just take a look at my response above your last post on this very page (10-07-2013, 09:33 AM). I believe Ilya also responded to you on this directly before via our helpdesk.

Here it is again
Your "SERVER" is retuning the correct "vary" header - not xmobile.
The default functionality of xmobile does NOT return this header because it is not coded to do that. However, a server can be configured to return this header when it receives a HTTP request for a page. In your case, your server is responding with the correct vary header.

I also told you that we would update xmobile to include this option in the next version - allowing the admin to force the vary header to be returned from within xmobile itself (this way, we are not relying on the server response to intervene).

Install the following plugin for Firefox and check the headers from your xmobile page:
http://livehttpheaders.mozdev.org

regards
Will.

[carpeperdiem]

Originally Posted by Will Hayes

I have no idea why you are confused,

I'm confused because you said you were going to add this to xMobile, yet Ilya advised that my server is already sending the Vary: header, yet, I have no record of adding it, and a fulltext search on my server can't locate the source of this.

livehttpheaders reports:
Vary: Accept-Encoding,User-Agent

Ok. Is that the correct header?
If so, how is it getting there?

Is the Vary header something the host could have included in the php build?

Please help me understand what is going on... what does
Vary: Accept-Encoding,User-Agent
mean to the search engines?

I see the header entry:
Vary: Accept-Encoding,User-Agent

for both xMobile and desktop.
Is that telling Google that we are serving dynamic content.

I am truly not grasping what Google is expecting and what the server needs to send and what xMobile should be sending.
If this is a server side configuration, why would my VPS host setup php for this under normal circumstances?

I am going to ask my host for clarification as well. Thanks,
J