Worked perfectly.
Many thanks for that.
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.
Could this reference be stuck in the db cache?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.
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?
Last edited by jabbawest; 30 Aug 2010 at 04:56 PM. Reason: anal about grammer
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.
Last edited by jabbawest; 30 Aug 2010 at 06:28 PM. Reason: grammer
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
Whew!PHP Code:<?php
// Wishlist
define('UN_TABLE_WISHLISTS', 'ste0929305535146.un_wishlists');
define('UN_TABLE_PRODUCTS_TO_WISHLISTS', 'ste0929305535146.un_products_to_wishlists');
?>
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!