Westminster New

gsh68:

Anyone know how to get the categories sidebox showing on the main page on 1.5.6C and v2.0 template?
On the previous versions (1.5.5 + v1.3 template) it was simply a case of removing/commenting out a line in tpl_main_page.php

if ($this_is_home_page) {
$flag_disable_right = true;
/* $flag_disable_left = true;*/
}

> However v2 has significantly changed and I can't find a way to do it.
> Thanks.

Bumping hoping someone has found a way to display category left column on main page.

One quick question. Is there any way I can "zoom in" my whole page permanently? This template looks a little bit too close to me (font is large, picture is large, spacing is large, etc), so I have to use the zoom in/out tool from my browser to zoom in my page.

njcyx:

One quick question. Is there any way I can "zoom in" my whole page permanently? This template looks a little bit too close to me (font is large, picture is large, spacing is large, etc), so I have to use the zoom in/out tool from my browser to zoom in my page.

I put "zoom:80% !important" to body of stylesheet.css, and it worked. All pages have been zoomed in to 80%. But it somehow broke the display of reCaptcha. Need to find a way to resize reCaptcha...

njcyx:

I put "zoom:80% !important" to body of stylesheet.css, and it worked. All pages have been zoomed in to 80%. But it somehow broke the display of reCaptcha. Need to find a way to resize reCaptcha...

Update. Still cannot find good way to resize reCaptcha. Tried to use "transform: scale" to zoom out the page instead (sorry for my typo in my previous posts), and it worked. It doesn't break reCaptcha neither.

It appears there are some issues with this template on PHP newer then 7.0. If I go up to PHP 7.1, I get this error log:

[18-Jan-2020 07:20:59 Australia/Sydney] Request URI: /, IP address: 173.183.94.130
#1  require(/***/includes/templates/westminster_new/common/tpl_main_page.php) called at [/***/index.php:97]
--> PHP Warning: A non-numeric value encountered in /***/includes/templates/westminster_new/common/tpl_main_page.php on line 74.

If I go up to PHP 7.3, I get this error log:

[18-Jan-2020 07:22:54 Australia/Sydney] Request URI: /, IP address: 173.183.94.130
#1  require(/***/includes/templates/westminster_new/common/tpl_main_page.php) called at [/***/index.php:97]
--> PHP Warning: Use of undefined constant SET_COLUMN_LEFT_LAYOUT - assumed 'SET_COLUMN_LEFT_LAYOUT' (this will throw an Error in a future version of PHP) in /***/includes/templates/westminster_new/common/tpl_main_page.php on line 69.

[18-Jan-2020 07:22:54 Australia/Sydney] Request URI: /, IP address: 173.183.94.130
#1  require(/***/includes/templates/westminster_new/common/tpl_main_page.php) called at [/***/index.php:97]
--> PHP Warning: Use of undefined constant SET_COLUMN_CENTER_LAYOUT - assumed 'SET_COLUMN_CENTER_LAYOUT' (this will throw an Error in a future version of PHP) in /***/includes/templates/westminster_new/common/tpl_main_page.php on line 74.

[18-Jan-2020 07:22:54 Australia/Sydney] Request URI: /, IP address: 173.183.94.130
#1  require(/***/includes/templates/westminster_new/common/tpl_main_page.php) called at [/***/index.php:97]
--> PHP Warning: Use of undefined constant SET_COLUMN_RIGHT_LAYOUT - assumed 'SET_COLUMN_RIGHT_LAYOUT' (this will throw an Error in a future version of PHP) in /***/includes/templates/westminster_new/common/tpl_main_page.php on line 74.

[18-Jan-2020 07:22:54 Australia/Sydney] Request URI: /, IP address: 173.183.94.130
#1  require(/***/includes/templates/westminster_new/common/tpl_main_page.php) called at [/***/index.php:97]
--> PHP Warning: A non-numeric value encountered in /***/includes/templates/westminster_new/common/tpl_main_page.php on line 74.

This is a fresh install on 1.5.6c.

Fresh install 1.5.6c
Westminster New installed 2.0
PHP 7.1.33

No Log errors

Mike

I just updated my templated to the westminster new and now my admin panel is not loading.

WARNING: An Error occurred, please refresh the page and try again.If you were entering information, press the BACK button in your browser and re-check the information you had entered to be sure you left no blank fields.

The body width in desktop mode is 980px, but the header and footer are 100%. So my logo moves to the far left behind the Left Slider Icon.

I found in Firefox Web Tools the <div id-"mainwrapper" class-"layout" style-"max-width: 100%; margin:auto;">

I changed the width in web tools to 980px and it worked on the current browser view. But I cannot find where to change it in the CSS files or template files.

I too have been trying to get the left sideboxes on the home page. Have spend about 10 hours trying to figure it out! Extremely frustrating. I keep finding references to the fix for the older version, but nothing for Version 2.0. Anne, if your listening, I will gladly pay to end this suffering :)

Working on Meta Tags. I added the necessary tags in the english/westminister_new/meta_tags.php file. But when I look at the html source, they are either not there or incorrect. Any idea why ??

meta_tags.php

// Home Page Only:
define('HOME_PAGE_META_TITLE', 'Free Style Horse Walkers and Hot Walkers By ProWalk Mfg.');

define('HOME_PAGE_META_DESCRIPTION', 'Horse Walkers By Prowalk. The Best Value Horse Walker In America. Several Lead Models and Free Style Designs. Most Models Come With Lifetime Chassis Warranty.');

define('HOME_PAGE_META_KEYWORDS', 'automatic horse walker,4 horse walker,6 horse walker,horse walker texas,horse walking machine,horse-walker,equine exercise,equine exercisers,equine fitness,equine training,free style walker,free style walkers,free walker,free walkers,horse exerciser,horse fitness,horse gyms,horse training,horse walker,horse walkers,hot walker,hot walkers,lead walker,prowalk,prowalk horse walker,prowalk mfg,superior horse walker,superior walker,superior walkers,bucking bronc,compare horse walkers,quarterhorse,race horses,race track,rodeo horse,roping horse,roping horse fitness');

// NOTE: If HOME_PAGE_TITLE is left blank (default) then TITLE and SITE_TAGLINE will be used instead.
define('HOME_PAGE_TITLE', 'Free Style and Lead Horse Walkers by Prowalk'); // usually best left blank

Home Page HTML Code

Figured it out. Godaddy migrated my sites to a different server. My FTP program was set for the old IP and I was sending updated files to it. Got it fixed this morning, ftp'ed over the fixed mega_tags.php file and now all the meta tags are correct. Been doing web sites since 1996, never had that happen before. Lesson learned: Don't use the IP address in your FTP program if you have shared hosting.

My concern would be a host that changed IP addresses without notifying the customer.

a site that has zc 1.5.0 has this template. So though there is a upgrade included in the most recent template version, has anyone tried upgrading from such an old version? The template version is 1.3.

I have installed "fresh install" on Zen-cart 1.5.5f of the westminster_new2.0 template. When I select the template and refresh my site, I get a completely blank page in firefox, opera, ie and so on. If I change back the the standard responsive template, my site loads up just fine. Now for the kicker. I've looked in all the log file locations both in zencart and also on my host and find nothing pointing to any errors. Can someone point me in the direction of find the errors and then possibly fixing them.

Thanks

mstevens23:

I have installed "fresh install" on Zen-cart 1.5.5f of the westminster_new2.0 template. When I select the template and refresh my site, I get a completely blank page in firefox, opera, ie and so on. If I change back the the standard responsive template, my site loads up just fine. Now for the kicker. I've looked in all the log file locations both in zencart and also on my host and find nothing pointing to any errors. Can someone point me in the direction of find the errors and then possibly fixing them.

Thanks

I think you will find westminster_new 2.0 only works with zc version 1.5.6 - you will need version 1.4 to make it work with zc 1.5.5f or do fresh install of zc 1.5.6 then 2.0

Looks like I had to add the following entry into the includes/filenames.php:

define('FILENAME_META_TAGS', 'meta_tags');[/QUOTE]

Thanks for posting that, had me stumped.

Hi Team

I've just installed a fresh install of 1.5.7 (06232020) - does anyone who knows this template think it will install okay on it? I really like the look of it and have used it for a 1.5.6c (06172019) version, however from what I have been reading, not everything is crossing over easily.

Would love to know before I progress any further. I'm in the process of a full redesign of my old 1.3.7h instead of an upgrade. :-)

So I uploaded this on to my new 1.5.7 install last night (yeah right, more like 3am this morning), and it all seems to be okay.

However, the search bar is in an annoying position for me as I have a long tagline (which I've currently had to wrap) and would prefer it as one line. Does anyone know how to adjust the position of the search bar - either up or down?

https://www.AmorAromatherapy.com is the new creation underway...

Your quickest option is to take line 148 of the stylesheet.css#navMainSearch {margin:0;float:right;margin-top:-40px;}and make it ```
#navMainSearch {margin:0;/* float:right;*//margin-top:-40px;/}

For those that think you should just remove the float and margin, in case you change things around, you will still have the options in the Development Tools.

Adjust as necessary.

All that said, consider what your goal is here. Do you want to take up the majority of a desktop or mobile screen with the name and tag line?

On a large screen, you will never see the entire slide show. The decision point is, "What do I want the customer to concentrate on when the come to the main page.?" And, are they going to come to the main page or to a product's page from a search.

Long time customers will probably have a bookmark to your home. Others will rely on the search to take them to the product they're looking for. Again, adjust as necessary.

BTW - HTML verifier says you are using </br> in your tagline which is generally accepted now as simply <br>. It may be a false positive but, you might want to check it out.