Template Fluorspar

Quote:

---

Originally Posted by simon1066

Check your \includes\modules\fluorspar\product_listing.php file and make sure this line is as the original:

Code:

---

'text' => TEXT_NO_PRODUCTS);

---

If it this then I'm out of ideas I'm afraid.

---

Yes, the line is correct.

Quote:

---

Originally Posted by simon1066

I think that then points to an error in the PHP file that calls the define, on which page are you seeing the TEXT_NO_PRODUCTS text? I assume it's a product listing page but it could also be on the Advanced Search page.

---

On the advanced search, the constant's value is being displayed correctly. It's only on the product listing page where the problem occurs.

Is there any reasonably simple way to remove the Nivo slider altogether, without going through and eliminating every reference to it individually? There does not appear to be any way to apply an alt attribute to the individual image slices, amongst other problems with it. I have stopped it from being displayed on my website, and WAVE no longer shows errors for it. But the code is still present, but aXe dev tools found problems.

Quote:

---

Originally Posted by HeleneWallis

Is there any reasonably simple way to remove the Nivo slider altogether, without going through and eliminating every reference to it individually? There does not appear to be any way to apply an alt attribute to the individual image slices, amongst other problems with it. I have stopped it from being displayed on my website, and WAVE no longer shows errors for it. But the code is still present, but aXe dev tools found problems.

---

I don't use this template but it seems that the content of the slider is controlled by tpl_nivo_top.php and that that file is called in includes\templates\fluorspar\common\tpl_header.php

This is the code, in that file, that either need to be disabled or removed:

Code:

---

<?php
  if ($this_is_home_page) {
?>
<div id="home-banner"><?php require($template->get_template_dir('tpl_nivo_top.php',DIR_WS_TEMPLATE, $current_page_base,'common'). '/tpl_nivo_top.php');?></div>
<?php
 }
?>

---

If you don't want to delete it altogether but just 'hide' it from the code than I would change it to:

Code:

---

<?php /* ?>
<?php
  if ($this_is_home_page) {
?>
<div id="home-banner"><?php require($template->get_template_dir('tpl_nivo_top.php',DIR_WS_TEMPLATE, $current_page_base,'common'). '/tpl_nivo_top.php');?></div>
<?php
 }
?>
<?php */ ?>

---

Edit: there is a javascript file in includes\templates\fluorspar\jscript that no longer needs to load - can be renamed (jquery.nivo.slider.js_old) or deleted. I can't think of anything else that might need considering.

Quote:

---

Originally Posted by simon1066

I don't use this template but it seems that the content of the slider is controlled by tpl_nivo_top.php and that that file is called in includes\templates\fluorspar\common\tpl_header.php

This is the code, in that file, that either need to be disabled or removed:

Code:

---

<?php
  if ($this_is_home_page) {
?>
<div id="home-banner"><?php require($template->get_template_dir('tpl_nivo_top.php',DIR_WS_TEMPLATE, $current_page_base,'common'). '/tpl_nivo_top.php');?></div>
<?php
 }
?>

---

If you don't want to delete it altogether but just 'hide' it from the code than I would change it to:

Code:

---

<?php /* ?>
<?php
  if ($this_is_home_page) {
?>
<div id="home-banner"><?php require($template->get_template_dir('tpl_nivo_top.php',DIR_WS_TEMPLATE, $current_page_base,'common'). '/tpl_nivo_top.php');?></div>
<?php
 }
?>
<?php */ ?>

---

Edit: there is a javascript file in includes\templates\fluorspar\jscript that no longer needs to load - can be renamed (jquery.nivo.slider.js_old) or deleted. I can't think of anything else that might need considering.

---

Thanks, I had already removed that section of code, but aXe was still finding references to Nivo. I'll rename or delete the javascript file too. This template has enough accessibility issues as it is without the slider. I've addressed all the others, but I could not make the slider accessible (and apparently no one else has been able to either).

Just a little FYI. If a file is renamed using old or bak, it may still be run by the system AND, any *.bak files on a server are a direct PCI violation.

I try to use my initials as the file extension. Since I'm not J Paul Getty, Gary Ignacious Franken, or Paul Norman Gordon, Peter Henry Porter, Charles Stanley Smith, or any other name that results in a known file extension; the file won't run AND, I can easily find what I did by searching for *.bst.:P

Yes, it's a valid file extension but requires a special viewer to open on line.

Quote:

---

Originally Posted by dbltoe

Just a little FYI. If a file is renamed using old or bak, it may still be run by the system ...

---

Now I didn't know that.

Quote:

---

Originally Posted by dbltoe

Just a little FYI. If a file is renamed using old or bak, it may still be run by the system AND, any *.bak files on a server are a direct PCI violation..

---

Thanks, I did not know that either. I used 'old,' but I can easily go back and substitute my initials, which I don't think correspond to anything currently in use either :)

Btw, the error I was getting with aXe went away after I renamed the file with 'old,' so aXe wasn't finding it. But I'll avoid the use of 'old' in the future anyway.

Quote:

---

Originally Posted by HeleneWallis

Btw, the error I was getting with aXe went away after I renamed the file with 'old,' so aXe wasn't finding it. But I'll avoid the use of 'old' in the future anyway.

---

Yep, those are PCI problems versus accessibility items. Not on the aXe radar.

What's quick and easy with cPanel's File Manager is to search your entire site for *.old or *.bak. Sometimes they get created by routine maintenance.

Quote:

---

Originally Posted by dbltoe

Yep, those are PCI problems versus accessibility items. Not on the aXe radar.

What's quick and easy with cPanel's File Manager is to search your entire site for *.old or *.bak. Sometimes they get created by routine maintenance.

---

Good idea, I'll do that. I use 'old' when I'm testing things and want to make sure I've preserved the original in case I break something. I usually remember to go back and remove the redundant one, but not always.