X-Cart forums

[albertchui]

i solved most of the insecured item, now only left one "canonical " which locate in /skin/common_files/customer/service_head.tpl


{if $config.SEO.canonical eq 'Y'}
<link rel="canonical" href="{$current_location}/{$canonical_url}" />
{/if}


this show: <link rel="canonical" href="http://www.iphonecasestudio.com/"



does anyone advise how to fix it, very appreciated, thanks

albert

[DavyMac]

I've just noticed that the register page is missing some useful javascript that is available on the default XC. Specifically, the XC default register page has a javascript that provides an information block that explains why the email address is required, and also the default XC ensures that a password is at least 7 characters long.

With my xtreme gear template clicking in the email field doesn't provide the information block and users can set passwords with only one character!!

Could you please let me know if these scripts are working for you? If they are then I'll know that I need to do some digging - thanks

EDIT - Sorry, just noticed that default XC doesn't check length of password, so I'm only missing the email information block

[carpeperdiem]

Originally Posted by DavyMac

I've just noticed that the register page is missing some useful javascript that is available on the default XC. Specifically, the XC default register page has a javascript that provides an information block that explains why the email address is required

With my xtreme gear template clicking in the email field doesn't provide the information block

In my 4.5.5 and 4.5.4 dev, AND my production 4.5.4, there is a script that includes:

$(function() {
  $('#email')
    .live('blur submit', function(){
      $('#email_note').hide();
    })
    .live('focus', function(){
      showNote('email_note', this)
    });

This is loaded via an include in file,
/skin/xtreme_gear/customer/main/register.tpl

{include file="check_registerform_fields_js.tpl"}

and I have no idea why the function does not work????

I will open a ticket with TXS on this.

[carpeperdiem]

This js popup doesn't work on xTreme demo site either...

http://demo.thexcartstore.com/xgear/register.php

[carpeperdiem]

xTreme featured category items do not include image size or image alt/title tags... you can fix this:

file:
/skin/xtreme_gear/customer/main/featured_categories.tpl

FIND:

<img src="{$fc.image_url}" alt="" title="" />

REPLACE WITH:

<img src="{$fc.image_url}" alt="{$fc.short_tag}" title="{$fc.title}" width="{$fc.image_x}" height="{$fc.image_y}" />

[DavyMac]

This is such a newbie question that I'm embarressed to ask, but I never get this right - I wish to change the background-image in the altskin.css but when I do the change is not reflected in the cached file!
I call cleanup.php and force cache regeneration but the cached file is not updated.

How do I get my background-image edit picked up?

What confuses me is that when I change other elements in the altskin.css I don't need to do anything to get the changes copied to cache!!

[carpeperdiem]

Originally Posted by DavyMac

This is such a newbie question that I'm embarressed to ask, but I never get this right - I wish to change the background-image in the altskin.css but when I do the change is not reflected in the cached file!
I call cleanup.php and force cache regeneration but the cached file is not updated.

How do I get my background-image edit picked up?

I know, css images can be frustrating.
Browser also caches images... try purging your browser cache?
Verify the path to the new image. Did you rename the image?
Css images appear to play by different rules... and they cache.
HTH
J

[DavyMac]

Originally Posted by carpeperdiem

HTH
J

It does by confirming what should be done, thank you. css images are my kryptonite - I rarely get the process right!

EDIT - I'd forgotten to uncheck the "Use speed-up tool for CSS" under the optimization settings. All sorted now!

[carpeperdiem]

While I'm solving the CDN image calls in xMenus, may as well solve the remaining image in xTreme that is not served vy the cdn.

for xMenus, see:
http://forum.x-cart.com/showthread.php?p=362638#post362638

If anyone is going to use xtReme with a CDN AND you want the images served from your cdn, you need to edit file:
/skin/xtreme_gear/customer/footer.tpl
FIND:

{if $xg_config.footer_secured ne ''}
	<div class="footer-bottom-icons">
		{$xg_config.footer_secured} 
	</div>
	{/if}

REPLACE WITH:

{if $xg_config.footer_secured ne ''}
	<div class="footer-bottom-icons" >{if $smarty.server.HTTPS eq "on"}{$xg_config.footer_secured}{else}
		{$xg_config.footer_secured|replace:'img src="images':'img src="http://cdn.domain.com/images'}{/if}
	</div>
	{/if}

This traps for https.
Uses CDN if http. Else htps (not cdn)

Your paths may be different, but this is the general idea.

HTH

J

[carpeperdiem]

<rant>
There is no justification for

<meta http-equiv="X-UA-Compatible" content="IE=8" />

to be a DEFAULT in 2013

in file
/skin/xtreme_gear/customer/meta.tpl

FIND:

<meta http-equiv="X-UA-Compatible" content="IE=8" />

REPLACE WITH:

<meta http-equiv="X-UA-Compatible" content="IE=9; IE=8; IE=7; IE=EDGE" />

Geez. I thought IE just sucked (that's debatable) - but finding disruptive code in a MODERN template is simply bad... make that code go away!

</rant>

PS -- IE10 doesn't suck as much as some have been saying. IE10 "metro" on the other hand...