WishList v0.4 -- v1.3.7 compatible

Sure, if you look just below where you removed the Add to Cart button, you'll see the following code:

		<label class="tabbed-m" for="wishlist_quantity[]"><?php echo UN_TEXT_QUANTITY . UN_LABEL_DELIMITER; ?></label>
		<?php echo zen_draw_input_field('wishlist_quantity[]', $products->fields['quantity'], 'size="2" maxlength="3" class="xs"'); ?>
		</li>
		<li>
		<label class="tabbed-m" for="comment[]"><?php echo UN_TEXT_COMMENT . UN_LABEL_DELIMITER; ?></label>
		<?php 
		echo zen_draw_input_field('comment[]', $products->fields['comment'], 'maxlength="255" class="l"');
		?>
		</li>
		<li>
		<label class="tabbed-m" for="priority[]"><?php echo UN_TEXT_PRIORITY . UN_LABEL_DELIMITER; ?></label>
		<?php 
		echo un_draw_priority_pull_down_menu('priority[]', '', $products->fields['priority'], 'class="l"');
		?>

Remove that, and you should be good to go

Worked perfectly.
Many thanks for that.

I have un_wishlist_0.41installed on ZC v1.3.8a and it worked just fine.
However, I recently changed hosts and am receiving the following error on the backend after ticking the Wishlist, the frontend is still functioning normally.
Unless I mis-reading this error, It's still looking for my old database. I've looked for any references to the old database within the un_wishlist tables, heck, I've searched the entire database and cannot find any.

1142 SELECT command denied to user '*******'@'localhost' for table 'un_wishlists'
in:
[SELECT w.id, w.customers_id, w.created, w.modified, w.name, w.comment, w.default_status, w.public_status, count(p.products_id) as items_count, c.customers_email_address, c.customers_firstname, c.customers_lastname FROM ste0929305535146.un_wishlists w LEFT JOIN ste0929305535146.un_products_to_wishlists p2w ON w.id=p2w.un_wishlists_id LEFT JOIN zen_products p ON p2w.products_id=p.products_id LEFT JOIN zen_customers c ON w.customers_id=c.customers_id GROUP BY w.id ]
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.
Could this reference be stuck in the db cache?

when you moved the site did you create a new user and password?

Try keeping the name of the database, user, and password the same and see if it works.

jackie.taferner:

when you moved the site did you create a new user and password?

Try keeping the name of the database, user, and password the same and see if it works.
Yes JT, I did change the name of the database when I moved to the ne host. Not that I do not mind changing it back but, shouldn't there be a way to change the mod so that it recognizes the newly renamed database instead?
I considered deleting the un_wishlist tables and installing them again. Would there be a problem with that and do you think it would fix my issue?

jabbawest, i think it would be a lot more work to modify the module. You can give it a shot, I haven't tried before

I think the simplest solution is to keep the same DB name and password. If you had prefixes you should keep that the same too. (ie when you first install, it asks if you want table prefixes like zen_ or mydb_).

The other option is to uninstall and re-install the module. But if this is a working site, you may have customers with wishlists that will get erased.

jackie.taferner:

jabbawest, i think it would be a lot more work to modify the module. You can give it a shot, I haven't tried before

I think the simplest solution is to keep the same DB name and password. If you had prefixes you should keep that the same too. (ie when you first install, it asks if you want table prefixes like zen_ or mydb_).

The other option is to uninstall and re-install the module. But if this is a working site, you may have customers with wishlists that will get erased.
I really wish I could find this elusive bit of data that is telling the backend of un_wishlist to look for my old db.
Where could it be stored? It certainly isn't in the db as a regular expression of ste0929305535146, so it might be encrypted within the products tables somewhere.
I will drop the un_wishlist tables and reinstall them unless someone more knowledgeable than me can give me a reason to revert back to the old db name for reasons other than the un_wishlist mod.
I would hate for this db naming issue to be a reoccurring problem that may affect other modules.

i think re-installing is a good option, as long as there aren't existing customer wish lists.

not sure if the new DB name change would affect any other modules, it would greatly depend on what modules you have installed.

Best way to find out is to test the entire store and make sure everything is working OK.

Nevermind, I found it.
was written to the following file:
admin/includes/extra_datafiles/un_database_tables.php

<?php

// Wishlist
define('UN_TABLE_WISHLISTS', 'ste0929305535146.un_wishlists');
define('UN_TABLE_PRODUCTS_TO_WISHLISTS', 'ste0929305535146.un_products_to_wishlists');

?>

Whew!

Thank you JT for responding and trying to help me fix this.

ah, that makes sense, seems it was customized into the module. Glad you were able to find it. good luck with the testing on the rest of your site!

digidiva-kathy:

Never mind, I also figured it out, but I think I'll share the solution for future frustrated users ;)

in includes>extra_datafiles>un_database_tables.php

add the prefix to the table names defined here.

You just saved me a heck of a lot of time!

Hey everyone

Just tried to install this

Got This error when adding an item to the wish list... I know enoupgh ta be dangerouse so any step by step help would be great

Thanks

1146 Table 'ohweb_ohsite.un_wishlists' doesn't exist
in:
[SELECT id FROM un_wishlists w WHERE w.customers_id=35 and w.default_status=1 ]

Hey Stavman, when installing did you follow this step?

-----[ 1. Create tables ]-----

Run 'un_wishlist.sql' in the Install SQL patches in the Zen Cart admin.

Important: If in your implementation of ZenCart you defined a database table prefix (see file "includes/configure.php", line 52), add that prefix to the table names in the sql file before running in the admin. ("un_wishlist.sql", lines 9, 10, 28 and 29).

I think I see a bug with the program, and I'd like to see if anyone else can see the same thing.

If you have more than one wishlist, it will only allow you to edit the items in your DEFAULT wishlist. If you try to change something in another wishlist which isn't the default, the changes do not stick.

So to test, create multiple wishlists. When you add items to the wishlist, it will put it in the default wishlist first (by design). Then you will move some of these items into your secondary wishlist.

Now when you try to change the priority of an item in the secondary wishlist (which is not your default wishlist), the changes will not stick. You have to set it as your primary wishlist in order to make the changes.

Is there any way around this?

Jeff_Mash:

I think I see a bug with the program, and I'd like to see if anyone else can see the same thing.

If you have more than one wishlist, it will only allow you to edit the items in your DEFAULT wishlist. If you try to change something in another wishlist which isn't the default, the changes do not stick.

So to test, create multiple wishlists. When you add items to the wishlist, it will put it in the default wishlist first (by design). Then you will move some of these items into your secondary wishlist.

Now when you try to change the priority of an item in the secondary wishlist (which is not your default wishlist), the changes will not stick. You have to set it as your primary wishlist in order to make the changes.

Is there any way around this?

I confirm, there really seems to be a bug :( Has anybody a patch to solve this?

Hi all,

Just wanted to add my $.02

If you have GoDaddy as a host when you run the scripts from the admin console your DB prefixes are automatically added to the tables. After you run your script look at the Query Results section to verify. I had to add the table prefix to the includes\extra_datafiles\un_database_tables.php file but not the DB scripts file.

I've tried installing wshlists on my local version of my webstore. It seems to have taken out the product detail page somehow. See attached thumbnail. Any ideas why this might be happening or where i should start to fix it?

If you have GoDaddy as a host when you run the scripts from the admin console your DB prefixes are automatically added to the tables. After you run your script look at the Query Results section to verify. I had to add the table prefix to the includes\extra_datafiles\un_database_tables.php file but not the DB scripts file.

my live server is on godaddy, so i want to ask a question here... did you need to modify the un_wishlists.sql to do this? or just modify the php files?

Hi everyone does anyone know where I would adjust the width of the wishlist default page? It's overlapping a bit on my sideboxes.

Also, can you change Wish List : default?

Thank you!

Jeff_Mash:

I think I see a bug with the program, and I'd like to see if anyone else can see the same thing.

If you have more than one wishlist, it will only allow you to edit the items in your DEFAULT wishlist. If you try to change something in another wishlist which isn't the default, the changes do not stick.

So to test, create multiple wishlists. When you add items to the wishlist, it will put it in the default wishlist first (by design). Then you will move some of these items into your secondary wishlist.

Now when you try to change the priority of an item in the secondary wishlist (which is not your default wishlist), the changes will not stick. You have to set it as your primary wishlist in order to make the changes.

Is there any way around this?

Yeah it seems we can't even use the multiple wishlists feature, adding products will only ever go to the default wishlist it seems.. ie users can't select a different wishlist to add products to.

Can't help but think we're overlooking something really simple here?

yeah I definitely think the bugs need to be worked out. I simply took the code that was on the forums and put it into the module, but haven't had time to carefully review it and fix any bugs :(

Hopefully I can get around to this soon, considering this is pretty much the only standalone wishlist option for zen cart - and it needs to WORK!

I might add - I haven't tested this add-on with 1.3.9 yet either, so unless you're on 1.3.8, bugs may be due to this. not sure though, give it a try.