Testimonial Manager Support Thread (for ZC v1.5.x)

Getting following error:

PHP Fatal error: 1327:Undeclared variable: MAX_DISPLAY_TESTIMONIALS_MANAGER_TITLES

This is located in includes/modules/sideboxes/testimonals_manager.php

tmccaff:

Getting following error:

PHP Fatal error: 1327:Undeclared variable: MAX_DISPLAY_TESTIMONIALS_MANAGER_TITLES

This is located in includes/modules/sideboxes/testimonals_manager.php

It would appear that the portion of the installation to set the configuration menu option has not been performed. Please see the instructions for installation or search this thread for the sql query to add that to the store.

v1.5.5f PHP7.1

I am confused (I am easily confused these days) about the intention of the Meta_Tags optional code shown in the README Install - even after reading posts #152-154 and #159-161. I am getting the same ' symptom' as the poster in post #159 ... browser for testimonials page shows META_TAG_TITLE_PAGE_TESTIMONIALS_MANAGER ... followed by testimonial title

So in post #153 DrByte said it appeared the plugin wasn't set up to accommodate meta_tags so I can only assume the add in code in the rREADME negates that comment? Y/N?

If so is the code supposed to automatically extract the title of the testimonial and make it the meta_title of that testimonial (and so on for description) or is it such that the meta data is to be manually inputted into (? file) and is such that it applies to the page (or pages) that the testimonials are on in the site? i.e. the title, description and keywords apply to the testimonial page, not to the testimonials?

The README states (save the edited file to includes/modules/YOUR_TEMPLATE/meta_tags.php and upload to your server.) - it didn't suggest that the modified file be re-loaded into where it cane from, includes/modules/meta_tags.php ......... is that assumed? should it also be re-loaded back into that folder?

Post #160 mentions modifications to includes/languages/english/YOUR_TEMPLATE/meta_tags.php

So I am wondering exactly how the meta_tags works

cheers,
Mike

p.s. I reckon this is a great add on - not sure why it has taken me so long to apply it

shags38:

Post #160 mentions modifications to includes/languages/english/YOUR_TEMPLATE/meta_tags.php
Working on a massive update to this mod and figured out your question too..

the meta tag language needs to be defined in includes/languages/english/YOUR_TEMPLATE/meta_tags.php
the two line to add to the bottom of that file are..

// Testimonial manager meta tags change to your  
define('META_TAG_TITLE_PAGE_TESTIMONIALS_MANAGER_ALL_TESTIMONIALS', 'Testimonials at ' . STORE_NAME . ' '); 
define('META_TAG_TITLE_PAGE_TESTIMONIALS_MANAGER', 'Testimonials at ' . STORE_NAME . ' ');

This makes use of what you defined as your store name.. the meta tag file is in the default folder, just copy to your template folder and edit if you did not do that already..

So I am wondering exactly how the meta_tags works

This is some good info, in the eyes of Google...
https://www.wordstream.com/meta-tags

Hi all;

Thanks for your great addons. I was wondering about, are customers allowed to upload an image when they post a testimonials? if so, I should be blind :cool::blink: because i couldnt find the option to enable it.
where can I enable it if there is a upload image feature for this Addons?

my system as below :

Zencart 1.5.5f fresh installation
server PHP version 7.1
Testimonial plugin version 1.5.4

Thanks

probtc:

Hi all;

Thanks for your great addons. I was wondering about, are customers allowed to upload an image when they post a testimonials? if so, I should be blind :cool::blink: because i couldnt find the option to enable it.
where can I enable it if there is a upload image feature for this Addons?

my system as below :

Zencart 1.5.5f fresh installation
server PHP version 7.1
Testimonial plugin version 1.5.4

Thanks

Currently.. no abilities to upload an image.... There was some crossing with this one and link manager somewhere... currently, working on a replacement and considering doing the image upload.

davewest:

Working on a massive update to this mod and figured out your question too..

the meta tag language needs to be defined in includes/languages/english/YOUR_TEMPLATE/meta_tags.php
the two line to add to the bottom of that file are..

// Testimonial manager meta tags change to your
define('META_TAG_TITLE_PAGE_TESTIMONIALS_MANAGER_ALL_TESTIMONIALS', 'Testimonials at ' . STORE_NAME . ' ');
define('META_TAG_TITLE_PAGE_TESTIMONIALS_MANAGER', 'Testimonials at ' . STORE_NAME . ' ');

> 
> This makes use of what you defined as your store name..  the meta tag file is in the default folder, just copy to your template folder and edit if you did not do that already..
> 
> ```
So I am wondering exactly how the meta_tags works

This is some good info, in the eyes of Google...
https://www.wordstream.com/meta-tags

Thanks for that Dave, much appreciated. So tell me, does Google take any notice of Testimonials? if so are they treated in the same way as they do with Product Reviews? .... or are Testimonials simply a marketing tool?

Looking forward to your updated version.

cheers, Mike

shags38:

Thanks for that Dave, much appreciated. So tell me, does Google take any notice of Testimonials? if so are they treated in the same way as they do with Product Reviews? .... or are Testimonials simply a marketing tool?

Looking forward to your updated version.

cheers, Mike

Its been debated on the net like so many other things... I've been tracking hits form search bots pulling both product reviews and testimonials so good content always helps... If you google a product name review and that product review is on the first page of the search... I would say it helps..

I have a working version on my site and was about to push up to github, but found some more wording issues to fix and started adding more to it.....

davewest:

I have a working version on my site and was about to push up to github, but found some more wording issues to fix and started adding more to it.....

If your interested I pushed.. https://github.com/davesaddle/Testimonial-Manager

What is the desire on image uploads.. Avatars or products??

I know on some sites products are displayed by users. Basically to add with the product reviews..

After going around and about with html5/jQuery and coming up with some really cool upload scripts, I decide to skip uploads and use a avatar picker... Was not an issue with uploading, but a desire to sale vs blogging...

Still working on some things..

davewest:

If your interested I pushed.. https://github.com/davesaddle/Testimonial-Manager

What is the desire on image uploads.. Avatars or products??

I know on some sites products are displayed by users. Basically to add with the product reviews..

After going around and about with html5/jQuery and coming up with some really cool upload scripts, I decide to skip uploads and use a avatar picker... Was not an issue with uploading, but a desire to sale vs blogging...

Still working on some things..

Hi Dave, good job - if you are still looking for input I would think product images would be more appropriate to an eCommerce site - IMHO avatars are more suited to forums and blogs :smile:
I assume the site owner can add the image of the product to the customers testimonial, right?

cheers,
Mike

shags38:

Hi Dave, good job - if you are still looking for input I would think product images would be more appropriate to an eCommerce site - IMHO avatars are more suited to forums and blogs :smile:
I assume the site owner can add the image of the product to the customers testimonial, right?

cheers,
Mike

Avatars can be eye catching.. many big box eCommerce sites use them and give the ability of account holders to add there own, like amaz0n. which wouldn't be that hard to do.

I don't think site owners should have to do anything with image uploads was the path I was headed! With code, images can be sized, stripped and file typed before uploading securely..

updated and pushed up to gethub... the EXIF Metadata Information is stripped out of jpg's, sized, renamed during upload.. all the image work is done in the user browser before sending to the server..

Still have some testing to do... so far tested with ZC 155f, 156, 160, php7.2 and 7.1 only using HTML5 browsers both android and ios..

Davewest, I've started updating your beta on GitHub, if you've got more to add I'll wait, if not we will test and publish the next release to the forum shortly for 1.55f compatibility.

For those using the current Beta Testimonials Manager version 2.1 on GitHub...

Bug - This lookup has been shorted from the original (Assumed Testimonials Manager for 1.55e) and will not install correctly out of the box as a result in 1.55f.

includes/modules/pages/testimonials_add/header_php.php
replace line 242
** $sql = "SELECT customers_id, customers_firstname, customers_email_address, customers_telephone,** FROM " . TABLE_CUSTOMERS . " WHERE c.customers_id = :customersID ";

with this:
$sql = "SELECT customers_id, customers_firstname, customers_email_address, customers_telephone FROM " . TABLE_CUSTOMERS . " c WHERE c.customers_id = :customersID ";

twitchtoo:

Davewest, I've started updating your beta on GitHub, if you've got more to add I'll wait, if not we will test and publish the next release to the forum shortly for 1.55f compatibility.

For those using the current Beta Testimonials Manager version 2.1 on GitHub...

Bug - This lookup has been shorted from the original (Assumed Testimonials Manager for 1.55e) and will not install correctly out of the box as a result in 1.55f.

includes/modules/pages/testimonials_add/header_php.php
replace line 242
** $sql = "SELECT customers_id, customers_firstname, customers_email_address, customers_telephone,** FROM " . TABLE_CUSTOMERS . " WHERE c.customers_id = :customersID ";

with this:
$sql = "SELECT customers_id, customers_firstname, customers_email_address, customers_telephone FROM " . TABLE_CUSTOMERS . " c WHERE c.customers_id = :customersID ";

The c. is not needed at all and came from another mod that I was working on more then likely.. That line should read..

 $sql = "SELECT customers_id, customers_firstname, customers_email_address, customers_telephone, FROM " . TABLE_CUSTOMERS . " WHERE customers_id = :customersID "; 
  
 $sql = $db->bindVars($sql, ':customersID', $_SESSION['customer_id'], 'integer'); 
 $check_customer = $db->Execute($sql);

The entire mod was re-work for ZC156 release and php7.3 just not had time to finish testing and push it up...

I take it you don't get the gethub process of cooperation or bata testing than!!

davewest:

The c. is not needed at all and came from another mod that I was working on more then likely.. That line should read..

$sql = "SELECT customers_id, customers_firstname, customers_email_address, customers_telephone, FROM " . TABLE_CUSTOMERS . " WHERE customers_id = :customersID ";

$sql = $db->bindVars($sql, ':customersID', $_SESSION['customer_id'], 'integer');
$check_customer = $db->Execute($sql);

> The entire mod was re-work for ZC156 release and php7.3  just not had time to finish testing and push it up... 
> 
> I take it you don't get the gethub process  of cooperation or bata testing than!!

**Davewest**, I'm interested in publishing a working 1.55f version for the Zen Cart Forum within a **short** period of time so that clients have a** working **copy for **1.55f**.  

Considering that the current **forum **version is **not **functioning out of the box on **1.55f** nor does the recommended** GitHub** version **you** have provided that ***thankfully ***cleans up a lot of the files... but also does not work out of the **GitHub** box - I updated both the Zen Cart Forum and GitHub so that anyone using the beta has access to the fix... with the intent to further support using the now working 1.55f beta.

Your fix above ^ implies the lookup won't have other things to look for in the future, mine declares the first group (c) in case another group is worth looking through - same result it just depends on your needs moving forward.

I simply have a client that needs a stable 1.55f version for their shop and I intend to share one with the group in the process.

There is no need for me to interfere with anything ZC 1.56 related at this time - so those files and anything you'd like to add will not be affected.

**'Tic Toc I'm On The Clock!' 
:cheers:**

We are still on version 1.5.2 and ZC 1.50, lately I am getting spam testimonials from registered customers, I think these are paid people that create account and put spam testimonials, I am having a hard time finding the customer that wrote the testimonials so that I could block him/her from logging in to the account.

I think it would great if there was a way to hide the email address box/field when I require testimonials be written for registered customers, this would help me great deal finding the spam customer by email address. Currently, the Spam Customers fills in a bogus email address in the field which makes it difficult finding him without going into the database or doing searches by name etc.

see attached image.

Can someone help me change the code?

Thanx

Coins2012:

We are still on version 1.5.2 and ZC 1.50, lately I am getting spam testimonials from registered customers, I think these are paid people that create account and put spam testimonials, I am having a hard time finding the customer that wrote the testimonials so that I could block him/her from logging in to the account.

I think it would great if there was a way to hide the email address box/field when I require testimonials be written for registered customers, this would help me great deal finding the spam customer by email address. Currently, the Spam Customers fills in a bogus email address in the field which makes it difficult finding him without going into the database or doing searches by name etc.

see attached image.

Can someone help me change the code?

Thanx

You can try adding read only to the input field... if the user is not logged in, they would not have an email address or option to add one.. if the spam is from bots, there is no code on the back end to stop them..

<?php echo (($error == true && $entry_email_error == true) ? zen_draw_input_field('testimonials_mail', $testimonials_mail, 'size="25" id="testimonials_mail" readonly') . ERROR_TESTIMONIALS_EMAIL_REQUIRED : zen_draw_input_field('testimonials_mail', $testimonials_mail, 'size="25" id="testimonials_mail" readonly')); ?>

I would say, let them enter what they want to enter and when the header_php.php file processes the request that if the user is logged in to attach the email or whatever desired information is to be kept to track the individual (customer id, email address, name, whatever) with the information being saved. This way they can try to provide some sort of information that they may prefer, but could also capture the known information.

The check for logged in could be if (!empty($_SESSION['customer_id']))

Just a thought because then real people could put in something that may want instead of their on file information and those that are putting in false information could be identified and there wouldn't be an impact on legitimate entries just those entries that may be fictitious.

mc12345678:

I would say, let them enter what they want to enter and when the header_php.php file processes the request that if the user is logged in to attach the email or whatever desired information is to be kept to track the individual (customer id, email address, name, whatever) with the information being saved. This way they can try to provide some sort of information that they may prefer, but could also capture the known information.

The check for logged in could be if (!empty($_SESSION['customer_id']))

Just a thought because then real people could put in something that may want instead of their on file information and those that are putting in false information could be identified and there wouldn't be an impact on legitimate entries just those entries that may be fictitious.

Customer info gathering for account holders is just a nice part of having an account... The read only is just a band-aid on a very old version of TM and changing email addresses could be their attempt not to post identifiable info to prevent there address from receiving spam!

But..

spam testimonials from registered customers, I think these are paid people that create account and put spam testimonials, I am having a hard time finding the customer that wrote the testimonials
We could add an extra hidden field to admin with the true account email or user ID into the database maybe. Currently the user ID is not added, but we also offer same use to none account holders! Well have to play with this idea some more....

Also thinking back I should have some help info tags here so they know email address is not publicly posted....

Thing I was getting at is that anything that is $_POSTed is editable prior to the page being sent.

mc12345678:

Thing I was getting at is that anything that is $_POSTed is editable prior to the page being sent.

True... which is why I started working on a filter for the address field.